* show error when clone fails due to no index pattern
* default results_field unless specified
* results field switch set to on if resultsField for cloned job is default
* ensure cloned job config not overwritten in advanced editor
* show errorToast if unable to clone anomalyDetection job due to no indexPattern
* ensure jobConfig query getting saved in form state
* ensure index patterns with commas handled correctly
* clone should accept comma separated index patterns
* use nullish coalescing operator when checking for undefined analysisFields
Renames "Built-In Alerts" feature to "Stack Alerts" and "Actions" feature to "Actions and Connectors" as we've decided these names make more appropriate and better communicate what these features are.
resolves https://github.com/elastic/kibana/issues/72058
Finally, we're logging the action executor error responses to the Kibana log.
We have not been doing this previously, out of an abundance of caution. The
message written may contain data returned from a 3rd party service call, and
we weren't sure this would be "safe" to log, in a PII sense.
After several minor releases, and seeing these service messages in the event
log for almost all the built-in action types, we've decided they are "safe" and
it's time to add them, as they provide some **very** helpful diagnostic
feedback to customers.
* Remove APM stacktrace snapshots
These are not necessary and have caused problems for other contributors. Replace the snapshots with tests that check for errors or the structure of the results.
Move the test files out of the __test__ directory and rename the directory to __fixtures__.
* Refactored store code to group properties related to location so that would be easy to introduce a new view type parameter.
* Added view type to the location and routing.
* Added a simple hook to make navigation easier.
* Improved the navigation hook to get params.
* Some fix for double notification after creating trusted app.
* Added a hook to perform trusted app store actions.
* Fixed trusted app card delete callback.
* Added grid view.
* Fixed the stories structuring.
* Shared more logic between grid and list.
* Finalized the grid view.
* Flattened the props.
* Improved memoization.
* Moved the flex item elements inside conditions.
* Fixed broken stories.
* Updated the snapshot.
* Updated the snapshot.
This creates new Add Data tutorials for Filebeat modules.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
In #79000 the way we create the telemetry schema was updated and APM is no longer excluded from the telemetry scripts.
Update the docs to be more correct about this.
* Adding X-Kibana header for the legacy client requests
* Specifying `X-Kibana: true` header for all requests coming from Kibana
* Dev Tools now override the X-Kibana header to false
* DevTools doesn't need to do anything, it's not using the ES client
* Switching from `X-Kibana: true` to `User-Agent: Kibana`
* Switching from `X-Kibana: true` to `User-Agent: Kibana`
* Adding a constant
* Starting to add unit tests...
We currently allow end-users to set whatever headers they'd like to be
forwarded to Elasticsearch with `elasticsearch.customHeaders` and
`elasticsearch.requestHeadersWhitelist`. This is potentially problematic
with us always specifying `User-Agent: kibana` as it could interfere
with what our end-users have done...
* Switching from user-agent to X-elastic-product-origin
* Adding some tests
* Adding and updating the legacy client unit tests
T#
* /s/KIBANA_HEADERS/DEFAULT_HEADERS and a deepFreeze
* Adding comment for why `x-elastic-product-origin` exists
* using kibana persisted date when available to set the date time
* fixing types
* adding setTime when changin the dates in the url
* renaming
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
