* [chrome/breadcrumbs] don't clear the breadcrumbs on redirect routes
* [ui/topNav/breadcrumbs] don't set k7 breadcrumbs
* [management] implement k7Breadcrumbs in kibana mangement routes
* Avoid title case
* [chrome/breadcrumbs] protect against times where route did not match anything
* [chrome] only load route is available
* move breadcrumb modules into new location
* fix i18n message id
* Update reference to renamed variable
Co-Authored-By: spalger <email@spalger.com>
* simplify redirectTo and avoid mutable var
* fix eslint issues
* [APM] Split API into transactions and transaction_groups (#26349)
* [APM] Sort by score to get transaction samples with sampled:true (#26389)
* [APM] Move impact calculation to Elasticsearch (#26436)
* [APM] Move impact calculation to Elasticsearch
* Renamed “durationSum” to “sum” and went back to single, mutable impact
This changes the header to be conditionally rendered based on the k7design UI setting. If the setting is false, the header is rendered as before. If it is true, the header is hidden and the breadcrumbs are set via the Kibana breadcrumbs api.
* Specifying the timeout for the msearch in the body
* Revert "Specifying the timeout for the msearch in the body"
This reverts commit 7b07bfa2e6.
* Fixing the courier and the index pattern execute script timeouts
* adds global, workpad css styling feature
* fixes checkered position and default CSS in textarea
* adds global, workpad css styling feature
* fixes checkered position and default CSS in textarea
* Added global styles to page manager
* Added 'apply stylesheet' button
* fix after rebase
* change style to css
* move default workpad CSS class to constant
* unwind the empty page color pieces
Url's from EMS ((files and tiles) should be resolved ad-hoc. The one that is stored in the saved object should not be used. This change removes the URL from the saved object. It also provides fallback functionality so old saved objects continue to be loaded correctly.
Provides protection against reading/re-indexing against an index with missing
shards which could result in data loss. This shouldn't be common, as the Saved
Object indices should only ever have a single shard. This is more to handle
instances where customers manually expand the shards of an index.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
- Fixes 25707 by parsing the colors generated for the node and adding a
try/catch to prevent an errors by returning the default color
- Set the min bounds to zero when there is only one data point
* fix: relative link instead of static
* fix: handle missing reporting config value
* chore: refactor reportingBrowserType check
* fix: core interpreter reportingBrowserType
the code was duplicated from canvas, so it's equally as broken, this duplicates the fix
