* Convert info button and the rest of the page to EUI
* Update other overview pages
* Use Page directive
* Give the tooltip some more space
* Add page body to a couple places
* PR feedback
* Convert beats overview page to use EUI components
* More UI components for beats overview
* Set background color to white
* Update snapshots
* Add PageBody wrapper
* Update snapshots
* Use panels
* PR feedback
* Update snapshots
* Turn reporting snapshot tests back on with new baselines
* Use snapshots generated from chromium. Bump the threshold so phantom comparisons pass
* Increase timeouts because of chromium functional tests.
* remove accidentally checked in session snapshots
* add a better vis baseline, run once through at 0 to check expected threshold
* turn on verbose logs
* Use threshold, turn debug mode on in jenkins
* Wrap both convert pages in the retry
* Update baselines
Preserve layout one got messed up - it was actually a print layout.
* bump threshold even more
* set pause to 'true' when refresh interval is zero
* keep original assertion
* fix expect message in functional tests now that pause is set to true
* fix executorProvider mocha test
* move global state update from kbn_global_timepicker to timefilter
* add functional test
* update time and refreshInterval when either update
* use same function name from kbn_global_timepicker
* call globalState.save in context of a digest cycle
* ensure callers of registerTimefilterWithGlobalState pass in
- Enables support for the rare detector for the charts in Anomaly Explorer and Single Metric Viewer.
- The charts use a count aggregation. The anomaly records for rare detectors include actual/typical values, but they don't refer to values we have for other detectors. actual is always 1 and doesn't refer to the actual count. typical has the probability as its value. To avoid confusing users by displaying these values as actual/typical in the tooltip, just the value of count of the aggregation will be shown.
- This enables the existing charts to be able to visualize rare detectors. A follow-up to this PR will introduce a specific chart for rare detectors.
* Support legacy use cases for passthrough
* Support generic case too
* Add legacy flag
* Do not format api field names in legacy mode
* Add basic test for legacy parameter
* Add more tests
* Ensure we pass down the expiry_date for the license
* Update tests
* Update fixtues
* Update fixture
* Revert "Update fixture"
This reverts commit 0a1e7a5b29.
* Revert "Update fixtues"
This reverts commit b0c0e70200.
* Revert "Update tests"
This reverts commit 6a4421bb4e.
* Revert "Ensure we pass down the expiry_date for the license"
This reverts commit 2562395a78.
* Use expiry_date_in_millis value instead of expiry_date
This upgrades prettier to version 1.14.0. The main motivation is to gain support for the new TypeScript language features introduced in 2.9 and 3.0.
Prettier versions 1.13 and 1.14 also introduced some other JavaScript and TypeScript style improvements resulting in a few small line break and parenthesis changes.
The relevant release notes are:
* [Prettier 1.13.0 Release Notes](https://prettier.io/blog/2018/05/27/1.13.0.html)
* [Prettier 1.40.0 Release Notes](https://prettier.io/blog/2018/07/29/1.14.0.html)
* Retry the entire screenshotStitcher call
* Go back to a single run
* Only retry for this specific error. Post more information including the git issue link
This is a breaking change that removes the
`xpack.monitoring.node_resolver` setting. This setting was deprecated in
5.6, and in 6.1 the setting was limited to `uuid` explicitly. Beginning in
7.0, after this is merged, the setting will no longer exist.
- Fixes the bucket span estimator when median is selected as a detector function. agg.type.name is median and therefor not usable for an Elasticsearch aggregation. agg.type.dslName is percentile and is the correct mapping. .dslName is also used for the aggregations used for the preview charts.
- 7.0 will introduce a search.max_buckets setting which defaults to 10000. This could lead to failing bucket estimations because the values used for creating the required aggregations could result in more buckets. This PR fixes it by taking search.max_buckets into account when calculating the time range used for the bucket estimation. (Since 6.2 that setting is available so backporting this to current unreleased minor releases 6.4 and 6.5)
Improvements to job validation messages:
- Changed cardinality_over_field_low "might be less suitable" to "might not be suitable".
- Fixed documentation URLs.
- Extended categorization_filters_invalid message + documentation URL.