* fixes#28899 by using the correct object path to the url `transaction.context.request.url.full`
* [APM] fixed IStickeyProperty.val to be stricter to prevent this bug from happening again
* To prevent risk of startup errors, put template index before any write operation
* await the put template
* remove no-longer-needed promises
* remove CRUFT test
* [Maps] handle extent filtering when extent crosses dateline
* ensure lat within range
* use geo_bounding_box instead of geo_polygon since it supports dateline
* add geo_shape functional test
* get functional tests running
* update convertMapExtentToPolygon so its not recursive
* clean up comment
* Prefer count over search for counting docs in HB index.
* Write test for updated adapter function.
* Remove unused body from request to avoid breaking ES change.
As suggested by @legrego in #28792, this PR adds a config flag to completely disable the welcome screen, which is enabled by the functional test runner to ensure that the welcome screen doesn't pop up.
* Move os info into OSS collection so the stats api can access it
* Fix tests
* copy this back for now
* Use server decorate to share from OSS to x-pack/plugins
In preparation for a updates to the nav bar I'd like to consume the `recentlyAccessed` service from Typescript, which would be easier if more of the ui/persisted_log module was written in TypeScript.
With https://github.com/elastic/kibana/pull/28503 we will be enabling the k7design by default, which adds a fixed header to the top of the page. This causes issues with the default "scroll into view" logic, as elements which are in the top overflow will be scrolled into view but then covered by the header.
My first attempt to solve this was adjusting the layout to only scroll the content below the header. This allowed the [standard scroll into view algorithm](https://drafts.csswg.org/cssom-view/#element-scrolling-members) to function as intended, but had a slightly worse UX on OSes like macOS, and @elastic/kibana-design ultimately pushed back because not allowing the body to scroll has other implications.
Instead I have implemented a `LeadfootElementWrapper#scrollIntoViewIfNecessary()` method which is automatically called before each `#click()` and `#moveMouseTo()` call. This new method scrolls the element into view when necessary, and then additionally adjusts the scroll position of the root scroll element by the necessary pixels if the top of the element is within `layout.fixedHeaderHeight` pixels.
* [DOCS] Adds documentation for index lifecycle policies
* [DOCS] Updated image for policy options to show all menu items
* Update create-policy.asciidoc
* [DOCS] Incorporated review comments on hot and warm phase
* [DOCS] Additional changes to warm phase
* [DOCS] Removed the word open in the warm phase
* Made change to cluster overview service to more reliably check if the page has loaded.
* Made change to cluster overview service to more reliably check if the page has loaded.
* Adds available memory stats (in percent) to metrics server response
* Updates UI memory charts for new data
* Updates memory chart metrics to be usage (average and max), removes other unused metrics
* Review feedback addressed, small refactors
* Updates memory chart tests
* add rollup toggle to index management
* adjusting i18n labels
* addressing PR feedback
* fixing tests
* exiting early when there are no toggles configured
* swallow exception and return original indicesList from rollupDataEnricher
* Disable responsiveness of table in small screens
Disabling the resposiveness of cells and table will avoid showing
empty areas around elements of the inspector table.
* Fix responsive table in requests view stats
* Remove tableLayout inline style
Previously, the Logs UI assumes that the index mapping of the logs indices has a default date format including `epoch_millis` configured for the timestamp field. If that is not the case queries can fail, leaving parsing exceptions in the Elasticsearch logs.
This PR fixes the Elasticsearch queries related to the Logs UI to explicitly specify the `epoch_millis` format for date range queries and aggregations.
fixeselastic/kibana#27554
Date field is the only field that can have a format specified in mappings.
The result of a top_hit aggregation, shown through visualize,
is formatted with the kibana formatter for the specific field type.
Setting data_time instead of use_field_mapping for date keeps the
visualization output consistent between es 6.3 and newer versions.
