mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
6545 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Gerard Soldevila
|
36fa5a4da6
|
[8.18] SKA: Relocate "platform" packages that remain on /packages (208704) (#212751)
# Backport This will backport the following commits from `main` to `8.18`: - #208704 |
||
Kibana Machine
|
9320518f54
|
[8.18] Decouple some modules from 'webpack' (#212746) (#212898)
# Backport This will backport the following commits from `main` to `8.18`: - [Decouple some modules from 'webpack' (#212746)](https://github.com/elastic/kibana/pull/212746) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T12:21:50Z","message":"Decouple some modules from 'webpack' (#212746)\n\n## Summary\n\nRemove extraneous dependencies:\n* `canvas` was depending on 'webpack' purely for a type (dev-time).\n* `@kbn/optimizer-webpack-helpers` (canvas depends on it 🤨) was\ndepending on 'webpack' solely for a function that could be defined in\n`@kbn/optimizer` (devOnly).","sha":"3fcd11ce4dc1e464b0d653e79453b87296ac25c6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:version","v8.18.0","v9.1.0"],"title":"Decouple some modules from 'webpack'","number":212746,"url":"https://github.com/elastic/kibana/pull/212746","mergeCommit":{"message":"Decouple some modules from 'webpack' (#212746)\n\n## Summary\n\nRemove extraneous dependencies:\n* `canvas` was depending on 'webpack' purely for a type (dev-time).\n* `@kbn/optimizer-webpack-helpers` (canvas depends on it 🤨) was\ndepending on 'webpack' solely for a function that could be defined in\n`@kbn/optimizer` (devOnly).","sha":"3fcd11ce4dc1e464b0d653e79453b87296ac25c6"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212746","number":212746,"mergeCommit":{"message":"Decouple some modules from 'webpack' (#212746)\n\n## Summary\n\nRemove extraneous dependencies:\n* `canvas` was depending on 'webpack' purely for a type (dev-time).\n* `@kbn/optimizer-webpack-helpers` (canvas depends on it 🤨) was\ndepending on 'webpack' solely for a function that could be defined in\n`@kbn/optimizer` (devOnly).","sha":"3fcd11ce4dc1e464b0d653e79453b87296ac25c6"}}]}] BACKPORT--> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co> |
||
Jean-Louis Leysens
|
a4cd9d31f1
|
[8.18] [OAS] Remove Elastic-Api-Version (#207071) (#210835)
# Backport This will backport the following commits from `main` to `8.18`: - [[OAS] Remove `Elastic-Api-Version` (#207071)](https://github.com/elastic/kibana/pull/207071) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T15:59:45Z","message":"[OAS] Remove `Elastic-Api-Version` (#207071)\n\n## Summary\r\n\r\nWe anticipate generating a single document per API version for the\r\nforeseeable future. This PR updates our OAS document merging logic to\r\navoid adding the `Elastic-Api-Version` header to our spec.\r\n\r\nThis will also remove this header from current documentation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"53cba303e55c6c7d0060908938c343931513d114","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport missing","v9.0.0","Feature:OAS","backport:version","v8.18.0"],"title":"[OAS] Remove `Elastic-Api-Version`","number":207071,"url":"https://github.com/elastic/kibana/pull/207071","mergeCommit":{"message":"[OAS] Remove `Elastic-Api-Version` (#207071)\n\n## Summary\r\n\r\nWe anticipate generating a single document per API version for the\r\nforeseeable future. This PR updates our OAS document merging logic to\r\navoid adding the `Elastic-Api-Version` header to our spec.\r\n\r\nThis will also remove this header from current documentation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"53cba303e55c6c7d0060908938c343931513d114"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207071","number":207071,"mergeCommit":{"message":"[OAS] Remove `Elastic-Api-Version` (#207071)\n\n## Summary\r\n\r\nWe anticipate generating a single document per API version for the\r\nforeseeable future. This PR updates our OAS document merging logic to\r\navoid adding the `Elastic-Api-Version` header to our spec.\r\n\r\nThis will also remove this header from current documentation.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"53cba303e55c6c7d0060908938c343931513d114"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Shahzad
|
8dd76bedd8
|
[8.18] [Synthetics] Fix overview error popover !! (#211431) (#212620)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Fix overview error popover !! (#211431)](https://github.com/elastic/kibana/pull/211431) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-02-21T16:38:54Z","message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0"],"title":"[Synthetics] Fix overview error popover !!","number":211431,"url":"https://github.com/elastic/kibana/pull/211431","mergeCommit":{"message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212123","number":212123,"state":"MERGED","mergeCommit":{"sha":"83e37babbff8e702c51c2746c790930510f4ccb4","message":"[9.0] [Synthetics] Fix overview error popover !! (#211431) (#212123)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Synthetics] Fix overview error popover !!\n(#211431)](https://github.com/elastic/kibana/pull/211431)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211431","number":211431,"mergeCommit":{"message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Gerard Soldevila
|
e2497bec0c
|
[8.18] SKA: Misc cleanup and enhancements (#212207) (#212352)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Misc cleanup and enhancements (#212207)](https://github.com/elastic/kibana/pull/212207) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T13:31:00Z","message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Misc cleanup and enhancements","number":212207,"url":"https://github.com/elastic/kibana/pull/212207","mergeCommit":{"message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212207","number":212207,"mergeCommit":{"message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
bdeda8a477
|
[8.18] [scout] Don't mix await with promise callbacks (#211905) (#211914)
# Backport This will backport the following commits from `main` to `8.18`: - [[scout] Don't mix `await` with promise callbacks (#211905)](https://github.com/elastic/kibana/pull/211905) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Olaru","email":"dolaru@elastic.co"},"sourceCommit":{"committedDate":"2025-02-20T15:05:17Z","message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[scout] Don't mix `await` with promise callbacks","number":211905,"url":"https://github.com/elastic/kibana/pull/211905","mergeCommit":{"message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211905","number":211905,"mergeCommit":{"message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: David Olaru <dolaru@elastic.co> |
||
|
Gerard Soldevila
|
920b398e8c
|
[8.18] SKA: Categorise platform devOnly packages under /packages (#211560) (#211740)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Categorise platform devOnly packages under `/packages` (#211560)](https://github.com/elastic/kibana/pull/211560) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T09:38:42Z","message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Categorise platform devOnly packages under `/packages`","number":211560,"url":"https://github.com/elastic/kibana/pull/211560","mergeCommit":{"message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211560","number":211560,"mergeCommit":{"message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211702","number":211702,"state":"OPEN"}]}] BACKPORT--> |
||
|
Gerard Soldevila
|
6f0dd13c49
|
[8.18] SKA: Fix kebab-case issues in security-threat-hunting packages (#211349) (#211734)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)](https://github.com/elastic/kibana/pull/211349) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T10:21:45Z","message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Fix kebab-case issues in security-threat-hunting packages","number":211349,"url":"https://github.com/elastic/kibana/pull/211349","mergeCommit":{"message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211722","number":211722,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211349","number":211349,"mergeCommit":{"message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Gerard Soldevila
|
b2b8cfa1c4
|
[8.18] SKA: Unify kbn-management folders + storybook config (#211564) (#211691)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Unify `kbn-management` folders + storybook config (#211564)](https://github.com/elastic/kibana/pull/211564) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T08:10:22Z","message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Unify `kbn-management` folders + storybook config","number":211564,"url":"https://github.com/elastic/kibana/pull/211564","mergeCommit":{"message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211564","number":211564,"mergeCommit":{"message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Gerard Soldevila
|
e25318f13a
|
[8.18] SKA: Unify serverless modules + storybook config (#211570) (#211694)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Unify `serverless` modules + storybook config (#211570)](https://github.com/elastic/kibana/pull/211570) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T08:10:35Z","message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Unify `serverless` modules + storybook config","number":211570,"url":"https://github.com/elastic/kibana/pull/211570","mergeCommit":{"message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211570","number":211570,"mergeCommit":{"message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
6c7783de5a
|
[8.18] fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121) (#211615)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)](https://github.com/elastic/kibana/pull/211121) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Rafael Lüder","email":"rlueder@pm.me"},"sourceCommit":{"committedDate":"2025-02-18T16:37:57Z","message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.18.0","v9.1.0"],"title":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config","number":211121,"url":"https://github.com/elastic/kibana/pull/211121","mergeCommit":{"message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211121","number":211121,"mergeCommit":{"message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b"}}]}] BACKPORT--> Co-authored-by: Rafael Lüder <rlueder@pm.me> |
||
|
Kibana Machine
|
4bcd166b3a
|
[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)
# Backport This will backport the following commits from `main` to `8.18`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:07:41Z","message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin","number":211231,"url":"https://github.com/elastic/kibana/pull/211231","mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211231","number":211231,"mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
Karen Grigoryan
|
ef85e7491b
|
[8.18] [Security Solution][Explore] Migrate from styled-components in shared (#210311) (#211226)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Explore] Migrate from styled-components in shared (#210311)](https://github.com/elastic/kibana/pull/210311) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T16:14:34Z","message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution][Explore] Migrate from styled-components in shared","number":210311,"url":"https://github.com/elastic/kibana/pull/210311","mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210311","number":210311,"mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Tiago Costa
|
c7f893aebd
|
[8.18] chore(NA): upgrade to webpack 5 (#191106) (#211147)
# Backport This will backport the following commits from `main` to `8.18`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},{"url":"https://github.com/elastic/kibana/pull/211146","number":211146,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Karen Grigoryan
|
39b493c84f
|
[8.18] [Security Solution] [EUI Refresh] styled component migration Dashboards (#208731) (#210983)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)](https://github.com/elastic/kibana/pull/208731) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T15:05:27Z","message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution] [EUI Refresh] styled component migration Dashboards","number":208731,"url":"https://github.com/elastic/kibana/pull/208731","mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210886","number":210886,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208731","number":208731,"mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210967","number":210967,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com> |
||
Angela Chuang
|
224f94591c
|
[8.18] [Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631) (#210566)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)](https://github.com/elastic/kibana/pull/204631) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-09T12:46:55Z","message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","ci:cloud-deploy","EUI Visual Refresh"],"title":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex","number":204631,"url":"https://github.com/elastic/kibana/pull/204631","mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204631","number":204631,"mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}}]}] BACKPORT--> |
||
Jared Burgett
|
930465848e
|
[8.18] [Entity Analytics] Consider Closed alerts for Risk Scoring (#193667) (#210941)
# Backport This will backport the following commits from `main` to `8.18`: - [[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)](https://github.com/elastic/kibana/pull/193667) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-08T07:28:54Z","message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport","v9.0.0","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Entity Analytics] Consider Closed alerts for Risk Scoring","number":193667,"url":"https://github.com/elastic/kibana/pull/193667","mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193667","number":193667,"mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
|
Karen Grigoryan
|
40be9df6e9
|
[8.18] [Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318) (#209852)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)](https://github.com/elastic/kibana/pull/207318) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-30T12:24:05Z","message":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)\n\n## Summary\r\nAddresses [#206437](https://github.com/elastic/kibana/issues/206437)\r\nThis PR migrates `explore page` from `styled-components` to\r\n`@emotion/styled`.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/f1702c0d-78f7-4e17-a8d6-c7c9ae19d3b7\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1e63b5ae999eb5022f9f02626db9f70e17d28a92","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Threat Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0"],"title":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components","number":207318,"url":"https://github.com/elastic/kibana/pull/207318","mergeCommit":{"message":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)\n\n## Summary\r\nAddresses [#206437](https://github.com/elastic/kibana/issues/206437)\r\nThis PR migrates `explore page` from `styled-components` to\r\n`@emotion/styled`.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/f1702c0d-78f7-4e17-a8d6-c7c9ae19d3b7\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1e63b5ae999eb5022f9f02626db9f70e17d28a92"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/208928","number":208928,"state":"OPEN"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com> |
||
|
Gerard Soldevila
|
144ccad614
|
[8.18] SKA: Follow-up relocations (#209477) (#210507)
# Backport This will backport the following commits from `main` to `8.18`: - [SKA: Follow-up relocations (#209477)](https://github.com/elastic/kibana/pull/209477) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T18:53:36Z","message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport missing","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v9.1.0"],"title":"SKA: Follow-up relocations","number":209477,"url":"https://github.com/elastic/kibana/pull/209477","mergeCommit":{"message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209477","number":209477,"mergeCommit":{"message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b"}}]}] BACKPORT--> |
||
Jatin Kathuria
|
45f6001978
|
[8.18] [Security Solution] Fix timeline dynamic batching (#204034) | [ Security Solution ] Fix Refetch logic with new timeline batching (#205893) (#210066)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix timeline dynamic batching (#204034)](https://github.com/elastic/kibana/pull/204034) - [[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)](https://github.com/elastic/kibana/pull/205893) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-01-07T06:20:30Z","message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport missing","v9.0.0","Team:Threat Hunting:Investigations","backport:prev-minor","v8.16.3","v8.19.0"],"title":"[Security Solution] Fix timeline dynamic batching","number":204034,"url":"https://github.com/elastic/kibana/pull/204034","mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204034","number":204034,"mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/205674","number":205674,"state":"OPEN"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/205676","number":205676,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/205702","number":205702,"branch":"8.x","state":"MERGED","mergeCommit":{"sha":"e480de112ae6bc121c4415e2e1726dd551805672","message":"[8.x] [Security Solution] Fix timeline dynamic batching (#204034) (#205702)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Fix timeline dynamic batching\n(#204034)](https://github.com/elastic/kibana/pull/204034)\n - https://github.com/elastic/kibana/pull/205893\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-07T06:20:30Z\",\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"v8.16.3\"],\"number\":204034,\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"number\":204034,\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},{\"branch\":\"8.16\",\"label\":\"v8.16.3\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/205674\",\"number\":205674,\"state\":\"OPEN\"},{\"url\":\"https://github.com/elastic/kibana/pull/205676\",\"number\":205676,\"branch\":\"8.17\",\"state\":\"OPEN\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]},{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T21:12:38Z","message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"54b4fac705c231b52396d70906f3259f9b129a3b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v9.1.0"],"title":"[ Security Solution ] Fix Refetch logic with new timeline batching","number":205893,"url":"https://github.com/elastic/kibana/pull/205893","mergeCommit":{"message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"54b4fac705c231b52396d70906f3259f9b129a3b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209916","number":209916,"state":"MERGED","mergeCommit":{"sha":"aeaff4957aded708fecfa0e57f16b3cba5f77485","message":"[9.0] [ Security Solution ] Fix Refetch logic with new timeline batching (#205893) (#209916)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[ Security Solution ] Fix Refetch logic with new timeline batching\n(#205893)](https://github.com/elastic/kibana/pull/205893)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T21:12:38Z\",\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"backport\",\"release_note:skip\",\"Team:Threat\nHunting:Investigations\",\"v8.9.1\",\"v9.1.0\"],\"title\":\"[ Security Solution\n] Fix Refetch logic with new timeline\nbatching\",\"number\":205893,\"url\":\"https://github.com/elastic/kibana/pull/205893\",\"mergeCommit\":{\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.9\"],\"targetPullRequestStates\":[{\"branch\":\"8.9\",\"label\":\"v8.9.1\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/205893\",\"number\":205893,\"mergeCommit\":{\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205893","number":205893,"mergeCommit":{"message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"54b4fac705c231b52396d70906f3259f9b129a3b"}},{"url":"https://github.com/elastic/kibana/pull/205676","number":205676,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/205702","number":205702,"branch":"8.x","state":"MERGED","mergeCommit":{"sha":"e480de112ae6bc121c4415e2e1726dd551805672","message":"[8.x] [Security Solution] Fix timeline dynamic batching (#204034) (#205702)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Fix timeline dynamic batching\n(#204034)](https://github.com/elastic/kibana/pull/204034)\n - https://github.com/elastic/kibana/pull/205893\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-07T06:20:30Z\",\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"v8.16.3\"],\"number\":204034,\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"number\":204034,\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},{\"branch\":\"8.16\",\"label\":\"v8.16.3\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/205674\",\"number\":205674,\"state\":\"OPEN\"},{\"url\":\"https://github.com/elastic/kibana/pull/205676\",\"number\":205676,\"branch\":\"8.17\",\"state\":\"OPEN\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"url":"https://github.com/elastic/kibana/pull/205674","number":205674,"branch":"8.16","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
443bfc7537
|
[8.18] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#210087)
# Backport This will backport the following commits from `main` to `8.18`: - [[scout] unique runId for reporting, disabled failed test reporter locally (#209507)](https://github.com/elastic/kibana/pull/209507) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T15:35:26Z","message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","test:scout","v9.1.0"],"title":"[scout] unique runId for reporting, disabled failed test reporter locally","number":209507,"url":"https://github.com/elastic/kibana/pull/209507","mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209808","number":209808,"state":"MERGED","mergeCommit":{"sha":"2c04505bd6ad9db59e0ea3aa617d649b41134294","message":"[9.0] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#209808)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[scout] unique runId for reporting, disabled failed test reporter\nlocally (#209507)](https://github.com/elastic/kibana/pull/209507)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T15:35:26Z\",\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"test:scout\",\"v9.1.0\"],\"title\":\"[scout]\nunique runId for reporting, disabled failed test reporter\nlocally\",\"number\":209507,\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"number\":209507,\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be enough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209507","number":209507,"mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Kibana Machine
|
cd940ff75f
|
[8.18] [Journeys] Set traceparent for Playwright (#189800) (#209859)
# Backport This will backport the following commits from `main` to `8.18`: - [[Journeys] Set traceparent for Playwright (#189800)](https://github.com/elastic/kibana/pull/189800) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T17:53:34Z","message":"[Journeys] Set traceparent for Playwright (#189800)\n\nSets the traceparent for Playwright, so the trace from the test runner\nincludes the trace events from the browser and Kibana server.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"27893f5fcd8ef9775df54e8aadaa41f3b2d78c3a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Journeys] Set traceparent for Playwright","number":189800,"url":"https://github.com/elastic/kibana/pull/189800","mergeCommit":{"message":"[Journeys] Set traceparent for Playwright (#189800)\n\nSets the traceparent for Playwright, so the trace from the test runner\nincludes the trace events from the browser and Kibana server.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"27893f5fcd8ef9775df54e8aadaa41f3b2d78c3a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/189800","number":189800,"mergeCommit":{"message":"[Journeys] Set traceparent for Playwright (#189800)\n\nSets the traceparent for Playwright, so the trace from the test runner\nincludes the trace events from the browser and Kibana server.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"27893f5fcd8ef9775df54e8aadaa41f3b2d78c3a"}}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> |
||
|
Kibana Machine
|
349a5b7817
|
[8.18] [Synthtrace] Introducing teardown for scenarios (#209739) (#209798)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthtrace] Introducing teardown for scenarios (#209739)](https://github.com/elastic/kibana/pull/209739) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yngrid Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T14:57:50Z","message":"[Synthtrace] Introducing teardown for scenarios (#209739)\n\n### Background\r\n\r\nIn some scenarios we need to perform some setup at bootstrap time, this\r\nsetup could affect following scenarios.\r\nTake for example\r\n[failed_logs](https://github.com/elastic/kibana/blob/main/packages/kbn-apm-synthtrace/src/scenarios/failed_logs.ts)\r\nscenario where we create a pipeline that will do some checks in\r\n`log.level` property, if we try to run an scenario after that one we\r\nwill enter into some issues.\r\n\r\n### Changes\r\n\r\nThis PR aims to introduce a `teardown` setup for scenarios where we\r\ncould undo the changes done at `bootstrap` time.","sha":"c56d7ea24a898cbf6943719af1ef37c03250e2ee","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.18.0","v9.1.0","v8.19.0"],"title":"[Synthtrace] Introducing teardown for scenarios","number":209739,"url":"https://github.com/elastic/kibana/pull/209739","mergeCommit":{"message":"[Synthtrace] Introducing teardown for scenarios (#209739)\n\n### Background\r\n\r\nIn some scenarios we need to perform some setup at bootstrap time, this\r\nsetup could affect following scenarios.\r\nTake for example\r\n[failed_logs](https://github.com/elastic/kibana/blob/main/packages/kbn-apm-synthtrace/src/scenarios/failed_logs.ts)\r\nscenario where we create a pipeline that will do some checks in\r\n`log.level` property, if we try to run an scenario after that one we\r\nwill enter into some issues.\r\n\r\n### Changes\r\n\r\nThis PR aims to introduce a `teardown` setup for scenarios where we\r\ncould undo the changes done at `bootstrap` time.","sha":"c56d7ea24a898cbf6943719af1ef37c03250e2ee"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209739","number":209739,"mergeCommit":{"message":"[Synthtrace] Introducing teardown for scenarios (#209739)\n\n### Background\r\n\r\nIn some scenarios we need to perform some setup at bootstrap time, this\r\nsetup could affect following scenarios.\r\nTake for example\r\n[failed_logs](https://github.com/elastic/kibana/blob/main/packages/kbn-apm-synthtrace/src/scenarios/failed_logs.ts)\r\nscenario where we create a pipeline that will do some checks in\r\n`log.level` property, if we try to run an scenario after that one we\r\nwill enter into some issues.\r\n\r\n### Changes\r\n\r\nThis PR aims to introduce a `teardown` setup for scenarios where we\r\ncould undo the changes done at `bootstrap` time.","sha":"c56d7ea24a898cbf6943719af1ef37c03250e2ee"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Yngrid Coello <yngrid.coello@elastic.co> |
||
|
Kibana Machine
|
8653660363
|
[8.18] [SLO]: require instance id in slo details schema (#209020) (#209568)
# Backport This will backport the following commits from `main` to `8.18`: - [[SLO]: require instance id in slo details schema (#209020)](https://github.com/elastic/kibana/pull/209020) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T15:20:03Z","message":"[SLO]: require instance id in slo details schema (#209020)\n\n## Summary\r\n\r\nResolves #180590\r\n\r\nSince SLO instanceId is provided in all APIs, it will be made required\r\nfor sloWithDataResponseSchema and the SLOWithSummaryResponse type.\r\nChecks for the existence of instanceId have either been removed or\r\nchanged to check for ALL_VALUE (`*`)\r\n\r\n---------\r\n\r\nCo-authored-by: Kevin Delemme <kevin.delemme@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df573d75968a0f0c4535b75131df51d160d8d10a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:prev-minor","Team:obs-ux-management","v8.18.0","v9.1.0"],"title":"[SLO]: require instance id in slo details schema","number":209020,"url":"https://github.com/elastic/kibana/pull/209020","mergeCommit":{"message":"[SLO]: require instance id in slo details schema (#209020)\n\n## Summary\r\n\r\nResolves #180590\r\n\r\nSince SLO instanceId is provided in all APIs, it will be made required\r\nfor sloWithDataResponseSchema and the SLOWithSummaryResponse type.\r\nChecks for the existence of instanceId have either been removed or\r\nchanged to check for ALL_VALUE (`*`)\r\n\r\n---------\r\n\r\nCo-authored-by: Kevin Delemme <kevin.delemme@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df573d75968a0f0c4535b75131df51d160d8d10a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209020","number":209020,"mergeCommit":{"message":"[SLO]: require instance id in slo details schema (#209020)\n\n## Summary\r\n\r\nResolves #180590\r\n\r\nSince SLO instanceId is provided in all APIs, it will be made required\r\nfor sloWithDataResponseSchema and the SLOWithSummaryResponse type.\r\nChecks for the existence of instanceId have either been removed or\r\nchanged to check for ALL_VALUE (`*`)\r\n\r\n---------\r\n\r\nCo-authored-by: Kevin Delemme <kevin.delemme@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"df573d75968a0f0c4535b75131df51d160d8d10a"}}]}] BACKPORT--> Co-authored-by: Bailey Cash <bailey.cash@elastic.co> |
||
|
Kibana Machine
|
ea3e7589e6
|
[8.18] [Synthtrace] Fix synthtrace to work with 7.x clusters (#209447) (#209480)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthtrace] Fix synthtrace to work with 7.x clusters (#209447)](https://github.com/elastic/kibana/pull/209447) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Achyut Jhunjhunwala","email":"achyut.jhunjhunwala@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T09:25:00Z","message":"[Synthtrace] Fix synthtrace to work with 7.x clusters (#209447)\n\n## Summary\r\n\r\nWhile working on 9.x Upgrade testing, i found that when running\r\nsynthtrace scenarios pointing to a 7.x cluster, it tries to fetch the\r\nlatest version of the APM package. In 7.x, the `latestVersion` item was\r\npresent under a different node in the API response. Hence adding this\r\nfix.","sha":"032337332c020baeabc215f123eaca833efafdd5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-logs","Team:obs-ux-infra_services","v9.1.0"],"title":"[Synthtrace] Fix synthtrace to work with 7.x clusters","number":209447,"url":"https://github.com/elastic/kibana/pull/209447","mergeCommit":{"message":"[Synthtrace] Fix synthtrace to work with 7.x clusters (#209447)\n\n## Summary\r\n\r\nWhile working on 9.x Upgrade testing, i found that when running\r\nsynthtrace scenarios pointing to a 7.x cluster, it tries to fetch the\r\nlatest version of the APM package. In 7.x, the `latestVersion` item was\r\npresent under a different node in the API response. Hence adding this\r\nfix.","sha":"032337332c020baeabc215f123eaca833efafdd5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209447","number":209447,"mergeCommit":{"message":"[Synthtrace] Fix synthtrace to work with 7.x clusters (#209447)\n\n## Summary\r\n\r\nWhile working on 9.x Upgrade testing, i found that when running\r\nsynthtrace scenarios pointing to a 7.x cluster, it tries to fetch the\r\nlatest version of the APM package. In 7.x, the `latestVersion` item was\r\npresent under a different node in the API response. Hence adding this\r\nfix.","sha":"032337332c020baeabc215f123eaca833efafdd5"}}]}] BACKPORT--> Co-authored-by: Achyut Jhunjhunwala <achyut.jhunjhunwala@elastic.co> |
||
|
Tiago Costa
|
7fdf1892bb
|
fix(NA): fixtures at packages/kbn-plugin-helpers/src/integration_tests/build.test.ts | ||
|
Kibana Machine
|
019de9a8a3
|
[8.x] [scout] add script to discover playwright configs in repo (#208733) (#208886)
# Backport This will backport the following commits from `main` to `8.x`: - [[scout] add script to discover playwright configs in repo (#208733)](https://github.com/elastic/kibana/pull/208733) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T08:42:15Z","message":"[scout] add script to discover playwright configs in repo (#208733)\n\n## Summary\r\n\r\nAdding script to discover Scout playwright tests in Kibana repo, will be\r\nused to build CI pipeline step (running tests per plugin in a separate\r\nworker for the start). We can also consider using it to decide if code\r\nchange should trigger only specific plugin tests to run.\r\n\r\nUsage:\r\n```\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform/plugins/private/discover_enhanced\r\n```\r\n\r\nOutput:\r\n```\r\n info Searching for playwright config files in the following paths:\r\n info - x-pack/platform/plugins/private/discover_enhanced/**/ui_tests/{playwright.config.ts,parallel.playwright.config.ts}\r\n info\r\n info Discovered playwright config files in '1' plugins\r\n info [discover_enhanced] plugin:\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\r\n```\r\n\r\nMore usage examples:\r\n```\r\nnode scripts/scout.js discover-playwright-configs // by default will search in ['src/platform/plugins', 'x-pack/**/plugins'] and return all existing ones\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform // platform ones under x-pack\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/** // all under x-pack\r\n```","sha":"cf7debdfa3fb4a253ac0ec1b43e588e5163f8a98","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","test:scout"],"title":"[scout] add script to discover playwright configs in repo","number":208733,"url":"https://github.com/elastic/kibana/pull/208733","mergeCommit":{"message":"[scout] add script to discover playwright configs in repo (#208733)\n\n## Summary\r\n\r\nAdding script to discover Scout playwright tests in Kibana repo, will be\r\nused to build CI pipeline step (running tests per plugin in a separate\r\nworker for the start). We can also consider using it to decide if code\r\nchange should trigger only specific plugin tests to run.\r\n\r\nUsage:\r\n```\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform/plugins/private/discover_enhanced\r\n```\r\n\r\nOutput:\r\n```\r\n info Searching for playwright config files in the following paths:\r\n info - x-pack/platform/plugins/private/discover_enhanced/**/ui_tests/{playwright.config.ts,parallel.playwright.config.ts}\r\n info\r\n info Discovered playwright config files in '1' plugins\r\n info [discover_enhanced] plugin:\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\r\n```\r\n\r\nMore usage examples:\r\n```\r\nnode scripts/scout.js discover-playwright-configs // by default will search in ['src/platform/plugins', 'x-pack/**/plugins'] and return all existing ones\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform // platform ones under x-pack\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/** // all under x-pack\r\n```","sha":"cf7debdfa3fb4a253ac0ec1b43e588e5163f8a98"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208733","number":208733,"mergeCommit":{"message":"[scout] add script to discover playwright configs in repo (#208733)\n\n## Summary\r\n\r\nAdding script to discover Scout playwright tests in Kibana repo, will be\r\nused to build CI pipeline step (running tests per plugin in a separate\r\nworker for the start). We can also consider using it to decide if code\r\nchange should trigger only specific plugin tests to run.\r\n\r\nUsage:\r\n```\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform/plugins/private/discover_enhanced\r\n```\r\n\r\nOutput:\r\n```\r\n info Searching for playwright config files in the following paths:\r\n info - x-pack/platform/plugins/private/discover_enhanced/**/ui_tests/{playwright.config.ts,parallel.playwright.config.ts}\r\n info\r\n info Discovered playwright config files in '1' plugins\r\n info [discover_enhanced] plugin:\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n info - x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\r\n```\r\n\r\nMore usage examples:\r\n```\r\nnode scripts/scout.js discover-playwright-configs // by default will search in ['src/platform/plugins', 'x-pack/**/plugins'] and return all existing ones\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/platform // platform ones under x-pack\r\nnode scripts/scout.js discover-playwright-configs --searchPaths x-pack/** // all under x-pack\r\n```","sha":"cf7debdfa3fb4a253ac0ec1b43e588e5163f8a98"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Jared Burgett
|
ad15e7d4d1
|
[8.x] [Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints (#208201) (#208866)
# Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints (#208201)](https://github.com/elastic/kibana/pull/208201) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-29T23:49:13Z","message":"[Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints (#208201)\n\n## Summary\n\nThis PR introduces support for configuring the `timestamp` field for\nentity store enablement.\n\nBy default, the `timestamp` field is set to `@timestamp`, but users can\nopt to use `event.ingested` or another preferred value based on their\nrequirements.\n\n\n### Entity Store API changes\n\n#### Entity Store enable\n\n```\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n```\n\n#### Result \n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n```\nPOST kbn:/api/entity_store/enable\n{\n}\n```\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\nDifferent entity types can have distinct `timestampField` values, as\ndescribed below:\n\nFor instance, the `host` entity uses `event.ingested` as its\n`timestampField`, while other entities default to the `@timestamp`\nfield.\n\n```\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n### Testing steps\n\n- Check out this PR branch.\n- Start Kibana.\n- Avoid enabling the Entity Store from the UI initially. Instead, enable\nit via the API by following the steps outlined below.\n\n```\nDELETE kbn:/api/entity_store/engines/user\nDELETE kbn:/api/entity_store/engines/host\n\nGET kbn:/api/entity_store/status\n\n All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n\n# All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n}\n\n# Different entity with different timestamp Field\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n4. Afterward, you can test the functionality through the UI. First,\nclear the entity data from the UI, then start the Entity Store. Note\nthat the UI currently does not offer a way to configure this parameter.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a060baee83f9be2402cb1a48b0ff2126d8938b56","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","Team:Entity Analytics","backport:version","v8.18.0"],"title":"[Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints","number":208201,"url":"https://github.com/elastic/kibana/pull/208201","mergeCommit":{"message":"[Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints (#208201)\n\n## Summary\n\nThis PR introduces support for configuring the `timestamp` field for\nentity store enablement.\n\nBy default, the `timestamp` field is set to `@timestamp`, but users can\nopt to use `event.ingested` or another preferred value based on their\nrequirements.\n\n\n### Entity Store API changes\n\n#### Entity Store enable\n\n```\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n```\n\n#### Result \n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n```\nPOST kbn:/api/entity_store/enable\n{\n}\n```\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\nDifferent entity types can have distinct `timestampField` values, as\ndescribed below:\n\nFor instance, the `host` entity uses `event.ingested` as its\n`timestampField`, while other entities default to the `@timestamp`\nfield.\n\n```\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n### Testing steps\n\n- Check out this PR branch.\n- Start Kibana.\n- Avoid enabling the Entity Store from the UI initially. Instead, enable\nit via the API by following the steps outlined below.\n\n```\nDELETE kbn:/api/entity_store/engines/user\nDELETE kbn:/api/entity_store/engines/host\n\nGET kbn:/api/entity_store/status\n\n All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n\n# All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n}\n\n# Different entity with different timestamp Field\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n4. Afterward, you can test the functionality through the UI. First,\nclear the entity data from the UI, then start the Entity Store. Note\nthat the UI currently does not offer a way to configure this parameter.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a060baee83f9be2402cb1a48b0ff2126d8938b56"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208201","number":208201,"mergeCommit":{"message":"[Entity Analytics] [Entity Store] [API] Changes to support event.ingested as a configurable timestamp field for init and enable endpoints (#208201)\n\n## Summary\n\nThis PR introduces support for configuring the `timestamp` field for\nentity store enablement.\n\nBy default, the `timestamp` field is set to `@timestamp`, but users can\nopt to use `event.ingested` or another preferred value based on their\nrequirements.\n\n\n### Entity Store API changes\n\n#### Entity Store enable\n\n```\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n```\n\n#### Result \n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n```\nPOST kbn:/api/entity_store/enable\n{\n}\n```\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\nDifferent entity types can have distinct `timestampField` values, as\ndescribed below:\n\nFor instance, the `host` entity uses `event.ingested` as its\n`timestampField`, while other entities default to the `@timestamp`\nfield.\n\n```\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n#### Result\n\n```\n{\n \"engines\": [\n {\n \"status\": \"started\",\n \"type\": \"universal\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n },\n {\n \"status\": \"started\",\n \"type\": \"host\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"event.ingested\"\n },\n {\n \"status\": \"started\",\n \"type\": \"user\",\n \"indexPattern\": \"\",\n \"filter\": \"\",\n \"fieldHistoryLength\": 10,\n \"timestampField\": \"@timestamp\"\n }\n ],\n \"status\": \"running\"\n}\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n### Testing steps\n\n- Check out this PR branch.\n- Start Kibana.\n- Avoid enabling the Entity Store from the UI initially. Instead, enable\nit via the API by following the steps outlined below.\n\n```\nDELETE kbn:/api/entity_store/engines/user\nDELETE kbn:/api/entity_store/engines/host\n\nGET kbn:/api/entity_store/status\n\n All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n \"timestampField\": \"event.ingested\"\n}\n\n# All engines with the same timestamp Field\nPOST kbn:/api/entity_store/enable\n{\n}\n\n# Different entity with different timestamp Field\nPOST kbn:/api/entity_store/engines/host/init\n{\n \"timestampField\": \"event.ingested\"\n}\n\nPOST kbn:/api/entity_store/engines/user/init\n{\n}\n```\n\n4. Afterward, you can test the functionality through the UI. First,\nclear the entity data from the UI, then start the Entity Store. Note\nthat the UI currently does not offer a way to configure this parameter.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a060baee83f9be2402cb1a48b0ff2126d8938b56"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
Larry Gregory
|
24f82ee808
|
[8.x] Additional prototype pollution protections (#206073) (#208742)
# Backport This will backport the following commits from `main` to `8.x`: - [Additional prototype pollution protections (#206073)](https://github.com/elastic/kibana/pull/206073) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T22:00:43Z","message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Hardening","v9.0.0","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-elasticsearch","ci:all-gen-ai-suites"],"title":"Additional prototype pollution protections","number":206073,"url":"https://github.com/elastic/kibana/pull/206073","mergeCommit":{"message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206073","number":206073,"mergeCommit":{"message":"Additional prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends the server-side prototype pollution protections introduced in\nhttps://github.com/elastic/kibana/pull/190716 to include\n`Array.prototype`.\n2. Applies the same prototype pollution protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] Sealing prototypes on the client can lead to failures in\nthird-party dependencies. I'm relying on sufficient functional test\ncoverage to detect issues here. As a result, these protections are\ndisabled by default for now, and can be controlled via setting\n`server.prototypeHardening: true/false`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
7dc27d0f2b
|
[8.x] [scout] custom logger + clients as singleton (#208435) (#208779)
# Backport This will backport the following commits from `main` to `8.x`: - [[scout] custom logger + clients as singleton (#208435)](https://github.com/elastic/kibana/pull/208435) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T15:20:43Z","message":"[scout] custom logger + clients as singleton (#208435)\n\n## Summary\r\n\r\nAdding custom `ScoutLogger` class to use across its services so that we\r\ncan better read logs related only to test framework runner.\r\nWe can also later migrate from `ToolingLog` to something better\r\nintegrated with Playwright to unify logs from different levels\r\nhttps://github.com/elastic/kibana/issues/203591\r\n\r\nTo make sure we use the same instance, I converted few core services\r\n(logger, kbnClient, esClient, esArchiver) to singletons.\r\n\r\n\r\nLog output example:\r\n\r\n```\r\nRunning 1 test using 1 worker\r\n\r\n› should allow removing the dashboard panel after the underlying saved search has been deleted @svlSecurity @svlOblt @svlSearch @ess\r\n debg [scout] [service] logger\r\n info [scout] [config] Reading test servers confiuration from file: /Users/dmle/github/kibana/.scout/servers/local.json\r\n debg [scout] [service] config\r\n debg [scout] [service] esClient\r\n debg [scout] [service] kbnClient\r\n debg [scout] [service] esArchiver\r\n debg [scout] [service] uiSettings\r\n debg [scout] Requesting url (redacted): [http://localhost:5620/api/status]\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"mappings.json\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"data.json.gz\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.22\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.20\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.21\"\r\n```","sha":"38fc6344c60a87a9ec275ba5f0d3b187a3513e58","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","test:scout"],"title":"[scout] custom logger + clients as singleton","number":208435,"url":"https://github.com/elastic/kibana/pull/208435","mergeCommit":{"message":"[scout] custom logger + clients as singleton (#208435)\n\n## Summary\r\n\r\nAdding custom `ScoutLogger` class to use across its services so that we\r\ncan better read logs related only to test framework runner.\r\nWe can also later migrate from `ToolingLog` to something better\r\nintegrated with Playwright to unify logs from different levels\r\nhttps://github.com/elastic/kibana/issues/203591\r\n\r\nTo make sure we use the same instance, I converted few core services\r\n(logger, kbnClient, esClient, esArchiver) to singletons.\r\n\r\n\r\nLog output example:\r\n\r\n```\r\nRunning 1 test using 1 worker\r\n\r\n› should allow removing the dashboard panel after the underlying saved search has been deleted @svlSecurity @svlOblt @svlSearch @ess\r\n debg [scout] [service] logger\r\n info [scout] [config] Reading test servers confiuration from file: /Users/dmle/github/kibana/.scout/servers/local.json\r\n debg [scout] [service] config\r\n debg [scout] [service] esClient\r\n debg [scout] [service] kbnClient\r\n debg [scout] [service] esArchiver\r\n debg [scout] [service] uiSettings\r\n debg [scout] Requesting url (redacted): [http://localhost:5620/api/status]\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"mappings.json\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"data.json.gz\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.22\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.20\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.21\"\r\n```","sha":"38fc6344c60a87a9ec275ba5f0d3b187a3513e58"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208435","number":208435,"mergeCommit":{"message":"[scout] custom logger + clients as singleton (#208435)\n\n## Summary\r\n\r\nAdding custom `ScoutLogger` class to use across its services so that we\r\ncan better read logs related only to test framework runner.\r\nWe can also later migrate from `ToolingLog` to something better\r\nintegrated with Playwright to unify logs from different levels\r\nhttps://github.com/elastic/kibana/issues/203591\r\n\r\nTo make sure we use the same instance, I converted few core services\r\n(logger, kbnClient, esClient, esArchiver) to singletons.\r\n\r\n\r\nLog output example:\r\n\r\n```\r\nRunning 1 test using 1 worker\r\n\r\n› should allow removing the dashboard panel after the underlying saved search has been deleted @svlSecurity @svlOblt @svlSearch @ess\r\n debg [scout] [service] logger\r\n info [scout] [config] Reading test servers confiuration from file: /Users/dmle/github/kibana/.scout/servers/local.json\r\n debg [scout] [service] config\r\n debg [scout] [service] esClient\r\n debg [scout] [service] kbnClient\r\n debg [scout] [service] esArchiver\r\n debg [scout] [service] uiSettings\r\n debg [scout] Requesting url (redacted): [http://localhost:5620/api/status]\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"mappings.json\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Loading \"data.json.gz\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.22\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.20\"\r\n info [scout] [x-pack/test/functional/es_archives/logstash_functional] Skipped restore for existing index \"logstash-2015.09.21\"\r\n```","sha":"38fc6344c60a87a9ec275ba5f0d3b187a3513e58"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Gerard Soldevila
|
28ca7d52d3
|
[8.x] SKA: Relocate core mock and test-helper modules (#208538) (#208725)
# Backport This will backport the following commits from `main` to `8.x`: - [SKA: Relocate core mock and test-helper modules (#208538)](https://github.com/elastic/kibana/pull/208538) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T11:14:44Z","message":"SKA: Relocate core mock and test-helper modules (#208538)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 55 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/core-analytics-browser-mocks` |\r\n`src/core/packages/analytics/browser-mocks` |\r\n| `@kbn/core-analytics-server-mocks` |\r\n`src/core/packages/analytics/server-mocks` |\r\n| `@kbn/core-application-browser-mocks` |\r\n`src/core/packages/application/browser-mocks` |\r\n| `@kbn/core-apps-browser-mocks` |\r\n`src/core/packages/apps/browser-mocks` |\r\n| `@kbn/core-base-browser-mocks` |\r\n`src/core/packages/base/browser-mocks` |\r\n| `@kbn/core-base-server-mocks` | `src/core/packages/base/server-mocks`\r\n|\r\n| `@kbn/core-capabilities-browser-mocks` |\r\n`src/core/packages/capabilities/browser-mocks` |\r\n| `@kbn/core-capabilities-server-mocks` |\r\n`src/core/packages/capabilities/server-mocks` |\r\n| `@kbn/core-chrome-browser-mocks` |\r\n`src/core/packages/chrome/browser-mocks` |\r\n| `@kbn/core-deprecations-browser-mocks` |\r\n`src/core/packages/deprecations/browser-mocks` |\r\n| `@kbn/core-deprecations-server-mocks` |\r\n`src/core/packages/deprecations/server-mocks` |\r\n| `@kbn/core-doc-links-browser-mocks` |\r\n`src/core/packages/doc-links/browser-mocks` |\r\n| `@kbn/core-doc-links-server-mocks` |\r\n`src/core/packages/doc-links/server-mocks` |\r\n| `@kbn/core-elasticsearch-client-server-mocks` |\r\n`src/core/packages/elasticsearch/client-server-mocks` |\r\n| `@kbn/core-elasticsearch-server-mocks` |\r\n`src/core/packages/elasticsearch/server-mocks` |\r\n| `@kbn/core-environment-server-mocks` |\r\n`src/core/packages/environment/server-mocks` |\r\n| `@kbn/core-execution-context-browser-mocks` |\r\n`src/core/packages/execution-context/browser-mocks` |\r\n| `@kbn/core-execution-context-server-mocks` |\r\n`src/core/packages/execution-context/server-mocks` |\r\n| `@kbn/core-fatal-errors-browser-mocks` |\r\n`src/core/packages/fatal-errors/browser-mocks` |\r\n| `@kbn/core-http-browser-mocks` |\r\n`src/core/packages/http/browser-mocks` |\r\n| `@kbn/core-http-context-server-mocks` |\r\n`src/core/packages/http/context-server-mocks` |\r\n| `@kbn/core-http-resources-server-mocks` |\r\n`src/core/packages/http/resources-server-mocks` |\r\n| `@kbn/core-http-router-server-mocks` |\r\n`src/core/packages/http/router-server-mocks` |\r\n| `@kbn/core-http-server-mocks` | `src/core/packages/http/server-mocks`\r\n|\r\n| `@kbn/core-i18n-browser-mocks` |\r\n`src/core/packages/i18n/browser-mocks` |\r\n| `@kbn/core-i18n-server-mocks` | `src/core/packages/i18n/server-mocks`\r\n|\r\n| `@kbn/core-injected-metadata-browser-mocks` |\r\n`src/core/packages/injected-metadata/browser-mocks` |\r\n| `@kbn/core-integrations-browser-mocks` |\r\n`src/core/packages/integrations/browser-mocks` |\r\n| `@kbn/core-lifecycle-browser-mocks` |\r\n`src/core/packages/lifecycle/browser-mocks` |\r\n| `@kbn/core-lifecycle-server-mocks` |\r\n`src/core/packages/lifecycle/server-mocks` |\r\n| `@kbn/core-logging-browser-mocks` |\r\n`src/core/packages/logging/browser-mocks` |\r\n| `@kbn/core-logging-server-mocks` |\r\n`src/core/packages/logging/server-mocks` |\r\n| `@kbn/core-metrics-collectors-server-mocks` |\r\n`src/core/packages/metrics/collectors-server-mocks` |\r\n| `@kbn/core-metrics-server-mocks` |\r\n`src/core/packages/metrics/server-mocks` |\r\n| `@kbn/core-node-server-mocks` | `src/core/packages/node/server-mocks`\r\n|\r\n| `@kbn/core-notifications-browser-mocks` |\r\n`src/core/packages/notifications/browser-mocks` |\r\n| `@kbn/core-overlays-browser-mocks` |\r\n`src/core/packages/overlays/browser-mocks` |\r\n| `@kbn/core-plugins-browser-mocks` |\r\n`src/core/packages/plugins/browser-mocks` |\r\n| `@kbn/core-plugins-server-mocks` |\r\n`src/core/packages/plugins/server-mocks` |\r\n| `@kbn/core-preboot-server-mocks` |\r\n`src/core/packages/preboot/server-mocks` |\r\n| `@kbn/core-rendering-browser-mocks` |\r\n`src/core/packages/rendering/browser-mocks` |\r\n| `@kbn/core-rendering-server-mocks` |\r\n`src/core/packages/rendering/server-mocks` |\r\n| `@kbn/core-saved-objects-api-server-mocks` |\r\n`src/core/packages/saved-objects/api-server-mocks` |\r\n| `@kbn/core-saved-objects-base-server-mocks` |\r\n`src/core/packages/saved-objects/base-server-mocks` |\r\n| `@kbn/core-saved-objects-browser-mocks` |\r\n`src/core/packages/saved-objects/browser-mocks` |\r\n| `@kbn/core-saved-objects-import-export-server-mocks` |\r\n`src/core/packages/saved-objects/import-export-server-mocks` |\r\n| `@kbn/core-saved-objects-migration-server-mocks` |\r\n`src/core/packages/saved-objects/migration-server-mocks` |\r\n| `@kbn/core-saved-objects-server-mocks` |\r\n`src/core/packages/saved-objects/server-mocks` |\r\n| `@kbn/core-status-server-mocks` |\r\n`src/core/packages/status/server-mocks` |\r\n| `@kbn/core-test-helpers-kbn-server` |\r\n`src/dev/packages/core-test-helpers-kbn-server` |\r\n| `@kbn/core-test-helpers-model-versions` |\r\n`src/dev/packages/core-test-helpers-model-versions` |\r\n| `@kbn/core-theme-browser-mocks` |\r\n`src/core/packages/theme/browser-mocks` |\r\n| `@kbn/core-ui-settings-browser-mocks` |\r\n`src/core/packages/ui-settings/browser-mocks` |\r\n| `@kbn/core-ui-settings-server-mocks` |\r\n`src/core/packages/ui-settings/server-mocks` |\r\n| `@kbn/core-usage-data-server-mocks` |\r\n`src/core/packages/usage-data/server-mocks` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.github/codeql/codeql-config.yml\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/core/packages/analytics/browser-mocks/jest.config.js\r\n./src/core/packages/analytics/server-mocks/jest.config.js\r\n./src/core/packages/application/browser-mocks/jest.config.js\r\n./src/core/packages/apps/browser-mocks/jest.config.js\r\n./src/core/packages/base/browser-mocks/jest.config.js\r\n./src/core/packages/base/server-mocks/jest.config.js\r\n./src/core/packages/capabilities/browser-mocks/jest.config.js\r\n./src/core/packages/capabilities/server-mocks/jest.config.js\r\n./src/core/packages/chrome/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/server-mocks/jest.config.js\r\n./src/core/packages/doc-links/browser-mocks/jest.config.js\r\n./src/core/packages/doc-links/server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/client-server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/server-mocks/jest.config.js\r\n./src/core/packages/environment/server-mocks/jest.config.js\r\n./src/core/packages/execution-context/browser-mocks/jest.config.js\r\n./src/core/packages/execution-context/server-mocks/jest.config.js\r\n./src/core/packages/fatal-errors/browser-mocks/jest.config.js\r\n./src/core/packages/http/browser-mocks/jest.config.js\r\n./src/core/packages/http/context-server-mocks/jest.config.js\r\n./src/core/packages/http/resources-server-mocks/jest.config.js\r\n./src/core/packages/http/router-server-mocks/jest.config.js\r\n./src/core/packages/http/server-mocks/jest.config.js\r\n./src/core/packages/i18n/browser-mocks/jest.config.js\r\n./src/core/packages/i18n/server-mocks/jest.config.js\r\n./src/core/packages/injected-metadata/browser-mocks/jest.config.js\r\n./src/core/packages/integrations/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/server-mocks/jest.config.js\r\n./src/core/packages/logging/browser-mocks/jest.config.js\r\n./src/core/packages/logging/server-mocks/jest.config.js\r\n./src/core/packages/metrics/collectors-server-mocks/jest.config.js\r\n./src/core/packages/metrics/server-mocks/jest.config.js\r\n./src/core/packages/node/server-mocks/jest.config.js\r\n./src/core/packages/notifications/browser-mocks/jest.config.js\r\n./src/core/packages/overlays/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/server-mocks/jest.config.js\r\n./src/core/packages/preboot/server-mocks/jest.config.js\r\n./src/core/packages/rendering/browser-mocks/jest.config.js\r\n./src/core/packages/rendering/server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/api-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/base-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/browser-mocks/jest.config.js\r\n./src/core/packages/saved-objects/import-export-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/migration-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/server-mocks/jest.config.js\r\n./src/core/packages/status/server-mocks/jest.config.js\r\n./src/core/packages/theme/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/server-mocks/jest.config.js\r\n./src/core/packages/usage-data/server-mocks/jest.config.js\r\n./src/core/system/tsconfig.type_check.json\r\n./src/dev/packages/core-test-helpers-kbn-server/jest.config.js\r\n./src/dev/packages/core-test-helpers-model-versions/jest.config.js\r\n./src/dev/tsconfig.type_check.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/plugins/private/interactive_setup/tsconfig.type_check.json\r\n./src/platform/plugins/shared/console/tsconfig.type_check.json\r\n./src/plugins/kibana_usage_collection/tsconfig.type_check.json\r\n./src/plugins/saved_objects_management/tsconfig.type_check.json\r\n./src/plugins/telemetry/tsconfig.type_check.json\r\n./src/plugins/usage_collection/tsconfig.type_check.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/platform/plugins/private/index_lifecycle_management/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/remote_clusters/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/snapshot_restore/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/watcher/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/encrypted_saved_objects/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/fleet/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/security/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/spaces/tsconfig.type_check.json\r\n./x-pack/plugins/actions/tsconfig.type_check.json\r\n./x-pack/plugins/aiops/tsconfig.type_check.json\r\n./x-pack/plugins/alerting/tsconfig.type_check.json\r\n./x-pack/plugins/cases/tsconfig.type_check.json\r\n./x-pack/plugins/enterprise_search/tsconfig.type_check.json\r\n./x-pack/plugins/integration_assistant/tsconfig.type_check.json\r\n./x-pack/plugins/ml/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm_data_access/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/entity_manager/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/exploratory_view/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/observability/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/slo/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/synthetics/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/uptime/tsconfig.type_check.json\r\n./x-pack/plugins/rule_registry/tsconfig.type_check.json\r\n./x-pack/plugins/search_playground/tsconfig.type_check.json\r\n./x-pack/plugins/serverless_search/tsconfig.type_check.json\r\n./x-pack/plugins/stack_alerts/tsconfig.type_check.json\r\n./x-pack/plugins/stack_connectors/tsconfig.type_check.json\r\n./x-pack/plugins/task_manager/tsconfig.type_check.json\r\n./x-pack/plugins/transform/tsconfig.type_check.json\r\n./x-pack/solutions/observability/plugins/dataset_quality/tsconfig.type_check.json\r\n./x-pack/solutions/security/packages/security-solution/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./x-pack/solutions/security/plugins/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/core/packages/analytics/browser-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/analytics/server-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/application/browser-mocks/jest.config.js:12\r\nsrc/core/packages/application/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/apps/browser-mocks/jest.config.js:12\r\nsrc/core/packages/apps/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/browser-mocks/jest.config.js:12\r\nsrc/core/packages/base/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/server-mocks/jest.config.js:12\r\nsrc/core/packages/base/server-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/browser-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/server-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/server-mocks/tsconfig.json:2\r\nsrc/core/packages/chrome/browser-mocks/jest.config.js:12\r\nsrc/core/packages/chrome/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/server-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/server-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/browser-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/server-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/client-server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/client-server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/server-mocks/tsconfig.json:2\r\nsrc/core/packages/environment/server-mocks/jest.config.js:12\r\nsrc/core/packages/environment/server-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/browser-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/server-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/server-mocks/tsconfig.json:2\r\nsrc/core/packages/fatal-errors/browser-mocks/jest.config.js:12\r\nsrc/core/packages/fatal-errors/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/browser-mocks/jest.config.js:12\r\nsrc/core/packages/http/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/context-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/context-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/resources-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/resources-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/router-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/router-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/server-mocks/jest.config.js:12\r\nsrc/core/packages/http/server-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/browser-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/server-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/server-mocks/tsconfig.json:2\r\nsrc/core/packages/injected-metadata/browser-mocks/jest.config.js:12\r\nsrc/core/packages/injected-metadata/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/integrations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/integrations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/browser-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/server-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/server-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/browser-mocks/jest.config.js:12\r\nsrc/core/packages/logging/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/server-mocks/jest.config.js:12\r\nsrc/core/packages/logging/server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/collectors-server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/collectors-server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/node/server-mocks/jest.config.js:12\r\nsrc/core/packages/node/server-mocks/tsconfig.json:2\r\nsrc/core/packages/notifications/browser-mocks/jest.config.js:12\r\nsrc/core/packages/notifications/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/overlays/browser-mocks/jest.config.js:12\r\nsrc/core/packages/overlays/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/browser-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/server-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/server-mocks/tsconfig.json:2\r\nsrc/core/packages/preboot/server-mocks/jest.config.js:12\r\nsrc/core/packages/preboot/server-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/browser-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/server-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/api-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/api-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/base-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/base-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/browser-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/import-export-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/import-export-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/migration-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/migration-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/server-mocks/tsconfig.json:2\r\nsrc/core/packages/status/server-mocks/jest.config.js:12\r\nsrc/core/packages/status/server-mocks/tsconfig.json:2\r\nsrc/core/packages/theme/browser-mocks/jest.config.js:12\r\nsrc/core/packages/theme/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/browser-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/server-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/server-mocks/tsconfig.json:2\r\nsrc/core/packages/usage-data/server-mocks/jest.config.js:12\r\nsrc/core/packages/usage-data/server-mocks/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-kbn-server/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-kbn-server/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-model-versions/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-model-versions/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"4a00449bdcd699f89294536a86dffcbeab4daf53","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"SKA: Relocate core mock and test-helper modules","number":208538,"url":"https://github.com/elastic/kibana/pull/208538","mergeCommit":{"message":"SKA: Relocate core mock and test-helper modules (#208538)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 55 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/core-analytics-browser-mocks` |\r\n`src/core/packages/analytics/browser-mocks` |\r\n| `@kbn/core-analytics-server-mocks` |\r\n`src/core/packages/analytics/server-mocks` |\r\n| `@kbn/core-application-browser-mocks` |\r\n`src/core/packages/application/browser-mocks` |\r\n| `@kbn/core-apps-browser-mocks` |\r\n`src/core/packages/apps/browser-mocks` |\r\n| `@kbn/core-base-browser-mocks` |\r\n`src/core/packages/base/browser-mocks` |\r\n| `@kbn/core-base-server-mocks` | `src/core/packages/base/server-mocks`\r\n|\r\n| `@kbn/core-capabilities-browser-mocks` |\r\n`src/core/packages/capabilities/browser-mocks` |\r\n| `@kbn/core-capabilities-server-mocks` |\r\n`src/core/packages/capabilities/server-mocks` |\r\n| `@kbn/core-chrome-browser-mocks` |\r\n`src/core/packages/chrome/browser-mocks` |\r\n| `@kbn/core-deprecations-browser-mocks` |\r\n`src/core/packages/deprecations/browser-mocks` |\r\n| `@kbn/core-deprecations-server-mocks` |\r\n`src/core/packages/deprecations/server-mocks` |\r\n| `@kbn/core-doc-links-browser-mocks` |\r\n`src/core/packages/doc-links/browser-mocks` |\r\n| `@kbn/core-doc-links-server-mocks` |\r\n`src/core/packages/doc-links/server-mocks` |\r\n| `@kbn/core-elasticsearch-client-server-mocks` |\r\n`src/core/packages/elasticsearch/client-server-mocks` |\r\n| `@kbn/core-elasticsearch-server-mocks` |\r\n`src/core/packages/elasticsearch/server-mocks` |\r\n| `@kbn/core-environment-server-mocks` |\r\n`src/core/packages/environment/server-mocks` |\r\n| `@kbn/core-execution-context-browser-mocks` |\r\n`src/core/packages/execution-context/browser-mocks` |\r\n| `@kbn/core-execution-context-server-mocks` |\r\n`src/core/packages/execution-context/server-mocks` |\r\n| `@kbn/core-fatal-errors-browser-mocks` |\r\n`src/core/packages/fatal-errors/browser-mocks` |\r\n| `@kbn/core-http-browser-mocks` |\r\n`src/core/packages/http/browser-mocks` |\r\n| `@kbn/core-http-context-server-mocks` |\r\n`src/core/packages/http/context-server-mocks` |\r\n| `@kbn/core-http-resources-server-mocks` |\r\n`src/core/packages/http/resources-server-mocks` |\r\n| `@kbn/core-http-router-server-mocks` |\r\n`src/core/packages/http/router-server-mocks` |\r\n| `@kbn/core-http-server-mocks` | `src/core/packages/http/server-mocks`\r\n|\r\n| `@kbn/core-i18n-browser-mocks` |\r\n`src/core/packages/i18n/browser-mocks` |\r\n| `@kbn/core-i18n-server-mocks` | `src/core/packages/i18n/server-mocks`\r\n|\r\n| `@kbn/core-injected-metadata-browser-mocks` |\r\n`src/core/packages/injected-metadata/browser-mocks` |\r\n| `@kbn/core-integrations-browser-mocks` |\r\n`src/core/packages/integrations/browser-mocks` |\r\n| `@kbn/core-lifecycle-browser-mocks` |\r\n`src/core/packages/lifecycle/browser-mocks` |\r\n| `@kbn/core-lifecycle-server-mocks` |\r\n`src/core/packages/lifecycle/server-mocks` |\r\n| `@kbn/core-logging-browser-mocks` |\r\n`src/core/packages/logging/browser-mocks` |\r\n| `@kbn/core-logging-server-mocks` |\r\n`src/core/packages/logging/server-mocks` |\r\n| `@kbn/core-metrics-collectors-server-mocks` |\r\n`src/core/packages/metrics/collectors-server-mocks` |\r\n| `@kbn/core-metrics-server-mocks` |\r\n`src/core/packages/metrics/server-mocks` |\r\n| `@kbn/core-node-server-mocks` | `src/core/packages/node/server-mocks`\r\n|\r\n| `@kbn/core-notifications-browser-mocks` |\r\n`src/core/packages/notifications/browser-mocks` |\r\n| `@kbn/core-overlays-browser-mocks` |\r\n`src/core/packages/overlays/browser-mocks` |\r\n| `@kbn/core-plugins-browser-mocks` |\r\n`src/core/packages/plugins/browser-mocks` |\r\n| `@kbn/core-plugins-server-mocks` |\r\n`src/core/packages/plugins/server-mocks` |\r\n| `@kbn/core-preboot-server-mocks` |\r\n`src/core/packages/preboot/server-mocks` |\r\n| `@kbn/core-rendering-browser-mocks` |\r\n`src/core/packages/rendering/browser-mocks` |\r\n| `@kbn/core-rendering-server-mocks` |\r\n`src/core/packages/rendering/server-mocks` |\r\n| `@kbn/core-saved-objects-api-server-mocks` |\r\n`src/core/packages/saved-objects/api-server-mocks` |\r\n| `@kbn/core-saved-objects-base-server-mocks` |\r\n`src/core/packages/saved-objects/base-server-mocks` |\r\n| `@kbn/core-saved-objects-browser-mocks` |\r\n`src/core/packages/saved-objects/browser-mocks` |\r\n| `@kbn/core-saved-objects-import-export-server-mocks` |\r\n`src/core/packages/saved-objects/import-export-server-mocks` |\r\n| `@kbn/core-saved-objects-migration-server-mocks` |\r\n`src/core/packages/saved-objects/migration-server-mocks` |\r\n| `@kbn/core-saved-objects-server-mocks` |\r\n`src/core/packages/saved-objects/server-mocks` |\r\n| `@kbn/core-status-server-mocks` |\r\n`src/core/packages/status/server-mocks` |\r\n| `@kbn/core-test-helpers-kbn-server` |\r\n`src/dev/packages/core-test-helpers-kbn-server` |\r\n| `@kbn/core-test-helpers-model-versions` |\r\n`src/dev/packages/core-test-helpers-model-versions` |\r\n| `@kbn/core-theme-browser-mocks` |\r\n`src/core/packages/theme/browser-mocks` |\r\n| `@kbn/core-ui-settings-browser-mocks` |\r\n`src/core/packages/ui-settings/browser-mocks` |\r\n| `@kbn/core-ui-settings-server-mocks` |\r\n`src/core/packages/ui-settings/server-mocks` |\r\n| `@kbn/core-usage-data-server-mocks` |\r\n`src/core/packages/usage-data/server-mocks` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.github/codeql/codeql-config.yml\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/core/packages/analytics/browser-mocks/jest.config.js\r\n./src/core/packages/analytics/server-mocks/jest.config.js\r\n./src/core/packages/application/browser-mocks/jest.config.js\r\n./src/core/packages/apps/browser-mocks/jest.config.js\r\n./src/core/packages/base/browser-mocks/jest.config.js\r\n./src/core/packages/base/server-mocks/jest.config.js\r\n./src/core/packages/capabilities/browser-mocks/jest.config.js\r\n./src/core/packages/capabilities/server-mocks/jest.config.js\r\n./src/core/packages/chrome/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/server-mocks/jest.config.js\r\n./src/core/packages/doc-links/browser-mocks/jest.config.js\r\n./src/core/packages/doc-links/server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/client-server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/server-mocks/jest.config.js\r\n./src/core/packages/environment/server-mocks/jest.config.js\r\n./src/core/packages/execution-context/browser-mocks/jest.config.js\r\n./src/core/packages/execution-context/server-mocks/jest.config.js\r\n./src/core/packages/fatal-errors/browser-mocks/jest.config.js\r\n./src/core/packages/http/browser-mocks/jest.config.js\r\n./src/core/packages/http/context-server-mocks/jest.config.js\r\n./src/core/packages/http/resources-server-mocks/jest.config.js\r\n./src/core/packages/http/router-server-mocks/jest.config.js\r\n./src/core/packages/http/server-mocks/jest.config.js\r\n./src/core/packages/i18n/browser-mocks/jest.config.js\r\n./src/core/packages/i18n/server-mocks/jest.config.js\r\n./src/core/packages/injected-metadata/browser-mocks/jest.config.js\r\n./src/core/packages/integrations/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/server-mocks/jest.config.js\r\n./src/core/packages/logging/browser-mocks/jest.config.js\r\n./src/core/packages/logging/server-mocks/jest.config.js\r\n./src/core/packages/metrics/collectors-server-mocks/jest.config.js\r\n./src/core/packages/metrics/server-mocks/jest.config.js\r\n./src/core/packages/node/server-mocks/jest.config.js\r\n./src/core/packages/notifications/browser-mocks/jest.config.js\r\n./src/core/packages/overlays/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/server-mocks/jest.config.js\r\n./src/core/packages/preboot/server-mocks/jest.config.js\r\n./src/core/packages/rendering/browser-mocks/jest.config.js\r\n./src/core/packages/rendering/server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/api-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/base-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/browser-mocks/jest.config.js\r\n./src/core/packages/saved-objects/import-export-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/migration-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/server-mocks/jest.config.js\r\n./src/core/packages/status/server-mocks/jest.config.js\r\n./src/core/packages/theme/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/server-mocks/jest.config.js\r\n./src/core/packages/usage-data/server-mocks/jest.config.js\r\n./src/core/system/tsconfig.type_check.json\r\n./src/dev/packages/core-test-helpers-kbn-server/jest.config.js\r\n./src/dev/packages/core-test-helpers-model-versions/jest.config.js\r\n./src/dev/tsconfig.type_check.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/plugins/private/interactive_setup/tsconfig.type_check.json\r\n./src/platform/plugins/shared/console/tsconfig.type_check.json\r\n./src/plugins/kibana_usage_collection/tsconfig.type_check.json\r\n./src/plugins/saved_objects_management/tsconfig.type_check.json\r\n./src/plugins/telemetry/tsconfig.type_check.json\r\n./src/plugins/usage_collection/tsconfig.type_check.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/platform/plugins/private/index_lifecycle_management/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/remote_clusters/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/snapshot_restore/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/watcher/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/encrypted_saved_objects/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/fleet/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/security/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/spaces/tsconfig.type_check.json\r\n./x-pack/plugins/actions/tsconfig.type_check.json\r\n./x-pack/plugins/aiops/tsconfig.type_check.json\r\n./x-pack/plugins/alerting/tsconfig.type_check.json\r\n./x-pack/plugins/cases/tsconfig.type_check.json\r\n./x-pack/plugins/enterprise_search/tsconfig.type_check.json\r\n./x-pack/plugins/integration_assistant/tsconfig.type_check.json\r\n./x-pack/plugins/ml/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm_data_access/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/entity_manager/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/exploratory_view/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/observability/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/slo/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/synthetics/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/uptime/tsconfig.type_check.json\r\n./x-pack/plugins/rule_registry/tsconfig.type_check.json\r\n./x-pack/plugins/search_playground/tsconfig.type_check.json\r\n./x-pack/plugins/serverless_search/tsconfig.type_check.json\r\n./x-pack/plugins/stack_alerts/tsconfig.type_check.json\r\n./x-pack/plugins/stack_connectors/tsconfig.type_check.json\r\n./x-pack/plugins/task_manager/tsconfig.type_check.json\r\n./x-pack/plugins/transform/tsconfig.type_check.json\r\n./x-pack/solutions/observability/plugins/dataset_quality/tsconfig.type_check.json\r\n./x-pack/solutions/security/packages/security-solution/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./x-pack/solutions/security/plugins/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/core/packages/analytics/browser-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/analytics/server-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/application/browser-mocks/jest.config.js:12\r\nsrc/core/packages/application/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/apps/browser-mocks/jest.config.js:12\r\nsrc/core/packages/apps/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/browser-mocks/jest.config.js:12\r\nsrc/core/packages/base/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/server-mocks/jest.config.js:12\r\nsrc/core/packages/base/server-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/browser-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/server-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/server-mocks/tsconfig.json:2\r\nsrc/core/packages/chrome/browser-mocks/jest.config.js:12\r\nsrc/core/packages/chrome/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/server-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/server-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/browser-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/server-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/client-server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/client-server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/server-mocks/tsconfig.json:2\r\nsrc/core/packages/environment/server-mocks/jest.config.js:12\r\nsrc/core/packages/environment/server-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/browser-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/server-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/server-mocks/tsconfig.json:2\r\nsrc/core/packages/fatal-errors/browser-mocks/jest.config.js:12\r\nsrc/core/packages/fatal-errors/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/browser-mocks/jest.config.js:12\r\nsrc/core/packages/http/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/context-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/context-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/resources-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/resources-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/router-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/router-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/server-mocks/jest.config.js:12\r\nsrc/core/packages/http/server-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/browser-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/server-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/server-mocks/tsconfig.json:2\r\nsrc/core/packages/injected-metadata/browser-mocks/jest.config.js:12\r\nsrc/core/packages/injected-metadata/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/integrations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/integrations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/browser-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/server-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/server-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/browser-mocks/jest.config.js:12\r\nsrc/core/packages/logging/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/server-mocks/jest.config.js:12\r\nsrc/core/packages/logging/server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/collectors-server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/collectors-server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/node/server-mocks/jest.config.js:12\r\nsrc/core/packages/node/server-mocks/tsconfig.json:2\r\nsrc/core/packages/notifications/browser-mocks/jest.config.js:12\r\nsrc/core/packages/notifications/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/overlays/browser-mocks/jest.config.js:12\r\nsrc/core/packages/overlays/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/browser-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/server-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/server-mocks/tsconfig.json:2\r\nsrc/core/packages/preboot/server-mocks/jest.config.js:12\r\nsrc/core/packages/preboot/server-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/browser-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/server-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/api-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/api-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/base-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/base-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/browser-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/import-export-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/import-export-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/migration-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/migration-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/server-mocks/tsconfig.json:2\r\nsrc/core/packages/status/server-mocks/jest.config.js:12\r\nsrc/core/packages/status/server-mocks/tsconfig.json:2\r\nsrc/core/packages/theme/browser-mocks/jest.config.js:12\r\nsrc/core/packages/theme/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/browser-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/server-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/server-mocks/tsconfig.json:2\r\nsrc/core/packages/usage-data/server-mocks/jest.config.js:12\r\nsrc/core/packages/usage-data/server-mocks/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-kbn-server/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-kbn-server/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-model-versions/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-model-versions/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"4a00449bdcd699f89294536a86dffcbeab4daf53"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208538","number":208538,"mergeCommit":{"message":"SKA: Relocate core mock and test-helper modules (#208538)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 55 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/core-analytics-browser-mocks` |\r\n`src/core/packages/analytics/browser-mocks` |\r\n| `@kbn/core-analytics-server-mocks` |\r\n`src/core/packages/analytics/server-mocks` |\r\n| `@kbn/core-application-browser-mocks` |\r\n`src/core/packages/application/browser-mocks` |\r\n| `@kbn/core-apps-browser-mocks` |\r\n`src/core/packages/apps/browser-mocks` |\r\n| `@kbn/core-base-browser-mocks` |\r\n`src/core/packages/base/browser-mocks` |\r\n| `@kbn/core-base-server-mocks` | `src/core/packages/base/server-mocks`\r\n|\r\n| `@kbn/core-capabilities-browser-mocks` |\r\n`src/core/packages/capabilities/browser-mocks` |\r\n| `@kbn/core-capabilities-server-mocks` |\r\n`src/core/packages/capabilities/server-mocks` |\r\n| `@kbn/core-chrome-browser-mocks` |\r\n`src/core/packages/chrome/browser-mocks` |\r\n| `@kbn/core-deprecations-browser-mocks` |\r\n`src/core/packages/deprecations/browser-mocks` |\r\n| `@kbn/core-deprecations-server-mocks` |\r\n`src/core/packages/deprecations/server-mocks` |\r\n| `@kbn/core-doc-links-browser-mocks` |\r\n`src/core/packages/doc-links/browser-mocks` |\r\n| `@kbn/core-doc-links-server-mocks` |\r\n`src/core/packages/doc-links/server-mocks` |\r\n| `@kbn/core-elasticsearch-client-server-mocks` |\r\n`src/core/packages/elasticsearch/client-server-mocks` |\r\n| `@kbn/core-elasticsearch-server-mocks` |\r\n`src/core/packages/elasticsearch/server-mocks` |\r\n| `@kbn/core-environment-server-mocks` |\r\n`src/core/packages/environment/server-mocks` |\r\n| `@kbn/core-execution-context-browser-mocks` |\r\n`src/core/packages/execution-context/browser-mocks` |\r\n| `@kbn/core-execution-context-server-mocks` |\r\n`src/core/packages/execution-context/server-mocks` |\r\n| `@kbn/core-fatal-errors-browser-mocks` |\r\n`src/core/packages/fatal-errors/browser-mocks` |\r\n| `@kbn/core-http-browser-mocks` |\r\n`src/core/packages/http/browser-mocks` |\r\n| `@kbn/core-http-context-server-mocks` |\r\n`src/core/packages/http/context-server-mocks` |\r\n| `@kbn/core-http-resources-server-mocks` |\r\n`src/core/packages/http/resources-server-mocks` |\r\n| `@kbn/core-http-router-server-mocks` |\r\n`src/core/packages/http/router-server-mocks` |\r\n| `@kbn/core-http-server-mocks` | `src/core/packages/http/server-mocks`\r\n|\r\n| `@kbn/core-i18n-browser-mocks` |\r\n`src/core/packages/i18n/browser-mocks` |\r\n| `@kbn/core-i18n-server-mocks` | `src/core/packages/i18n/server-mocks`\r\n|\r\n| `@kbn/core-injected-metadata-browser-mocks` |\r\n`src/core/packages/injected-metadata/browser-mocks` |\r\n| `@kbn/core-integrations-browser-mocks` |\r\n`src/core/packages/integrations/browser-mocks` |\r\n| `@kbn/core-lifecycle-browser-mocks` |\r\n`src/core/packages/lifecycle/browser-mocks` |\r\n| `@kbn/core-lifecycle-server-mocks` |\r\n`src/core/packages/lifecycle/server-mocks` |\r\n| `@kbn/core-logging-browser-mocks` |\r\n`src/core/packages/logging/browser-mocks` |\r\n| `@kbn/core-logging-server-mocks` |\r\n`src/core/packages/logging/server-mocks` |\r\n| `@kbn/core-metrics-collectors-server-mocks` |\r\n`src/core/packages/metrics/collectors-server-mocks` |\r\n| `@kbn/core-metrics-server-mocks` |\r\n`src/core/packages/metrics/server-mocks` |\r\n| `@kbn/core-node-server-mocks` | `src/core/packages/node/server-mocks`\r\n|\r\n| `@kbn/core-notifications-browser-mocks` |\r\n`src/core/packages/notifications/browser-mocks` |\r\n| `@kbn/core-overlays-browser-mocks` |\r\n`src/core/packages/overlays/browser-mocks` |\r\n| `@kbn/core-plugins-browser-mocks` |\r\n`src/core/packages/plugins/browser-mocks` |\r\n| `@kbn/core-plugins-server-mocks` |\r\n`src/core/packages/plugins/server-mocks` |\r\n| `@kbn/core-preboot-server-mocks` |\r\n`src/core/packages/preboot/server-mocks` |\r\n| `@kbn/core-rendering-browser-mocks` |\r\n`src/core/packages/rendering/browser-mocks` |\r\n| `@kbn/core-rendering-server-mocks` |\r\n`src/core/packages/rendering/server-mocks` |\r\n| `@kbn/core-saved-objects-api-server-mocks` |\r\n`src/core/packages/saved-objects/api-server-mocks` |\r\n| `@kbn/core-saved-objects-base-server-mocks` |\r\n`src/core/packages/saved-objects/base-server-mocks` |\r\n| `@kbn/core-saved-objects-browser-mocks` |\r\n`src/core/packages/saved-objects/browser-mocks` |\r\n| `@kbn/core-saved-objects-import-export-server-mocks` |\r\n`src/core/packages/saved-objects/import-export-server-mocks` |\r\n| `@kbn/core-saved-objects-migration-server-mocks` |\r\n`src/core/packages/saved-objects/migration-server-mocks` |\r\n| `@kbn/core-saved-objects-server-mocks` |\r\n`src/core/packages/saved-objects/server-mocks` |\r\n| `@kbn/core-status-server-mocks` |\r\n`src/core/packages/status/server-mocks` |\r\n| `@kbn/core-test-helpers-kbn-server` |\r\n`src/dev/packages/core-test-helpers-kbn-server` |\r\n| `@kbn/core-test-helpers-model-versions` |\r\n`src/dev/packages/core-test-helpers-model-versions` |\r\n| `@kbn/core-theme-browser-mocks` |\r\n`src/core/packages/theme/browser-mocks` |\r\n| `@kbn/core-ui-settings-browser-mocks` |\r\n`src/core/packages/ui-settings/browser-mocks` |\r\n| `@kbn/core-ui-settings-server-mocks` |\r\n`src/core/packages/ui-settings/server-mocks` |\r\n| `@kbn/core-usage-data-server-mocks` |\r\n`src/core/packages/usage-data/server-mocks` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.github/codeql/codeql-config.yml\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/core/packages/analytics/browser-mocks/jest.config.js\r\n./src/core/packages/analytics/server-mocks/jest.config.js\r\n./src/core/packages/application/browser-mocks/jest.config.js\r\n./src/core/packages/apps/browser-mocks/jest.config.js\r\n./src/core/packages/base/browser-mocks/jest.config.js\r\n./src/core/packages/base/server-mocks/jest.config.js\r\n./src/core/packages/capabilities/browser-mocks/jest.config.js\r\n./src/core/packages/capabilities/server-mocks/jest.config.js\r\n./src/core/packages/chrome/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/browser-mocks/jest.config.js\r\n./src/core/packages/deprecations/server-mocks/jest.config.js\r\n./src/core/packages/doc-links/browser-mocks/jest.config.js\r\n./src/core/packages/doc-links/server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/client-server-mocks/jest.config.js\r\n./src/core/packages/elasticsearch/server-mocks/jest.config.js\r\n./src/core/packages/environment/server-mocks/jest.config.js\r\n./src/core/packages/execution-context/browser-mocks/jest.config.js\r\n./src/core/packages/execution-context/server-mocks/jest.config.js\r\n./src/core/packages/fatal-errors/browser-mocks/jest.config.js\r\n./src/core/packages/http/browser-mocks/jest.config.js\r\n./src/core/packages/http/context-server-mocks/jest.config.js\r\n./src/core/packages/http/resources-server-mocks/jest.config.js\r\n./src/core/packages/http/router-server-mocks/jest.config.js\r\n./src/core/packages/http/server-mocks/jest.config.js\r\n./src/core/packages/i18n/browser-mocks/jest.config.js\r\n./src/core/packages/i18n/server-mocks/jest.config.js\r\n./src/core/packages/injected-metadata/browser-mocks/jest.config.js\r\n./src/core/packages/integrations/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/browser-mocks/jest.config.js\r\n./src/core/packages/lifecycle/server-mocks/jest.config.js\r\n./src/core/packages/logging/browser-mocks/jest.config.js\r\n./src/core/packages/logging/server-mocks/jest.config.js\r\n./src/core/packages/metrics/collectors-server-mocks/jest.config.js\r\n./src/core/packages/metrics/server-mocks/jest.config.js\r\n./src/core/packages/node/server-mocks/jest.config.js\r\n./src/core/packages/notifications/browser-mocks/jest.config.js\r\n./src/core/packages/overlays/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/browser-mocks/jest.config.js\r\n./src/core/packages/plugins/server-mocks/jest.config.js\r\n./src/core/packages/preboot/server-mocks/jest.config.js\r\n./src/core/packages/rendering/browser-mocks/jest.config.js\r\n./src/core/packages/rendering/server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/api-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/base-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/browser-mocks/jest.config.js\r\n./src/core/packages/saved-objects/import-export-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/migration-server-mocks/jest.config.js\r\n./src/core/packages/saved-objects/server-mocks/jest.config.js\r\n./src/core/packages/status/server-mocks/jest.config.js\r\n./src/core/packages/theme/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/browser-mocks/jest.config.js\r\n./src/core/packages/ui-settings/server-mocks/jest.config.js\r\n./src/core/packages/usage-data/server-mocks/jest.config.js\r\n./src/core/system/tsconfig.type_check.json\r\n./src/dev/packages/core-test-helpers-kbn-server/jest.config.js\r\n./src/dev/packages/core-test-helpers-model-versions/jest.config.js\r\n./src/dev/tsconfig.type_check.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/plugins/private/interactive_setup/tsconfig.type_check.json\r\n./src/platform/plugins/shared/console/tsconfig.type_check.json\r\n./src/plugins/kibana_usage_collection/tsconfig.type_check.json\r\n./src/plugins/saved_objects_management/tsconfig.type_check.json\r\n./src/plugins/telemetry/tsconfig.type_check.json\r\n./src/plugins/usage_collection/tsconfig.type_check.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/platform/plugins/private/index_lifecycle_management/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/remote_clusters/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/snapshot_restore/tsconfig.type_check.json\r\n./x-pack/platform/plugins/private/watcher/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/encrypted_saved_objects/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/fleet/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/security/tsconfig.type_check.json\r\n./x-pack/platform/plugins/shared/spaces/tsconfig.type_check.json\r\n./x-pack/plugins/actions/tsconfig.type_check.json\r\n./x-pack/plugins/aiops/tsconfig.type_check.json\r\n./x-pack/plugins/alerting/tsconfig.type_check.json\r\n./x-pack/plugins/cases/tsconfig.type_check.json\r\n./x-pack/plugins/enterprise_search/tsconfig.type_check.json\r\n./x-pack/plugins/integration_assistant/tsconfig.type_check.json\r\n./x-pack/plugins/ml/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/apm_data_access/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/entity_manager/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/exploratory_view/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/observability/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/slo/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/synthetics/tsconfig.type_check.json\r\n./x-pack/plugins/observability_solution/uptime/tsconfig.type_check.json\r\n./x-pack/plugins/rule_registry/tsconfig.type_check.json\r\n./x-pack/plugins/search_playground/tsconfig.type_check.json\r\n./x-pack/plugins/serverless_search/tsconfig.type_check.json\r\n./x-pack/plugins/stack_alerts/tsconfig.type_check.json\r\n./x-pack/plugins/stack_connectors/tsconfig.type_check.json\r\n./x-pack/plugins/task_manager/tsconfig.type_check.json\r\n./x-pack/plugins/transform/tsconfig.type_check.json\r\n./x-pack/solutions/observability/plugins/dataset_quality/tsconfig.type_check.json\r\n./x-pack/solutions/security/packages/security-solution/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./x-pack/solutions/security/plugins/ecs_data_quality_dashboard/tsconfig.type_check.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/core/packages/analytics/browser-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/analytics/server-mocks/jest.config.js:12\r\nsrc/core/packages/analytics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/application/browser-mocks/jest.config.js:12\r\nsrc/core/packages/application/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/apps/browser-mocks/jest.config.js:12\r\nsrc/core/packages/apps/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/browser-mocks/jest.config.js:12\r\nsrc/core/packages/base/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/base/server-mocks/jest.config.js:12\r\nsrc/core/packages/base/server-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/browser-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/capabilities/server-mocks/jest.config.js:12\r\nsrc/core/packages/capabilities/server-mocks/tsconfig.json:2\r\nsrc/core/packages/chrome/browser-mocks/jest.config.js:12\r\nsrc/core/packages/chrome/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/deprecations/server-mocks/jest.config.js:12\r\nsrc/core/packages/deprecations/server-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/browser-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/doc-links/server-mocks/jest.config.js:12\r\nsrc/core/packages/doc-links/server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/client-server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/client-server-mocks/tsconfig.json:2\r\nsrc/core/packages/elasticsearch/server-mocks/jest.config.js:12\r\nsrc/core/packages/elasticsearch/server-mocks/tsconfig.json:2\r\nsrc/core/packages/environment/server-mocks/jest.config.js:12\r\nsrc/core/packages/environment/server-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/browser-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/execution-context/server-mocks/jest.config.js:12\r\nsrc/core/packages/execution-context/server-mocks/tsconfig.json:2\r\nsrc/core/packages/fatal-errors/browser-mocks/jest.config.js:12\r\nsrc/core/packages/fatal-errors/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/browser-mocks/jest.config.js:12\r\nsrc/core/packages/http/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/http/context-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/context-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/resources-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/resources-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/router-server-mocks/jest.config.js:12\r\nsrc/core/packages/http/router-server-mocks/tsconfig.json:2\r\nsrc/core/packages/http/server-mocks/jest.config.js:12\r\nsrc/core/packages/http/server-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/browser-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/i18n/server-mocks/jest.config.js:12\r\nsrc/core/packages/i18n/server-mocks/tsconfig.json:2\r\nsrc/core/packages/injected-metadata/browser-mocks/jest.config.js:12\r\nsrc/core/packages/injected-metadata/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/integrations/browser-mocks/jest.config.js:12\r\nsrc/core/packages/integrations/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/browser-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/lifecycle/server-mocks/jest.config.js:12\r\nsrc/core/packages/lifecycle/server-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/browser-mocks/jest.config.js:12\r\nsrc/core/packages/logging/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/logging/server-mocks/jest.config.js:12\r\nsrc/core/packages/logging/server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/collectors-server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/collectors-server-mocks/tsconfig.json:2\r\nsrc/core/packages/metrics/server-mocks/jest.config.js:12\r\nsrc/core/packages/metrics/server-mocks/tsconfig.json:2\r\nsrc/core/packages/node/server-mocks/jest.config.js:12\r\nsrc/core/packages/node/server-mocks/tsconfig.json:2\r\nsrc/core/packages/notifications/browser-mocks/jest.config.js:12\r\nsrc/core/packages/notifications/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/overlays/browser-mocks/jest.config.js:12\r\nsrc/core/packages/overlays/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/browser-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/plugins/server-mocks/jest.config.js:12\r\nsrc/core/packages/plugins/server-mocks/tsconfig.json:2\r\nsrc/core/packages/preboot/server-mocks/jest.config.js:12\r\nsrc/core/packages/preboot/server-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/browser-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/rendering/server-mocks/jest.config.js:12\r\nsrc/core/packages/rendering/server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/api-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/api-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/base-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/base-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/browser-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/import-export-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/import-export-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/migration-server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/migration-server-mocks/tsconfig.json:2\r\nsrc/core/packages/saved-objects/server-mocks/jest.config.js:12\r\nsrc/core/packages/saved-objects/server-mocks/tsconfig.json:2\r\nsrc/core/packages/status/server-mocks/jest.config.js:12\r\nsrc/core/packages/status/server-mocks/tsconfig.json:2\r\nsrc/core/packages/theme/browser-mocks/jest.config.js:12\r\nsrc/core/packages/theme/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/browser-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/browser-mocks/tsconfig.json:2\r\nsrc/core/packages/ui-settings/server-mocks/jest.config.js:12\r\nsrc/core/packages/ui-settings/server-mocks/tsconfig.json:2\r\nsrc/core/packages/usage-data/server-mocks/jest.config.js:12\r\nsrc/core/packages/usage-data/server-mocks/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-kbn-server/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-kbn-server/tsconfig.json:2\r\nsrc/dev/packages/core-test-helpers-model-versions/jest.config.js:12\r\nsrc/dev/packages/core-test-helpers-model-versions/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"4a00449bdcd699f89294536a86dffcbeab4daf53"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
96a4c33070
|
[8.x] [kbn-scout] Scout reporter updates (#206431) (#208651)
# Backport This will backport the following commits from `main` to `8.x`: - [[kbn-scout] Scout reporter updates (#206431)](https://github.com/elastic/kibana/pull/206431) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"David Olaru","email":"dolaru@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T23:08:37Z","message":"[kbn-scout] Scout reporter updates (#206431)\n\n## Summary\r\n\r\n- Centralized Scout reporter settings\r\n- Added owner area and config/test file information to reporter events\r\n- Attempt to upload events at the end of a test run\r\n- Enable Scout reporter test events upload for the `pull request` and\r\n`on merge` pipelines","sha":"fd7053b319f3df2820e3e1879092703635bbc3ae","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor"],"title":"[kbn-scout] Scout reporter updates","number":206431,"url":"https://github.com/elastic/kibana/pull/206431","mergeCommit":{"message":"[kbn-scout] Scout reporter updates (#206431)\n\n## Summary\r\n\r\n- Centralized Scout reporter settings\r\n- Added owner area and config/test file information to reporter events\r\n- Attempt to upload events at the end of a test run\r\n- Enable Scout reporter test events upload for the `pull request` and\r\n`on merge` pipelines","sha":"fd7053b319f3df2820e3e1879092703635bbc3ae"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206431","number":206431,"mergeCommit":{"message":"[kbn-scout] Scout reporter updates (#206431)\n\n## Summary\r\n\r\n- Centralized Scout reporter settings\r\n- Added owner area and config/test file information to reporter events\r\n- Attempt to upload events at the end of a test run\r\n- Enable Scout reporter test events upload for the `pull request` and\r\n`on merge` pipelines","sha":"fd7053b319f3df2820e3e1879092703635bbc3ae"}}]}] BACKPORT--> Co-authored-by: David Olaru <dolaru@elastic.co> |
||
|
Kibana Machine
|
71ad7a230c
|
[8.x] Support for saved objects name attribute in audit log (#206644) (#208680)
# Backport This will backport the following commits from `main` to `8.x`: - [Support for saved objects name attribute in audit log (#206644)](https://github.com/elastic/kibana/pull/206644) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-29T08:03:26Z","message":"Support for saved objects name attribute in audit log (#206644)\n\n## Summary\r\n\r\nAdded support for human readable `name` attribute for saved objects\r\naudit.\r\n- Updated the saved object type/registration with `nameAttribute` option\r\n- Updated the Saved Objects Security Extension to support passing object\r\nnames to the audit functions\r\n- Updated the audit logger with a configuration option to opt out of\r\nincluding saved object names (the SOR and SSC should be aware of this to\r\navoid operations when they are not necessary)\r\n- Updated Saved Object Repository functions\r\n - [x] `bulkCreate`\r\n - [x] `bulkGet`\r\n - [x] `bulkResolve`\r\n - [x] `bulkUpdate`\r\n - [x] `collectMultiNamespaceReferences`\r\n - [x] `get`\r\n - [x] `updateObjectsSpaces`\r\n - [x] `bulkDelete`\r\n - [x] `delete`\r\n - [x] `removeReferencesTo`\r\n- [x] Updated Secure Spaces Client functions\r\n - [x] `auditObjectsForSpaceDeletion`\r\n \r\nFunctions that were not updated:\r\n\r\n- `authorizeFind` - now we log audit before the actual find with only\r\ntypes. Find is complex one, that can return a lot of saved objects. The\r\nbenefit of adding a separate audit event vs potential performance cost\r\ncan be considered negligible.\r\n\r\n |
||
Steph Milovic
|
ca5cf095a4
|
[8.x] [Security AI] Add Kibana Support for Security AI Prompts Integration (#207138) (#208648)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security AI] Add Kibana Support for Security AI Prompts Integration (#207138)](https://github.com/elastic/kibana/pull/207138) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T22:35:39Z","message":"[Security AI] Add Kibana Support for Security AI Prompts Integration (#207138)","sha":"7af5a8338bab6da9bc45eccfd21b11129b05048c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Fleet","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Security Generative AI","v8.18.0"],"title":"[Security AI] Add Kibana Support for Security AI Prompts Integration","number":207138,"url":"https://github.com/elastic/kibana/pull/207138","mergeCommit":{"message":"[Security AI] Add Kibana Support for Security AI Prompts Integration (#207138)","sha":"7af5a8338bab6da9bc45eccfd21b11129b05048c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207138","number":207138,"mergeCommit":{"message":"[Security AI] Add Kibana Support for Security AI Prompts Integration (#207138)","sha":"7af5a8338bab6da9bc45eccfd21b11129b05048c"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
cda402ffc6
|
[8.x] [kbn-test] improve saml auth failure logging (#208216) (#208444)
# Backport This will backport the following commits from `main` to `8.x`: - [[kbn-test] improve saml auth failure logging (#208216)](https://github.com/elastic/kibana/pull/208216) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-27T20:13:50Z","message":"[kbn-test] improve saml auth failure logging (#208216)\n\n## Summary\r\n\r\nsometimes we face failure during saml authentication and error message\r\nis not very helpful:\r\n\r\n```\r\nError: Failed to parse 'set-cookie' header\r\n at getCookieFromResponseHeaders (packages/kbn-test/src/auth/saml_auth.ts:61:11)\r\n at finishSAMLHandshake (packages/kbn-test/src/auth/saml_auth.ts:280:10)\r\n at createLocalSAMLSession (packages/kbn-test/src/auth/saml_auth.ts:333:18)\r\n```\r\n\r\nWith this change we should know when it happened:\r\n\r\n- we create SAML request by calling `/internal/security/login\r\n- we finish SAML handshake by calling `/api/security/saml/callback`\r\n\r\nI also hope `response.data` to be useful for investigation","sha":"10505bd488f9ddd16fca5ce43784ed61b5b10e41","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor"],"title":"[kbn-test] improve saml auth failure logging","number":208216,"url":"https://github.com/elastic/kibana/pull/208216","mergeCommit":{"message":"[kbn-test] improve saml auth failure logging (#208216)\n\n## Summary\r\n\r\nsometimes we face failure during saml authentication and error message\r\nis not very helpful:\r\n\r\n```\r\nError: Failed to parse 'set-cookie' header\r\n at getCookieFromResponseHeaders (packages/kbn-test/src/auth/saml_auth.ts:61:11)\r\n at finishSAMLHandshake (packages/kbn-test/src/auth/saml_auth.ts:280:10)\r\n at createLocalSAMLSession (packages/kbn-test/src/auth/saml_auth.ts:333:18)\r\n```\r\n\r\nWith this change we should know when it happened:\r\n\r\n- we create SAML request by calling `/internal/security/login\r\n- we finish SAML handshake by calling `/api/security/saml/callback`\r\n\r\nI also hope `response.data` to be useful for investigation","sha":"10505bd488f9ddd16fca5ce43784ed61b5b10e41"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208216","number":208216,"mergeCommit":{"message":"[kbn-test] improve saml auth failure logging (#208216)\n\n## Summary\r\n\r\nsometimes we face failure during saml authentication and error message\r\nis not very helpful:\r\n\r\n```\r\nError: Failed to parse 'set-cookie' header\r\n at getCookieFromResponseHeaders (packages/kbn-test/src/auth/saml_auth.ts:61:11)\r\n at finishSAMLHandshake (packages/kbn-test/src/auth/saml_auth.ts:280:10)\r\n at createLocalSAMLSession (packages/kbn-test/src/auth/saml_auth.ts:333:18)\r\n```\r\n\r\nWith this change we should know when it happened:\r\n\r\n- we create SAML request by calling `/internal/security/login\r\n- we finish SAML handshake by calling `/api/security/saml/callback`\r\n\r\nI also hope `response.data` to be useful for investigation","sha":"10505bd488f9ddd16fca5ce43784ed61b5b10e41"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
Giorgos Bamparopoulos
|
7ebef44cf5
|
[8.x] [One Discover] Display stacktrace in the logs overview tab (#204521) (#208115)
# Backport This will backport the following commits from `main` to `8.x`: - [[One Discover] Display stacktrace in the logs overview tab (#204521)](https://github.com/elastic/kibana/pull/204521) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Giorgos Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:06:14Z","message":"[One Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓 Summary\r\nAdds a new section to the overview tab in the log details flyout in\r\nDiscover to display stacktrace information for logs and exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a new tab in the log\r\ndetails flyout and actions can be added to the stacktrace (and quality)\r\nicons in the document table to open the relevant sections in the flyout.\r\n\r\nCloses https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log stacktrace (library frames)\r\n<img width=\"1470\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n### APM - Exception (with cause)\r\n<img width=\"1476\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n### APM - Exception (simple stacktrace)\r\n<img width=\"1474\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n### Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n## 📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as platform / shared as it's\r\nbeing used by the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n- The code used to render stacktraces in APM was moved into a new\r\n`@kbn/event-stacktrace` package as it is reused in the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table in APM was moved into a new\r\n`@kbn/key-value-metadata-table` package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments have sample logs that can be used (time range:\r\nJan 1, 2025 - now). For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1. Ingest sample logs with stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease note that these are test data and some fields that are not used\r\nby stacktraces might not be consistent\r\n2. View relevant logs in Discover (Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v8.18.0"],"title":"[One Discover] Display stacktrace in the logs overview tab","number":204521,"url":"https://github.com/elastic/kibana/pull/204521","mergeCommit":{"message":"[One Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓 Summary\r\nAdds a new section to the overview tab in the log details flyout in\r\nDiscover to display stacktrace information for logs and exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a new tab in the log\r\ndetails flyout and actions can be added to the stacktrace (and quality)\r\nicons in the document table to open the relevant sections in the flyout.\r\n\r\nCloses https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log stacktrace (library frames)\r\n<img width=\"1470\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n### APM - Exception (with cause)\r\n<img width=\"1476\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n### APM - Exception (simple stacktrace)\r\n<img width=\"1474\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n### Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n## 📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as platform / shared as it's\r\nbeing used by the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n- The code used to render stacktraces in APM was moved into a new\r\n`@kbn/event-stacktrace` package as it is reused in the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table in APM was moved into a new\r\n`@kbn/key-value-metadata-table` package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments have sample logs that can be used (time range:\r\nJan 1, 2025 - now). For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1. Ingest sample logs with stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease note that these are test data and some fields that are not used\r\nby stacktraces might not be consistent\r\n2. View relevant logs in Discover (Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204521","number":204521,"mergeCommit":{"message":"[One Discover] Display stacktrace in the logs overview tab (#204521)\n\n## 📓 Summary\r\nAdds a new section to the overview tab in the log details flyout in\r\nDiscover to display stacktrace information for logs and exceptions.\r\n\r\nIn a follow-up, the stacktrace could be moved to a new tab in the log\r\ndetails flyout and actions can be added to the stacktrace (and quality)\r\nicons in the document table to open the relevant sections in the flyout.\r\n\r\nCloses https://github.com/elastic/kibana/issues/190460\r\n\r\n### APM - Log stacktrace (library frames)\r\n<img width=\"1470\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8991f882-d329-4bc5-aa37-424576bcee72\"\r\n/>\r\n\r\n### APM - Exception (with cause)\r\n<img width=\"1476\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cfbf24a7-6f82-48f1-b275-5aac977411ac\"\r\n/>\r\n\r\n### APM - Exception (simple stacktrace)\r\n<img width=\"1474\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/fc0306c4-5fcd-4b74-bb0d-c1784a48d677\"\r\n/>\r\n\r\n### Apache Tomcat Integration (Catalina) - Stacktrace\r\n<img width=\"1472\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/281f1822-faea-4e2d-9515-c11a9ee12f50\"\r\n/>\r\n\r\n## 📝 Notes for reviewers\r\n- The `@kbn/apm-types` package was marked as platform / shared as it's\r\nbeing used by the\r\n[unified_doc_viewer](https://github.com/elastic/kibana/blob/main/src/plugins/unified_doc_viewer/kibana.jsonc)\r\n- The code used to render stacktraces in APM was moved into a new\r\n`@kbn/event-stacktrace` package as it is reused in the\r\n`unified_doc_viewer`\r\n- The code used to render metadata table in APM was moved into a new\r\n`@kbn/key-value-metadata-table` package\r\n\r\n## 🧪 Testing instructions\r\nThe deployed environments have sample logs that can be used (time range:\r\nJan 1, 2025 - now). For a local setup, please follow the instructions\r\nbelow:\r\n\r\n1. Ingest sample logs with stacktraces\r\n([gist](https://gist.github.com/gbamparop/0da21ca7f65b24c4a9c071ce9e9b97b0)).\r\nPlease note that these are test data and some fields that are not used\r\nby stacktraces might not be consistent\r\n2. View relevant logs in Discover (Query: `service.name: \"synth-node-0\"\r\nOR apache_tomcat :*`, Time range: Jan 1, 2025 - now)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"368475e8e55845e17fd4621c1ae60ba1e983bb8f"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Michael Dokolin
|
f7234d92f9
|
[8.x] [HTTP] Add a circuit breaker for the HTTP server (#190684) (#208494)
# Backport This will backport the following commits from `main` to `8.x`: - [[HTTP] Add a circuit breaker for the HTTP server (#190684)](https://github.com/elastic/kibana/pull/190684) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Dokolin","email":"mikhail.dokolin@elastic.co"},"sourceCommit":{"committedDate":"2025-01-27T20:29:21Z","message":"[HTTP] Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves #194605 and closes #170132 and brings the following\nchanges:\n- changed ELU metrics evaluation used for autoscaling;\n- a rate limiter to throttle incoming requests when under a high load;\n- a configuration option to exclude some routes from the rate limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:http","Team:Core","v9.0.0","ci:build-serverless-image","backport:version","v8.18.0"],"title":"Add a circuit breaker for the HTTP server","number":190684,"url":"https://github.com/elastic/kibana/pull/190684","mergeCommit":{"message":"[HTTP] Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves #194605 and closes #170132 and brings the following\nchanges:\n- changed ELU metrics evaluation used for autoscaling;\n- a rate limiter to throttle incoming requests when under a high load;\n- a configuration option to exclude some routes from the rate limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190684","number":190684,"mergeCommit":{"message":"[HTTP] Add a circuit breaker for the HTTP server (#190684)\n\nThis PR resolves #194605 and closes #170132 and brings the following\nchanges:\n- changed ELU metrics evaluation used for autoscaling;\n- a rate limiter to throttle incoming requests when under a high load;\n- a configuration option to exclude some routes from the rate limiter.","sha":"52b7bc6f06d2651a5b8f9023e1e526147a659ab0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Gerard Soldevila
|
6a6d3d61ca
|
[8.x] SKA: Update broken references and URLs (#206836) (#208479)
# Backport This will backport the following commits from `main` to `8.x`: - [SKA: Update broken references and URLs (#206836)](https://github.com/elastic/kibana/pull/206836) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T03:32:48Z","message":"SKA: Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates a number of broken file references and broken links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Feature:ExpressionLanguage","release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management"],"title":"SKA: Update broken references and URLs","number":206836,"url":"https://github.com/elastic/kibana/pull/206836","mergeCommit":{"message":"SKA: Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates a number of broken file references and broken links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206836","number":206836,"mergeCommit":{"message":"SKA: Update broken references and URLs (#206836)\n\n## Summary\r\n\r\nUpdates a number of broken file references and broken links.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"fb26c1c683453faa7f8218df094f90d9ad070a23"}}]}] BACKPORT--> |
||
|
Gerard Soldevila
|
4ba1a0ae0d
|
[8.x] SKA: Follow-up relocation (#208474)
## Summary Manually backport https://github.com/elastic/kibana/pull/207041 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d416693834
|
[8.x] [SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege (#208155) (#208420)
# Backport This will backport the following commits from `main` to `8.x`: - [[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege (#208155)](https://github.com/elastic/kibana/pull/208155) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T17:40:28Z","message":"[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege (#208155)\n\n## Summary\n\nAdds EDR stack connectors sub-privilege to serverless roles.\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"ba8d83a14c7e736abe74164f37e868db6376c340","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","OLM Sprint","backport:version","v8.18.0"],"title":"[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege","number":208155,"url":"https://github.com/elastic/kibana/pull/208155","mergeCommit":{"message":"[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege (#208155)\n\n## Summary\n\nAdds EDR stack connectors sub-privilege to serverless roles.\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"ba8d83a14c7e736abe74164f37e868db6376c340"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208155","number":208155,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege (#208155)\n\n## Summary\n\nAdds EDR stack connectors sub-privilege to serverless roles.\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"ba8d83a14c7e736abe74164f37e868db6376c340"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com> |
||
Dzmitry Lemechko
|
a1a0bf119a
|
[8.x] Scout: run tests in parallel (with spaces) (#207253) (#208147)
# Backport This will backport the following commits from `main` to `8.x`: - [Scout: run tests in parallel (with spaces) (#207253)](https://github.com/elastic/kibana/pull/207253) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-23T19:09:06Z","message":"Scout: run tests in parallel (with spaces) (#207253)\n\n## Summary\r\n\r\nThis PR adds `spaceTest` interface to `kbn-scout` to run space aware\r\ntests, that can be executed in parallel. Most of Discover tests were\r\nconverted to parallel run because we see runtime improvement with 2\r\nparallel workers.\r\n\r\nExperiment 1: **ES data pre-ingested**, running 9 Discover **stateful**\r\ntests in **5 files** locally\r\n| Run setup | Took time |\r\n| ------------- | ------------- |\r\n| 1 worker | `1.3` min |\r\n| 2 workers | `58.7` sec |\r\n| 3 workers | `48.3` sec |\r\n| 4 workers | **tests fail** |\r\n\r\nConclusion: using **2** workers is the optimal solution to continue\r\n\r\nExperiment 2: Running Discover tests for stateful/serverless in **Kibana\r\nCI** (starting servers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 9 tests / 5 files | `1.7` min | `1.2` min | `-29.4%`|\r\n| svl ES, 8 tests / 4 files | `1.7` min | `1.3` min | `-23.5%`|\r\n| svl Oblt, 8 tests / 4 files | `1.8` min | `1.4` min | `-22.2%`|\r\n| svl Search, 5 tests / 2 files | `59.9` sec | `51.6` sec | `-13.8%`|\r\n\r\nConclusion: parallel run effectiveness benefits from tests being split\r\nin **more test files**.\r\n\r\nExperiment 3: Clone existing tests to have **3 times more test files**\r\nand re-run tests for stateful/serverless in **Kibana CI** (starting\r\nservers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 27 tests / 15 files | `4.3` min | `2.7` min | `-37.2%`|\r\n| svl ES, 24 tests / 12 files | `4.3` min | `2.7` min | `-37.2%`|\r\n\r\nConclusion: parallel run effectiveness is **increasing** with more test\r\nfiles in place, **not linear** but with good test design we can expect\r\n**up to 40%** or maybe a bit more.\r\n\r\nHow parallel run works:\r\n- `scoutSpace` fixture is loaded on Playwright worker setup (using\r\n`auto: true` config), creates a new Kibana Space, expose its id to other\r\nfixtures and deletes the space on teardown.\r\n- `browserAuth` fixture for parallel run caches Cookie per worker/space\r\nlike `role:spaceId`. It is needed because Playwright doesn't spin up new\r\nbrowser for worker, but only new context.\r\n- kbnClient was updated to allow passing `createNewCopies: true` in\r\nquery, it is needed to load the same Saved Objects in parallel\r\nworkers/spaces and generate new ids to work with them. `scoutSpace`\r\ncaches ids and allows to reach saved object by its name. This logic is\r\ndifferent from single thread run, where we can use default ids from\r\nkbnArchives.\r\n\r\nHow to run parallel tests locally, e.g. for stateful: \r\n```\r\nnode scripts/scout run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```","sha":"14c3235182d04be7879ecda25ac79c06e5ce91fd","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","test:scout"],"title":"Scout: run tests in parallel (with spaces)","number":207253,"url":"https://github.com/elastic/kibana/pull/207253","mergeCommit":{"message":"Scout: run tests in parallel (with spaces) (#207253)\n\n## Summary\r\n\r\nThis PR adds `spaceTest` interface to `kbn-scout` to run space aware\r\ntests, that can be executed in parallel. Most of Discover tests were\r\nconverted to parallel run because we see runtime improvement with 2\r\nparallel workers.\r\n\r\nExperiment 1: **ES data pre-ingested**, running 9 Discover **stateful**\r\ntests in **5 files** locally\r\n| Run setup | Took time |\r\n| ------------- | ------------- |\r\n| 1 worker | `1.3` min |\r\n| 2 workers | `58.7` sec |\r\n| 3 workers | `48.3` sec |\r\n| 4 workers | **tests fail** |\r\n\r\nConclusion: using **2** workers is the optimal solution to continue\r\n\r\nExperiment 2: Running Discover tests for stateful/serverless in **Kibana\r\nCI** (starting servers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 9 tests / 5 files | `1.7` min | `1.2` min | `-29.4%`|\r\n| svl ES, 8 tests / 4 files | `1.7` min | `1.3` min | `-23.5%`|\r\n| svl Oblt, 8 tests / 4 files | `1.8` min | `1.4` min | `-22.2%`|\r\n| svl Search, 5 tests / 2 files | `59.9` sec | `51.6` sec | `-13.8%`|\r\n\r\nConclusion: parallel run effectiveness benefits from tests being split\r\nin **more test files**.\r\n\r\nExperiment 3: Clone existing tests to have **3 times more test files**\r\nand re-run tests for stateful/serverless in **Kibana CI** (starting\r\nservers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 27 tests / 15 files | `4.3` min | `2.7` min | `-37.2%`|\r\n| svl ES, 24 tests / 12 files | `4.3` min | `2.7` min | `-37.2%`|\r\n\r\nConclusion: parallel run effectiveness is **increasing** with more test\r\nfiles in place, **not linear** but with good test design we can expect\r\n**up to 40%** or maybe a bit more.\r\n\r\nHow parallel run works:\r\n- `scoutSpace` fixture is loaded on Playwright worker setup (using\r\n`auto: true` config), creates a new Kibana Space, expose its id to other\r\nfixtures and deletes the space on teardown.\r\n- `browserAuth` fixture for parallel run caches Cookie per worker/space\r\nlike `role:spaceId`. It is needed because Playwright doesn't spin up new\r\nbrowser for worker, but only new context.\r\n- kbnClient was updated to allow passing `createNewCopies: true` in\r\nquery, it is needed to load the same Saved Objects in parallel\r\nworkers/spaces and generate new ids to work with them. `scoutSpace`\r\ncaches ids and allows to reach saved object by its name. This logic is\r\ndifferent from single thread run, where we can use default ids from\r\nkbnArchives.\r\n\r\nHow to run parallel tests locally, e.g. for stateful: \r\n```\r\nnode scripts/scout run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```","sha":"14c3235182d04be7879ecda25ac79c06e5ce91fd"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207253","number":207253,"mergeCommit":{"message":"Scout: run tests in parallel (with spaces) (#207253)\n\n## Summary\r\n\r\nThis PR adds `spaceTest` interface to `kbn-scout` to run space aware\r\ntests, that can be executed in parallel. Most of Discover tests were\r\nconverted to parallel run because we see runtime improvement with 2\r\nparallel workers.\r\n\r\nExperiment 1: **ES data pre-ingested**, running 9 Discover **stateful**\r\ntests in **5 files** locally\r\n| Run setup | Took time |\r\n| ------------- | ------------- |\r\n| 1 worker | `1.3` min |\r\n| 2 workers | `58.7` sec |\r\n| 3 workers | `48.3` sec |\r\n| 4 workers | **tests fail** |\r\n\r\nConclusion: using **2** workers is the optimal solution to continue\r\n\r\nExperiment 2: Running Discover tests for stateful/serverless in **Kibana\r\nCI** (starting servers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 9 tests / 5 files | `1.7` min | `1.2` min | `-29.4%`|\r\n| svl ES, 8 tests / 4 files | `1.7` min | `1.3` min | `-23.5%`|\r\n| svl Oblt, 8 tests / 4 files | `1.8` min | `1.4` min | `-22.2%`|\r\n| svl Search, 5 tests / 2 files | `59.9` sec | `51.6` sec | `-13.8%`|\r\n\r\nConclusion: parallel run effectiveness benefits from tests being split\r\nin **more test files**.\r\n\r\nExperiment 3: Clone existing tests to have **3 times more test files**\r\nand re-run tests for stateful/serverless in **Kibana CI** (starting\r\nservers, ingesting ES data, running tests)\r\n| Run setup | 1 worker | 2 workers | diff\r\n| ------------- | ------------- |------------- |------------- |\r\n| stateful, 27 tests / 15 files | `4.3` min | `2.7` min | `-37.2%`|\r\n| svl ES, 24 tests / 12 files | `4.3` min | `2.7` min | `-37.2%`|\r\n\r\nConclusion: parallel run effectiveness is **increasing** with more test\r\nfiles in place, **not linear** but with good test design we can expect\r\n**up to 40%** or maybe a bit more.\r\n\r\nHow parallel run works:\r\n- `scoutSpace` fixture is loaded on Playwright worker setup (using\r\n`auto: true` config), creates a new Kibana Space, expose its id to other\r\nfixtures and deletes the space on teardown.\r\n- `browserAuth` fixture for parallel run caches Cookie per worker/space\r\nlike `role:spaceId`. It is needed because Playwright doesn't spin up new\r\nbrowser for worker, but only new context.\r\n- kbnClient was updated to allow passing `createNewCopies: true` in\r\nquery, it is needed to load the same Saved Objects in parallel\r\nworkers/spaces and generate new ids to work with them. `scoutSpace`\r\ncaches ids and allows to reach saved object by its name. This logic is\r\ndifferent from single thread run, where we can use default ids from\r\nkbnArchives.\r\n\r\nHow to run parallel tests locally, e.g. for stateful: \r\n```\r\nnode scripts/scout run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```","sha":"14c3235182d04be7879ecda25ac79c06e5ce91fd"}}]}] BACKPORT--> |
||
|
Dzmitry Lemechko
|
602b3a26e2
|
[8.x] [kbn-scout-reporting] escape html characters in html report (#206987) (#208146)
# Backport This will backport the following commits from `main` to `8.x`: - [[kbn-scout-reporting] escape html characters in html report (#206987)](https://github.com/elastic/kibana/pull/206987) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-01-17T09:16:15Z","message":"[kbn-scout-reporting] escape html characters in html report (#206987)\n\n## Summary\r\n\r\nFixing `Error details` section not properly displaying html characters\r\nin error stacktrace.\r\n\r\nBefore:\r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1821751f-3a89-46a6-bf55-ed2fe845a196\"\r\n/>\r\n\r\nAfter: \r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/83526d8a-ca3c-4b62-a01e-69029f0e8e7e\"\r\n/>","sha":"158146402e936cac3fce881c47900a49283e7360","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","v9.0.0","backport:prev-minor","test:scout"],"title":"[kbn-scout-reporting] escape html characters in html report","number":206987,"url":"https://github.com/elastic/kibana/pull/206987","mergeCommit":{"message":"[kbn-scout-reporting] escape html characters in html report (#206987)\n\n## Summary\r\n\r\nFixing `Error details` section not properly displaying html characters\r\nin error stacktrace.\r\n\r\nBefore:\r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1821751f-3a89-46a6-bf55-ed2fe845a196\"\r\n/>\r\n\r\nAfter: \r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/83526d8a-ca3c-4b62-a01e-69029f0e8e7e\"\r\n/>","sha":"158146402e936cac3fce881c47900a49283e7360"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206987","number":206987,"mergeCommit":{"message":"[kbn-scout-reporting] escape html characters in html report (#206987)\n\n## Summary\r\n\r\nFixing `Error details` section not properly displaying html characters\r\nin error stacktrace.\r\n\r\nBefore:\r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1821751f-3a89-46a6-bf55-ed2fe845a196\"\r\n/>\r\n\r\nAfter: \r\n\r\n<img width=\"1347\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/83526d8a-ca3c-4b62-a01e-69029f0e8e7e\"\r\n/>","sha":"158146402e936cac3fce881c47900a49283e7360"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
b7e7374a3f
|
[8.x] [visualizations] lazy load actions (#207147) (#208111)
# Backport This will backport the following commits from `main` to `8.x`: - [[visualizations] lazy load actions (#207147)](https://github.com/elastic/kibana/pull/207147) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-01-23T18:33:23Z","message":"[visualizations] lazy load actions (#207147)\n\nClean up visualizations page load size by\r\n* lazy loading actions\r\n* avoid exporting from index files to avoid exporting unused code\r\n* move `urlFor` and `getFullPath` into `url_utils` to avoid including\r\n`utils/saved_visualize_utils` in page load bundle\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d7f801ab3e9c22cc77c0fc3da9492008a5a5252a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v9.0.0","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[visualizations] lazy load actions","number":207147,"url":"https://github.com/elastic/kibana/pull/207147","mergeCommit":{"message":"[visualizations] lazy load actions (#207147)\n\nClean up visualizations page load size by\r\n* lazy loading actions\r\n* avoid exporting from index files to avoid exporting unused code\r\n* move `urlFor` and `getFullPath` into `url_utils` to avoid including\r\n`utils/saved_visualize_utils` in page load bundle\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d7f801ab3e9c22cc77c0fc3da9492008a5a5252a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207147","number":207147,"mergeCommit":{"message":"[visualizations] lazy load actions (#207147)\n\nClean up visualizations page load size by\r\n* lazy loading actions\r\n* avoid exporting from index files to avoid exporting unused code\r\n* move `urlFor` and `getFullPath` into `url_utils` to avoid including\r\n`utils/saved_visualize_utils` in page load bundle\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d7f801ab3e9c22cc77c0fc3da9492008a5a5252a"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
Yngrid Coello
|
69b10ccae9
|
[8.x] [Dataset quality] Failure store support (#206758) (#208051)
# Backport This will backport the following commits from `main` to `8.x`: - [[Dataset quality] Failure store support (#206758)](https://github.com/elastic/kibana/pull/206758) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yngrid Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2025-01-23T08:13:28Z","message":"[Dataset quality] Failure store support (#206758)\n\nCloses https://github.com/elastic/logs-dev/issues/183,\nhttps://github.com/elastic/logs-dev/issues/184 and\nhttps://github.com/elastic/logs-dev/issues/185.\n\n## Summary\nThis PR aims to support failure store in dataset quality page. The\nfollowing acceptance criteria items were resolved\n\n### Dataset quality page\n- [x] A column for Failed docs is included in the table\n- [x] A tooltip is placed in the title of the column\n- [x] A % of documents inside Failure store is calculated for every\ndataStream\n- [x] If % is lesser than 0.0001 but greater than 0 we should show ⚠\nsymbol next to the ~0 value (as we do with degraded docs)\n- [x] Failed docs percentages greater than 0 should link to discover\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6d9e3f4c-02d9-43ab-88cb-ae70716b05d9\n\n### Dataset details page\n- [x] A metric, Failed docs, is included in the Overview panel under\nData set quality. This metric includes the number of documents inside\nthe failure store for the specific dataStream.\n- [x] A tooltip is placed in the title of the Failed docs metric with\nmessage: `The percentage of docs sent to failure store due to an issue\nduring ingestion.`\n- [x] Degraded docs graph section is transformed to Document trends\nallowing the users to switch between Degraded docs and Failed docs\ntrends over time.\n- [x] A new chart for failed documents is created with links to\ndiscover/Logs explorer using the right dataView\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6a3a1f09-2668-4e83-938e-ecdda798c199\n\n### Failed docs ingestion issue flyout\n\n- [x] Whenever documents are found in failure store we should list\nDocument indexing failed in Quality issues table\n- [x] User should be able to expand Document indexing failed and see\nmore information in the flyout\n- [x] The flyout will show Docs count, an aggregation of the number of\ndocuments inside failure store for the selected timeframe\n- [x] The flyout will show Last ocurrence, the datetime registered for\nthe most recent document in the failure store.\n- [x] The flyout will contain a section called Error messages where a\nlist of unique error messages should be shown, exposing Content (error\nmessage) and Type (Error Type).\n- [x] Type should contain a tooltip where message (`Error message\ncategory`) explain users how we are categorising the errors.\n- [x] Other issues inside Quality issues table will be appended by field\nignored and the field will be shown in bold.\n\n\nhttps://github.com/user-attachments/assets/94dc81f0-9720-4596-b256-c9d289cefd94\n\nNote: This PR was reconstructed from\nhttps://github.com/elastic/kibana/pull/199806 which it supersedes.\n\n## How to test\n\n1. Execute `failed_logs` synthtrace scenario\n2. Open dataset quality page\n\n## Follow ups\n- Enable in serverless\n- Deployment agnostic tests cannot be added until we enable this in\nserverless\n- FTR tests will be added as part of\nhttps://github.com/elastic/logs-dev/issues/182\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"511f77c231b1d0639bd1ebf0987d93317d389d5a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Feature:Dataset Health"],"title":"[Dataset quality] Failure store support","number":206758,"url":"https://github.com/elastic/kibana/pull/206758","mergeCommit":{"message":"[Dataset quality] Failure store support (#206758)\n\nCloses https://github.com/elastic/logs-dev/issues/183,\nhttps://github.com/elastic/logs-dev/issues/184 and\nhttps://github.com/elastic/logs-dev/issues/185.\n\n## Summary\nThis PR aims to support failure store in dataset quality page. The\nfollowing acceptance criteria items were resolved\n\n### Dataset quality page\n- [x] A column for Failed docs is included in the table\n- [x] A tooltip is placed in the title of the column\n- [x] A % of documents inside Failure store is calculated for every\ndataStream\n- [x] If % is lesser than 0.0001 but greater than 0 we should show ⚠\nsymbol next to the ~0 value (as we do with degraded docs)\n- [x] Failed docs percentages greater than 0 should link to discover\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6d9e3f4c-02d9-43ab-88cb-ae70716b05d9\n\n### Dataset details page\n- [x] A metric, Failed docs, is included in the Overview panel under\nData set quality. This metric includes the number of documents inside\nthe failure store for the specific dataStream.\n- [x] A tooltip is placed in the title of the Failed docs metric with\nmessage: `The percentage of docs sent to failure store due to an issue\nduring ingestion.`\n- [x] Degraded docs graph section is transformed to Document trends\nallowing the users to switch between Degraded docs and Failed docs\ntrends over time.\n- [x] A new chart for failed documents is created with links to\ndiscover/Logs explorer using the right dataView\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6a3a1f09-2668-4e83-938e-ecdda798c199\n\n### Failed docs ingestion issue flyout\n\n- [x] Whenever documents are found in failure store we should list\nDocument indexing failed in Quality issues table\n- [x] User should be able to expand Document indexing failed and see\nmore information in the flyout\n- [x] The flyout will show Docs count, an aggregation of the number of\ndocuments inside failure store for the selected timeframe\n- [x] The flyout will show Last ocurrence, the datetime registered for\nthe most recent document in the failure store.\n- [x] The flyout will contain a section called Error messages where a\nlist of unique error messages should be shown, exposing Content (error\nmessage) and Type (Error Type).\n- [x] Type should contain a tooltip where message (`Error message\ncategory`) explain users how we are categorising the errors.\n- [x] Other issues inside Quality issues table will be appended by field\nignored and the field will be shown in bold.\n\n\nhttps://github.com/user-attachments/assets/94dc81f0-9720-4596-b256-c9d289cefd94\n\nNote: This PR was reconstructed from\nhttps://github.com/elastic/kibana/pull/199806 which it supersedes.\n\n## How to test\n\n1. Execute `failed_logs` synthtrace scenario\n2. Open dataset quality page\n\n## Follow ups\n- Enable in serverless\n- Deployment agnostic tests cannot be added until we enable this in\nserverless\n- FTR tests will be added as part of\nhttps://github.com/elastic/logs-dev/issues/182\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"511f77c231b1d0639bd1ebf0987d93317d389d5a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206758","number":206758,"mergeCommit":{"message":"[Dataset quality] Failure store support (#206758)\n\nCloses https://github.com/elastic/logs-dev/issues/183,\nhttps://github.com/elastic/logs-dev/issues/184 and\nhttps://github.com/elastic/logs-dev/issues/185.\n\n## Summary\nThis PR aims to support failure store in dataset quality page. The\nfollowing acceptance criteria items were resolved\n\n### Dataset quality page\n- [x] A column for Failed docs is included in the table\n- [x] A tooltip is placed in the title of the column\n- [x] A % of documents inside Failure store is calculated for every\ndataStream\n- [x] If % is lesser than 0.0001 but greater than 0 we should show ⚠\nsymbol next to the ~0 value (as we do with degraded docs)\n- [x] Failed docs percentages greater than 0 should link to discover\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6d9e3f4c-02d9-43ab-88cb-ae70716b05d9\n\n### Dataset details page\n- [x] A metric, Failed docs, is included in the Overview panel under\nData set quality. This metric includes the number of documents inside\nthe failure store for the specific dataStream.\n- [x] A tooltip is placed in the title of the Failed docs metric with\nmessage: `The percentage of docs sent to failure store due to an issue\nduring ingestion.`\n- [x] Degraded docs graph section is transformed to Document trends\nallowing the users to switch between Degraded docs and Failed docs\ntrends over time.\n- [x] A new chart for failed documents is created with links to\ndiscover/Logs explorer using the right dataView\n\n 🎥 Demo \n\n\nhttps://github.com/user-attachments/assets/6a3a1f09-2668-4e83-938e-ecdda798c199\n\n### Failed docs ingestion issue flyout\n\n- [x] Whenever documents are found in failure store we should list\nDocument indexing failed in Quality issues table\n- [x] User should be able to expand Document indexing failed and see\nmore information in the flyout\n- [x] The flyout will show Docs count, an aggregation of the number of\ndocuments inside failure store for the selected timeframe\n- [x] The flyout will show Last ocurrence, the datetime registered for\nthe most recent document in the failure store.\n- [x] The flyout will contain a section called Error messages where a\nlist of unique error messages should be shown, exposing Content (error\nmessage) and Type (Error Type).\n- [x] Type should contain a tooltip where message (`Error message\ncategory`) explain users how we are categorising the errors.\n- [x] Other issues inside Quality issues table will be appended by field\nignored and the field will be shown in bold.\n\n\nhttps://github.com/user-attachments/assets/94dc81f0-9720-4596-b256-c9d289cefd94\n\nNote: This PR was reconstructed from\nhttps://github.com/elastic/kibana/pull/199806 which it supersedes.\n\n## How to test\n\n1. Execute `failed_logs` synthtrace scenario\n2. Open dataset quality page\n\n## Follow ups\n- Enable in serverless\n- Deployment agnostic tests cannot be added until we enable this in\nserverless\n- FTR tests will be added as part of\nhttps://github.com/elastic/logs-dev/issues/182\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"511f77c231b1d0639bd1ebf0987d93317d389d5a"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Amir Ben Nun
|
747e766250
|
[8.x] [Fleet] Send Agentless API resources (#206042) (#207701)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Send Agentless API resources (#206042)](https://github.com/elastic/kibana/pull/206042) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Amir Ben Nun","email":"34831306+amirbenun@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-19T10:52:10Z","message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Fleet","v9.0.0","Team:Cloud Security","backport:prev-minor","ci:project-deploy-security"],"title":"[Fleet] Send Agentless API resources","number":206042,"url":"https://github.com/elastic/kibana/pull/206042","mergeCommit":{"message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206042","number":206042,"mergeCommit":{"message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
656bf4afce
|
[8.x] [Inventory v2][APM] Remove redundant synthtrace scenario (#207716) (#207742)
# Backport This will backport the following commits from `main` to `8.x`: - [[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)](https://github.com/elastic/kibana/pull/207716) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T11:38:15Z","message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[Inventory v2][APM] Remove redundant synthtrace scenario","number":207716,"url":"https://github.com/elastic/kibana/pull/207716","mergeCommit":{"message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207716","number":207716,"mergeCommit":{"message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Jan Monschke
|
8e02172e2e
|
[8.x] [SecuritySolution] Breaking out timeline & note privileges (#201780) (#207367)
# Backport This will backport the following commits from `main` to `8.x`: - [[SecuritySolution] Breaking out timeline & note privileges (#201780)](https://github.com/elastic/kibana/pull/201780) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T13:09:16Z","message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Fleet","v9.0.0","release_note:feature","Team:Threat Hunting:Investigations","backport:prev-minor","ci:cloud-deploy","ci:project-persist-deployment","v8.18.0"],"title":"[SecuritySolution] Breaking out timeline & note privileges","number":201780,"url":"https://github.com/elastic/kibana/pull/201780","mergeCommit":{"message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201780","number":201780,"mergeCommit":{"message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
b58c5a9e3a
|
[8.x] [Inventory v2] Fix issue with logs only views (#207305) (#207399)
# Backport This will backport the following commits from `main` to `8.x`: - [[Inventory v2] Fix issue with logs only views (#207305)](https://github.com/elastic/kibana/pull/207305) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-21T16:29:05Z","message":"[Inventory v2] Fix issue with logs only views (#207305)\n\nCloses https://github.com/elastic/kibana/issues/206967\r\n\r\n## Summary\r\n\r\nAfter some changes related to V2 migration of getting the entities,\r\nthere was an issue with the new data coming from the endpoint - the\r\n`data_stream.type` is a string instead of an array in case of a single\r\ndata stream so this PR adds a fix to support that (and a test)\r\n\r\n## Bug fixes\r\n- Service overview page loads for a logs-only data stream\r\n- After adding the fix, I saw another error related to the `useTheme`\r\nand changed it to use the `euiTheme` similar to the other changes\r\nrelated to the Borealis team upgrade\r\n\r\n## Testing\r\nTo test the scenario with services and hosts coming from logs (without\r\nAPM / metrics) I added a new scenario in synthtrace so to test then we\r\nshould:\r\n- Run the new scenario: `node scripts/synthtrace logs_only` (if possible\r\non a clean ES)\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n- Go to Inventory and click on a service\r\n - The logs-only views should be available\r\n- Go to Inventory and click on a host\r\n - The logs-only views should be available\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/cfd5fd40-ac44-4807-9a29-f3ee3015d814\r\n\r\n\r\n - Test one of the scenarios with mix of APM/metrics/logs\r\n - Run `node scripts/synthtrace infra_hosts_with_apm_hosts`\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n - Go to Inventory and click on a service from APM\r\n - The APM views (service/traces) should be available\r\n - Go to Inventory and click on a host\r\n - The asset details view should be available and show metrics\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/894c7c1a-aaa1-42cb-9dcb-05c9a5ca8177\r\n\r\n\r\n\r\n- Infrastructure (Inventory/Hosts, etc) and Applications (Service\r\nInventory/Traces, etc) should load the data for this scenario and not\r\nfor the logs only (also for an oblt cluster connection)\r\n \r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d092cc6-a8ad-4022-b980-b443be09acc9","sha":"bd5e8ca3209886d5d67e5c78eaf9f3a55b6df55a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[Inventory v2] Fix issue with logs only views","number":207305,"url":"https://github.com/elastic/kibana/pull/207305","mergeCommit":{"message":"[Inventory v2] Fix issue with logs only views (#207305)\n\nCloses https://github.com/elastic/kibana/issues/206967\r\n\r\n## Summary\r\n\r\nAfter some changes related to V2 migration of getting the entities,\r\nthere was an issue with the new data coming from the endpoint - the\r\n`data_stream.type` is a string instead of an array in case of a single\r\ndata stream so this PR adds a fix to support that (and a test)\r\n\r\n## Bug fixes\r\n- Service overview page loads for a logs-only data stream\r\n- After adding the fix, I saw another error related to the `useTheme`\r\nand changed it to use the `euiTheme` similar to the other changes\r\nrelated to the Borealis team upgrade\r\n\r\n## Testing\r\nTo test the scenario with services and hosts coming from logs (without\r\nAPM / metrics) I added a new scenario in synthtrace so to test then we\r\nshould:\r\n- Run the new scenario: `node scripts/synthtrace logs_only` (if possible\r\non a clean ES)\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n- Go to Inventory and click on a service\r\n - The logs-only views should be available\r\n- Go to Inventory and click on a host\r\n - The logs-only views should be available\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/cfd5fd40-ac44-4807-9a29-f3ee3015d814\r\n\r\n\r\n - Test one of the scenarios with mix of APM/metrics/logs\r\n - Run `node scripts/synthtrace infra_hosts_with_apm_hosts`\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n - Go to Inventory and click on a service from APM\r\n - The APM views (service/traces) should be available\r\n - Go to Inventory and click on a host\r\n - The asset details view should be available and show metrics\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/894c7c1a-aaa1-42cb-9dcb-05c9a5ca8177\r\n\r\n\r\n\r\n- Infrastructure (Inventory/Hosts, etc) and Applications (Service\r\nInventory/Traces, etc) should load the data for this scenario and not\r\nfor the logs only (also for an oblt cluster connection)\r\n \r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d092cc6-a8ad-4022-b980-b443be09acc9","sha":"bd5e8ca3209886d5d67e5c78eaf9f3a55b6df55a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207305","number":207305,"mergeCommit":{"message":"[Inventory v2] Fix issue with logs only views (#207305)\n\nCloses https://github.com/elastic/kibana/issues/206967\r\n\r\n## Summary\r\n\r\nAfter some changes related to V2 migration of getting the entities,\r\nthere was an issue with the new data coming from the endpoint - the\r\n`data_stream.type` is a string instead of an array in case of a single\r\ndata stream so this PR adds a fix to support that (and a test)\r\n\r\n## Bug fixes\r\n- Service overview page loads for a logs-only data stream\r\n- After adding the fix, I saw another error related to the `useTheme`\r\nand changed it to use the `euiTheme` similar to the other changes\r\nrelated to the Borealis team upgrade\r\n\r\n## Testing\r\nTo test the scenario with services and hosts coming from logs (without\r\nAPM / metrics) I added a new scenario in synthtrace so to test then we\r\nshould:\r\n- Run the new scenario: `node scripts/synthtrace logs_only` (if possible\r\non a clean ES)\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n- Go to Inventory and click on a service\r\n - The logs-only views should be available\r\n- Go to Inventory and click on a host\r\n - The logs-only views should be available\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/cfd5fd40-ac44-4807-9a29-f3ee3015d814\r\n\r\n\r\n - Test one of the scenarios with mix of APM/metrics/logs\r\n - Run `node scripts/synthtrace infra_hosts_with_apm_hosts`\r\n- Enable `observability:entityCentricExperience` in Stack Management >\r\nAdvanced Setting\r\n - Go to Inventory and click on a service from APM\r\n - The APM views (service/traces) should be available\r\n - Go to Inventory and click on a host\r\n - The asset details view should be available and show metrics\r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/894c7c1a-aaa1-42cb-9dcb-05c9a5ca8177\r\n\r\n\r\n\r\n- Infrastructure (Inventory/Hosts, etc) and Applications (Service\r\nInventory/Traces, etc) should load the data for this scenario and not\r\nfor the logs only (also for an oblt cluster connection)\r\n \r\n \r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d092cc6-a8ad-4022-b980-b443be09acc9","sha":"bd5e8ca3209886d5d67e5c78eaf9f3a55b6df55a"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
jennypavlova
|
7a212212d3
|
[8.x] [APM][Transactions] Test trace summary (#207115) (#207358)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM][Transactions] Test trace summary (#207115)](https://github.com/elastic/kibana/pull/207115) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-21T08:49:03Z","message":"[APM][Transactions] Test trace summary (#207115)\n\nCloses #206947\r\n\r\n## Summary\r\n\r\nThis PR adds tests for trace summary (Otel / APM cases) and changes the\r\n`styled-components` to `css`.","sha":"8b97ad0b1332fbef0e0e13ac3a01d842a8f7b8c9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[APM][Transactions] Test trace summary","number":207115,"url":"https://github.com/elastic/kibana/pull/207115","mergeCommit":{"message":"[APM][Transactions] Test trace summary (#207115)\n\nCloses #206947\r\n\r\n## Summary\r\n\r\nThis PR adds tests for trace summary (Otel / APM cases) and changes the\r\n`styled-components` to `css`.","sha":"8b97ad0b1332fbef0e0e13ac3a01d842a8f7b8c9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207115","number":207115,"mergeCommit":{"message":"[APM][Transactions] Test trace summary (#207115)\n\nCloses #206947\r\n\r\n## Summary\r\n\r\nThis PR adds tests for trace summary (Otel / APM cases) and changes the\r\n`styled-components` to `css`.","sha":"8b97ad0b1332fbef0e0e13ac3a01d842a8f7b8c9"}}]}] BACKPORT--> |
||
Nathan Reese
|
c570a3431f
|
[8.x] [controls] lazy load control actions (#206876) (#207277)
# Backport This will backport the following commits from `main` to `8.x`: - [[controls] lazy load control actions (#206876)](https://github.com/elastic/kibana/pull/206876) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T21:00:48Z","message":"[controls] lazy load control actions (#206876)\n\n* register control actions with async method\r\n* move floating actions into controls plugin\r\n* replace `PANEL_HOVER_TRIGGER` => `CONTROL_HOVER_TRIGGER`\r\n* Load controls in single chunk\r\n<img width=\"400\" alt=\"Screenshot 2025-01-16 at 11 40 08 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/3171c9bf-26bc-4c07-950d-c35603cfb65a\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f4df5856f249552f01ccb020a3ffd90c1517b71d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","v9.0.0","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[controls] lazy load control actions","number":206876,"url":"https://github.com/elastic/kibana/pull/206876","mergeCommit":{"message":"[controls] lazy load control actions (#206876)\n\n* register control actions with async method\r\n* move floating actions into controls plugin\r\n* replace `PANEL_HOVER_TRIGGER` => `CONTROL_HOVER_TRIGGER`\r\n* Load controls in single chunk\r\n<img width=\"400\" alt=\"Screenshot 2025-01-16 at 11 40 08 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/3171c9bf-26bc-4c07-950d-c35603cfb65a\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f4df5856f249552f01ccb020a3ffd90c1517b71d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206876","number":206876,"mergeCommit":{"message":"[controls] lazy load control actions (#206876)\n\n* register control actions with async method\r\n* move floating actions into controls plugin\r\n* replace `PANEL_HOVER_TRIGGER` => `CONTROL_HOVER_TRIGGER`\r\n* Load controls in single chunk\r\n<img width=\"400\" alt=\"Screenshot 2025-01-16 at 11 40 08 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/3171c9bf-26bc-4c07-950d-c35603cfb65a\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f4df5856f249552f01ccb020a3ffd90c1517b71d"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |