* [Cases] [108671] Fix faulty status api call, if selection is same
* Add unit test to ensure selecting same status message does not call api
Co-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kristof C <kpac.ja@gmail.com>
Co-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>
* [Fleet] Show callout when EPR unavailable (#117598)
* Update src/core/public/doc_links/doc_links_service.ts
Co-authored-by: Thomas Neirynck <thomas@elastic.co>
* feat: allow to pass `tooltipPosition` to `DefaultDraggable`
* fix: prevent suricata field name and google url tooltips from overlapping
* test: add test for passing the tooltipPosition
* chore: distinguish between type imports and regular imports
* test: update suricata signature snapshots
* test: make sure that suricata signature tooltips do not overlap
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Jan Monschke <jan.monschke@elastic.co>
* wrap UX dashboard into an error boundary (fixes#117543)
* refactor APM root app tests to reuse coreMock
Before this change, the tests for the root application component of the
APM app were manually mocking the `coreStart` objects required to render
the component.
After this change, these tests will now reuse the relevant `coreMock`
methods.
* refactor: fix typo on createAppMountParameters test utility
Co-authored-by: Lucas Fernandes da Costa <lucas.fernandesdacosta@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Lucas F. da Costa <lucas@lucasfcosta.com>
Co-authored-by: Lucas Fernandes da Costa <lucas.fernandesdacosta@elastic.co>
* [Security Solution] Fix/host isolation exceptions header (#118041)
* Copy changes for host isolation exceptions form
* Fix hasDataToShow condition to show search bar and header
* Remove copy changes from other branch
* commit using @elastic.co
* [SecuritySolution] Fixes deprecated use of Spaces API (#118121)
* Set up our app client in start() instead of setup()
We don't use it during setup, and since the spaces client is now only
available in start(), we need to respond accordingly.
* Move appClientFactory setup back into the setup phase
Albeit in the getStartServices callback, so it's really in the start
phase.
* Use spaces service from start contract in RequestContextFactory
The setup contract variants have been deprecated.
* Remove unused dependency from EndpointAppContextService
It no longer needs the appClientFactory, as that functionality is
provided through securitySolutionRequestContextFactory, which wraps an
instance of that client itself.
# Conflicts:
# x-pack/plugins/security_solution/server/request_context_factory.ts
* Remove unused var
* chore(NA): moves disk_cache and repository_cache bazel flags from common to specific commands (#118037)
# Conflicts:
# .bazelrc.common
* commit using @elastic.co
* [SecuritySolution][Detections] Fixes rule status migration when alertId is not a string (#117962)
## Summary
Resolves https://github.com/elastic/kibana/issues/116423, and adds an e2e test catching this behavior as we can't test via the migration test harness since the `siem-detection-engine-rule-status` SO isn't exposed within the SO Manager UI.
Also adds note with regards to changes necessary once core issue https://github.com/elastic/kibana/issues/115153 is resolved. See https://github.com/elastic/kibana/pull/114585/files#r729620927. Note: existing `find_statuses`/`find_rules` integration tests will fail once fixed, so no additional tests necessary.
### Checklist
Delete any items that are not applicable to this PR.
- [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
* Fixes typecheck in test
Co-authored-by: Garrett Spong <spong@users.noreply.github.com>
Co-authored-by: Garrett Spong <garrett.spong@elastic.co>
- The way we customized the use of search strategies caused issues with race conditions when multiple Kibana instances were used for load balancing. This PR migrates away from search strategies and uses regular APM API endpoints.
- The task that manages calling the sequence of queries to run the correlations analysis is now in a custom React hook (useFailedTransactionsCorrelations / useLatencyCorrelations) instead of a task on the Kibana server side. While they show up as new lines/files in the git diff, the code for the hooks is more or less a combination of the previous useSearchStrategy and the server side service files that managed queries and state.
- The consuming React UI components only needed minimal changes. The above mentioned hooks return the same data structure as the previously used useSearchStrategy. This also means functional UI tests didn't need any changes and should pass as is.
- API integration tests have been added for the individual new endpoints. The test files that were previously used for the search strategies are still there to simulate a full analysis run, the assertions for the resulting data have the same values, it's just the structure that had to be adapted.
- Previously all ES queries of the analysis were run sequentially. The new endpoints run ES queries in parallel where possible. Chunking is managed in the hooks on the client side.
- For now the endpoints use the standard current user's esClient. I tried to use the APM client, but it was missing a wrapper for the fieldCaps method and I ran into a problem when trying to construct a random_score query. Sticking to the esClient allowed to leave most of the functions that run the actual queries unchanged. If possible I'd like to pick this up in a follow up. All the endpoints still use withApmSpan() now though.
- The previous use of generators was also refactored away, as mentioned above, the queries are now run in parallel.
Because we might run up to hundreds of similar requests for correlation analysis, we don't want the analysis to fail if just a single query fails like we did in the previous search strategy based task. I created a util splitAllSettledPromises() to handle Promise.allSettled() and split the results and errors to make the handling easier. Better naming suggestions are welcome 😅 . A future improvement could be to not run individual queries but combine them into nested aggs or using msearch. That's out of scope for this PR though.
* [TSVB] Fix reappearing of hidden series on refresh and styles loading
* Add functional test
* Update condition and move loading component to another file
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
