Drilldowns now support trigger picker. It allows to create a drilldown and specify which trigger it should be attached to.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Handles the case where two operations for the same entity make it into a single batched bulk operation and avoid the clashing ID issue that could cause the poller to hang and stop poling for work).
* Fixed issue with query bar not taking full width in safari
* Replace legacy esClient with search API
* Fix tests and typing issues
* Revert "Fixed issue with query bar not taking full width in safari"
This reverts commit a83e5d9f2c.
Co-authored-by: Shamin <shamin616@gmail.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Adding /etc/rc.d/init.d/functions to the init script when present to improve integration with systemd on systemd-based distros. See https://github.com/elastic/kibana/issues/22255
* Adding SysV Init Functions for Debian and SUSE distros
* Adding /etc/rc.d/init.d/functions to the init script when present to improve integration with systemd on systemd-based distros. See https://github.com/elastic/kibana/issues/22255
* Adding SysV Init Functions for Debian and SUSE distros
* docs(NA): include a comment to explain the change
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Tiago Costa <tiagoffcc@hotmail.com>
* Added proxy support for action types
* Fixed tests
* added rejectUnauthorizedCertificates config setting
* removed slack not used code
* Fixed Slack proxy
* fixed typecheck errors
* Cleanup code
* Fixed slack
* Added unit tests
* added proxy server for test
* Fixed build
* Added functional tests
* fixed due to comments
* Fixed tests and some changes due to comments
* Fixed functional tests
* fixed circular deps
* Added proxy unit test to action type
Our tests shouldn't rely on the DOM structure of Resolver (when its arbitrary) because that will make them brittle. If the user doesn't care about the DOM structure, then neither should our tests.
Note: sometimes the user does care about the DOM structure, and in those cases the tests should as well.
* Add routes
* Add version for use in doc link
* Set up basic router layout + WorkplaceSearchNav
* Update views to account for Layout
* Move version to common folder
* Fix version path
* Remove product button
No longer needed since we have all top-level app links in Kibana as a part of this PR
* You know, for search
* Remove comment
* Remove unused i18n properties from JSON
Tests were failing after removing component:
https://kibana-ci.elastic.co/job/elastic+kibana+pipeline-pull-request/67797/execution/node/382/log/
* Revert button and i18n copy removal
This reverts commit ba0535187e.
* Move Overview out of layout to hide nav
For now, the route for groups was added to avoid having comment out the code. Will add the groups component in a future PR
* Revert layout changes to Overview
Since there is no nav, the padding was missing and the view looked off. Reverting to the 7.9, centered column view
* Remove extra Overview component
Was causing tests to fail
* Revert error state to use EuiPage
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This replaces the use of the old graphql-based `useSource` hook with the new plain JSON `useLogSource` hook.
It also fixes two more problems:
- A rendering problem with the source configuration loading screen and a `setState` race condition in the `useLogSource` hook.
- A non-backwards-compatible change of the `/link-to/:sourceId/logs` route in #61162.
* Initial work
* Expand generic support to alert instances
* Convert index threshold to use generics
* Make fixture alert types use generics
* Make alert instance related types use unknown
* Fix typecheck failures
* Cleanup + add instance generic support to registry.get API
* Shallow clone
* Rename some TS variables
* Fix failing api integration tests
* Change code for easier review and keep more history
* Fix
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* _cluster/state/metadata/* and added a comment to function
* add another comment regarding why we are asking for *
* update jest test
* refactor and clean up use of cluster status to get index state
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Adding api test for custom link transaction example
* expecting specific fields
* expecting specific fields
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
The app can show more than 1 Resolver at a time. Each instance has a unique ID called the `resolverComponentInstanceID`.
When the user interacts with Resolver it will add values to the query string. The query string values will contain the `resolverComponentInstanceID`. This allows each Resolver to keep its state separate. When resolver unmounts it will remove any query string values related to it.
If Resolver's `resolverComponentInstanceID` changes it should remove query string values related to the old instance ID. It does not. This PR fixes that.
Note: I don't know if it was possible for this bug to actually happen. I can't make it happen, but depending on how Resolver is mounted by its consumers it *could*
