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.
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
* [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>
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
Co-authored-by: ymao1 <ying.mao@elastic.co>
* 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>
Co-authored-by: Xavier Mouligneau <189600+XavierM@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
Co-authored-by: Frank Hassanabad <frank.hassanabad@elastic.co>
* [Fleet] Make integration names globally unique
* Fix Jest tests
* Append (copy) to names of integration packages belonging to duplicated policy
* Update current policy maintaining its name
* Fix failing tests
Co-authored-by: Cristina Amico <criamico@users.noreply.github.com>
### Summary
Went back to add audit logging to the alerts table search strategy used to query RAC alerts. This PR also includes tests for the logging.
Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
* Fix add to case functionality
* Use appropriate owner when attaching an alert to a case
* Use field name constants
* Gotta reskip the test
* Better error handling
* Fix type errors
* Fix tests
Co-authored-by: Madison Caldwell <madison.rey.caldwell@gmail.com>
Drop all empty kibana calls
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tre <wayne.seymour@elastic.co>
Drop all empty kibana calls
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tre <wayne.seymour@elastic.co>
* Add API tests for dependencies metadata (#116648)
* Add API tests for dependencies metadata
* Rename metadata tests to event metadata
Co-authored-by: Nathan L Smith <nathan.smith@elastic.co>
* Add API tests for top dependencies (#116788)
* Add top dependencies API tests
Co-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>
* [APM] Adding api tests for error group (#116771)
* adding api tests for error group
* addresing pr changes
* [APM] Synthtrace ES Client (#116770)
Co-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>
* Revert "[APM] Adding api tests for error group (#116771)"
This reverts commit f2402cef37.
* [APM] Apm errors api tests (#116764)
* changes after review
* move file to errors folder
* [APM] Fixing synthtrace import location (#117017)
Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>
Co-authored-by: Nathan L Smith <nathan.smith@elastic.co>
Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>
Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
* [Maps] fix unable to pluck style meta from local data for geo_grid vector tiles for any property other then count
* use metric instead of field value to be more precise
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Nathan Reese <reese.nathan@gmail.com>
* [Fleet] cypress setup (#113106)
* added cypress setup for fleet
* updated readme
* fixed types
* fix unused
* starting up fleet server in cypress
* added more fleet tests
* added package update test
* updated readme
* trying jenkins run
* trying jenkins run
* trying jenkins run
* fix types, cypress config
* example of mocked requests
* added getBySel
* fix test after refactor
* removed duplication
* fix tests
* added to buildkite
* updated tests
* starting agent with docker
* trying to fix ip address
* ifconfig
* ip address
* ip address
* ip address
* type fix
* remove extra logging
* fixed test
* fix buildkite
* cleanup
* cleanup
* using docker for fleet_server
* fix
* fix
* trying to fix
* update config
* test
* test
* test
* test
* revert changes
* test
* test
* static ip on linux
* docker version
* try again
* fixed review comments
* fixed types
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Patryk Kopycinski <contact@patrykkopycinski.com>
* using 8.0.0 docker image for backport
Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
Co-authored-by: Patryk Kopycinski <contact@patrykkopycinski.com>
Co-authored-by: Julia Bardi <julia.bardi@elastic.co>
## Summary
e2e tests are still seeing flake with conflicts and it looks like it _might_ be with querying and not with inserting data. Hard to tell. This PR:
* Adds more console logging when the response is not a 200
* Removes the 200 expect statement and hopes for the best but should blow up if it's not 200 in a different way and we will get the console logging statements.
* Fixes one other flake with the matrix histogram having different counts. We have encountered this before and are applying the same fix which is to just have it check > 0.
* This does fix the timeouts seen where 1 in every 1k rule runs, a rule will not fire until _after_ the 5 minute mark. The timeouts were seen when running the flake runner.
Flake failures around `conflict`:
https://github.com/elastic/kibana/issues/116926https://github.com/elastic/kibana/issues/116904https://github.com/elastic/kibana/issues/116231
Not saying this is going to fix those yet, but it's the last 200 ok's we did an expect on, so it might if we are ignoring the conflict. If it fails again I am hopeful beyond hope that we get the body message and line number within the utilities to determine where/why we are getting these from time to time. It does look to fix the timeouts when a rule misfires and slows down the rate at which we continuously query for rule results.
Failure around matrix histogram (The error messages are slightly different on CI each time):
https://github.com/elastic/kibana/issues/97365
Ran this with the flake runner across groups 11 and 12 100 times each and did not see the conflict crop up:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/128https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/129
The 1 failure in each of those runs were due to something on startup that prevented it from running.
### Checklist
Delete any items that are not applicable to this PR.
- [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
Co-authored-by: Frank Hassanabad <frank.hassanabad@elastic.co>
* [Global Nav] Moved Overview page/link to the accordion/Solution title
* Using Cloud logo for deployment link and fixing isActive state
* Change Deployment section to dark background
* Completely remove locking ability
* Change buttonElement if overview page exists
* Snaps from button/div
* PR Feedback:
- Puts `Overview` links back for Observability and Security
- Increases hit area and scopes underline of anchor tag within the accordion header
- Uses `id`’s to find Overview pages instead of `title` text
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
* [ILM] Fixed ILM a11y test by creating a snapshot repo that is now required in the ILM API
* [ILM] Fixed functional test by creating a snapshot repository
* [ILM] Updated the params after es client update
* [ILM] Added filtering by policy name to the a11y test to find the correct ILM policy in the list
* [ILM] Added filtering by policy name to the a11y test to find the correct ILM policy in the list
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* use event.ingested for datastream last activity
* remove ms precision from datastream dates
* add timestamp check to test
* fix type error
* split test out to be less complex and more reliable 🤞
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co>
* unskip test suite
* Fix functional tests and some refactoring
* Refactor Policy Details test and centralize getting of Agent Policy combined input for endpoint
* Change approach for checking policy data in fleet pages
* Change Policy Settings displayed in Fleet to a) show a loader while retrieving settings and b) show loading errors if any
* Close any visible toasts before clicking on the save button
Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>
This PR removes the `monitor` cluster privilege from the `ft_ml_ui_extras` test role as it's no longer required by the categorization wizard and we want to stay close to the minimum set of required privileges for our test users.
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
