github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-20 07:48:52 -04:00
Code Issues Projects Releases Packages Wiki Activity
84501 commits 430 branches 495 tags 21 GiB
Commit graph

84501 commits

This branch
This branch
All branches
Author SHA1 Message Date
Kibana Machine
6387080d0c
[9.0] [Security Solution][Telemetry] Collect additional index stats (#213822) (#215877) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution][Telemetry] Collect additional index stats
(#213822)](https://github.com/elastic/kibana/pull/213822)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sebastián
Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T13:18:31Z","message":"[Security
Solution][Telemetry] Collect additional index stats (#213822)\n\n##
Summary\n\n- Collect information about index_failed stats: Adds two new
fields,\n`index_failed_due_to_version_conflict` and `index_failed` to
the\nexistent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event.\n- Since the `docs_count`, `docs_deleted` and
`docs_total_size_in_bytes`\nrepresent the totals (i.e., primaries and
replicas), add the counterpart\n`_primaries` fields to collect values
from primaries to the
existent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event\n- Add a new `IndexSettings` ebt event with the following
information\n```js\nexport interface IndicesSettings {\n items:
IndexSettings[];\n}\n\nexport interface IndexSettings {\n index_name:
string;\n default_pipeline?: string;\n final_pipeline?:
string;\n}\n```\n\n### Checklist\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"82f6a89e62cfd3cc3cd1cf5a2159c871d91f0e5b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:prev-minor","backport:prev-major","ci:build-cloud-image","ci:cloud-deploy","ci:cloud-redeploy","ci:project-deploy-security","v9.1.0"],"title":"[Security
Solution][Telemetry] Collect additional index
stats","number":213822,"url":"https://github.com/elastic/kibana/pull/213822","mergeCommit":{"message":"[Security
Solution][Telemetry] Collect additional index stats (#213822)\n\n##
Summary\n\n- Collect information about index_failed stats: Adds two new
fields,\n`index_failed_due_to_version_conflict` and `index_failed` to
the\nexistent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event.\n- Since the `docs_count`, `docs_deleted` and
`docs_total_size_in_bytes`\nrepresent the totals (i.e., primaries and
replicas), add the counterpart\n`_primaries` fields to collect values
from primaries to the
existent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event\n- Add a new `IndexSettings` ebt event with the following
information\n```js\nexport interface IndicesSettings {\n items:
IndexSettings[];\n}\n\nexport interface IndexSettings {\n index_name:
string;\n default_pipeline?: string;\n final_pipeline?:
string;\n}\n```\n\n### Checklist\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"82f6a89e62cfd3cc3cd1cf5a2159c871d91f0e5b"}},"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/213822","number":213822,"mergeCommit":{"message":"[Security
Solution][Telemetry] Collect additional index stats (#213822)\n\n##
Summary\n\n- Collect information about index_failed stats: Adds two new
fields,\n`index_failed_due_to_version_conflict` and `index_failed` to
the\nexistent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event.\n- Since the `docs_count`, `docs_deleted` and
`docs_total_size_in_bytes`\nrepresent the totals (i.e., primaries and
replicas), add the counterpart\n`_primaries` fields to collect values
from primaries to the
existent\n[TELEMETRY_INDEX_STATS_EVENT](933564d713/x-pack/solutions/security/plugins/security_solution/server/lib/telemetry/event_based/events.ts (L325))\nEBT
event\n- Add a new `IndexSettings` ebt event with the following
information\n```js\nexport interface IndicesSettings {\n items:
IndexSettings[];\n}\n\nexport interface IndexSettings {\n index_name:
string;\n default_pipeline?: string;\n final_pipeline?:
string;\n}\n```\n\n### Checklist\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\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine
<elasticmachine@users.noreply.github.com>","sha":"82f6a89e62cfd3cc3cd1cf5a2159c871d91f0e5b"}}]}]
BACKPORT-->

Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co>
 2025-03-25 17:31:58 +02:00
Marco Liberati
e163ff3c49
[9.0] [Lens] Do not crash when editing a Lens chart with a by reference annotation layer (#213090) (#215654) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Lens] Do not crash when editing a Lens chart with a by reference
annotation layer
(#213090)](https://github.com/elastic/kibana/pull/213090)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T11:44:30Z","message":"[Lens]
Do not crash when editing a Lens chart with a by reference annotation
layer (#213090)\n\n## Summary\n\nFixes #212917\n\nThe root problem is
belongs into the annotation layer logic to produce\nthe reference id for
the persisted saved object.\nIn the previous logic a new `uuid` was
generated all the time leading to\na continuous flow of `setState` calls
to update the \"runtime\" state of\nthe Lens object when inline editing:
the fix was to produce a stable id\nin the `extractReferences` logic to
avoid the re-renders.\nThe logic has been tweaked a bit now with some
extra explanations inline\nto make it more understandable.\n\nNew tests
have been added to smoke test this scenario.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \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\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"48926e5173ebec2444a3ec6f244bbadb42eab3b0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:version","v8.18.0","v9.1.0"],"title":"[Lens]
Do not crash when editing a Lens chart with a by reference annotation
layer","number":213090,"url":"https://github.com/elastic/kibana/pull/213090","mergeCommit":{"message":"[Lens]
Do not crash when editing a Lens chart with a by reference annotation
layer (#213090)\n\n## Summary\n\nFixes #212917\n\nThe root problem is
belongs into the annotation layer logic to produce\nthe reference id for
the persisted saved object.\nIn the previous logic a new `uuid` was
generated all the time leading to\na continuous flow of `setState` calls
to update the \"runtime\" state of\nthe Lens object when inline editing:
the fix was to produce a stable id\nin the `extractReferences` logic to
avoid the re-renders.\nThe logic has been tweaked a bit now with some
extra explanations inline\nto make it more understandable.\n\nNew tests
have been added to smoke test this scenario.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \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\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"48926e5173ebec2444a3ec6f244bbadb42eab3b0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213366","number":213366,"state":"MERGED","mergeCommit":{"sha":"fc72350d24acfcb9018176752fa931fe6018072d","message":"[8.18]
[Lens] Do not crash when editing a Lens chart with a by reference
annotation layer (#213090) (#213366)\n\n# Backport\n\nThis will backport
the following commits from `main` to `8.18`:\n- [[Lens] Do not crash
when editing a Lens chart with a by reference\nannotation
layer\n(#213090)](https://github.com/elastic/kibana/pull/213090)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Marco Liberati
<dej611@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213090","number":213090,"mergeCommit":{"message":"[Lens]
Do not crash when editing a Lens chart with a by reference annotation
layer (#213090)\n\n## Summary\n\nFixes #212917\n\nThe root problem is
belongs into the annotation layer logic to produce\nthe reference id for
the persisted saved object.\nIn the previous logic a new `uuid` was
generated all the time leading to\na continuous flow of `setState` calls
to update the \"runtime\" state of\nthe Lens object when inline editing:
the fix was to produce a stable id\nin the `extractReferences` logic to
avoid the re-renders.\nThe logic has been tweaked a bit now with some
extra explanations inline\nto make it more understandable.\n\nNew tests
have been added to smoke test this scenario.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \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\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"48926e5173ebec2444a3ec6f244bbadb42eab3b0"}}]}]
BACKPORT-->
 2025-03-25 16:26:54 +01:00
Marco Liberati
673c43bf3e
[9.0] [Lens][Embeddable] fix can edit check (#213887) (#215452) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Lens][Embeddable] fix can edit check
(#213887)](https://github.com/elastic/kibana/pull/213887)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T11:50:04Z","message":"[Lens][Embeddable]
fix can edit check (#213887)\n\n## Summary\n\nThis PR fixes a regression
introduced for user messages.\nThe `viewMode` check moved from
observable to its raw value but still\nperforming the observable
check.\n\nThe fix is to check both the panel `viewMode` AND as fallback
the\nembeddable hierarchy viewMode until the `edit` mode is
met.\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"cc52db1474298bc25906294978c3eeef56df364a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","Feature:Embeddables","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.4","v9.0.1"],"title":"[Lens][Embeddable]
fix can edit
check","number":213887,"url":"https://github.com/elastic/kibana/pull/213887","mergeCommit":{"message":"[Lens][Embeddable]
fix can edit check (#213887)\n\n## Summary\n\nThis PR fixes a regression
introduced for user messages.\nThe `viewMode` check moved from
observable to its raw value but still\nperforming the observable
check.\n\nThe fix is to check both the panel `viewMode` AND as fallback
the\nembeddable hierarchy viewMode until the `edit` mode is
met.\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"cc52db1474298bc25906294978c3eeef56df364a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213887","number":213887,"mergeCommit":{"message":"[Lens][Embeddable]
fix can edit check (#213887)\n\n## Summary\n\nThis PR fixes a regression
introduced for user messages.\nThe `viewMode` check moved from
observable to its raw value but still\nperforming the observable
check.\n\nThe fix is to check both the panel `viewMode` AND as fallback
the\nembeddable hierarchy viewMode until the `edit` mode is
met.\n\n---------\n\nCo-authored-by: Nick Partridge
<nick.ryan.partridge@gmail.com>","sha":"cc52db1474298bc25906294978c3eeef56df364a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-25 16:26:41 +01:00
Kibana Machine
e541bb29e5
[9.0] [Synthetics] Fix issue when selecting monitor frequency (#215823) (#215871) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Synthetics] Fix issue when selecting monitor frequency
(#215823)](https://github.com/elastic/kibana/pull/215823)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-03-25T13:16:37Z","message":"[Synthetics]
Fix issue when selecting monitor frequency (#215823)\n\nThis PR closes
issue #209188.\n\nIf the frequency is set to seconds, when setting it
back to minutes the\ntime unit is correctly
changed.\n\n\n\nhttps://github.com/user-attachments/assets/1a65b130-9740-41f1-94dc-f97cf887ff1a\n\n---------\n\nCo-authored-by:
Shahzad
<shahzad31comp@gmail.com>","sha":"7429c29522579f9c3e9d5c76df8ea58dca583d97","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.4","v9.0.1"],"title":"[Synthetics]
Fix issue when selecting monitor
frequency","number":215823,"url":"https://github.com/elastic/kibana/pull/215823","mergeCommit":{"message":"[Synthetics]
Fix issue when selecting monitor frequency (#215823)\n\nThis PR closes
issue #209188.\n\nIf the frequency is set to seconds, when setting it
back to minutes the\ntime unit is correctly
changed.\n\n\n\nhttps://github.com/user-attachments/assets/1a65b130-9740-41f1-94dc-f97cf887ff1a\n\n---------\n\nCo-authored-by:
Shahzad
<shahzad31comp@gmail.com>","sha":"7429c29522579f9c3e9d5c76df8ea58dca583d97"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215823","number":215823,"mergeCommit":{"message":"[Synthetics]
Fix issue when selecting monitor frequency (#215823)\n\nThis PR closes
issue #209188.\n\nIf the frequency is set to seconds, when setting it
back to minutes the\ntime unit is correctly
changed.\n\n\n\nhttps://github.com/user-attachments/assets/1a65b130-9740-41f1-94dc-f97cf887ff1a\n\n---------\n\nCo-authored-by:
Shahzad
<shahzad31comp@gmail.com>","sha":"7429c29522579f9c3e9d5c76df8ea58dca583d97"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
 2025-03-25 17:10:11 +02:00
Kibana Machine
dbf34e58ef
[9.0] [docs] Miscellaneous docs clean up (#215260) (#215860) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[docs] Miscellaneous docs clean up
(#215260)](https://github.com/elastic/kibana/pull/215260)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Colleen
McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T12:57:00Z","message":"[docs]
Miscellaneous docs clean up (#215260)\n\nMiscellaneous docs clean up
including: \n\n* [x] Removing unused substitutions\n* [x] Moving images
per https://github.com/elastic/docs-builder/pull/774\n* [x] ~~Clean up
redirecting links~~\n* [x] ~~Clean up asciidoc-style
links~~","sha":"5e5aff3b5b890abbb9652f8bef2484e10c8341c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","backport:version","v9.1.0"],"title":"[docs]
Miscellaneous docs clean
up","number":215260,"url":"https://github.com/elastic/kibana/pull/215260","mergeCommit":{"message":"[docs]
Miscellaneous docs clean up (#215260)\n\nMiscellaneous docs clean up
including: \n\n* [x] Removing unused substitutions\n* [x] Moving images
per https://github.com/elastic/docs-builder/pull/774\n* [x] ~~Clean up
redirecting links~~\n* [x] ~~Clean up asciidoc-style
links~~","sha":"5e5aff3b5b890abbb9652f8bef2484e10c8341c4"}},"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/215260","number":215260,"mergeCommit":{"message":"[docs]
Miscellaneous docs clean up (#215260)\n\nMiscellaneous docs clean up
including: \n\n* [x] Removing unused substitutions\n* [x] Moving images
per https://github.com/elastic/docs-builder/pull/774\n* [x] ~~Clean up
redirecting links~~\n* [x] ~~Clean up asciidoc-style
links~~","sha":"5e5aff3b5b890abbb9652f8bef2484e10c8341c4"}}]}]
BACKPORT-->

Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co>
 2025-03-25 13:26:30 +00:00
Kibana Machine
7e423e8ad2
[9.0] Unskip space solution tour test (#215519) (#215855) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Unskip space solution tour test
(#215519)](https://github.com/elastic/kibana/pull/215519)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Eyo O.
Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-25T11:10:45Z","message":"Unskip
space solution tour test (#215519)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/204082\n\nWhilst the
aforementioned issue has seen quite a number of failed tests\ninstances,
it's worth pointing out that for most of those instances on\nsecond
attempt the test usually passes. Running this particular test\nsuite
locally succeeds, for sanity sake, I also ran the same test
suite\nunskipped through the flaky test run for a 100 passes with
success in\nall instances.\n\nFYI;\nThe test in the referenced issue
checks that the on boarding tour\ndoesn't show after it's been
acknowleged.\n\n\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"23c74421b6d71a034ee28d2f2f51c725597dc571","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:prev-minor","v9.1.0"],"title":"Unskip
space solution tour test
","number":215519,"url":"https://github.com/elastic/kibana/pull/215519","mergeCommit":{"message":"Unskip
space solution tour test (#215519)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/204082\n\nWhilst the
aforementioned issue has seen quite a number of failed tests\ninstances,
it's worth pointing out that for most of those instances on\nsecond
attempt the test usually passes. Running this particular test\nsuite
locally succeeds, for sanity sake, I also ran the same test
suite\nunskipped through the flaky test run for a 100 passes with
success in\nall instances.\n\nFYI;\nThe test in the referenced issue
checks that the on boarding tour\ndoesn't show after it's been
acknowleged.\n\n\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"23c74421b6d71a034ee28d2f2f51c725597dc571"}},"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/215519","number":215519,"mergeCommit":{"message":"Unskip
space solution tour test (#215519)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/204082\n\nWhilst the
aforementioned issue has seen quite a number of failed tests\ninstances,
it's worth pointing out that for most of those instances on\nsecond
attempt the test usually passes. Running this particular test\nsuite
locally succeeds, for sanity sake, I also ran the same test
suite\nunskipped through the flaky test run for a 100 passes with
success in\nall instances.\n\nFYI;\nThe test in the referenced issue
checks that the on boarding tour\ndoesn't show after it's been
acknowleged.\n\n\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"23c74421b6d71a034ee28d2f2f51c725597dc571"}}]}]
BACKPORT-->

Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com>
 2025-03-25 15:23:38 +02:00
Kibana Machine
31409f1b1b
[9.0] Update enterprise test license, unskip tests (#215448) (#215853) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Update enterprise test license, unskip tests
(#215448)](https://github.com/elastic/kibana/pull/215448)

<!--- 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-25T10:41:40Z","message":"Update
enterprise test license, unskip tests (#215448)\n\n##
Summary\n\nAddresses
https://github.com/elastic/kibana/issues/53575","sha":"2556b13d347cfe796c39760808700a0a9e0d52d7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:all-open","v9.1.0"],"title":"Update
enterprise test license, unskip
tests","number":215448,"url":"https://github.com/elastic/kibana/pull/215448","mergeCommit":{"message":"Update
enterprise test license, unskip tests (#215448)\n\n##
Summary\n\nAddresses
https://github.com/elastic/kibana/issues/53575","sha":"2556b13d347cfe796c39760808700a0a9e0d52d7"}},"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/215448","number":215448,"mergeCommit":{"message":"Update
enterprise test license, unskip tests (#215448)\n\n##
Summary\n\nAddresses
https://github.com/elastic/kibana/issues/53575","sha":"2556b13d347cfe796c39760808700a0a9e0d52d7"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
 2025-03-25 14:39:06 +02:00
Kibana Machine
438e9506ab
[9.0] [Visualize] Unskip smoke test (#214960) (#215839) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Visualize] Unskip smoke test
(#214960)](https://github.com/elastic/kibana/pull/214960)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Marco
Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T09:30:07Z","message":"[Visualize]
Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing
skipped test\n\nThe reported issue was referring to an issue with a TSVB
chart that was\ntrying to load a missing data view.\nIf not explicitly
configured in the configuration, TSVB can load the\ndefault data view
configured in the Advanced Settings.\nThere is no mention of the missing
dataview ID in the the dashboard nor\nin the TSVB panel
configuration.\nThe TSVB configuration uses at this point the default
index coming from\nthe Advanced Settings, so that ID seems to be
configured as the default\nID but there is no loaded dataview with that
name.\nThe data view ID appearing in the error was referencing the
ecommerce\ndashboard, that was not used and not loaded in this test (all
charts\nrefers to the logs* data
view).\n\n\n![image](https://github.com/user-attachments/assets/d79c4945-11b5-4ee4-88a2-5b13ee9bc2f2)\n\nI
believe this issues was caused by other tests in the same
suite/config\nthat configured the `defaultIndex` setting without
unsetting
it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Visualizations","skipped-test","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Visualize]
Unskip smoke
test","number":214960,"url":"https://github.com/elastic/kibana/pull/214960","mergeCommit":{"message":"[Visualize]
Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing
skipped test\n\nThe reported issue was referring to an issue with a TSVB
chart that was\ntrying to load a missing data view.\nIf not explicitly
configured in the configuration, TSVB can load the\ndefault data view
configured in the Advanced Settings.\nThere is no mention of the missing
dataview ID in the the dashboard nor\nin the TSVB panel
configuration.\nThe TSVB configuration uses at this point the default
index coming from\nthe Advanced Settings, so that ID seems to be
configured as the default\nID but there is no loaded dataview with that
name.\nThe data view ID appearing in the error was referencing the
ecommerce\ndashboard, that was not used and not loaded in this test (all
charts\nrefers to the logs* data
view).\n\n\n![image](https://github.com/user-attachments/assets/d79c4945-11b5-4ee4-88a2-5b13ee9bc2f2)\n\nI
believe this issues was caused by other tests in the same
suite/config\nthat configured the `defaultIndex` setting without
unsetting
it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b"}},"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/214960","number":214960,"mergeCommit":{"message":"[Visualize]
Unskip smoke test (#214960)\n\n## Summary\n\nUnskipping and fixing
skipped test\n\nThe reported issue was referring to an issue with a TSVB
chart that was\ntrying to load a missing data view.\nIf not explicitly
configured in the configuration, TSVB can load the\ndefault data view
configured in the Advanced Settings.\nThere is no mention of the missing
dataview ID in the the dashboard nor\nin the TSVB panel
configuration.\nThe TSVB configuration uses at this point the default
index coming from\nthe Advanced Settings, so that ID seems to be
configured as the default\nID but there is no loaded dataview with that
name.\nThe data view ID appearing in the error was referencing the
ecommerce\ndashboard, that was not used and not loaded in this test (all
charts\nrefers to the logs* data
view).\n\n\n![image](https://github.com/user-attachments/assets/d79c4945-11b5-4ee4-88a2-5b13ee9bc2f2)\n\nI
believe this issues was caused by other tests in the same
suite/config\nthat configured the `defaultIndex` setting without
unsetting it.","sha":"12aa3fc6ca8124db8cf5e940baec121482fd1a4b"}}]}]
BACKPORT-->

Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co>
 2025-03-25 13:15:19 +02:00
Kibana Machine
d6b244241a
[9.0] Disable allowAbsoluteUrls for axios (#215138) (#215830) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Disable `allowAbsoluteUrls` for axios
(#215138)](https://github.com/elastic/kibana/pull/215138)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Alex
Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T08:52:36Z","message":"Disable
`allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter
https://github.com/elastic/kibana/pull/214843, `axios` client\nusages
need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers:
if you think it's a mistake, and you created a client to\nrequest for
absolute URLs, consider unsetting the `baseURL` to\ncommunicate
intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","Team:QA","Team:Security","release_note:skip","backport:all-open","Team:obs-ux-logs","Team:obs-ux-infra_services","v9.1.0"],"title":"Disable
`allowAbsoluteUrls` for
axios","number":215138,"url":"https://github.com/elastic/kibana/pull/215138","mergeCommit":{"message":"Disable
`allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter
https://github.com/elastic/kibana/pull/214843, `axios` client\nusages
need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers:
if you think it's a mistake, and you created a client to\nrequest for
absolute URLs, consider unsetting the `baseURL` to\ncommunicate
intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}},"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/215138","number":215138,"mergeCommit":{"message":"Disable
`allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter
https://github.com/elastic/kibana/pull/214843, `axios` client\nusages
need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers:
if you think it's a mistake, and you created a client to\nrequest for
absolute URLs, consider unsetting the `baseURL` to\ncommunicate
intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
 2025-03-25 12:43:09 +02:00
Kibana Machine
5f3a62c004
[9.0] [Synonyms] Update Synonyms Text and Enable (#215618) (#215814) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Synonyms] Update Synonyms Text and Enable
(#215618)](https://github.com/elastic/kibana/pull/215618)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Efe Gürkan
YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T23:30:55Z","message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\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] 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-
[ ] [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- [ ] [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\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Synonyms]
Update Synonyms Text and
Enable","number":215618,"url":"https://github.com/elastic/kibana/pull/215618","mergeCommit":{"message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\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] 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-
[ ] [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- [ ] [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\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215618","number":215618,"mergeCommit":{"message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\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] 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-
[ ] [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- [ ] [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\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co>
 2025-03-25 03:10:30 +02:00
Kibana Machine
8df649a47a
[9.0] [SecuritySolution] Fix host details flyout left panel tabs (#215672) (#215801) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[SecuritySolution] Fix host details flyout left panel tabs
(#215672)](https://github.com/elastic/kibana/pull/215672)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Pablo
Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T19:47:15Z","message":"[SecuritySolution]
Fix host details flyout left panel tabs (#215672)\n\n## Summary\n\nFix
Unable to switch between Risk Contributions and Insights on
host\ndetails flyout.\n\n\n**Pre Conditions**\n1. Alerts should be
available on Kibana.\n2. Entity Risk Score must be
enabled.\n\n**Steps**\n1. Navigate to a page where the flyout is
available.\n3. For any Entity, open details flyout\n4. Expand Details
flyout (left panel).\n5. Observe that the user cannot switch between
`Risk Contributions` and\n`Insights` tabs.\n\n**Expected Result**\nThe
user should be able to switch between `Risk Contributions`
and\n`Insights` tabs.\n\n**Screen
Recording**\n\n\nhttps://github.com/user-attachments/assets/3aae6291-5b5b-49a4-83c2-ac657e4e9524\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] [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":"6cdbeb95377cb95df567c067c03d0fa33d182b8c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:
SecuritySolution","Theme: entity_analytics","Feature:Entity
Analytics","Team:Entity
Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution]
Fix host details flyout left panel
tabs","number":215672,"url":"https://github.com/elastic/kibana/pull/215672","mergeCommit":{"message":"[SecuritySolution]
Fix host details flyout left panel tabs (#215672)\n\n## Summary\n\nFix
Unable to switch between Risk Contributions and Insights on
host\ndetails flyout.\n\n\n**Pre Conditions**\n1. Alerts should be
available on Kibana.\n2. Entity Risk Score must be
enabled.\n\n**Steps**\n1. Navigate to a page where the flyout is
available.\n3. For any Entity, open details flyout\n4. Expand Details
flyout (left panel).\n5. Observe that the user cannot switch between
`Risk Contributions` and\n`Insights` tabs.\n\n**Expected Result**\nThe
user should be able to switch between `Risk Contributions`
and\n`Insights` tabs.\n\n**Screen
Recording**\n\n\nhttps://github.com/user-attachments/assets/3aae6291-5b5b-49a4-83c2-ac657e4e9524\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] [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":"6cdbeb95377cb95df567c067c03d0fa33d182b8c"}},"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/215672","number":215672,"mergeCommit":{"message":"[SecuritySolution]
Fix host details flyout left panel tabs (#215672)\n\n## Summary\n\nFix
Unable to switch between Risk Contributions and Insights on
host\ndetails flyout.\n\n\n**Pre Conditions**\n1. Alerts should be
available on Kibana.\n2. Entity Risk Score must be
enabled.\n\n**Steps**\n1. Navigate to a page where the flyout is
available.\n3. For any Entity, open details flyout\n4. Expand Details
flyout (left panel).\n5. Observe that the user cannot switch between
`Risk Contributions` and\n`Insights` tabs.\n\n**Expected Result**\nThe
user should be able to switch between `Risk Contributions`
and\n`Insights` tabs.\n\n**Screen
Recording**\n\n\nhttps://github.com/user-attachments/assets/3aae6291-5b5b-49a4-83c2-ac657e4e9524\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] [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":"6cdbeb95377cb95df567c067c03d0fa33d182b8c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co>
 2025-03-24 23:31:19 +02:00
Kibana Machine
813cc115e9
[9.0] [Security Solution] Adding video links to the onboarding cards selector (#215215) (#215790) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Adding video links to the onboarding cards
selector (#215215)](https://github.com/elastic/kibana/pull/215215)

<!--- Backport version: 9.6.6 -->

### 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-03-24T18:23:49Z","message":"[Security
Solution] Adding video links to the onboarding cards selector
(#215215)\n\n## Summary\n\nThis PR adds the provided onboarding videos
to the corresponding\nthumbnail cards in the onboarding
experience.\nhttps://github.com/elastic/kibana/issues/215212\nThe videos
have been placed as
follows:\n\n\nhttps://github.com/user-attachments/assets/38254883-6a7d-46ac-bac7-df1334d66e3f\n\n\n`Rules
Card`\n\n[Video
1](https://videos.elastic.co/watch/2q7LSLrsC8qEFQUNHFu9zf)\n[Video
2](https://videos.elastic.co/watch/jpy1CcpBuowsA4a8t7gNDE)\n\n`Alerts
Card`\n\n[Video
1](https://videos.elastic.co/watch/Qgt9SCJqLmMN7P289ffSo4)\n[Video
2](https://videos.elastic.co/watch/nXC8MSkzDBWajoXWJ3QeQp)\n[Video
3](https://videos.elastic.co/watch/VSvxJeSQzrFN9K6hdeLz58)\n[Video
4](https://videos.elastic.co/watch/evxFZ8dqfjH6SGPtRriyE6)\n\n`Dashboards
Card`\n\n[Video
1](https://videos.elastic.co/watch/5UvJBpzFVoEfpDLnjzTbfn)\n[Video
2](https://videos.elastic.co/watch/SpKecbJxeYWzXVpGvgxMah)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] UI
Layout: Verify that the added videos do not break the existing\nlayout
or cause issues.\n\nCo-authored-by: Michael Olorunnisola
<michael.olorunnisola@elastic.co>","sha":"f723aa25d9076a190ba3ad14e14005e9b112e290","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","backport:prev-minor","ci:cloud-deploy","v9.1.0","v8.19.0"],"title":"[Security
Solution] Adding video links to the onboarding cards
selector","number":215215,"url":"https://github.com/elastic/kibana/pull/215215","mergeCommit":{"message":"[Security
Solution] Adding video links to the onboarding cards selector
(#215215)\n\n## Summary\n\nThis PR adds the provided onboarding videos
to the corresponding\nthumbnail cards in the onboarding
experience.\nhttps://github.com/elastic/kibana/issues/215212\nThe videos
have been placed as
follows:\n\n\nhttps://github.com/user-attachments/assets/38254883-6a7d-46ac-bac7-df1334d66e3f\n\n\n`Rules
Card`\n\n[Video
1](https://videos.elastic.co/watch/2q7LSLrsC8qEFQUNHFu9zf)\n[Video
2](https://videos.elastic.co/watch/jpy1CcpBuowsA4a8t7gNDE)\n\n`Alerts
Card`\n\n[Video
1](https://videos.elastic.co/watch/Qgt9SCJqLmMN7P289ffSo4)\n[Video
2](https://videos.elastic.co/watch/nXC8MSkzDBWajoXWJ3QeQp)\n[Video
3](https://videos.elastic.co/watch/VSvxJeSQzrFN9K6hdeLz58)\n[Video
4](https://videos.elastic.co/watch/evxFZ8dqfjH6SGPtRriyE6)\n\n`Dashboards
Card`\n\n[Video
1](https://videos.elastic.co/watch/5UvJBpzFVoEfpDLnjzTbfn)\n[Video
2](https://videos.elastic.co/watch/SpKecbJxeYWzXVpGvgxMah)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] UI
Layout: Verify that the added videos do not break the existing\nlayout
or cause issues.\n\nCo-authored-by: Michael Olorunnisola
<michael.olorunnisola@elastic.co>","sha":"f723aa25d9076a190ba3ad14e14005e9b112e290"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/215215","number":215215,"mergeCommit":{"message":"[Security
Solution] Adding video links to the onboarding cards selector
(#215215)\n\n## Summary\n\nThis PR adds the provided onboarding videos
to the corresponding\nthumbnail cards in the onboarding
experience.\nhttps://github.com/elastic/kibana/issues/215212\nThe videos
have been placed as
follows:\n\n\nhttps://github.com/user-attachments/assets/38254883-6a7d-46ac-bac7-df1334d66e3f\n\n\n`Rules
Card`\n\n[Video
1](https://videos.elastic.co/watch/2q7LSLrsC8qEFQUNHFu9zf)\n[Video
2](https://videos.elastic.co/watch/jpy1CcpBuowsA4a8t7gNDE)\n\n`Alerts
Card`\n\n[Video
1](https://videos.elastic.co/watch/Qgt9SCJqLmMN7P289ffSo4)\n[Video
2](https://videos.elastic.co/watch/nXC8MSkzDBWajoXWJ3QeQp)\n[Video
3](https://videos.elastic.co/watch/VSvxJeSQzrFN9K6hdeLz58)\n[Video
4](https://videos.elastic.co/watch/evxFZ8dqfjH6SGPtRriyE6)\n\n`Dashboards
Card`\n\n[Video
1](https://videos.elastic.co/watch/5UvJBpzFVoEfpDLnjzTbfn)\n[Video
2](https://videos.elastic.co/watch/SpKecbJxeYWzXVpGvgxMah)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] UI
Layout: Verify that the added videos do not break the existing\nlayout
or cause issues.\n\nCo-authored-by: Michael Olorunnisola
<michael.olorunnisola@elastic.co>","sha":"f723aa25d9076a190ba3ad14e14005e9b112e290"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com>
 2025-03-24 22:11:44 +02:00
Kibana Machine
9d9917c365
[9.0] [ci] More info to test annotation failure logging (#215515) (#215785) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[ci] More info to test annotation failure logging
(#215515)](https://github.com/elastic/kibana/pull/215515)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Alex
Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T18:01:32Z","message":"[ci]
More info to test annotation failure logging (#215515)\n\n##
Summary\nWhile annotating test failures, we're seeing increased amount
of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads
completed successfully\n--\n  | Annotate test failures error Request
failed with status code 404\n  | HTTP Error Response Status 404\n  |
HTTP Error Response Body { message: 'Not Found' }\n  | user command
error: exit status 10\n```\n\nIt would be nicer to show a bit more from
the error to help
debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:all-open","v9.1.0"],"title":"[ci]
More info to test annotation failure
logging","number":215515,"url":"https://github.com/elastic/kibana/pull/215515","mergeCommit":{"message":"[ci]
More info to test annotation failure logging (#215515)\n\n##
Summary\nWhile annotating test failures, we're seeing increased amount
of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads
completed successfully\n--\n  | Annotate test failures error Request
failed with status code 404\n  | HTTP Error Response Status 404\n  |
HTTP Error Response Body { message: 'Not Found' }\n  | user command
error: exit status 10\n```\n\nIt would be nicer to show a bit more from
the error to help
debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d"}},"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/215515","number":215515,"mergeCommit":{"message":"[ci]
More info to test annotation failure logging (#215515)\n\n##
Summary\nWhile annotating test failures, we're seeing increased amount
of errors\nlike this:\n```\n2025-03-21 13:52:32 INFO Artifact uploads
completed successfully\n--\n  | Annotate test failures error Request
failed with status code 404\n  | HTTP Error Response Status 404\n  |
HTTP Error Response Body { message: 'Not Found' }\n  | user command
error: exit status 10\n```\n\nIt would be nicer to show a bit more from
the error to help
debugging.","sha":"7120074ec32dcf693580244a01475a2af065a33d"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
 2025-03-24 21:47:40 +02:00
Kibana Machine
f795a24d77
[9.0] [Security Solution] Rework test plan for importing prebuilt rules (#213434) (#215796) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Rework test plan for importing prebuilt rules
(#213434)](https://github.com/elastic/kibana/pull/213434)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Georgii
Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T19:00:36Z","message":"[Security
Solution] Rework test plan for importing prebuilt rules
(#213434)\n\n**Epic:**
https://github.com/elastic/kibana/issues/174168\n**Partially
addresses:**\nhttps://github.com/elastic/kibana/issues/202079,\nhttps://github.com/elastic/kibana/issues/210358\n\n##
Summary\n\nWe started to rework and introduce functional changes to our
existing\ntest plans for prebuilt rule customization, upgrade, and
export/import\nworkflows.\n\nSpecifically, this PR:\n\n- Restructures
the test plan, introduces a more fine-grained list of\nsections.\n-
Rewrites almost all the existing scenarios. In most cases it boils\ndown
to splitting a scenario into 2+ more specific scenarios, where
each\ndescribes _exactly_ what happens in the GIVEN and THEN sections.
This is\nvery important, as it:\n- makes these scenarios ready to be
implemented right away: 1 scenario =\n1 test to write\n - helps with
ensuring that we covered edge cases\n- Adds new scenarios for handling
missing base versions according
to\n[#210358](https://github.com/elastic/kibana/issues/210358).\n- Adds
a placeholder section for licensing scenarios according
to\n[#11502](https://github.com/elastic/security-team/issues/11502).\n-
Removes scenarios for the `overwrite` request parameter - this
is\ncommon importing logic which is not related to prebuilt rules.\n-
Addresses my own comments from
[this\nreview](https://github.com/elastic/kibana/pull/206893#pullrequestreview-2633863218).\n\nThe
new test plan should be in line with the changes discussed
in\nhttps://github.com/elastic/kibana/issues/210358.","sha":"a9106c69904e259412df9bbc77b4411507e1d011","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Rework test plan for importing prebuilt
rules","number":213434,"url":"https://github.com/elastic/kibana/pull/213434","mergeCommit":{"message":"[Security
Solution] Rework test plan for importing prebuilt rules
(#213434)\n\n**Epic:**
https://github.com/elastic/kibana/issues/174168\n**Partially
addresses:**\nhttps://github.com/elastic/kibana/issues/202079,\nhttps://github.com/elastic/kibana/issues/210358\n\n##
Summary\n\nWe started to rework and introduce functional changes to our
existing\ntest plans for prebuilt rule customization, upgrade, and
export/import\nworkflows.\n\nSpecifically, this PR:\n\n- Restructures
the test plan, introduces a more fine-grained list of\nsections.\n-
Rewrites almost all the existing scenarios. In most cases it boils\ndown
to splitting a scenario into 2+ more specific scenarios, where
each\ndescribes _exactly_ what happens in the GIVEN and THEN sections.
This is\nvery important, as it:\n- makes these scenarios ready to be
implemented right away: 1 scenario =\n1 test to write\n - helps with
ensuring that we covered edge cases\n- Adds new scenarios for handling
missing base versions according
to\n[#210358](https://github.com/elastic/kibana/issues/210358).\n- Adds
a placeholder section for licensing scenarios according
to\n[#11502](https://github.com/elastic/security-team/issues/11502).\n-
Removes scenarios for the `overwrite` request parameter - this
is\ncommon importing logic which is not related to prebuilt rules.\n-
Addresses my own comments from
[this\nreview](https://github.com/elastic/kibana/pull/206893#pullrequestreview-2633863218).\n\nThe
new test plan should be in line with the changes discussed
in\nhttps://github.com/elastic/kibana/issues/210358.","sha":"a9106c69904e259412df9bbc77b4411507e1d011"}},"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/213434","number":213434,"mergeCommit":{"message":"[Security
Solution] Rework test plan for importing prebuilt rules
(#213434)\n\n**Epic:**
https://github.com/elastic/kibana/issues/174168\n**Partially
addresses:**\nhttps://github.com/elastic/kibana/issues/202079,\nhttps://github.com/elastic/kibana/issues/210358\n\n##
Summary\n\nWe started to rework and introduce functional changes to our
existing\ntest plans for prebuilt rule customization, upgrade, and
export/import\nworkflows.\n\nSpecifically, this PR:\n\n- Restructures
the test plan, introduces a more fine-grained list of\nsections.\n-
Rewrites almost all the existing scenarios. In most cases it boils\ndown
to splitting a scenario into 2+ more specific scenarios, where
each\ndescribes _exactly_ what happens in the GIVEN and THEN sections.
This is\nvery important, as it:\n- makes these scenarios ready to be
implemented right away: 1 scenario =\n1 test to write\n - helps with
ensuring that we covered edge cases\n- Adds new scenarios for handling
missing base versions according
to\n[#210358](https://github.com/elastic/kibana/issues/210358).\n- Adds
a placeholder section for licensing scenarios according
to\n[#11502](https://github.com/elastic/security-team/issues/11502).\n-
Removes scenarios for the `overwrite` request parameter - this
is\ncommon importing logic which is not related to prebuilt rules.\n-
Addresses my own comments from
[this\nreview](https://github.com/elastic/kibana/pull/206893#pullrequestreview-2633863218).\n\nThe
new test plan should be in line with the changes discussed
in\nhttps://github.com/elastic/kibana/issues/210358.","sha":"a9106c69904e259412df9bbc77b4411507e1d011"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
 2025-03-24 19:30:04 +00:00
Aleh Zasypkin
7779a13ded
[9.0] fix(security): topologically sort composable feature privileges before composing actions (#211035) (#215755) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [fix(security): topologically sort composable feature privileges
before composing actions
(#211035)](https://github.com/elastic/kibana/pull/211035)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Aleh
Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T13:09:36Z","message":"fix(security):
topologically sort composable feature privileges before composing
actions (#211035)\n\n## Summary\n\nThis PR changes the privilege's
actions merging logic for the composable\nand deprecated Kibana
features. The change makes it possible to have any\nnumber of composable
and deprecated features chained by `replaceBy`,\n`composedOf`, or a
combination of the two.\n\nUnder the hood, the privileges factory sorts
all deprecated and\ncomposable privileges using Kahn's algorithm for
topological sorting,\nsimilar to what is used to sort Kibana plugin
dependencies. This allows\nus to not only detect cyclical dependencies
but also sort privileges in\nthe proper order depending on their
dependency chain.\n\nThe use cases addressed by this change are best
illustrated by the\n`actions should respect composedOf when specified
with replaceBy at the\nprivilege` test in
`privileges.test.ts`.","sha":"6bbc4b67a589794c3b639a28cb87d82f3da0342a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Security/Authorization","backport:prev-major","v9.1.0"],"title":"fix(security):
topologically sort composable feature privileges before composing
actions","number":211035,"url":"https://github.com/elastic/kibana/pull/211035","mergeCommit":{"message":"fix(security):
topologically sort composable feature privileges before composing
actions (#211035)\n\n## Summary\n\nThis PR changes the privilege's
actions merging logic for the composable\nand deprecated Kibana
features. The change makes it possible to have any\nnumber of composable
and deprecated features chained by `replaceBy`,\n`composedOf`, or a
combination of the two.\n\nUnder the hood, the privileges factory sorts
all deprecated and\ncomposable privileges using Kahn's algorithm for
topological sorting,\nsimilar to what is used to sort Kibana plugin
dependencies. This allows\nus to not only detect cyclical dependencies
but also sort privileges in\nthe proper order depending on their
dependency chain.\n\nThe use cases addressed by this change are best
illustrated by the\n`actions should respect composedOf when specified
with replaceBy at the\nprivilege` test in
`privileges.test.ts`.","sha":"6bbc4b67a589794c3b639a28cb87d82f3da0342a"}},"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/211035","number":211035,"mergeCommit":{"message":"fix(security):
topologically sort composable feature privileges before composing
actions (#211035)\n\n## Summary\n\nThis PR changes the privilege's
actions merging logic for the composable\nand deprecated Kibana
features. The change makes it possible to have any\nnumber of composable
and deprecated features chained by `replaceBy`,\n`composedOf`, or a
combination of the two.\n\nUnder the hood, the privileges factory sorts
all deprecated and\ncomposable privileges using Kahn's algorithm for
topological sorting,\nsimilar to what is used to sort Kibana plugin
dependencies. This allows\nus to not only detect cyclical dependencies
but also sort privileges in\nthe proper order depending on their
dependency chain.\n\nThe use cases addressed by this change are best
illustrated by the\n`actions should respect composedOf when specified
with replaceBy at the\nprivilege` test in
`privileges.test.ts`.","sha":"6bbc4b67a589794c3b639a28cb87d82f3da0342a"}}]}]
BACKPORT-->
 2025-03-24 15:12:11 -04:00
Kibana Machine
0f7ddb0a4f
[9.0] Entity Analytics Dashboard refresh button breaks risk score tables: refetchEnginestatus Fix (#215472) (#215732) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [ Entity Analytics Dashboard refresh button breaks risk score tables:
refetchEnginestatus Fix
(#215472)](https://github.com/elastic/kibana/pull/215472)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Charlotte Alexandra
Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-24T14:51:37Z","message":"
Entity Analytics Dashboard refresh button breaks risk score tables:
refetchEnginestatus Fix (#215472)\n\n## Summary\n\nThis PR fixes the
issue where clicking the refresh button, the risk\nscore panel throws
errors, and the table displays no data.\nThe root cause was that the
`refetchAll` callback did not include\n`refetchEngineStatus`, which is
responsible for refreshing the risk\nengine status. As a result, the
risk engine status\n`hasEngineBeenInstalled` could become stale, leading
to incorrect\nbehavior.\n\n### Reproduce bug\n(as per
[#12017](https://github.com/elastic/security-team/issues/12017))\n\n**Preconditions**
\n\nKibana started with user and host data\nAlerts created\nEnable risk
engine\nTo Reproduce\n\n**Steps to reproduce the behavior:**\n\nOpen the
page and press refresh\nExpected behavior\nAll panels should
refresh\n\n### Screenshots: Fixed Version\nThe bug appeared only on the
static time options - \"Today\" and \"This\nWeek\". Fixed for both,
confirmed working for the other
options.\n\n\n\nhttps://github.com/user-attachments/assets/bf2866cf-4e16-466f-8686-0c1b0bf5e7cb","sha":"19d2776b18247e1acf732da5a21c30a77fd20fa6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:
SecuritySolution","Theme: entity_analytics","Feature:Entity
Analytics","Team:Entity
Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"
Entity Analytics Dashboard refresh button breaks risk score tables:
refetchEnginestatus
Fix","number":215472,"url":"https://github.com/elastic/kibana/pull/215472","mergeCommit":{"message":"
Entity Analytics Dashboard refresh button breaks risk score tables:
refetchEnginestatus Fix (#215472)\n\n## Summary\n\nThis PR fixes the
issue where clicking the refresh button, the risk\nscore panel throws
errors, and the table displays no data.\nThe root cause was that the
`refetchAll` callback did not include\n`refetchEngineStatus`, which is
responsible for refreshing the risk\nengine status. As a result, the
risk engine status\n`hasEngineBeenInstalled` could become stale, leading
to incorrect\nbehavior.\n\n### Reproduce bug\n(as per
[#12017](https://github.com/elastic/security-team/issues/12017))\n\n**Preconditions**
\n\nKibana started with user and host data\nAlerts created\nEnable risk
engine\nTo Reproduce\n\n**Steps to reproduce the behavior:**\n\nOpen the
page and press refresh\nExpected behavior\nAll panels should
refresh\n\n### Screenshots: Fixed Version\nThe bug appeared only on the
static time options - \"Today\" and \"This\nWeek\". Fixed for both,
confirmed working for the other
options.\n\n\n\nhttps://github.com/user-attachments/assets/bf2866cf-4e16-466f-8686-0c1b0bf5e7cb","sha":"19d2776b18247e1acf732da5a21c30a77fd20fa6"}},"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/215472","number":215472,"mergeCommit":{"message":"
Entity Analytics Dashboard refresh button breaks risk score tables:
refetchEnginestatus Fix (#215472)\n\n## Summary\n\nThis PR fixes the
issue where clicking the refresh button, the risk\nscore panel throws
errors, and the table displays no data.\nThe root cause was that the
`refetchAll` callback did not include\n`refetchEngineStatus`, which is
responsible for refreshing the risk\nengine status. As a result, the
risk engine status\n`hasEngineBeenInstalled` could become stale, leading
to incorrect\nbehavior.\n\n### Reproduce bug\n(as per
[#12017](https://github.com/elastic/security-team/issues/12017))\n\n**Preconditions**
\n\nKibana started with user and host data\nAlerts created\nEnable risk
engine\nTo Reproduce\n\n**Steps to reproduce the behavior:**\n\nOpen the
page and press refresh\nExpected behavior\nAll panels should
refresh\n\n### Screenshots: Fixed Version\nThe bug appeared only on the
static time options - \"Today\" and \"This\nWeek\". Fixed for both,
confirmed working for the other
options.\n\n\n\nhttps://github.com/user-attachments/assets/bf2866cf-4e16-466f-8686-0c1b0bf5e7cb","sha":"19d2776b18247e1acf732da5a21c30a77fd20fa6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com>
 2025-03-24 20:41:19 +02:00
Kibana Machine
8ad935e910
[9.0] Hide the chrome popup about leaked passwords (#215414) (#215481) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Hide the chrome popup about leaked passwords
(#215414)](https://github.com/elastic/kibana/pull/215414)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T12:04:25Z","message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","backport:all-open","v9.1.0"],"title":"Hide
the chrome popup about leaked
passwords","number":215414,"url":"https://github.com/elastic/kibana/pull/215414","mergeCommit":{"message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}},"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/215414","number":215414,"mergeCommit":{"message":"Hide
the chrome popup about leaked passwords (#215414)\n\n## Summary\nCloses
https://github.com/elastic/kibana/issues/214355\n\nTesting with Chrome
135.x.x.x resulted in a pop up that was breaking the\nflow of
tests:\n\n<img width=\"470\" alt=\"Screenshot 2025-03-20 at 4 25
17 PM\"\nsrc=\"https://github.com/user-attachments/assets/df908294-1881-4b6d-b9a2-3027b37b06ad\"\n/>\n\nThis
isn't captured by the screenshotting plugin, but is visible if you\nrun
`headless=0`\n\nThis adds the config to disable that popup since our
generic testing\npasswords are very common and therefor
flagged","sha":"f5cebe2c23dff4454ec948358cc0a938400d5ede"}}]}]
BACKPORT-->

Co-authored-by: Kurt <kc13greiner@users.noreply.github.com>
 2025-03-24 20:35:01 +02:00
Kibana Machine
29b255c23d
[9.0] [A11y][APM] Add aria-label to "Try our new inventory" button (#215633) (#215760) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[A11y][APM] Add `aria-label` to "Try our new inventory" button
(#215633)](https://github.com/elastic/kibana/pull/215633)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T16:12:15Z","message":"[A11y][APM]
Add `aria-label` to \"Try our new inventory\" button (#215633)\n\n##
Summary\n\nFixes #210253\n\nThis PR adds an `aria-label` with the same
content as the tooltip to\nsolve the \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Enable ECO feature flag\n3. Go into service inventory and run the
scanner from axe devtools\n4. You should see a critical error\n5.
Checkout this branch\n6. Error should be
solved\n\n---------\n\nCo-authored-by: Carlos Crespo
<crespocarlos@users.noreply.github.com>","sha":"7512aa30fa242e892f2729a1e2cd44e8a779341f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0"],"title":"[A11y][APM]
Add `aria-label` to \"Try our new inventory\" button
","number":215633,"url":"https://github.com/elastic/kibana/pull/215633","mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to \"Try our new inventory\" button (#215633)\n\n##
Summary\n\nFixes #210253\n\nThis PR adds an `aria-label` with the same
content as the tooltip to\nsolve the \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Enable ECO feature flag\n3. Go into service inventory and run the
scanner from axe devtools\n4. You should see a critical error\n5.
Checkout this branch\n6. Error should be
solved\n\n---------\n\nCo-authored-by: Carlos Crespo
<crespocarlos@users.noreply.github.com>","sha":"7512aa30fa242e892f2729a1e2cd44e8a779341f"}},"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/215633","number":215633,"mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to \"Try our new inventory\" button (#215633)\n\n##
Summary\n\nFixes #210253\n\nThis PR adds an `aria-label` with the same
content as the tooltip to\nsolve the \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Enable ECO feature flag\n3. Go into service inventory and run the
scanner from axe devtools\n4. You should see a critical error\n5.
Checkout this branch\n6. Error should be
solved\n\n---------\n\nCo-authored-by: Carlos Crespo
<crespocarlos@users.noreply.github.com>","sha":"7512aa30fa242e892f2729a1e2cd44e8a779341f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-03-24 20:11:39 +02:00
Kibana Machine
30fe2f3c69
[9.0] [Obs AI Assistant] Update EIS Elastic LLM naming (#215659) (#215754) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Obs AI Assistant] Update EIS Elastic LLM naming
(#215659)](https://github.com/elastic/kibana/pull/215659)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Viduni
Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T16:11:19Z","message":"[Obs
AI Assistant] Update EIS Elastic LLM naming (#215659)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/236\n\n##
Summary\n\n1. Renames name of model in model settings in search
playground from\n`Elastic LLM (AI Connector)` to `Elastic LLM`.\n\n<img
width=\"1616\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0be2ac02-1fcf-4167-b06e-de2e5af2f529\"\n/>\n\n2.
Renames the description of the Elastic LLM in the stack
connector\nflyout to `Use the Elastic LLM for your chat and RAG
usecases.`\n\n<img width=\"1620\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/15ad52de-c916-4653-bf06-ccf4adeff170\"\n/>\n\n###
Checklist\n\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)","sha":"1c738f6e1386e09569b0568d2ce656c8a0930f29","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
AI
Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs
AI Assistant] Update EIS Elastic LLM
naming","number":215659,"url":"https://github.com/elastic/kibana/pull/215659","mergeCommit":{"message":"[Obs
AI Assistant] Update EIS Elastic LLM naming (#215659)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/236\n\n##
Summary\n\n1. Renames name of model in model settings in search
playground from\n`Elastic LLM (AI Connector)` to `Elastic LLM`.\n\n<img
width=\"1616\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0be2ac02-1fcf-4167-b06e-de2e5af2f529\"\n/>\n\n2.
Renames the description of the Elastic LLM in the stack
connector\nflyout to `Use the Elastic LLM for your chat and RAG
usecases.`\n\n<img width=\"1620\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/15ad52de-c916-4653-bf06-ccf4adeff170\"\n/>\n\n###
Checklist\n\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)","sha":"1c738f6e1386e09569b0568d2ce656c8a0930f29"}},"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/215659","number":215659,"mergeCommit":{"message":"[Obs
AI Assistant] Update EIS Elastic LLM naming (#215659)\n\nCloses
https://github.com/elastic/obs-ai-assistant-team/issues/236\n\n##
Summary\n\n1. Renames name of model in model settings in search
playground from\n`Elastic LLM (AI Connector)` to `Elastic LLM`.\n\n<img
width=\"1616\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0be2ac02-1fcf-4167-b06e-de2e5af2f529\"\n/>\n\n2.
Renames the description of the Elastic LLM in the stack
connector\nflyout to `Use the Elastic LLM for your chat and RAG
usecases.`\n\n<img width=\"1620\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/15ad52de-c916-4653-bf06-ccf4adeff170\"\n/>\n\n###
Checklist\n\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)","sha":"1c738f6e1386e09569b0568d2ce656c8a0930f29"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co>
 2025-03-24 19:57:53 +02:00
Tiago Costa
84f56bd371
chore(NA): removing specific default version qualifiers from 9.0 (#215777) 
This removes the previous default version qualifier from 9.0 as we move
close to GA
 2025-03-24 17:55:22 +00:00
Kibana Machine
9cb8577b77
[9.0] [Fleet] Use fleet error in cspm plugin (#215625) (#215750) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Fleet] Use fleet error in cspm plugin
(#215625)](https://github.com/elastic/kibana/pull/215625)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-24T16:05:38Z","message":"[Fleet]
Use fleet error in cspm plugin (#215625)\n\n## Summary\n\nCloses
https://github.com/elastic/ingest-dev/issues/5266\n\nChanged Error to
FleetError in CSPM so that the error response code is\n400 instead of
500.\n500 is not appropriate, it triggers alerts in our serverless
SLOs.\n\n<img width=\"1777\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b9b0e8cf-db54-427a-bc45-db0b806a150f\"\n/>","sha":"33db17768fb9ad28a82c7f435a6766076b6ff6bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[Fleet]
Use fleet error in cspm
plugin","number":215625,"url":"https://github.com/elastic/kibana/pull/215625","mergeCommit":{"message":"[Fleet]
Use fleet error in cspm plugin (#215625)\n\n## Summary\n\nCloses
https://github.com/elastic/ingest-dev/issues/5266\n\nChanged Error to
FleetError in CSPM so that the error response code is\n400 instead of
500.\n500 is not appropriate, it triggers alerts in our serverless
SLOs.\n\n<img width=\"1777\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b9b0e8cf-db54-427a-bc45-db0b806a150f\"\n/>","sha":"33db17768fb9ad28a82c7f435a6766076b6ff6bb"}},"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/215625","number":215625,"mergeCommit":{"message":"[Fleet]
Use fleet error in cspm plugin (#215625)\n\n## Summary\n\nCloses
https://github.com/elastic/ingest-dev/issues/5266\n\nChanged Error to
FleetError in CSPM so that the error response code is\n400 instead of
500.\n500 is not appropriate, it triggers alerts in our serverless
SLOs.\n\n<img width=\"1777\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b9b0e8cf-db54-427a-bc45-db0b806a150f\"\n/>","sha":"33db17768fb9ad28a82c7f435a6766076b6ff6bb"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-03-24 19:54:11 +02:00
Kibana Machine
349e4472ee
[9.0] [Synthetics] Only return 404 if screenshot_ref is truly not present (#215241) (#215726) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Synthetics] Only return 404 if `screenshot_ref` is truly not present
(#215241)](https://github.com/elastic/kibana/pull/215241)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Justin
Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:18Z","message":"[Synthetics]
Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n##
Summary\n\nRight now we return a 404 anytime that the data we're looking
for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts
check on the\ndata before returning. It's possible that that data will
fail the check,\nand we'd return a 404 anyway. This isn't a very
accurate reflection of\nwhat's happening on the server, and could
indicate a problem with the\nuser's data.\n\nInstead, we first check if
the data returned from Elasticsearch is\n`null`, and if it is we return
a 404. Otherwise, we compute the type\ncheck like normal and return the
result. In the case where the data\nfails the type check, we instead
return a 500 and include the malformed\ndata in the server
response.\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"[Synthetics]
Only return 404 if `screenshot_ref` is truly not
present","number":215241,"url":"https://github.com/elastic/kibana/pull/215241","mergeCommit":{"message":"[Synthetics]
Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n##
Summary\n\nRight now we return a 404 anytime that the data we're looking
for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts
check on the\ndata before returning. It's possible that that data will
fail the check,\nand we'd return a 404 anyway. This isn't a very
accurate reflection of\nwhat's happening on the server, and could
indicate a problem with the\nuser's data.\n\nInstead, we first check if
the data returned from Elasticsearch is\n`null`, and if it is we return
a 404. Otherwise, we compute the type\ncheck like normal and return the
result. In the case where the data\nfails the type check, we instead
return a 500 and include the malformed\ndata in the server
response.\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7"}},"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/215241","number":215241,"mergeCommit":{"message":"[Synthetics]
Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n##
Summary\n\nRight now we return a 404 anytime that the data we're looking
for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts
check on the\ndata before returning. It's possible that that data will
fail the check,\nand we'd return a 404 anyway. This isn't a very
accurate reflection of\nwhat's happening on the server, and could
indicate a problem with the\nuser's data.\n\nInstead, we first check if
the data returned from Elasticsearch is\n`null`, and if it is we return
a 404. Otherwise, we compute the type\ncheck like normal and return the
result. In the case where the data\nfails the type check, we instead
return a 500 and include the malformed\ndata in the server
response.\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7"}}]}]
BACKPORT-->

Co-authored-by: Justin Kambic <jk@elastic.co>
 2025-03-24 18:38:49 +02:00
Kibana Machine
7ea6aa7f69
[9.0] [Lens] Fix inline dimension button label (#215476) (#215724) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Lens] Fix inline dimension button label
(#215476)](https://github.com/elastic/kibana/pull/215476)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Andreana
Malama","email":"72010092+andrimal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-24T14:35:47Z","message":"[Lens]
Fix inline dimension button label (#215476)\n\n## Summary\n\nFix for
#209696. \n\n<img width=\"368\" alt=\"Screenshot 2025-03-21 at 1 49
14 PM\"\nsrc=\"https://github.com/user-attachments/assets/69052665-a194-459b-9c2a-835f4230a99b\"\n/>\n<img
width=\"381\" alt=\"Screenshot 2025-03-21 at 1 49
53 PM\"\nsrc=\"https://github.com/user-attachments/assets/7cf6b7eb-4d1e-40fc-a28f-597634441eb1\"\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] 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---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a3fe0cd46090d5b3210c423469ee424e646eeb5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Lens]
Fix inline dimension button
label","number":215476,"url":"https://github.com/elastic/kibana/pull/215476","mergeCommit":{"message":"[Lens]
Fix inline dimension button label (#215476)\n\n## Summary\n\nFix for
#209696. \n\n<img width=\"368\" alt=\"Screenshot 2025-03-21 at 1 49
14 PM\"\nsrc=\"https://github.com/user-attachments/assets/69052665-a194-459b-9c2a-835f4230a99b\"\n/>\n<img
width=\"381\" alt=\"Screenshot 2025-03-21 at 1 49
53 PM\"\nsrc=\"https://github.com/user-attachments/assets/7cf6b7eb-4d1e-40fc-a28f-597634441eb1\"\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] 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---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a3fe0cd46090d5b3210c423469ee424e646eeb5f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215476","number":215476,"mergeCommit":{"message":"[Lens]
Fix inline dimension button label (#215476)\n\n## Summary\n\nFix for
#209696. \n\n<img width=\"368\" alt=\"Screenshot 2025-03-21 at 1 49
14 PM\"\nsrc=\"https://github.com/user-attachments/assets/69052665-a194-459b-9c2a-835f4230a99b\"\n/>\n<img
width=\"381\" alt=\"Screenshot 2025-03-21 at 1 49
53 PM\"\nsrc=\"https://github.com/user-attachments/assets/7cf6b7eb-4d1e-40fc-a28f-597634441eb1\"\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] 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---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco
Liberati
<dej611@users.noreply.github.com>","sha":"a3fe0cd46090d5b3210c423469ee424e646eeb5f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Andreana Malama <72010092+andrimal@users.noreply.github.com>
 2025-03-24 18:26:50 +02:00
Kibana Machine
deaee35a4e
[9.0] Fix plugin-list script (#215648) (#215713) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Fix plugin-list script
(#215648)](https://github.com/elastic/kibana/pull/215648)

<!--- 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-24T13:53:17Z","message":"Fix
plugin-list script (#215648)\n\n## Summary\n\nA [recent
PR](https://github.com/elastic/kibana/pull/212558/files) (3\nweeks ago)
migrated docs under `/docs` folder, from `.asciidoc`
to\n`.md`.\n\nUnfortunately, some of these docs (well, at least one)
were generated\nautomatically using a script:\n\n`node
scripts/build_plugin_list_docs.js` was updating
the\n`docs/developer/plugin-list.asciidoc`\n\nAs a result of the
migration:\n\nThe CI pipeline step fails, and the list of plugins is no
longer\nupdated.\nBesides:\n* The
https://www.elastic.co/guide/en/kibana/current/plugin-list.html
is\ncurrently broken.\n* This page is (or should be) built
from\nhttps://github.com/elastic/kibana/blob/main/docs/extend/plugin-list.md,\nwhich
is also broken.\n\nThey are broken cause some plugins' descriptions use
the pipe `|`\ncharacter, which breaks the Markdown layout.\n\nThis PR
updates the logic that generates the plugin-list, switching
from\n`.asciidoc` to `.md`, and escaping `\\n` and `|` characters to
allow for\nbetter
descriptions.","sha":"366a0da35ce94ccf6b1bf01ec356549f512361d2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Team:Operations","release_note:skip","v9.0.0","backport:version","v9.1.0","v9.0.1"],"title":"Fix
plugin-list
script","number":215648,"url":"https://github.com/elastic/kibana/pull/215648","mergeCommit":{"message":"Fix
plugin-list script (#215648)\n\n## Summary\n\nA [recent
PR](https://github.com/elastic/kibana/pull/212558/files) (3\nweeks ago)
migrated docs under `/docs` folder, from `.asciidoc`
to\n`.md`.\n\nUnfortunately, some of these docs (well, at least one)
were generated\nautomatically using a script:\n\n`node
scripts/build_plugin_list_docs.js` was updating
the\n`docs/developer/plugin-list.asciidoc`\n\nAs a result of the
migration:\n\nThe CI pipeline step fails, and the list of plugins is no
longer\nupdated.\nBesides:\n* The
https://www.elastic.co/guide/en/kibana/current/plugin-list.html
is\ncurrently broken.\n* This page is (or should be) built
from\nhttps://github.com/elastic/kibana/blob/main/docs/extend/plugin-list.md,\nwhich
is also broken.\n\nThey are broken cause some plugins' descriptions use
the pipe `|`\ncharacter, which breaks the Markdown layout.\n\nThis PR
updates the logic that generates the plugin-list, switching
from\n`.asciidoc` to `.md`, and escaping `\\n` and `|` characters to
allow for\nbetter
descriptions.","sha":"366a0da35ce94ccf6b1bf01ec356549f512361d2"}},"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/215648","number":215648,"mergeCommit":{"message":"Fix
plugin-list script (#215648)\n\n## Summary\n\nA [recent
PR](https://github.com/elastic/kibana/pull/212558/files) (3\nweeks ago)
migrated docs under `/docs` folder, from `.asciidoc`
to\n`.md`.\n\nUnfortunately, some of these docs (well, at least one)
were generated\nautomatically using a script:\n\n`node
scripts/build_plugin_list_docs.js` was updating
the\n`docs/developer/plugin-list.asciidoc`\n\nAs a result of the
migration:\n\nThe CI pipeline step fails, and the list of plugins is no
longer\nupdated.\nBesides:\n* The
https://www.elastic.co/guide/en/kibana/current/plugin-list.html
is\ncurrently broken.\n* This page is (or should be) built
from\nhttps://github.com/elastic/kibana/blob/main/docs/extend/plugin-list.md,\nwhich
is also broken.\n\nThey are broken cause some plugins' descriptions use
the pipe `|`\ncharacter, which breaks the Markdown layout.\n\nThis PR
updates the logic that generates the plugin-list, switching
from\n`.asciidoc` to `.md`, and escaping `\\n` and `|` characters to
allow for\nbetter
descriptions.","sha":"366a0da35ce94ccf6b1bf01ec356549f512361d2"}}]}]
BACKPORT-->

---------

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
 2025-03-24 18:03:17 +02:00
Elena Shostak
b9652ca9b1
[9.0] Unauthorized route migration for routes owned by appex-sharedux (#214779) (#215704) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Unauthorized route migration for routes owned by appex-sharedux
(#214779)](https://github.com/elastic/kibana/pull/214779)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T17:00:53Z","message":"Unauthorized
route migration for routes owned by appex-sharedux (#214779)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a7cc00c4fe16d15584bd032bea729453d3b5fcac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","backport
missing","Team:SharedUX","backport:prev-minor","backport:version","Authz:
API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration
for routes owned by
appex-sharedux","number":214779,"url":"https://github.com/elastic/kibana/pull/214779","mergeCommit":{"message":"Unauthorized
route migration for routes owned by appex-sharedux (#214779)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a7cc00c4fe16d15584bd032bea729453d3b5fcac"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214779","number":214779,"mergeCommit":{"message":"Unauthorized
route migration for routes owned by appex-sharedux (#214779)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"a7cc00c4fe16d15584bd032bea729453d3b5fcac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-24 17:58:36 +02:00
Kibana Machine
2d53e251aa
[9.0] feat(slo): add saved query (#215566) (#215595) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [feat(slo): add saved query
(#215566)](https://github.com/elastic/kibana/pull/215566)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Kevin
Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T23:45:53Z","message":"feat(slo):
add saved query (#215566)\n\nResolves
https://github.com/elastic/kibana/issues/214478\n\n## Summary\n\nAdd
options to save query and load saved query to the various\nQueryBuilder
used in the SLO
form.\n\n\n\nhttps://github.com/user-attachments/assets/dbc614a9-add1-4781-b577-e5abc2b8ea24","sha":"f5424e0c51668bdc7f81575abb5366347beb9c02","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","v9.1.0","v8.19.0","v8.18.1","v8.17.4"],"title":"feat(slo):
add saved
query","number":215566,"url":"https://github.com/elastic/kibana/pull/215566","mergeCommit":{"message":"feat(slo):
add saved query (#215566)\n\nResolves
https://github.com/elastic/kibana/issues/214478\n\n## Summary\n\nAdd
options to save query and load saved query to the various\nQueryBuilder
used in the SLO
form.\n\n\n\nhttps://github.com/user-attachments/assets/dbc614a9-add1-4781-b577-e5abc2b8ea24","sha":"f5424e0c51668bdc7f81575abb5366347beb9c02"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18","8.17"],"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/215566","number":215566,"mergeCommit":{"message":"feat(slo):
add saved query (#215566)\n\nResolves
https://github.com/elastic/kibana/issues/214478\n\n## Summary\n\nAdd
options to save query and load saved query to the various\nQueryBuilder
used in the SLO
form.\n\n\n\nhttps://github.com/user-attachments/assets/dbc614a9-add1-4781-b577-e5abc2b8ea24","sha":"f5424e0c51668bdc7f81575abb5366347beb9c02"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co>
 2025-03-24 17:45:47 +02:00
Kibana Machine
9eacca23e1
[9.0] [ObsUX][A11y] Add area label to comparison drop down (#215664) (#215717) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[ObsUX][A11y] Add area label to comparison drop down
(#215664)](https://github.com/elastic/kibana/pull/215664)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-24T13:59:22Z","message":"[ObsUX][A11y]
Add area label to comparison drop down (#215664)\n\nCloses
https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51
01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49
51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd","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-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX][A11y]
Add area label to comparison drop
down","number":215664,"url":"https://github.com/elastic/kibana/pull/215664","mergeCommit":{"message":"[ObsUX][A11y]
Add area label to comparison drop down (#215664)\n\nCloses
https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51
01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49
51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd"}},"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/215664","number":215664,"mergeCommit":{"message":"[ObsUX][A11y]
Add area label to comparison drop down (#215664)\n\nCloses
https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51
01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img
width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49
51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
 2025-03-24 17:45:29 +02:00
Kibana Machine
6f39c1173a
[9.0] [Security Solution] Update prebuilt rule customization test plans to reflect licensing changes (#215008) (#215731) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Update prebuilt rule customization test plans to
reflect licensing changes
(#215008)](https://github.com/elastic/kibana/pull/215008)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:34Z","message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com/elastic/kibana/pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](https://github.com/elastic/kibana/pull/206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing
changes","number":215008,"url":"https://github.com/elastic/kibana/pull/215008","mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com/elastic/kibana/pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](https://github.com/elastic/kibana/pull/206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},"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/215008","number":215008,"mergeCommit":{"message":"[Security
Solution] Update prebuilt rule customization test plans to reflect
licensing changes (#215008)\n\n**Partially addresses:
https://github.com/elastic/kibana/issues/202068**\n**Related PR with
licensing checks
implementation:\nhttps://github.com/elastic/kibana/pull/206079**\n\n##
Summary\nThis PR updates the Prebuilt Rule Customization test plan to
reflect\n[recent changes](https://github.com/elastic/kibana/pull/206079)
related\nto licensing.\n\nChanges to rule upgrade scenarios will be
handled in a separate
PR.","sha":"2929f2857d585a6c1c60e09fc3616083527af410"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
 2025-03-24 15:25:24 +00:00
Kibana Machine
7943eefdc3
[9.0] [A11y][APM] Add aria-label to latency selector in service overview (#215644) (#215695) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[A11y][APM] Add `aria-label` to latency selector in service overview
(#215644)](https://github.com/elastic/kibana/pull/215644)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T12:54:17Z","message":"[A11y][APM]
Add `aria-label` to latency selector in service overview (#215644)\n\n##
Summary\n\nFixes #210270\n\nThis PR adds an `aria-label` to solve the
\"Element missing an accessible\nname\" A11y critical issue.\n\n## How
to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"6665dd377a5b9f20873e8491308a8e156c5ec460","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0"],"title":"[A11y][APM]
Add `aria-label` to latency selector in service
overview","number":215644,"url":"https://github.com/elastic/kibana/pull/215644","mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to latency selector in service overview (#215644)\n\n##
Summary\n\nFixes #210270\n\nThis PR adds an `aria-label` to solve the
\"Element missing an accessible\nname\" A11y critical issue.\n\n## How
to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"6665dd377a5b9f20873e8491308a8e156c5ec460"}},"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/215644","number":215644,"mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to latency selector in service overview (#215644)\n\n##
Summary\n\nFixes #210270\n\nThis PR adds an `aria-label` to solve the
\"Element missing an accessible\nname\" A11y critical issue.\n\n## How
to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"6665dd377a5b9f20873e8491308a8e156c5ec460"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-03-24 17:12:57 +02:00
Kibana Machine
6a0e800bf9
[9.0] [A11y][APM] Add aria-label to popover service in service overview (#215640) (#215696) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[A11y][APM] Add `aria-label` to popover service in service overview
(#215640)](https://github.com/elastic/kibana/pull/215640)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T12:54:30Z","message":"[A11y][APM]
Add `aria-label` to popover service in service overview (#215640)\n\n##
Summary\n\nFixes #210258\n\nThis PR adds an `aria-label` with the same
content as the title to solve\nthe \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"2654b8c702ae29dd2aad4fe9471d95dbdd8b17df","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0"],"title":"[A11y][APM]
Add `aria-label` to popover service in service
overview","number":215640,"url":"https://github.com/elastic/kibana/pull/215640","mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to popover service in service overview (#215640)\n\n##
Summary\n\nFixes #210258\n\nThis PR adds an `aria-label` with the same
content as the title to solve\nthe \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"2654b8c702ae29dd2aad4fe9471d95dbdd8b17df"}},"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/215640","number":215640,"mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to popover service in service overview (#215640)\n\n##
Summary\n\nFixes #210258\n\nThis PR adds an `aria-label` with the same
content as the title to solve\nthe \"Button must have a discernible
text\" A11y critical issue.\n\n## How to test\n1. Download the
[axe\ndevtools](https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd)\n2.
Go into a service overview and run the scanner from axe devtools\n3. You
should see a critical error\n4. Checkout this branch\n5. Error should be
solved","sha":"2654b8c702ae29dd2aad4fe9471d95dbdd8b17df"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-03-24 16:54:16 +02:00
jennypavlova
ba6aa259b1
[9.0] [APM] Fix: Add missing user_agent version field and show it on the trace summary (#215403) (#215550) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[APM] Fix: Add missing user_agent version field and show it on the
trace summary (#215403)](https://github.com/elastic/kibana/pull/215403)

<!--- Backport version: 9.6.6 -->

### 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-03-21T17:33:01Z","message":"[APM]
Fix: Add missing user_agent version field and show it on the trace
summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the
`USER_AGENT_VERSION` missing field to the\n`optionalFields` query
fields\n\n## Testing\n\n- Find a trace with user agent version (on the
edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to
the transaction tab (in case of `elastic-co-frontend` click
on\n`/blog/:id`)\nIf the user agent version is available it should be
visible in the trace\nsummary:\n\n<img width=\"1155\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM]
Fix: Add missing user_agent version field and show it on the trace
summary","number":215403,"url":"https://github.com/elastic/kibana/pull/215403","mergeCommit":{"message":"[APM]
Fix: Add missing user_agent version field and show it on the trace
summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the
`USER_AGENT_VERSION` missing field to the\n`optionalFields` query
fields\n\n## Testing\n\n- Find a trace with user agent version (on the
edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to
the transaction tab (in case of `elastic-co-frontend` click
on\n`/blog/:id`)\nIf the user agent version is available it should be
visible in the trace\nsummary:\n\n<img width=\"1155\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248"}},"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/215403","number":215403,"mergeCommit":{"message":"[APM]
Fix: Add missing user_agent version field and show it on the trace
summary (#215403)\n\nCloses #215229 \n\n## Summary\n\nThis PR adds the
`USER_AGENT_VERSION` missing field to the\n`optionalFields` query
fields\n\n## Testing\n\n- Find a trace with user agent version (on the
edge oblt we have it for\n`elastic-co-frontend` for example)\n- Go to
the transaction tab (in case of `elastic-co-frontend` click
on\n`/blog/:id`)\nIf the user agent version is available it should be
visible in the trace\nsummary:\n\n<img width=\"1155\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/75b7e331-44d0-4d1c-8060-815c269e23c9\"\n/>","sha":"42a66131c529ff3f48a037abd40fef118a09d248"}}]}]
BACKPORT-->
 2025-03-24 13:48:16 +02:00
Kibana Machine
3de7305e4b
[9.0] [Storybook] Use native theme switcher (#215443) (#215630) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Storybook] Use native theme switcher
(#215443)](https://github.com/elastic/kibana/pull/215443)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T08:54:15Z","message":"[Storybook]
Use native theme switcher (#215443)\n\n## Summary\n\nCloses
#213294\n\nThis PR replaces the custom theme switcher in favor of the
native\ntoolbar customization SB has integrated.\n\nAlso removed
`@storybook/icons` which was only used in the theme\nswitcher
component.\n\n## How to test\n1. Run `yarn storybook <plugin>`\n2. You
should be able to change between themes on the
toolbar.","sha":"965a69d9fbf47b5a7054c0ed8eeb60687e6707bc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Storybook","backport:prev-minor","ci:build-storybooks","Team:obs-ux-infra_services","v9.1.0"],"title":"[Storybook]
Use native theme
switcher","number":215443,"url":"https://github.com/elastic/kibana/pull/215443","mergeCommit":{"message":"[Storybook]
Use native theme switcher (#215443)\n\n## Summary\n\nCloses
#213294\n\nThis PR replaces the custom theme switcher in favor of the
native\ntoolbar customization SB has integrated.\n\nAlso removed
`@storybook/icons` which was only used in the theme\nswitcher
component.\n\n## How to test\n1. Run `yarn storybook <plugin>`\n2. You
should be able to change between themes on the
toolbar.","sha":"965a69d9fbf47b5a7054c0ed8eeb60687e6707bc"}},"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/215443","number":215443,"mergeCommit":{"message":"[Storybook]
Use native theme switcher (#215443)\n\n## Summary\n\nCloses
#213294\n\nThis PR replaces the custom theme switcher in favor of the
native\ntoolbar customization SB has integrated.\n\nAlso removed
`@storybook/icons` which was only used in the theme\nswitcher
component.\n\n## How to test\n1. Run `yarn storybook <plugin>`\n2. You
should be able to change between themes on the
toolbar.","sha":"965a69d9fbf47b5a7054c0ed8eeb60687e6707bc"}}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-03-24 13:42:32 +02:00
Kibana Machine
d8d718b6fd
[9.0] Update dependency elastic-apm-node to ^4.11.2 (main) (#214940) (#215632) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Update dependency elastic-apm-node to ^4.11.2 (main)
(#214940)](https://github.com/elastic/kibana/pull/214940)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-24T08:55:26Z","message":"Update
dependency elastic-apm-node to ^4.11.2 (main) (#214940)\n\nThis PR
contains the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n|
dependencies | patch | [`^4.11.1`
->\n`^4.11.2`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.1/4.11.2)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs
(elastic-apm-node)</summary>\n\n###\n[`v4.11.2`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.2)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.1...v4.11.2)\n\nFor
more information, please see
the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.2).\n\n#####
Elastic APM Node.js agent layer
ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"f81572e4627b4d9bc7515f146ffe0c8ec87c7e82","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update
dependency elastic-apm-node to ^4.11.2
(main)","number":214940,"url":"https://github.com/elastic/kibana/pull/214940","mergeCommit":{"message":"Update
dependency elastic-apm-node to ^4.11.2 (main) (#214940)\n\nThis PR
contains the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n|
dependencies | patch | [`^4.11.1`
->\n`^4.11.2`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.1/4.11.2)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs
(elastic-apm-node)</summary>\n\n###\n[`v4.11.2`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.2)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.1...v4.11.2)\n\nFor
more information, please see
the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.2).\n\n#####
Elastic APM Node.js agent layer
ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"f81572e4627b4d9bc7515f146ffe0c8ec87c7e82"}},"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/214940","number":214940,"mergeCommit":{"message":"Update
dependency elastic-apm-node to ^4.11.2 (main) (#214940)\n\nThis PR
contains the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n|
dependencies | patch | [`^4.11.1`
->\n`^4.11.2`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.1/4.11.2)\n|\n\n---\n\n###
Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs
(elastic-apm-node)</summary>\n\n###\n[`v4.11.2`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.2)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.1...v4.11.2)\n\nFor
more information, please see
the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.2).\n\n#####
Elastic APM Node.js agent layer
ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-2:1|\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"f81572e4627b4d9bc7515f146ffe0c8ec87c7e82"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-03-24 12:48:07 +02:00
Dzmitry Lemechko
db02ecf630
[9.0] [scout] Remove perf stats validation for Discover (#215130) (#215610) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[scout] Remove perf stats validation for Discover
(#215130)](https://github.com/elastic/kibana/pull/215130)

<!--- Backport version: 9.6.6 -->

### 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-03-22T18:31:54Z","message":"[scout]
Remove perf stats validation for Discover (#215130)\n\n##
Summary\n\nWith #212397 we added 2 tests for Discover app (loading
`/app/discover`)\nto track:\n- js bundles loaded on page\n- perf metrics
like CPU time, Layout time and Script time fetched with\nCDP Performance
Domain API\n\nWhile the first test for bundles _didn't report any
failures_, second\ntest to validate Perf metrics fails
periodically:\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34729#0195a4de-6cd5-4d1e-be11-5d02be6de2b0\n```\nError:
CPU time (seconds) usage during page navigation should not exceed 1.5
seconds\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
1.5\nReceived:
1.591343\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34877\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived:
0.601434\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34899\n```\nError:
Total layout computation time should not exceed 0.06
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.06\nReceived:
0.061723\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34912#0195adb8-4536-42b7-ab4d-524535fdad9a\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived: 0.561259\n```\n\nIt was worth an experiment, but due to
flakiness we decided to keep only\nbundles limits validation for now and
see if it is stable in the long\nrun.\n\nIf Data-Discovery team has
interest in collecting Perf metrics without\nstrict validation in PRs,
we can discuss the options. Alternatively we\ncan wait for Scout GA and
you can deep dive into your own performance\ntesting with
Playwright/CDP.","sha":"4dc27ba4aaa5bbc0a18a1964f58f2f63e2ccde16","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","test:scout","v9.1.0","v8.19.0"],"title":"[scout]
Remove perf stats validation for
Discover","number":215130,"url":"https://github.com/elastic/kibana/pull/215130","mergeCommit":{"message":"[scout]
Remove perf stats validation for Discover (#215130)\n\n##
Summary\n\nWith #212397 we added 2 tests for Discover app (loading
`/app/discover`)\nto track:\n- js bundles loaded on page\n- perf metrics
like CPU time, Layout time and Script time fetched with\nCDP Performance
Domain API\n\nWhile the first test for bundles _didn't report any
failures_, second\ntest to validate Perf metrics fails
periodically:\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34729#0195a4de-6cd5-4d1e-be11-5d02be6de2b0\n```\nError:
CPU time (seconds) usage during page navigation should not exceed 1.5
seconds\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
1.5\nReceived:
1.591343\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34877\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived:
0.601434\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34899\n```\nError:
Total layout computation time should not exceed 0.06
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.06\nReceived:
0.061723\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34912#0195adb8-4536-42b7-ab4d-524535fdad9a\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived: 0.561259\n```\n\nIt was worth an experiment, but due to
flakiness we decided to keep only\nbundles limits validation for now and
see if it is stable in the long\nrun.\n\nIf Data-Discovery team has
interest in collecting Perf metrics without\nstrict validation in PRs,
we can discuss the options. Alternatively we\ncan wait for Scout GA and
you can deep dive into your own performance\ntesting with
Playwright/CDP.","sha":"4dc27ba4aaa5bbc0a18a1964f58f2f63e2ccde16"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/215130","number":215130,"mergeCommit":{"message":"[scout]
Remove perf stats validation for Discover (#215130)\n\n##
Summary\n\nWith #212397 we added 2 tests for Discover app (loading
`/app/discover`)\nto track:\n- js bundles loaded on page\n- perf metrics
like CPU time, Layout time and Script time fetched with\nCDP Performance
Domain API\n\nWhile the first test for bundles _didn't report any
failures_, second\ntest to validate Perf metrics fails
periodically:\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34729#0195a4de-6cd5-4d1e-be11-5d02be6de2b0\n```\nError:
CPU time (seconds) usage during page navigation should not exceed 1.5
seconds\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
1.5\nReceived:
1.591343\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34877\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived:
0.601434\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34899\n```\nError:
Total layout computation time should not exceed 0.06
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.06\nReceived:
0.061723\n```\n\n\nhttps://buildkite.com/elastic/kibana-on-merge-unsupported-ftrs/builds/34912#0195adb8-4536-42b7-ab4d-524535fdad9a\n```\nError:
Additional time spent executing JS scripts should not exceed 0.5
second\n\nexpect(received).toBeLessThan(expected)\n\nExpected: <
0.5\nReceived: 0.561259\n```\n\nIt was worth an experiment, but due to
flakiness we decided to keep only\nbundles limits validation for now and
see if it is stable in the long\nrun.\n\nIf Data-Discovery team has
interest in collecting Perf metrics without\nstrict validation in PRs,
we can discuss the options. Alternatively we\ncan wait for Scout GA and
you can deep dive into your own performance\ntesting with
Playwright/CDP.","sha":"4dc27ba4aaa5bbc0a18a1964f58f2f63e2ccde16"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-24 11:34:35 +01:00
Paulina Shakirova
15f5173b24
[9.0] [fleet] fix overlay in integrations on mobile (#215312) (#215607) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[fleet] fix overlay in integrations on mobile
(#215312)](https://github.com/elastic/kibana/pull/215312)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Paulina
Shakirova","email":"paulina.shakirova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T18:50:12Z","message":"[fleet]
fix overlay in integrations on mobile (#215312)\n\n## Summary\n\nThis PR
resolves [Integrations
overlay\nmobile-view](https://github.com/elastic/kibana/issues/214146)
issue.","sha":"b39b8c4591609380719cf4f7ae6f2224b9a9c9fa","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport
missing","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[fleet]
fix overlay in integrations on
mobile","number":215312,"url":"https://github.com/elastic/kibana/pull/215312","mergeCommit":{"message":"[fleet]
fix overlay in integrations on mobile (#215312)\n\n## Summary\n\nThis PR
resolves [Integrations
overlay\nmobile-view](https://github.com/elastic/kibana/issues/214146)
issue.","sha":"b39b8c4591609380719cf4f7ae6f2224b9a9c9fa"}},"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/215312","number":215312,"mergeCommit":{"message":"[fleet]
fix overlay in integrations on mobile (#215312)\n\n## Summary\n\nThis PR
resolves [Integrations
overlay\nmobile-view](https://github.com/elastic/kibana/issues/214146)
issue.","sha":"b39b8c4591609380719cf4f7ae6f2224b9a9c9fa"}}]}]
BACKPORT-->
 2025-03-24 09:30:18 +01:00
Kibana Machine
ce8c17c9d9
[9.0] Register resident set size and limit bytes metrics in APM (#215458) (#215617) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Register resident set size and limit bytes metrics in APM
(#215458)](https://github.com/elastic/kibana/pull/215458)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Jesus
Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-23T21:22:30Z","message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\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] [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] 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)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","backport:current-major","v9.1.0"],"title":"Register
resident set size and limit bytes metrics in
APM","number":215458,"url":"https://github.com/elastic/kibana/pull/215458","mergeCommit":{"message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\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] [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] 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)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}},"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/215458","number":215458,"mergeCommit":{"message":"Register
resident set size and limit bytes metrics in APM (#215458)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana-team/issues/1565\n\nRegister resident
set size and limit bytes metrics in APM.\n\n<img width=\"1614\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5f1caf5-da4f-4acd-a63f-2b5256a91307\"\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] [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] 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)","sha":"04772fcc456aa6b03d9ecec540cc927c23c0dd9a"}}]}]
BACKPORT-->

Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>
 2025-03-24 01:07:05 +02:00
Kibana Machine
6d39f4e844
[9.0] [Lens] fix drag and drop ghost after Chrome update to 134 (#213928) (#214127) 
# Backport

This will backport the following commits from `main` to `9.0`:
 - https://github.com/elastic/kibana/pull/213928
 - https://github.com/elastic/kibana/pull/215439

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Marta
Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T11:30:51Z","message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","backport:prev-major","Feature:UnifiedFieldList","v9.1.0"],"title":"[Lens]
fix drag and drop ghost after Chrome update to
134","number":213928,"url":"https://github.com/elastic/kibana/pull/213928","mergeCommit":{"message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}},"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/213928","number":213928,"mergeCommit":{"message":"[Lens]
fix drag and drop ghost after Chrome update to 134 (#213928)\n\n##
Summary\nFixes https://github.com/elastic/kibana/issues/213708\n\nFixes
the ghost display. As @nickofthyme pointed
out\n[here](https://github.com/elastic/kibana/issues/213708#issuecomment-2712076212),\nthe
reason was using inset-inline-start: -10000px for the keyboard\nhandler
that is one of the children of the draggable component. The\nquick fix
is to just move it outside of the html element that is\ndragged.
@markov00 please assesswhere it should be merged
🙏🏼\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"84ae9c98c208957b3efc02c6b00bed8d567d4209"}}]}]
BACKPORT-->

---------

Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>
Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co>
 2025-03-22 03:05:12 +02:00
Kibana Machine
4c93922f99
[9.0] [Security Solution] [Attack discovery] Prompt updates (#215578) (#215590) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [ [Security Solution] [Attack discovery] Prompt updates
(#215578)](https://github.com/elastic/kibana/pull/215578)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Andrew
Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T23:06:37Z","message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Security Generative
AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"
[Security Solution] [Attack discovery] Prompt
updates","number":215578,"url":"https://github.com/elastic/kibana/pull/215578","mergeCommit":{"message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"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/215578","number":215578,"mergeCommit":{"message":"
[Security Solution] [Attack discovery] Prompt updates (#215578)\n\n##
[Security Solution] [Attack discovery] Prompt updates\n\nThis PR
contains updates to the following Attack discovery prompts:\n\n-
`attackDiscoveryPrompt`\n- `continuePrompt`\n- `refinePrompt`\n\nThank
you @mgarzon for these
improvements!","sha":"d52c5ed85cf31a14f3ee2b4c4d1ace62237fb23f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Andrew Macri <andrew.macri@elastic.co>
 2025-03-22 02:50:23 +02:00
Gloria Hornero
4695a7822a
[9.0] initial @kbn/scout-security plugin (#210433) (#215528) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [initial @kbn/scout-security plugin
(#210433)](https://github.com/elastic/kibana/pull/210433)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Gloria
Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T10:59:30Z","message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:version","Team: Sec Eng
Productivity","test:scout","v9.1.0","v8.19.0"],"title":"initial
@kbn/scout-security
plugin","number":210433,"url":"https://github.com/elastic/kibana/pull/210433","mergeCommit":{"message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},"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/210433","number":210433,"mergeCommit":{"message":"initial
@kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are
adding the initial structure for the\n@kibana/scout-security package,
note that this is not ready to be used\nand any new test using this
package, is not going to be executed as part\nof the regular pipelines,
meaning, you are not going to add coverage to\nthe
application.
\n\n@kibana/scout-security package is a test package that
extends @kbn/scout\nwith test helpers specifically designed to test
Security Solution\nfunctionalities in Kibana. All tests under Security
plugins should only\nimport from @kbn/scout-security, not
from @kbn/scout.

\n\nThis PR is a POC to start testing development by
providing custom\nPlaywright fixtures, page objects, and utilities
tailored for\nSecurity-related testing scenarios.\n\nThings to
follow-up:

\n\n- CustomQueryRule interface is already declared
in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas
`QueryRuleCreateProps`
\n- DETECTION_ENGINE_RULES_URL and
DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in
`@kbn/security-solution-plugin/common/constants`\n\nIt would be great if
all of that is extracted from the plugin to a\npackage so it can be
reused instead of having to duplicate the code.\n\nUntil the package is
not ready to be used and has not been introduced to\nthe different
teams, appex-qa and myself will be the owners of it to\nmake sure that
best practices are followed\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215527","number":215527,"state":"OPEN"}]}]
BACKPORT-->

---------

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2025-03-21 23:46:49 +02:00
Dzmitry Lemechko
32da780375
[9.0] [scout] extend config-discovery with CI validator (#214403) (#215340) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[scout] extend config-discovery with CI validator
(#214403)](https://github.com/elastic/kibana/pull/214403)

<!--- Backport version: 9.6.6 -->

### 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-03-18T20:24:54Z","message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366","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","test:scout","v9.1.0","v8.19.0"],"title":"[scout]
extend config-discovery with CI
validator","number":214403,"url":"https://github.com/elastic/kibana/pull/214403","mergeCommit":{"message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"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/214403","number":214403,"mergeCommit":{"message":"[scout]
extend config-discovery with CI validator (#214403)\n\n##
Summary\n\nMore teams are adding Scout tests in their plugins, often as
a PoC and\nnot stable yet for continuous execution.\nWe don't want to
block it, but need a way to manage the scope of Scout\npipeline and be
able to disable it quickly to unblock the Scout\ndevelopment.\n\nSince
Scout is in active development and we need it to be simple and\nquick as
possible (we can iterate and improve later), we agreed with\nRobert to
disable tests by plugin:\n\n```\nui_tests:\n enabled:\n - apm\n -
discover_enhanced\n - maps\n - observability_onboarding\n disabled:\n -
*skipped_plugin*\n```\n\nWhen scout configuration is added to the new
plugin, it will require to\nupdate `.buildkite/scout_ci_config.yml` that
is owned by `appex-qa`\nteam. If there is no intention to run Scout
tests on CI, plugin name\nshould be added under `disabled`
section.\n\n**How to test locally:**\n\n- Scout tests were added in
`observability_onboarding` plugin, pipeline\nwill throw error\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n```\n\nrun `node
scripts/scout discover-playwright-configs --validate
--save`\n\n```\nERROR The following plugins are not registered in Scout
CI config '.buildkite/scout_ci_config.yml'\n -
observability_onboarding\n```\n\n~~On CI annotation will be added to
clarify the failure:~~\n\nwe decided to move validation to \"Quick
Checks\", no need to annotate.\n\n<img width=\"1583\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed6b5778-74cb-4473-8218-b96239aab067\"\n/>\n\n\n-
`observability_onboarding` plugin is disabled, pipeline won't
include\nit (excluded in `scout_playwright_configs.json`)\n\nmodify
locally `.buildkite/scout_ci_config.yml`\n```\nui_tests:\n enabled:\n -
apm\n - discover_enhanced\n - maps\n disabled:\n -
observability_onboarding\n```\n\nrun `node scripts/scout
discover-playwright-configs --validate --save`\n\n```\n warn The
following plugins are disabled in '.buildkite/scout_ci_config.yml' and
will be excluded from CI run\n - observability_onboarding\n info Found
Playwright config files in '4' plugins.\n Saved '3' plugins to
'/Users/dmle/github/kibana/.scout/test_configs/scout_playwright_configs.json'\n```","sha":"05447fe978cd5fedbbaaf09e3f3d8ee41b760366"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-03-21 20:38:58 +01:00
Kibana Machine
8a3b6297d2
[9.0] Unauthorized route migration for routes owned by kibana-management (#214782) (#215539) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Unauthorized route migration for routes owned by kibana-management
(#214782)](https://github.com/elastic/kibana/pull/214782)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Elena
Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T16:37:07Z","message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","Team:Kibana
Management","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz:
API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration
for routes owned by
kibana-management","number":214782,"url":"https://github.com/elastic/kibana/pull/214782","mergeCommit":{"message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214782","number":214782,"mergeCommit":{"message":"Unauthorized
route migration for routes owned by kibana-management (#214782)\n\n###
Authz API migration for unauthorized routes\n\nThis PR migrates last
unauthorized routes owned by your team to a new\nsecurity
configuration.\nPlease refer to the documentation for more information:
[Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n###
**Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n
...\n}, handler);\n```\n\n### **After
migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n
authz: {\n enabled: false,\n reason: 'This route is opted out from
authorization because ...',\n },\n },\n ...\n},
handler);\n```","sha":"2160dd1d956a4d6dc6366dd0116ea68d58792537"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>
 2025-03-21 20:52:32 +02:00
Kibana Machine
ae0422a878
[9.0] [Fleet] update disabled inputs (#215512) (#215536) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Fleet] update disabled inputs
(#215512)](https://github.com/elastic/kibana/pull/215512)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T16:19:37Z","message":"[Fleet]
update disabled inputs (#215512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/215411\n\nDisable `aws-s3` and
`streaming` as an input type for agentless\n\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9ee96838-919c-4be3-851b-51afad6b6e06\"\n/>\n<img
width=\"1470\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a6f702cf-6885-4512-ae04-7074cbfa0a40\"\n/>","sha":"04cc68a2cb99f72595443c4f31d9f0de4e129845","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[Fleet]
update disabled
inputs","number":215512,"url":"https://github.com/elastic/kibana/pull/215512","mergeCommit":{"message":"[Fleet]
update disabled inputs (#215512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/215411\n\nDisable `aws-s3` and
`streaming` as an input type for agentless\n\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9ee96838-919c-4be3-851b-51afad6b6e06\"\n/>\n<img
width=\"1470\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a6f702cf-6885-4512-ae04-7074cbfa0a40\"\n/>","sha":"04cc68a2cb99f72595443c4f31d9f0de4e129845"}},"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/215512","number":215512,"mergeCommit":{"message":"[Fleet]
update disabled inputs (#215512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/215411\n\nDisable `aws-s3` and
`streaming` as an input type for agentless\n\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9ee96838-919c-4be3-851b-51afad6b6e06\"\n/>\n<img
width=\"1470\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a6f702cf-6885-4512-ae04-7074cbfa0a40\"\n/>","sha":"04cc68a2cb99f72595443c4f31d9f0de4e129845"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-03-21 20:19:14 +02:00
Kibana Machine
cd881bece5
[9.0] Updates navigation titles and descriptions for release notes (#215422) (#215540) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Updates navigation titles and descriptions for release notes
(#215422)](https://github.com/elastic/kibana/pull/215422)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Kaarina
Tungseth","email":"kaarina.tungseth@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T16:56:16Z","message":"Updates
navigation titles and descriptions for release notes (#215422)\n\n##
Summary\n\nUpdates the navigation titles, adds short descriptions, and
removes\nrelease
dates.","sha":"9bbfb7e7afb2e76f6aca0ed8c1862b188e9f4827","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"Updates
navigation titles and descriptions for release
notes","number":215422,"url":"https://github.com/elastic/kibana/pull/215422","mergeCommit":{"message":"Updates
navigation titles and descriptions for release notes (#215422)\n\n##
Summary\n\nUpdates the navigation titles, adds short descriptions, and
removes\nrelease
dates.","sha":"9bbfb7e7afb2e76f6aca0ed8c1862b188e9f4827"}},"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/215422","number":215422,"mergeCommit":{"message":"Updates
navigation titles and descriptions for release notes (#215422)\n\n##
Summary\n\nUpdates the navigation titles, adds short descriptions, and
removes\nrelease
dates.","sha":"9bbfb7e7afb2e76f6aca0ed8c1862b188e9f4827"}}]}]
BACKPORT-->

Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
 2025-03-21 17:25:28 +00:00
Kibana Machine
ecba121c96
[9.0] [EDR Workflows] Enable skipped defend workflows management cypress tests - response console processes (#215467) (#215524) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[EDR Workflows] Enable skipped defend workflows management cypress
tests - response console processes
(#215467)](https://github.com/elastic/kibana/pull/215467)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Gergő
Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T15:06:09Z","message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34","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:Defend
Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console
processes","number":215467,"url":"https://github.com/elastic/kibana/pull/215467","mergeCommit":{"message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34"}},"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/215467","number":215467,"mergeCommit":{"message":"[EDR
Workflows] Enable skipped defend workflows management cypress tests -
response console processes (#215467)\n\n## Summary\n\nthis PR unskips
and fixes defend workflows cypress tests\n\nflaky
runner:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8073\n-
50/50 ESS cypress ✅\n- serverless ✅ - lot of serverless tests failed
because of metering\ncypress test, but not because of processes
test\n\n> [!note]\n> flaky runner was performed together with metering
cypress test (see\nhttps://github.com/elastic/kibana/issues/187083),
which is indeed flaky,\nso it's removed from this PR\n\n\n- closes:
https://github.com/elastic/kibana/issues/170371\n- closes:
https://github.com/elastic/kibana/issues/170370\n- needs to be
backported to 8.18, 8.x, 9.0\n\n### Checklist\n\nCheck the PR satisfies
following conditions. \n\nReviewers should verify this PR satisfies this
list as well.\n\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"a3f6c179b2da72cebc0be9920f3b85c4f9110a34"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
 2025-03-21 19:05:12 +02:00
Bailey Cash
6fe8399078
[9.0] [SLO] Check for unique SLO ids across spaces (#214496) (#215379) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[SLO] Check for unique SLO ids across spaces
(#214496)](https://github.com/elastic/kibana/pull/214496)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Bailey
Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T14:44:58Z","message":"[SLO]
Check for unique SLO ids across spaces (#214496)\n\n## Summary
\nResolves #212784 \nEnsure that when an SLO is created, the id is
verified across all\nspaces.\n\n## Release Notes\nEnsure that when an
SLO is created, the id is verified across all\nspaces.\n\n## Testing\n1.
Create an SLO and save the id returned in the response in a space
\"A\"\n2. Create a second SLO with the id saved from the first SLO in
the\nrequest in a different space \"B\"\n3. User should receive a 409
error from the SLO API.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"56f1ebfca6300b1da68cf6fa721f450077aa1878","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","backport
missing","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"[SLO]
Check for unique SLO ids across
spaces","number":214496,"url":"https://github.com/elastic/kibana/pull/214496","mergeCommit":{"message":"[SLO]
Check for unique SLO ids across spaces (#214496)\n\n## Summary
\nResolves #212784 \nEnsure that when an SLO is created, the id is
verified across all\nspaces.\n\n## Release Notes\nEnsure that when an
SLO is created, the id is verified across all\nspaces.\n\n## Testing\n1.
Create an SLO and save the id returned in the response in a space
\"A\"\n2. Create a second SLO with the id saved from the first SLO in
the\nrequest in a different space \"B\"\n3. User should receive a 409
error from the SLO API.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"56f1ebfca6300b1da68cf6fa721f450077aa1878"}},"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/214496","number":214496,"mergeCommit":{"message":"[SLO]
Check for unique SLO ids across spaces (#214496)\n\n## Summary
\nResolves #212784 \nEnsure that when an SLO is created, the id is
verified across all\nspaces.\n\n## Release Notes\nEnsure that when an
SLO is created, the id is verified across all\nspaces.\n\n## Testing\n1.
Create an SLO and save the id returned in the response in a space
\"A\"\n2. Create a second SLO with the id saved from the first SLO in
the\nrequest in a different space \"B\"\n3. User should receive a 409
error from the SLO API.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"56f1ebfca6300b1da68cf6fa721f450077aa1878"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-03-21 18:07:37 +02:00
Kibana Machine
5ac71db387
[9.0] [Security Solution][Telemetry] Add ingest pipelines stats task (#213435) (#215502) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution][Telemetry] Add ingest pipelines stats task
(#213435)](https://github.com/elastic/kibana/pull/213435)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Sebastián
Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T13:38:58Z","message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\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] [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] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:prev-minor","backport:prev-major","ci:build-cloud-image","ci:cloud-deploy","v9.1.0"],"title":"[Security
Solution][Telemetry] Add ingest pipelines stats
task","number":213435,"url":"https://github.com/elastic/kibana/pull/213435","mergeCommit":{"message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\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] [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] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859"}},"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/213435","number":213435,"mergeCommit":{"message":"[Security
Solution][Telemetry] Add ingest pipelines stats task (#213435)\n\n##
Summary\n\nAdd a new telemetry task to the security solution plugin to
collect\ningest pipeline stats. The new task runs once a day, calls
the\n`_nodes/stats/ingest` API, and sends an EBT event with the
following\ninformation:\n\n```js\nexport interface
NodeIngestPipelinesStats {\n name: string;\n totals: Totals;\n
pipelines: Pipeline[];\n}\n\nexport interface Pipeline {\n name:
string;\n totals: Totals;\n processors: Processor[];\n}\n\nexport
interface Processor {\n name: string;\n totals: Totals;\n}\n\nexport
interface Totals {\n count: number;\n time_in_millis: number;\n current:
number;\n failed: number;\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] [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] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n\n---------\n\nCo-authored-by: Elastic
Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"9cf3bea759591738cec5847454d789d33ff1d859"}}]}]
BACKPORT-->

Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co>
 2025-03-21 17:42:03 +02:00
Kibana Machine
b6a0e0eee5
[9.0] [SecuritySolution][Endpoint] Re-enable endpoint permissions functional tests (#215446) (#215493) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[SecuritySolution][Endpoint] Re-enable endpoint permissions
functional tests
(#215446)](https://github.com/elastic/kibana/pull/215446)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T13:10:53Z","message":"[SecuritySolution][Endpoint]
Re-enable endpoint permissions functional tests (#215446)\n\n##
Summary\n\nUnskips the skipped FTR test.\ncloses
https://github.com/elastic/kibana/issues/191243\n\n### Flaky runner\n-
only the permission tests
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8071\nx
100 (all green)\n- all tests in the group
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8072\nx
100 ( all green)\n\n### Checklist\n\nCheck the PR satisfies following
conditions. \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- [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- [ ] 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":"bcf0d10df2d6ab58734fc55aa230945f2eb744cc","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:Defend
Workflows","OLM
Sprint","backport:version","v9.1.0"],"title":"[SecuritySolution][Endpoint]
Re-enable endpoint permissions functional
tests","number":215446,"url":"https://github.com/elastic/kibana/pull/215446","mergeCommit":{"message":"[SecuritySolution][Endpoint]
Re-enable endpoint permissions functional tests (#215446)\n\n##
Summary\n\nUnskips the skipped FTR test.\ncloses
https://github.com/elastic/kibana/issues/191243\n\n### Flaky runner\n-
only the permission tests
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8071\nx
100 (all green)\n- all tests in the group
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8072\nx
100 ( all green)\n\n### Checklist\n\nCheck the PR satisfies following
conditions. \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- [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- [ ] 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":"bcf0d10df2d6ab58734fc55aa230945f2eb744cc"}},"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/215446","number":215446,"mergeCommit":{"message":"[SecuritySolution][Endpoint]
Re-enable endpoint permissions functional tests (#215446)\n\n##
Summary\n\nUnskips the skipped FTR test.\ncloses
https://github.com/elastic/kibana/issues/191243\n\n### Flaky runner\n-
only the permission tests
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8071\nx
100 (all green)\n- all tests in the group
-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8072\nx
100 ( all green)\n\n### Checklist\n\nCheck the PR satisfies following
conditions. \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- [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- [ ] 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":"bcf0d10df2d6ab58734fc55aa230945f2eb744cc"}}]}]
BACKPORT-->

Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>
 2025-03-21 17:12:40 +02:00
Kibana Machine
c0a9009362
[9.0] [Security Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage on the Risk Score web page (#215304) (#215440) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution][Risk Score] Use Risk Engine SavedObject intead of
localStorage on the Risk Score web page
(#215304)](https://github.com/elastic/kibana/pull/215304)

<!--- Backport version: 9.6.6 -->

### 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-03-21T08:49:24Z","message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\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] [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] [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)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Entity
Analytics","backport:version","v9.1.0"],"title":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web
page","number":215304,"url":"https://github.com/elastic/kibana/pull/215304","mergeCommit":{"message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\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] [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] [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)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e"}},"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/215304","number":215304,"mergeCommit":{"message":"[Security
Solution][Risk Score] Use Risk Engine SavedObject intead of localStorage
on the Risk Score web page (#215304)\n\n## Summary\n\nThe PR updates the
implementation to fetch data from the Risk Engine\nSaved Object instead
of storing and reusing it from LocalStorage.\n\nThis change ensures that
settings are applied globally rather than being\nlimited to the
browser’s LocalStorage. Since the Saved Object holds the\nmost
up-to-date information, it is now used to update the \"Date\" and
the\ntoggle for \"including closed alerts for risk scoring\" across all
web\nbrowsers.\n\n\n### Normal and Incognito Mode :
\n\n\n\nhttps://github.com/user-attachments/assets/7638c88b-ff9e-4d42-9944-e55b53e33518\n\n\n###
Default space vs custom space :
\n\n\n\nhttps://github.com/user-attachments/assets/46bb35c7-3cd9-4b97-9f1c-90ec4ef1241a\n\n\n##
Testing Steps\n\n### Verify Initial Values\n1. Open the Entity Risk
Score web page where the settings are applied.\n2. Ensure that the date
picker and toggle for \"including closed alerts\"\nreflect the values
stored in the Risk Engine Saved Object rather than\nLocalStorage.\n3.
Modify and Save changes,\n - Change the date range in the date picker.\n
- Toggle the \"Include Closed Alerts\" switch.\n\n### Page Refresh
Test\n- Refresh the page and confirm that the modified values persist,
fetched\ncorrectly from the Risk Engine Saved Object.\n\n###
Cross-Browser Test\n- Open the same web page in a different browser or
incognito mode.\n- Verify that the settings are consistent and correctly
loaded from the\nRisk Engine Saved\n Object.\n\n### Expected
Outcome\nThe settings should persist after a page refresh or across
different\nbrowsers.\nThe latest values should always be pulled from the
Risk Engine Saved\nObject.\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] [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] [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)","sha":"dbe28b9f94a16fa09684f65ae813eb178672d14e"}}]}]
BACKPORT-->

Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com>
 2025-03-21 16:58:41 +02:00
Kibana Machine
9b73c01bd6
[9.0] Change "Close project" to "Log out" in nav menu in serverless mode (#211463) (#215486) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Change "Close project" to "Log out" in nav menu in serverless mode
(#211463)](https://github.com/elastic/kibana/pull/211463)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Paulina
Shakirova","email":"paulina.shakirova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T12:38:44Z","message":"Change
\"Close project\" to \"Log out\" in nav menu in serverless mode
(#211463)\n\n## Summary\n\nThis PR resolves [Unify user profile menu
\"Log\nout\"option](https://github.com/elastic/kibana/issues/209278)
issue.","sha":"6a9a1eeb8afd814fe3ada6ef487bc03185f6c63d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:SharedUX","backport:prev-minor","papercut","ci:project-deploy-observability","ci:project-redeploy","v9.1.0"],"title":"Change
\"Close project\" to \"Log out\" in nav menu in serverless
mode","number":211463,"url":"https://github.com/elastic/kibana/pull/211463","mergeCommit":{"message":"Change
\"Close project\" to \"Log out\" in nav menu in serverless mode
(#211463)\n\n## Summary\n\nThis PR resolves [Unify user profile menu
\"Log\nout\"option](https://github.com/elastic/kibana/issues/209278)
issue.","sha":"6a9a1eeb8afd814fe3ada6ef487bc03185f6c63d"}},"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/211463","number":211463,"mergeCommit":{"message":"Change
\"Close project\" to \"Log out\" in nav menu in serverless mode
(#211463)\n\n## Summary\n\nThis PR resolves [Unify user profile menu
\"Log\nout\"option](https://github.com/elastic/kibana/issues/209278)
issue.","sha":"6a9a1eeb8afd814fe3ada6ef487bc03185f6c63d"}}]}]
BACKPORT-->

Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co>
 2025-03-21 16:53:54 +02:00
Kibana Machine
53e55c2307
[9.0] [EDR Workflows] Unskip management Jest tests (#215324) (#215485) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[EDR Workflows] Unskip management Jest tests
(#215324)](https://github.com/elastic/kibana/pull/215324)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Konrad
Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T12:26:30Z","message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc","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:Defend
Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[EDR
Workflows] Unskip management Jest
tests","number":215324,"url":"https://github.com/elastic/kibana/pull/215324","mergeCommit":{"message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc"}},"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/215324","number":215324,"mergeCommit":{"message":"[EDR
Workflows] Unskip management Jest tests (#215324)\n\n8.17 PR -
https://github.com/elastic/kibana/pull/215474\nPart of
https://github.com/elastic/security-team/issues/12176\n\nUnskiped: \n###
`use_list_artifact.test.tsx`\nPath\n`.../plugins/security_solution/public/management/hooks/artifacts/use_list_artifact.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/196724\nCommit
438553a1d167d97cc730405783e21963b6a790a7\nReason for unskipping:
Couldn't recreate failure locally. Increased\ntimeout from 1000 to 5000
ms.\n\n\n###
`actions_log_users_filter.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/endpoint_response_actions_list/components/actions_log_users_filter.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193554\nhttps://github.com/elastic/kibana/issues/193092\nCommit
ca7b97168318ca39eedb5afa6f67fe5e0ea304ed\nde03fd5448740e5d3b7059fedbd2cd511bec110f\nfb3910e738fab4e158852f60f4f5471732a5b191\nReason
for unskipping: wrapped expects in waitFor since they are\nawaiting for
state change. Increased the delay between keystrokes when\ntyping.
Increased the timeout of tests since locally they are bordering\n5s
executions.\n\n###
`bad_argument.test.tsx`\nPath\n`.../plugins/security_solution/public/management/components/console/components/bad_argument.test.tsx`\nCloses
https://github.com/elastic/kibana/issues/193093\nCommit
6959cd2e3fb53fb4c13d482456cf9ce76682f332\nReason for unskipping: wrapped
expects in waitFor since they are\nawaiting for state change. Increased
timeout to 10s.\n\n###
`use_get_endpoint_details.test.ts`\nPath\n`.../plugins/security_solution/public/management/hooks/endpoint/use_get_endpoint_details.test.ts`\nCloses
https://github.com/elastic/kibana/issues/192435\nCommit
3ba10029b62cc63db2c2565de2a2e9ec5b913539\nReason for unskipping:
increased timeout of waitFor for\nrenderReactQueryHook to 5s since
locally it was bordering 3
seconds","sha":"f09945bb1b5d4e00a953da8a8cd8d677f3d21ecc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>
 2025-03-21 16:34:14 +02:00