Add user permission check to CreateFieldButton
Refetch data after creating field
Add global styles to make Overlay z-index higher than timeline z-index
Fix create runtime field loading state
Update alert table columns after adding a new runtime field
Updated documentation of 'overlays.openFlyout' public API
Add cypress test
Add CreateField button unit test
* [Maps] do not fail migration when JSON.parse fails
* review feedback, log warning on failed migration
* better test name
* eslint
* eslint xpack/plugins/maps
* more eslint
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [ML] allocated models as a table
* [ML] handle fetching stats for stopped model
* [ML] change date formatter, enable check for start and stop action, change icon
* [ML] hide stats tab when not stats are available
* [ML] update state on action
* [ML] update memory breakdown message
* [ML] fix type
* [ML] fix functional test
* [ML] render nodes as links
* [ML] fix locator types
* [ML] support node name in the URL state
* [ML] update icon
* [ML] routing state with reason tooltip
* [ML] move experimental tag
* [ML] add state column, fix import
* [ML] update stats on aciton
* [ML] refresh by timer
* [ML] rename fetchStats callback
* [ML] replace with promise.all
* [ML] add deployment state const
Since we've enabled auto upgrades for some packages in 7.16, we need to
revert a previous change that only considered policy validation errors
non-fatal. Any error encountered during the dry-run/upgrade process
should be considered non-fatal so that users can still access the Fleet
UI if setup fails.
Fixes#116985
* [Discover] Add a retry in a value suggestion non timebased test
* Dismiss popover before Discover even loads
* Set local storage value in navigateToApp
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* remove use of pdf to png conversion checker in comparison test
* remove use of pdf-to-img use in compare images service
* remove pdf-to-img dep from kibana
This PR re-activates and stabilizes the data frame analytics feature importance tests by reducing the job run time. It also scrolls the feature importance section into view during validation so in case of a failure the screenshot shows the relevant part of the screen.
* [Logs UI][Metrics UI] Remove deprecated config fields from APIs
* Fix typecheck
* Fix typecheck
* Fix typecheck
* Fix jest
* Fix functional test
* Remove extraneous timeField args
* Typecheck fix
* Consolidate log file changes to ResolvedLogSourceConfiguration
* Fix merge
* Revert additional logs files
* Revert inventory models
* Revert log_analysis api
* Fix timefield reference in process list
* Restore logs page files, fix typecheck on mock
* Fix functional test
* Restore inventory models index
* Fix typecheck on getFilteredMetrics
* Look CI if you don't tell me all the type errors at once I can't fix them all
* Maybe this is the last typecheck fix who knows
* Restore reading timestamp field from data view
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Unskipping test
* Commenting out fix and fixing another test
* Fixing functional test
* Fixing functional test agaaaiiinn
* Fixing the actual flake
* Splitting into two tests
* Maybe this time
* fix flaky test + adding functional test
* review + remove more jest flaky test
* fix type
* fix review/confusion
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This replaces the `console.log` we have with `ToolingLog` which is what the e2e tests want to use. Right now they're producing a lot of `console.log` debugging information and noise which we don't want. Instead we want to use the standard tool logging that e2e has for the FTR tests.
The two most important files with changes are:
* x-pack/test/detection_engine_api_integration/utils.ts
* x-pack/test/lists_api_integration/utils.ts
From there everything else is just a repeating pattern of:
```ts
const log = getService('log');
```
And then pushing the log into the utilities:
such as:
```ts
await deleteListsIndex(supertest, log);
```
For reviewers, if you want to, checkout this branch and just ensure I didn't miss a `console.log` statement within the e2e tests anywhere. Also double check I did the correct `log.debug` vs `log.error` or if you think I misinterpreted one, point it out. I use `log.debug` where I have retries and then I use `log.error` where I thought it would be most useful to call out a very probable or unexpected statement happening when the tests begin to go sideways or have issues.
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
