* 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
* 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
* [APM] fixes#25650 by using react-vis LineMarkSeries rathern than LineSeries to render a single data point
* [APM] bumped mark size form 0.5 to 1 and removed commented code lines
* [APM] reduced mark size back down to 0.5 from 1 so they are not visible from within lines
* Fixes#27573 by targeting `docker.container.id` to populate the action menu
* [APM] replace lodash get with idx accessor to not lose type information
* [APM] fix type inconsistencies between v1 and v2 transaction types
* Updating docs
- Configure data sources via config/kibana.yml
- Fix typo
* Adding timestamp override
* Documenting all settings
* Removing changes from a different PR
* Add settings docs
* Adding all the settings
* Updating docs based on feed back from PR
* Adding periods to lines; changing disabled to present tense
* Updates to docs per PR
* Updates per PR
* Fixes per PR
* Switched tabs to render to avoid unnecessary mount cycles
We were previously using the 'component' prop for React Router routes inside of our history tabs component, which causes lots of extra mount cycles. Using the 'render' prop avoids that.
We also decided to *only* allow the render prop, which means using a component is a little more verbose b/c you have to pass down props from the render method, but it's worth it to avoid accidentally using 'component'.
For more, see: https://reacttraining.com/react-router/web/api/Route
Specifically:
"When you use component (instead of render or children, below) the router uses React.createElement to create a new React element from the given component. That means if you provide an inline function to the component prop, you would create a new component every render. This results in the existing component unmounting and the new component mounting instead of just updating the existing component. When using an inline function for inline rendering, use the render or the children prop (below)."
* Prevents trace list from flickering on data load, while still preventing inaccurate no items message while loading
* Updates tests
* Added op value to compare error message. Removed duplicate unit test
* Added single quotes to ply error message to help distinguish incorrect value
* Added value of context to progress error message
* Added percent value to reveal image error message
* Added single quotes to alterColumn error message to help distinguish incorrect value
* Added single quotes to timefilter error message to help distinguish incorrect value
* Added single quotes to axisConfg error message to help distinguish incorrect value
* Cleaned up error message in compare
* Added single quotes to font error messages
* Added single quotes to getCell error messages
* Added single quotes to progress error messages
* Added single quotes to revealImage error messages
* Cleaned up timefilter error message
* Added single quotes to demodata error messages
* Added unit test back
* Updated error message in ply
* Only load ILM data enricher if UI is enabled
* Silently swallow errors from data enrichers
* Only add index management ILM extensions if ILM UI is enabled
* [BeatsCM] use static map of pages vs dynamic from FS
* remove snapshot
* Apply suggestions from code review
* Update x-pack/plugins/beats_management/public/pages/index.ts
* chore: revert #26809
it was a temp fix meant to be removed anyway
* chore: convert timelion to private browser function
allows access to ui/chrome, required for determining the server basepath
Plugins loaded by the `@kbn/interpreter` can sometimes setup global values while loading, like the regeneratorRuntime for instance, but the current plugin loading code is deleting every global that was added during plugin load. This changes the logic to only cleanup the `canvas` global after loading the canvas plugins.
resolves https://github.com/elastic/kibana/issues/27162
