* Adding specific apis for each plugin
* adding metric hosts stat
* addressing PR comment
* addressing PR comments
* changing series to key/value
* exporting interfaces
* adding label to stat
* refactoring types
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Change the bootstrap of the app
* rename SiemPageName to SecurityPageName
* modify alerts routes
* modify cases routes
* modify hosts routes
* modify network routes
* modify overview routes
* modify timelines routes
* wip change management route
* change route for common
* some fixing from the first commit
* modify route for management
* update url format hook to use history
* bug when you click on external alerts from host or network
* improvement from josh feedback
* redirect siem to security solution
* a little clean up
* Fix types
* fix breadcrumbs
* fix unit test
* Update index.tsx
* Fix cypress
* bug remove timeline when you are in case configure
* Fix functionel test for management
* Fix redirect siem + ml
* fixes some cypress tests
* adds 'URL compatibility' test
* bring ml back to alerts
* review I
* Fix memory leak in timelines page
* fix storage bug for timeline search bar
* fix endpoint merge + functional test
* avoid timeline flyout toggle
* Fix link to ml score
* Fix breadcrumb
* Fix management url
* fix unit test
* fixes typecheck issue
* fixes remaining url cypress tests
* fixes timeline scenario
* fix link to details rule from timeline
* review remove absolute path for consistency
* Fixing resolver alert generation (#69587)
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [Security_Solution][Endpoint] Resolver leverage ancestry array for queries (#69264)
* Adding alerts route
* Adding related alerts generator changes, tests, and script updates
* Fixing missed parameter
* Aligning the AlertEvent and ResolverEvent definition
* Fixing type errors
* Fixing import error
* Adding ancestry functionality in generator
* Creating some tests for ancestry field
* Making progress on the ancestry
* Fixing the ancestry verification
* Fixing existing tests
* Removing unused code and fixing test
* Adding more comments
* Fixing endgame queries
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* fix cypress test
* skip failing suite (#69595)
* [Endpoint] Fix flaky endpoints list unit test (#69591)
* Fix flaky endpoints list unit test
* un-skip test
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* remove flaky test
Co-authored-by: patrykkopycinski <contact@patrykkopycinski.com>
Co-authored-by: Gloria Hornero <snootchie.boochies@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Jonathan Buttner <56361221+jonathan-buttner@users.noreply.github.com>
Co-authored-by: spalger <spalger@users.noreply.github.com>
Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>
* Adding alerts route
* Adding related alerts generator changes, tests, and script updates
* Fixing missed parameter
* Aligning the AlertEvent and ResolverEvent definition
* Fixing type errors
* Fixing import error
* Adding ancestry functionality in generator
* Creating some tests for ancestry field
* Making progress on the ancestry
* Fixing the ancestry verification
* Fixing existing tests
* Removing unused code and fixing test
* Adding more comments
* Fixing endgame queries
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Use theme colors for stacktrace
* [APM] Use theme for all components
* Switch HoC withTheme to useTheme and convert classes to hooks
* Change hardcoded white to euiColorEmptyShade for ServiceMap
* Snapshots and Legends fix
* Switch to context and add test helper
* Fix tests and update snaps
* New snaps + new anomaly detection
* Remove shallow from testHelpers
* Remove commented tests
* Fix prettier
* Pass correct theme to cytoscape
* Fix ServiceMap
* fixes some rendering issues in service maps
* removed the old anomaly detection logic from service map popover contents, since it's been moved to a new component.
* Fix eslint, tsc lint issues and unit tests
* Remove types for styled-components default theme
* Update x-pack/plugins/apm/public/components/shared/KueryBar/Typeahead/Suggestions.js
Co-authored-by: Casper Hübertz <casper@formgeist.com>
* fix OuterTheme
* Ise function declaration instead of expression
Co-authored-by: Balthazar Gronon <git@balthazar.dev>
Co-authored-by: Balthazar Gronon <bgronon@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Oliver Gupte <olivergupte@gmail.com>
Co-authored-by: Casper Hübertz <casper@formgeist.com>
Adds support for histogram charts to data grid columns.
- Adds a toggle button to the data grid's header to enabled/disable column charts.
- When enabled, the charts get rendered as part of the data grid header.
- Histogram charts will get rendered for fields based on date, number, string and boolean.
## Summary
* https://github.com/elastic/kibana/issues/69463
* See here for manual backport to 7.8: https://github.com/elastic/kibana/pull/69434
This fixes a bug where if you import rules and set your overwrite to `true` multiple times in a row within 7.7 you can end up with a lists array. When upgrading to 7.8, we change the name of `lists` to `exceptions_lists` and suddenly when you enable/disable a rule you can get the following error below:
The fix is to allow the lists array still if it is present within saved objects to avoid seeing this error screen and being tolerant. We also fix the area of code that is causing the data bug so it cannot happen again with `exceptions_list` which is what the name of lists was renamed to causing this problem.
Note that this has unit tests and I also manually tested this by intentionally injecting a `lists` and `exceptions_lists` and using the UI to verify there wasn't another validation spot that needed to be relaxed to allow for the data.
### Checklist
- [x] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
* start redoing types
* finish redoing types
* fix bad test
* rework tests
* fix more types
* fix test
* Fix endpoints test and render error
* add deletePolicyStream to alerts api tests
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Paul Tavares <paul.tavares@elastic.co>
### Summary
This PR is meant to update the `ExceptionListItemSchema.entries` structure to align with the most recent conversations regarding the need for a more explicit depiction of `nested` fields. To summarize:
- Adds schema validation for requests and responses within `lists/public/exceptions/api.ts`. It was super helpful in catching existing bugs. Anyone that uses the api will run through this validation. If the client tries to send up a malformed request, the request will not be made and an error returned. If the request is successful, but somehow the response is malformed, an error is returned. There may be some UX things to figure out about how to best communicate these errors to the user, or if surfacing the raw error is fine.
- Updates `entries` structure in lists plugin api
- Updates hooks and tests within `lists/public` that make reference to new structure
- Updates and adds unit tests for updated schemas
- Removes unused temporary types in `security_solution/public/common/components/exceptions/` to now reference updated schema
- Updates UI tests
- Updates `lists/server/scripts`
* Embed documentation on input and output state
* json -> js
* Add section on how id is used by custom time range badge action to determine isCompatible
* [APM] Service map download in debug mode
Add a download button when debug mode is enabled that downloads JSON of
the map.
Add an upload button to the Storybook.
## Summary
Fixes io-ts formatter bugs for REST and validation by:
* First trying to get the correct key from the io-ts context. If no keys are found, then it will fall back on trying to get the first name from the context.
* If the key is a value and an object then this will do a `JSON.stringify()` on the value object
* This fixes a few places where `formatError` was not being used within the code base resulting in `[object Object]` within the validations to show up.
### Checklist
- [x] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
