Commit graph

81046 commits

Author SHA1 Message Date
Kibana Machine
a0ae908d11
[8.17] Improve accessibility in create connector flyout (#218426) (#218680)
# Backport

This will backport the following commits from `main` to `8.17`:
- [Improve accessibility in create connector flyout
(#218426)](https://github.com/elastic/kibana/pull/218426)

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

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

<!--BACKPORT [{"author":{"name":"Arturo
Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-04-18T20:32:17Z","message":"Improve
accessibility in create connector flyout (#218426)\n\npart of #212776
\n\n## Summary\nImproves screen reader accessibility for the GenAI
connector panels in\nthe Observability AI Assistant by providing more
descriptive\nannouncements when these panels are opened. Previously,
Kibana would\nannounce a generic modal dialog message (from EUI) without
context,\nwhich could confuse screen reader users.\n\n###
Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on
the “Set up\nGenAI connector” button, Kibana announces a generic message
like “modal\ndialog” without explaining what the modal is about.\n\n###
Fix\n•\tInclude aria-label to the `CreateConnectorFlyout`
component\n\n### How to Test\n1.\tNavigate to Observability → AI
Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick
“Set up GenAI connector”\n4.\tVerify that the screen reader announces
\"create connector
flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:feature","backport:prev-minor","backport:prev-major","Team:Obs
AI Assistant","v9.1.0"],"title":"Improve accessibility in create
connector flyout
","number":218426,"url":"https://github.com/elastic/kibana/pull/218426","mergeCommit":{"message":"Improve
accessibility in create connector flyout (#218426)\n\npart of #212776
\n\n## Summary\nImproves screen reader accessibility for the GenAI
connector panels in\nthe Observability AI Assistant by providing more
descriptive\nannouncements when these panels are opened. Previously,
Kibana would\nannounce a generic modal dialog message (from EUI) without
context,\nwhich could confuse screen reader users.\n\n###
Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on
the “Set up\nGenAI connector” button, Kibana announces a generic message
like “modal\ndialog” without explaining what the modal is about.\n\n###
Fix\n•\tInclude aria-label to the `CreateConnectorFlyout`
component\n\n### How to Test\n1.\tNavigate to Observability → AI
Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick
“Set up GenAI connector”\n4.\tVerify that the screen reader announces
\"create connector
flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061"}},"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/218426","number":218426,"mergeCommit":{"message":"Improve
accessibility in create connector flyout (#218426)\n\npart of #212776
\n\n## Summary\nImproves screen reader accessibility for the GenAI
connector panels in\nthe Observability AI Assistant by providing more
descriptive\nannouncements when these panels are opened. Previously,
Kibana would\nannounce a generic modal dialog message (from EUI) without
context,\nwhich could confuse screen reader users.\n\n###
Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on
the “Set up\nGenAI connector” button, Kibana announces a generic message
like “modal\ndialog” without explaining what the modal is about.\n\n###
Fix\n•\tInclude aria-label to the `CreateConnectorFlyout`
component\n\n### How to Test\n1.\tNavigate to Observability → AI
Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick
“Set up GenAI connector”\n4.\tVerify that the screen reader announces
\"create connector
flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061"}}]}]
BACKPORT-->

Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co>
2025-04-19 00:28:28 +02:00
elastic-renovate-prod[bot]
0b86ac2218
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 5ffa55a (8.17) (#218625)
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base | digest | `1c7f5aa` ->
`5ffa55a` |

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-18 23:55:12 +02:00
Kibana Machine
e54cb4a6ea
[8.17] fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576) (#218607)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space
flyout announced incorrectly
(#218576)](https://github.com/elastic/kibana/pull/218576)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-17T18:52:56Z","message":"fix:
[Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout
announced incorrectly (#218576)\n\nCloses:
#218351\n\n**Description**\nWhen user clicks on assign new roles to a
space button, the resulting\nflyout gets announced incorrectly as \"you
are in a modal dialog...\"\nwhich doesn't give any context to
non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby'
attribute\n\n**Screen:**\n<img width=\"1323\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout
announced
incorrectly","number":218576,"url":"https://github.com/elastic/kibana/pull/218576","mergeCommit":{"message":"fix:
[Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout
announced incorrectly (#218576)\n\nCloses:
#218351\n\n**Description**\nWhen user clicks on assign new roles to a
space button, the resulting\nflyout gets announced incorrectly as \"you
are in a modal dialog...\"\nwhich doesn't give any context to
non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby'
attribute\n\n**Screen:**\n<img width=\"1323\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad"}},"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/218576","number":218576,"mergeCommit":{"message":"fix:
[Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout
announced incorrectly (#218576)\n\nCloses:
#218351\n\n**Description**\nWhen user clicks on assign new roles to a
space button, the resulting\nflyout gets announced incorrectly as \"you
are in a modal dialog...\"\nwhich doesn't give any context to
non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby'
attribute\n\n**Screen:**\n<img width=\"1323\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
2025-04-18 15:19:16 +00:00
Kibana Machine
f69793e9fa
[8.17] [ML] Fix vCPU usage message in the Start deployment dialog (#218557) (#218577)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[ML] Fix vCPU usage message in the Start deployment dialog
(#218557)](https://github.com/elastic/kibana/pull/218557)

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

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

<!--BACKPORT [{"author":{"name":"Dima
Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T15:23:20Z","message":"[ML]
Fix vCPU usage message in the Start deployment dialog (#218557)\n\n##
Summary\n\nFixes the info callout message in the “Start model
deployment” dialog by\nreplacing the ELSER name with a generic model
reference.\n\n### Checklist\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[ML]
Fix vCPU usage message in the Start deployment dialog
","number":218557,"url":"https://github.com/elastic/kibana/pull/218557","mergeCommit":{"message":"[ML]
Fix vCPU usage message in the Start deployment dialog (#218557)\n\n##
Summary\n\nFixes the info callout message in the “Start model
deployment” dialog by\nreplacing the ELSER name with a generic model
reference.\n\n### Checklist\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218557","number":218557,"mergeCommit":{"message":"[ML]
Fix vCPU usage message in the Start deployment dialog (#218557)\n\n##
Summary\n\nFixes the info callout message in the “Start model
deployment” dialog by\nreplacing the ELSER name with a generic model
reference.\n\n### Checklist\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\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":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","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"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>
2025-04-17 19:22:23 +02:00
Kibana Machine
a961368f28
[8.17] [Synthetics] Fixed test run logs per page (#218458) (#218523)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Synthetics] Fixed test run logs per page
(#218458)](https://github.com/elastic/kibana/pull/218458)

<!--- 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-04-17T05:34:38Z","message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d","branchLabelMapping":{"^v9.1.0$":"main","^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","v9.0.1","v8.17.6"],"title":"[Synthetics]
Fixed test run logs per
page","number":218458,"url":"https://github.com/elastic/kibana/pull/218458","mergeCommit":{"message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218458","number":218458,"mergeCommit":{"message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","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"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
2025-04-17 09:33:06 +02:00
Kibana Machine
57825a2d8a
[8.17] fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement (#217829) (#218443)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix: [Analytics:Visualize Library page]Dialog modal missing title
from announcement
(#217829)](https://github.com/elastic/kibana/pull/217829)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-16T13:19:03Z","message":"fix:
[Analytics:Visualize Library page]Dialog modal missing title from
announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}`
for mentioned
places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Analytics:Visualize Library page]Dialog modal missing title from
announcement","number":217829,"url":"https://github.com/elastic/kibana/pull/217829","mergeCommit":{"message":"fix:
[Analytics:Visualize Library page]Dialog modal missing title from
announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}`
for mentioned
places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7"}},"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/217829","number":217829,"mergeCommit":{"message":"fix:
[Analytics:Visualize Library page]Dialog modal missing title from
announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}`
for mentioned
places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
2025-04-16 17:19:49 +02:00
Kibana Machine
2ea9d151ff
[8.17] fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827) (#218421)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix: [Analytics:Graph page]Dialog modal missing title from
announcement (#217827)](https://github.com/elastic/kibana/pull/217827)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-16T12:03:38Z","message":"fix:
[Analytics:Graph page]Dialog modal missing title from announcement
(#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout,
field visible title should be announced for the\nusers, especially using
assistive technology to know what dialog modal,\nflyout opened, what
field is active and what is needed to enter in it.\n\n**Changes
made:**\n\n1. Set correct value for` aria-labelledby`
attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Analytics:Graph page]Dialog modal missing title from
announcement","number":217827,"url":"https://github.com/elastic/kibana/pull/217827","mergeCommit":{"message":"fix:
[Analytics:Graph page]Dialog modal missing title from announcement
(#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout,
field visible title should be announced for the\nusers, especially using
assistive technology to know what dialog modal,\nflyout opened, what
field is active and what is needed to enter in it.\n\n**Changes
made:**\n\n1. Set correct value for` aria-labelledby`
attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0"}},"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/217827","number":217827,"mergeCommit":{"message":"fix:
[Analytics:Graph page]Dialog modal missing title from announcement
(#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout,
field visible title should be announced for the\nusers, especially using
assistive technology to know what dialog modal,\nflyout opened, what
field is active and what is needed to enter in it.\n\n**Changes
made:**\n\n1. Set correct value for` aria-labelledby`
attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0"}}]}] BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
2025-04-16 16:07:05 +02:00
Kibana Machine
98b578e245
[8.17] fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831) (#218272)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit
model snapshot flyout missing title from announcement
(#217831)](https://github.com/elastic/kibana/pull/217831)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T13:38:48Z","message":"fix:
[Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model
snapshot flyout missing title from announcement (#217831)\n\nCloses:
#216147\n\n**Description**\nDialog modal, flyout, field visible title
should be announced for the\nusers, especially using assistive
technology to know what dialog modal,\nflyout opened, what field is
active and what is needed to enter in it.\n\n**Changes made:**\n\n1.
Added` aria-labelledby={flyoutTitleId} `for mentioned
places","sha":"d47e77627ac594883969066205a0888bb5034efb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","Feature:Anomaly
Detection","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model
snapshot flyout missing title from
announcement","number":217831,"url":"https://github.com/elastic/kibana/pull/217831","mergeCommit":{"message":"fix:
[Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model
snapshot flyout missing title from announcement (#217831)\n\nCloses:
#216147\n\n**Description**\nDialog modal, flyout, field visible title
should be announced for the\nusers, especially using assistive
technology to know what dialog modal,\nflyout opened, what field is
active and what is needed to enter in it.\n\n**Changes made:**\n\n1.
Added` aria-labelledby={flyoutTitleId} `for mentioned
places","sha":"d47e77627ac594883969066205a0888bb5034efb"}},"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/217831","number":217831,"mergeCommit":{"message":"fix:
[Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model
snapshot flyout missing title from announcement (#217831)\n\nCloses:
#216147\n\n**Description**\nDialog modal, flyout, field visible title
should be announced for the\nusers, especially using assistive
technology to know what dialog modal,\nflyout opened, what field is
active and what is needed to enter in it.\n\n**Changes made:**\n\n1.
Added` aria-labelledby={flyoutTitleId} `for mentioned
places","sha":"d47e77627ac594883969066205a0888bb5034efb"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
2025-04-16 12:43:04 +02:00
Francesco Fagnani
f2e3ac3d71
[8.17] [Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197) (#218296)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Synthetics] Sync global parameters is called in the endpoints to
add, edit or delete global params
(#216197)](https://github.com/elastic/kibana/pull/216197)

<!--- 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-04-15T14:53:14Z","message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d","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","v9.0.1","v8.17.5"],"title":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global
params","number":216197,"url":"https://github.com/elastic/kibana/pull/216197","mergeCommit":{"message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216197","number":216197,"mergeCommit":{"message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},{"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,"url":"https://github.com/elastic/kibana/pull/218290","number":218290,"state":"OPEN"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-16 10:05:39 +02:00
Tiago Costa
d556e956e2
chore(NA): bump version to 8.17.6 (#218298)
Usually bump from 8.17.5 to 8.17.6
2025-04-16 05:26:51 +01:00
elastic-renovate-prod[bot]
11821fbcd8
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 1c7f5aa (8.17) (#218044)
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base | digest | `c56628d` ->
`1c7f5aa` |

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-15 19:49:49 -06:00
elastic-renovate-prod[bot]
5927294680
Update dependency selenium-webdriver to ^4.31.0 (8.17) (#216386)
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
|
[selenium-webdriver](https://redirect.github.com/SeleniumHQ/selenium/tree/trunk/javascript/selenium-webdriver#readme)
([source](https://redirect.github.com/SeleniumHQ/selenium)) |
devDependencies | minor | [`^4.29.0` ->
`^4.31.0`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.29.0/4.31.0)
|

---

### Release Notes

<details>
<summary>SeleniumHQ/selenium (selenium-webdriver)</summary>

###
[`v4.31.0`](509c7f17cc...1ef9f18787)

[Compare
Source](509c7f17cc...1ef9f18787)

###
[`v4.30.0`](5fc1ec94cb...509c7f17cc)

[Compare
Source](5fc1ec94cb...509c7f17cc)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-15 17:00:27 -06:00
Kibana Machine
6ab89eb1e0
[8.17] [Custom threshold rule] Allow group for ip type fields !! (#216062) (#218335)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Custom threshold rule] Allow group for ip type fields !!
(#216062)](https://github.com/elastic/kibana/pull/216062)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T18:15:02Z","message":"[Custom
threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow
group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:all-open","Team:obs-ux-management","v9.1.0"],"title":"[Custom
threshold rule] Allow group for ip type fields
!!","number":216062,"url":"https://github.com/elastic/kibana/pull/216062","mergeCommit":{"message":"[Custom
threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow
group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}},"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/216062","number":216062,"mergeCommit":{"message":"[Custom
threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow
group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout
<faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2025-04-15 22:31:34 +02:00
Kibana Machine
b8b29b1f38
[8.17] fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666) (#218257)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix: [ML] Data Frame Analytics: Analytics selection flyout missing
title from announcement
(#217666)](https://github.com/elastic/kibana/pull/217666)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T12:17:20Z","message":"fix:
[ML] Data Frame Analytics: Analytics selection flyout missing title from
announcement (#217666)\n\nCloses:
https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby`
attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","release_note:skip","Feature:Data
Frame Analytics","backport:prev-major","v9.1.0"],"title":"fix: [ML] Data
Frame Analytics: Analytics selection flyout missing title from
announcement","number":217666,"url":"https://github.com/elastic/kibana/pull/217666","mergeCommit":{"message":"fix:
[ML] Data Frame Analytics: Analytics selection flyout missing title from
announcement (#217666)\n\nCloses:
https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby`
attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}},"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/217666","number":217666,"mergeCommit":{"message":"fix:
[ML] Data Frame Analytics: Analytics selection flyout missing title from
announcement (#217666)\n\nCloses:
https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog
modal, flyout, field visible title should be announced for the\nusers,
especially using assistive technology to know what dialog modal,\nflyout
opened, what field is active and what is needed to enter in
it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby`
attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}}]}] BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
2025-04-15 16:08:54 +02:00
Kibana Machine
fc6555c621
[8.17] [Infra] Check ML permissions before requesting ML data (#218069) (#218227)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Infra] Check ML permissions before requesting ML data
(#218069)](https://github.com/elastic/kibana/pull/218069)

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T10:02:51Z","message":"[Infra]
Check ML permissions before requesting ML data (#218069)\n\nfixes
[#189213](https://github.com/elastic/kibana/issues/189213)\n\n##
Summary\n\nChecks whether the user has permission to ML before
triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a
user whose role doesn't have permission to ML, but has\npermission to
O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts
--live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts
View\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[Infra]
Check ML permissions before requesting ML
data","number":218069,"url":"https://github.com/elastic/kibana/pull/218069","mergeCommit":{"message":"[Infra]
Check ML permissions before requesting ML data (#218069)\n\nfixes
[#189213](https://github.com/elastic/kibana/issues/189213)\n\n##
Summary\n\nChecks whether the user has permission to ML before
triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a
user whose role doesn't have permission to ML, but has\npermission to
O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts
--live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts
View\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3"}},"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/218069","number":218069,"mergeCommit":{"message":"[Infra]
Check ML permissions before requesting ML data (#218069)\n\nfixes
[#189213](https://github.com/elastic/kibana/issues/189213)\n\n##
Summary\n\nChecks whether the user has permission to ML before
triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a
user whose role doesn't have permission to ML, but has\npermission to
O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts
--live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts
View\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3"}}]}]
BACKPORT-->

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
2025-04-15 14:42:17 +02:00
Kibana Machine
ef82214901
[8.17] [ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107) (#218215)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows
sidebar (#218107)](https://github.com/elastic/kibana/pull/218107)

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

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

<!--BACKPORT [{"author":{"name":"Georgiana-Andreea
Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T09:06:29Z","message":"[ResponseOps][Cases]Horizontal
scrolling in cases' comments overflows sidebar (#218107)\n\nCloses
https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe
comment section containing a table that requires horizontal\nscrolling
was being visually pushed to the right due to the presence of\nthe user
avatar. To ensure the comment section aligns properly with the\nrest of
the content and doesn't overlap the sidebar reserved for\nconnectors and
custom fields, the `max-width` property was
adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the
euiAvatar--m (which uses the `xl` size token)\n- the left padding of the
`euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base`
(16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[ResponseOps][Cases]Horizontal
scrolling in cases' comments overflows
sidebar","number":218107,"url":"https://github.com/elastic/kibana/pull/218107","mergeCommit":{"message":"[ResponseOps][Cases]Horizontal
scrolling in cases' comments overflows sidebar (#218107)\n\nCloses
https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe
comment section containing a table that requires horizontal\nscrolling
was being visually pushed to the right due to the presence of\nthe user
avatar. To ensure the comment section aligns properly with the\nrest of
the content and doesn't overlap the sidebar reserved for\nconnectors and
custom fields, the `max-width` property was
adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the
euiAvatar--m (which uses the `xl` size token)\n- the left padding of the
`euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base`
(16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"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/218107","number":218107,"mergeCommit":{"message":"[ResponseOps][Cases]Horizontal
scrolling in cases' comments overflows sidebar (#218107)\n\nCloses
https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe
comment section containing a table that requires horizontal\nscrolling
was being visually pushed to the right due to the presence of\nthe user
avatar. To ensure the comment section aligns properly with the\nrest of
the content and doesn't overlap the sidebar reserved for\nconnectors and
custom fields, the `max-width` property was
adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the
euiAvatar--m (which uses the `xl` size token)\n- the left padding of the
`euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base`
(16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>
2025-04-15 13:21:50 +02:00
Dmitrii Shevchenko
b18e545513
[8.17] [Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959) (#218209)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Security Solution] Fix prebuilt rules force upgrade on Endpoint
policy creation
(#217959)](https://github.com/elastic/kibana/pull/217959)

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

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

<!--BACKPORT [{"author":{"name":"Dmitrii
Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:22:38Z","message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:high","Feature:Endpoint","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","v8.18.1","v9.0.1","v8.17.5"],"title":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy
creation","number":217959,"url":"https://github.com/elastic/kibana/pull/217959","mergeCommit":{"message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218155","number":218155,"state":"MERGED","mergeCommit":{"sha":"06e5e580eb3930f49dbee485c4f8dc4fadd08bb2","message":"[9.0]
[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy
creation (#217959) (#218155)\n\n# Backport\n\nThis will backport the
following commits from `main` to `9.0`:\n- [[Security Solution] Fix
prebuilt rules force upgrade on Endpoint\npolicy
creation\n(#217959)](https://github.com/elastic/kibana/pull/217959)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Dmitrii Shevchenko
<dmitrii.shevchenko@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218153","number":218153,"state":"MERGED","mergeCommit":{"sha":"fc87edd906403629bb52efbdbbd20bbc7206d195","message":"[8.18]
[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy
creation (#217959) (#218153)\n\n# Backport\n\nThis will backport the
following commits from `main` to `8.18`:\n- [[Security Solution] Fix
prebuilt rules force upgrade on Endpoint\npolicy
creation\n(#217959)](https://github.com/elastic/kibana/pull/217959)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Dmitrii Shevchenko
<dmitrii.shevchenko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217959","number":217959,"mergeCommit":{"message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218154","number":218154,"state":"MERGED","mergeCommit":{"sha":"48554f91e1d749d56fc1fde076a3edd0143190b3","message":"[8.x]
[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy
creation (#217959) (#218154)\n\n# Backport\n\nThis will backport the
following commits from `main` to `8.x`:\n- [[Security Solution] Fix
prebuilt rules force upgrade on Endpoint\npolicy
creation\n(#217959)](https://github.com/elastic/kibana/pull/217959)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Dmitrii Shevchenko
<dmitrii.shevchenko@elastic.co>"}},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2025-04-15 12:39:47 +02:00
Shahzad
07c30c06f0
[8.17] [Synthetics] Fix tls alert data !! (#212758) (#218057)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Synthetics] Fix tls alert data !!
(#212758)](https://github.com/elastic/kibana/pull/212758)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-05T18:40:04Z","message":"[Synthetics]
Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and
fixes the TLS alert data handling in the Synthetics\nplugin. Key updates
include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added
`agent.name`.\n- Changed optional chaining to direct property access
for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n
- Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added
fields: `monitorName`, `monitorId`, `monitorType`,
`locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3.
**Observer Codec**:\n - Ensured `name` and `geo.name` are required
fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to
`MonitorType`.\n - Moved `@timestamp` to required fields in
`PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and
`getTLSAlertDocument` so that we can\nproperly generate alert
document","sha":"80f4aab305eb90646f418bc704423308d133d7d2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[Synthetics]
Fix tls alert data
!!","number":212758,"url":"https://github.com/elastic/kibana/pull/212758","mergeCommit":{"message":"[Synthetics]
Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and
fixes the TLS alert data handling in the Synthetics\nplugin. Key updates
include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added
`agent.name`.\n- Changed optional chaining to direct property access
for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n
- Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added
fields: `monitorName`, `monitorId`, `monitorType`,
`locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3.
**Observer Codec**:\n - Ensured `name` and `geo.name` are required
fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to
`MonitorType`.\n - Moved `@timestamp` to required fields in
`PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and
`getTLSAlertDocument` so that we can\nproperly generate alert
document","sha":"80f4aab305eb90646f418bc704423308d133d7d2"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213315","number":213315,"state":"MERGED","mergeCommit":{"sha":"ec0da627b205191fb6bb6326aa0b711aaeef2eb9","message":"[9.0]
[Synthetics] Fix tls alert data !! (#212758) (#213315)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[Synthetics] Fix tls alert data
!!\n(#212758)](https://github.com/elastic/kibana/pull/212758)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213317","number":213317,"state":"MERGED","mergeCommit":{"sha":"b05d493195346a14fd8b702bd97f79bb9576fac2","message":"[8.18]
[Synthetics] Fix tls alert data !! (#212758) (#213317)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.18`:\n- [[Synthetics] Fix tls alert data
!!\n(#212758)](https://github.com/elastic/kibana/pull/212758)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212758","number":212758,"mergeCommit":{"message":"[Synthetics]
Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and
fixes the TLS alert data handling in the Synthetics\nplugin. Key updates
include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added
`agent.name`.\n- Changed optional chaining to direct property access
for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n
- Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added
fields: `monitorName`, `monitorId`, `monitorType`,
`locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3.
**Observer Codec**:\n - Ensured `name` and `geo.name` are required
fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to
`MonitorType`.\n - Moved `@timestamp` to required fields in
`PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and
`getTLSAlertDocument` so that we can\nproperly generate alert
document","sha":"80f4aab305eb90646f418bc704423308d133d7d2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213321","number":213321,"state":"MERGED","mergeCommit":{"sha":"fd37b2ca299c70006e8b8a3dd9c7988f553ae754","message":"[8.x]
[Synthetics] Fix tls alert data !! (#212758) (#213321)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.x`:\n- [[Synthetics] Fix tls alert data
!!\n(#212758)](https://github.com/elastic/kibana/pull/212758)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2025-04-15 10:57:25 +02:00
Jeramy Soucy
d87ec5fe79
[8.17] Fixes bulk re-encryption for encrypted objects located in all spaces (#217625) (#218180)
# Backport

This will backport the following commits from `main` to `8.17`:
- [Fixes bulk re-encryption for encrypted objects located in all spaces
(#217625)](https://github.com/elastic/kibana/pull/217625)

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

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

<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T19:20:38Z","message":"Fixes
bulk re-encryption for encrypted objects located in all spaces
(#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects
Key Rotation service makes use of the Saved\nObjects Bulk Update API to
re-encrypt objects. Bulk update supports an\noptional 'namespace'
parameter, per-object, defining the space to access\na specific object.
This allows objects outside of the current space to\nbe affected in the
update operation. The Key Rotation service leverages\nthis optional
parameter for each object to ensure that the re-encryption\noperation is
not limited to the current space.\n\nHowever, should a multi-namespace
encrypted object reside in all spaces,\nthe only value in the object's
namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As
this is not a valid single\nnamespace, the Bulk Update operation will
skip updating the object.\n\nPR resolves the issue by only providing a
object namespace for objects\nthat do not reside in all spaces. Objects
that reside in all spaces can\nbe accessed from the current space
without the need for an override.\n\nThis PR also updates unit tests to
account for this case.\n\n### Testing\n- [x] Set the encrypted saved
objects encryption key to a known value\n(either in kibana.yml or
kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n
encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start
ES & Kibana\n- [x] You will need to set up a Fleet agent policy and
create a\nsynthetics location and monitor. The UI will guide you through
this when\nyou navigate to Observability -> Synthetics\n- [x] Create a
synthetics parameter, Observability -> Synthetics ->\nSettings, Global
Parameters tab. Use anything for a value, but be sure\nto check the
`Share across spaces` option.\n- [x] Update the kibana config to change
the encryption key, and use the\nold key as a decryption-only
key\n```\nxpack.encryptedSavedObjects:\n encryptionKey:
\"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n
decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x]
Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a
privileged user (I just used\nthe `elastic` superuser
account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n-
[x] Verify that 1 out of 1 objects were processed with 0 failures.\n-
[x] Repeat these steps from Main and note that 0 of 1
objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an
issue where the Saved Objects Rotate Encryption Key API would\nnot
affect sharable encrypted object types that exist in all
spaces.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","backport:all-open","v9.1.0"],"title":"Fixes
bulk re-encryption for encrypted objects located in all
spaces","number":217625,"url":"https://github.com/elastic/kibana/pull/217625","mergeCommit":{"message":"Fixes
bulk re-encryption for encrypted objects located in all spaces
(#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects
Key Rotation service makes use of the Saved\nObjects Bulk Update API to
re-encrypt objects. Bulk update supports an\noptional 'namespace'
parameter, per-object, defining the space to access\na specific object.
This allows objects outside of the current space to\nbe affected in the
update operation. The Key Rotation service leverages\nthis optional
parameter for each object to ensure that the re-encryption\noperation is
not limited to the current space.\n\nHowever, should a multi-namespace
encrypted object reside in all spaces,\nthe only value in the object's
namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As
this is not a valid single\nnamespace, the Bulk Update operation will
skip updating the object.\n\nPR resolves the issue by only providing a
object namespace for objects\nthat do not reside in all spaces. Objects
that reside in all spaces can\nbe accessed from the current space
without the need for an override.\n\nThis PR also updates unit tests to
account for this case.\n\n### Testing\n- [x] Set the encrypted saved
objects encryption key to a known value\n(either in kibana.yml or
kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n
encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start
ES & Kibana\n- [x] You will need to set up a Fleet agent policy and
create a\nsynthetics location and monitor. The UI will guide you through
this when\nyou navigate to Observability -> Synthetics\n- [x] Create a
synthetics parameter, Observability -> Synthetics ->\nSettings, Global
Parameters tab. Use anything for a value, but be sure\nto check the
`Share across spaces` option.\n- [x] Update the kibana config to change
the encryption key, and use the\nold key as a decryption-only
key\n```\nxpack.encryptedSavedObjects:\n encryptionKey:
\"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n
decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x]
Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a
privileged user (I just used\nthe `elastic` superuser
account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n-
[x] Verify that 1 out of 1 objects were processed with 0 failures.\n-
[x] Repeat these steps from Main and note that 0 of 1
objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an
issue where the Saved Objects Rotate Encryption Key API would\nnot
affect sharable encrypted object types that exist in all
spaces.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}},"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/217625","number":217625,"mergeCommit":{"message":"Fixes
bulk re-encryption for encrypted objects located in all spaces
(#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects
Key Rotation service makes use of the Saved\nObjects Bulk Update API to
re-encrypt objects. Bulk update supports an\noptional 'namespace'
parameter, per-object, defining the space to access\na specific object.
This allows objects outside of the current space to\nbe affected in the
update operation. The Key Rotation service leverages\nthis optional
parameter for each object to ensure that the re-encryption\noperation is
not limited to the current space.\n\nHowever, should a multi-namespace
encrypted object reside in all spaces,\nthe only value in the object's
namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As
this is not a valid single\nnamespace, the Bulk Update operation will
skip updating the object.\n\nPR resolves the issue by only providing a
object namespace for objects\nthat do not reside in all spaces. Objects
that reside in all spaces can\nbe accessed from the current space
without the need for an override.\n\nThis PR also updates unit tests to
account for this case.\n\n### Testing\n- [x] Set the encrypted saved
objects encryption key to a known value\n(either in kibana.yml or
kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n
encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start
ES & Kibana\n- [x] You will need to set up a Fleet agent policy and
create a\nsynthetics location and monitor. The UI will guide you through
this when\nyou navigate to Observability -> Synthetics\n- [x] Create a
synthetics parameter, Observability -> Synthetics ->\nSettings, Global
Parameters tab. Use anything for a value, but be sure\nto check the
`Share across spaces` option.\n- [x] Update the kibana config to change
the encryption key, and use the\nold key as a decryption-only
key\n```\nxpack.encryptedSavedObjects:\n encryptionKey:
\"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n
decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x]
Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a
privileged user (I just used\nthe `elastic` superuser
account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n-
[x] Verify that 1 out of 1 objects were processed with 0 failures.\n-
[x] Repeat these steps from Main and note that 0 of 1
objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an
issue where the Saved Objects Rotate Encryption Key API would\nnot
affect sharable encrypted object types that exist in all
spaces.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-14 22:23:18 -04:00
wajihaparvez
da6383ab38
[Docs] Backport 8.17.5 release notes to 8.17 (#218148)
## Backport

This will backport the following commits from `8.x` to `8.17`:

- [8.17.5 release notes
(#217919)](2d50a33948)
2025-04-14 15:00:48 -04:00
Milosz Marcinkowski
0fe80714cb
[8.17] [APM][UI] Sort environment dropdown alphabetically (#217710) (#217881)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[APM][UI] Sort environment dropdown alphabetically
(#217710)](https://github.com/elastic/kibana/pull/217710)

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

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

<!--BACKPORT [{"author":{"name":"Milosz
Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-10T15:38:20Z","message":"[APM][UI]
Sort environment dropdown alphabetically (#217710)\n\nCloses
#217814\n\n### Summary\n\nSort environment list
alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\"
alt=\"Screenshot 2025-04-10 at 12 01
15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img
width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58
27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][UI]
Sort environment dropdown
alphabetically","number":217710,"url":"https://github.com/elastic/kibana/pull/217710","mergeCommit":{"message":"[APM][UI]
Sort environment dropdown alphabetically (#217710)\n\nCloses
#217814\n\n### Summary\n\nSort environment list
alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\"
alt=\"Screenshot 2025-04-10 at 12 01
15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img
width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58
27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a"}},"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/217710","number":217710,"mergeCommit":{"message":"[APM][UI]
Sort environment dropdown alphabetically (#217710)\n\nCloses
#217814\n\n### Summary\n\nSort environment list
alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\"
alt=\"Screenshot 2025-04-10 at 12 01
15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img
width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58
27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-14 11:22:00 +02:00
Kibana Machine
ce991c2686
[8.17] Update dependency cytoscape to ^3.31.2 (main) (#217567) (#218011)
# Backport

This will backport the following commits from `main` to `8.17`:
- [Update dependency cytoscape to ^3.31.2 (main)
(#217567)](https://github.com/elastic/kibana/pull/217567)

<!--- 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-04-11T17:27:54Z","message":"Update
dependency cytoscape to ^3.31.2 (main) (#217567)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js))
|\ndependencies | patch | [`^3.31.1`
->\n`^3.31.2`](https://renovatebot.com/diffs/npm/cytoscape/3.31.1/3.31.2)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>cytoscape/cytoscape.js
(cytoscape)</summary>\n\n###\n[`v3.31.2`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.2)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.1...v3.31.2)\n\nRelease
version v3.31.2\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>\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>","sha":"7419bc354ceeb9f8fcbeeba79e007544829e50de","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Update
dependency cytoscape to ^3.31.2
(main)","number":217567,"url":"https://github.com/elastic/kibana/pull/217567","mergeCommit":{"message":"Update
dependency cytoscape to ^3.31.2 (main) (#217567)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js))
|\ndependencies | patch | [`^3.31.1`
->\n`^3.31.2`](https://renovatebot.com/diffs/npm/cytoscape/3.31.1/3.31.2)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>cytoscape/cytoscape.js
(cytoscape)</summary>\n\n###\n[`v3.31.2`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.2)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.1...v3.31.2)\n\nRelease
version v3.31.2\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>\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>","sha":"7419bc354ceeb9f8fcbeeba79e007544829e50de"}},"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/217567","number":217567,"mergeCommit":{"message":"Update
dependency cytoscape to ^3.31.2 (main) (#217567)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js))
|\ndependencies | patch | [`^3.31.1`
->\n`^3.31.2`](https://renovatebot.com/diffs/npm/cytoscape/3.31.1/3.31.2)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>cytoscape/cytoscape.js
(cytoscape)</summary>\n\n###\n[`v3.31.2`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.2)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.1...v3.31.2)\n\nRelease
version v3.31.2\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>\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>","sha":"7419bc354ceeb9f8fcbeeba79e007544829e50de"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-11 21:32:28 +02:00
Sergi Romeu
6de7f8b966
[8.17] [APM][Cypress] Attempt to fix mobile transactions test (#217648) (#217955)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[APM][Cypress] Attempt to fix mobile transactions test
(#217648)](https://github.com/elastic/kibana/pull/217648)

<!--- 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-04-11T08:28:49Z","message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","apm:mobile","backport:all-open","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][Cypress]
Attempt to fix mobile transactions
test","number":217648,"url":"https://github.com/elastic/kibana/pull/217648","mergeCommit":{"message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}},"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/217648","number":217648,"mergeCommit":{"message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}}]}]
BACKPORT-->
2025-04-11 14:32:48 +02:00
Ola Pawlus
a77e876a9d
[8.17] [Dashboards] Update response on HTTP API should return a 200, not 201 (#217054) (#217498)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Dashboards] Update response on HTTP API should return a 200, not 201
(#217054)](https://github.com/elastic/kibana/pull/217054)

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

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

<!--BACKPORT
[{"author":{"name":"Ola","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-04T17:48:58Z","message":"[Dashboards]
Update response on HTTP API should return a 200, not 201 (#217054)\n\n##
Summary\n\nChanges response from 201 to 200 in the dashboard
updateRoute.\n\nCloses:
#212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Presentation","backport:version","v9.1.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Dashboards]
Update response on HTTP API should return a 200, not 201
","number":217054,"url":"https://github.com/elastic/kibana/pull/217054","mergeCommit":{"message":"[Dashboards]
Update response on HTTP API should return a 200, not 201 (#217054)\n\n##
Summary\n\nChanges response from 201 to 200 in the dashboard
updateRoute.\n\nCloses:
#212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217054","number":217054,"mergeCommit":{"message":"[Dashboards]
Update response on HTTP API should return a 200, not 201 (#217054)\n\n##
Summary\n\nChanges response from 201 to 200 in the dashboard
updateRoute.\n\nCloses:
#212673","sha":"3c2b4daf97fdaea09cd1cd33b71c561344ec90b0"}},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-04-11 13:40:37 +02:00
Carlos Crespo
1249f75697
[8.17] [APM] Treat "links" field as array (#215906) (#217664)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[APM] Treat "links" field as array
(#215906)](https://github.com/elastic/kibana/pull/215906)

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T07:10:15Z","message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM]
Treat \"links\" field as
array","number":215906,"url":"https://github.com/elastic/kibana/pull/215906","mergeCommit":{"message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}},"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/215906","number":215906,"mergeCommit":{"message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}},{"url":"https://github.com/elastic/kibana/pull/217659","number":217659,"branch":"9.0","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217661","number":217661,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217662","number":217662,"branch":"8.18","state":"OPEN"}]}]
BACKPORT-->
2025-04-11 11:27:46 +02:00
elastic-vault-github-plugin-prod[bot]
db5ca7bf78
[8.17] Sync bundled packages with Package Storage (#217906)
Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2611

Co-authored-by: elasticmachine <elasticmachine@elastic.co>
Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
2025-04-11 11:13:15 +02:00
Alejandro Fernández Haro
654e4d8f10
[8.17] Update dependency @types/semver to ^7.7.0 (main) (#216932) (#217672)
# Backport

This will backport the following commits from `main` to `8.17`:
- [Update dependency @types/semver to ^7.7.0 (main)
(#216932)](https://github.com/elastic/kibana/pull/216932)

<!--- 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-04-07T20:36:17Z","message":"Update
dependency @types/semver to ^7.7.0 (main) (#216932)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/semver](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/semver)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/semver))\n|
devDependencies | minor | [`^7.5.8`
->\n`^7.7.0`](https://renovatebot.com/diffs/npm/@types%2fsemver/7.5.8/7.7.0)\n|\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>\nCo-authored-by:
Jean-Louis Leysens
<jeanlouis.leysens@elastic.co>","sha":"04a3d3308f5a8faffe6927c3d58d1ad81b2131b2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:all-open","v9.1.0","v8.19.0"],"title":"Update
dependency @types/semver to ^7.7.0
(main)","number":216932,"url":"https://github.com/elastic/kibana/pull/216932","mergeCommit":{"message":"Update
dependency @types/semver to ^7.7.0 (main) (#216932)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/semver](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/semver)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/semver))\n|
devDependencies | minor | [`^7.5.8`
->\n`^7.7.0`](https://renovatebot.com/diffs/npm/@types%2fsemver/7.5.8/7.7.0)\n|\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>\nCo-authored-by:
Jean-Louis Leysens
<jeanlouis.leysens@elastic.co>","sha":"04a3d3308f5a8faffe6927c3d58d1ad81b2131b2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217404","number":217404,"state":"MERGED","mergeCommit":{"sha":"c4ac2922eb008bda23ee40c1803a97291cc9dc66","message":"[9.0]
Update dependency @types/semver to ^7.7.0 (main) (#216932)
(#217404)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [Update dependency @types/semver to ^7.7.0
(main)\n(#216932)](https://github.com/elastic/kibana/pull/216932)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@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/216932","number":216932,"mergeCommit":{"message":"Update
dependency @types/semver to ^7.7.0 (main) (#216932)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/semver](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/semver)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/semver))\n|
devDependencies | minor | [`^7.5.8`
->\n`^7.7.0`](https://renovatebot.com/diffs/npm/@types%2fsemver/7.5.8/7.7.0)\n|\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>\nCo-authored-by:
Jean-Louis Leysens
<jeanlouis.leysens@elastic.co>","sha":"04a3d3308f5a8faffe6927c3d58d1ad81b2131b2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217403","number":217403,"state":"MERGED","mergeCommit":{"sha":"c4ed7040057b0c7e5f1e74aad7ef840efb2ccfb7","message":"[8.x]
Update dependency @types/semver to ^7.7.0 (main) (#216932)
(#217403)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [Update dependency @types/semver to ^7.7.0
(main)\n(#216932)](https://github.com/elastic/kibana/pull/216932)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by:
Alejandro Fernández Haro <alejandro.haro@elastic.co>"}}]}] BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-10 13:37:48 -07:00
Kevin Delemme
5688bcb371
[8.17] fix(slo): search bar filters (#217702) (#217870) 2025-04-10 14:00:05 -04:00
Kibana Machine
acdf775fe4
[8.17] [Dashboard] Fix page object getPanels method for new grid system (#217812) (#217856)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Dashboard] Fix page object getPanels method for new grid system
(#217812)](https://github.com/elastic/kibana/pull/217812)

<!--- 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-04-10T14:22:27Z","message":"[Dashboard]
Fix page object getPanels method for new grid system (#217812)\n\n##
Summary\n\n@umbopepato made me notice that this method was always
returning an\nempty list of element.\nThat was due to the selector used
was targeting the old grid system.\nThis PR fixes that using the right
selector for the new grid system.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","Team:Presentation","loe:small","release_note:skip","impact:low","backport:all-open","FTR","v9.1.0"],"title":"[Dashboard]
Fix page object getPanels method for new grid
system","number":217812,"url":"https://github.com/elastic/kibana/pull/217812","mergeCommit":{"message":"[Dashboard]
Fix page object getPanels method for new grid system (#217812)\n\n##
Summary\n\n@umbopepato made me notice that this method was always
returning an\nempty list of element.\nThat was due to the selector used
was targeting the old grid system.\nThis PR fixes that using the right
selector for the new grid system.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f"}},"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/217812","number":217812,"mergeCommit":{"message":"[Dashboard]
Fix page object getPanels method for new grid system (#217812)\n\n##
Summary\n\n@umbopepato made me notice that this method was always
returning an\nempty list of element.\nThat was due to the selector used
was targeting the old grid system.\nThis PR fixes that using the right
selector for the new grid system.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ff0ba15eaa2f63a6e8ba09454ac5fb4476d1353f"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
2025-04-10 18:41:26 +02:00
Brad White
5f31ec5951
[8.17] [build] Use docker hub to download ubi (#217322) (#217772)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[build] Use docker hub to download ubi
(#217322)](https://github.com/elastic/kibana/pull/217322)

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

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

<!--BACKPORT
[{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T17:06:38Z","message":"[build]
Use docker hub to download ubi (#217322)\n\nMoves away from our mirror
for all images based on UBI.\n\nBased on feedback
in\nhttps://github.com/docker-library/official-images/pull/18692.","sha":"87b3816a4c4a22bc6abacdebbf6184c2d4e47c38","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:all-open","v9.1.0"],"title":"[build]
Use docker hub to download
ubi","number":217322,"url":"https://github.com/elastic/kibana/pull/217322","mergeCommit":{"message":"[build]
Use docker hub to download ubi (#217322)\n\nMoves away from our mirror
for all images based on UBI.\n\nBased on feedback
in\nhttps://github.com/docker-library/official-images/pull/18692.","sha":"87b3816a4c4a22bc6abacdebbf6184c2d4e47c38"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217375","number":217375,"state":"MERGED","mergeCommit":{"sha":"b2f0e71be6cad6c343786a9ed87422fc0aa03a80","message":"[9.0]
[build] Use docker hub to download ubi (#217322) (#217375)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[build] Use docker hub to download
ubi\n(#217322)](https://github.com/elastic/kibana/pull/217322)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Jon
<jon@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217322","number":217322,"mergeCommit":{"message":"[build]
Use docker hub to download ubi (#217322)\n\nMoves away from our mirror
for all images based on UBI.\n\nBased on feedback
in\nhttps://github.com/docker-library/official-images/pull/18692.","sha":"87b3816a4c4a22bc6abacdebbf6184c2d4e47c38"}}]}]
BACKPORT-->

Co-authored-by: Jon <jon@elastic.co>
2025-04-10 08:23:16 -05:00
Matthew Kime
7670f61b09
[8.17] [index mgmt] Fix preview of index templates which are used by data streams (#217604) (#217768)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[index mgmt] Fix preview of index templates which are used by data
streams (#217604)](https://github.com/elastic/kibana/pull/217604)

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

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

<!--BACKPORT [{"author":{"name":"Matthew
Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-04-09T17:29:12Z","message":"[index
mgmt] Fix preview of index templates which are used by data streams
(#217604)\n\n## Summary\n\nFixes error message when attempting to
preview an index template which\nis used by a data stream.\n\nWhen
previewing a saved index template, a index template name and
index\npattern were provided. If the index pattern didn't match data
streams\nthat relied on the index template (and they never did) an error
would be\nshown. As it turns out, supplying the index pattern was
entirely\nunnecessary. This PR simply removes the index pattern from the
api call\nand adds a test to make sure that preview functionality works
when index\ntemplates match data streams.\n\nFollow up to
https://github.com/elastic/kibana/pull/195174\n\nCloses
https://github.com/elastic/kibana/issues/212781","sha":"b542a760cf5c87900c87b3f5424749eec52366c6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Index
Management","Team:Kibana
Management","backport:prev-major","v8.18.0","v9.1.0","v8.19.0"],"title":"[index
mgmt] Fix preview of index templates which are used by data
streams","number":217604,"url":"https://github.com/elastic/kibana/pull/217604","mergeCommit":{"message":"[index
mgmt] Fix preview of index templates which are used by data streams
(#217604)\n\n## Summary\n\nFixes error message when attempting to
preview an index template which\nis used by a data stream.\n\nWhen
previewing a saved index template, a index template name and
index\npattern were provided. If the index pattern didn't match data
streams\nthat relied on the index template (and they never did) an error
would be\nshown. As it turns out, supplying the index pattern was
entirely\nunnecessary. This PR simply removes the index pattern from the
api call\nand adds a test to make sure that preview functionality works
when index\ntemplates match data streams.\n\nFollow up to
https://github.com/elastic/kibana/pull/195174\n\nCloses
https://github.com/elastic/kibana/issues/212781","sha":"b542a760cf5c87900c87b3f5424749eec52366c6"}},"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/217737","number":217737,"state":"MERGED","mergeCommit":{"sha":"b652d91bd4dcace9f127c0e475ced46ef91388c6","message":"[8.18]
[index mgmt] Fix preview of index templates which are used by data
streams (#217604) (#217737)\n\n# Backport\n\nThis will backport the
following commits from `main` to `8.18`:\n- [[index mgmt] Fix preview of
index templates which are used by data\nstreams
(#217604)](https://github.com/elastic/kibana/pull/217604)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Matthew Kime
<matt@mattki.me>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217604","number":217604,"mergeCommit":{"message":"[index
mgmt] Fix preview of index templates which are used by data streams
(#217604)\n\n## Summary\n\nFixes error message when attempting to
preview an index template which\nis used by a data stream.\n\nWhen
previewing a saved index template, a index template name and
index\npattern were provided. If the index pattern didn't match data
streams\nthat relied on the index template (and they never did) an error
would be\nshown. As it turns out, supplying the index pattern was
entirely\nunnecessary. This PR simply removes the index pattern from the
api call\nand adds a test to make sure that preview functionality works
when index\ntemplates match data streams.\n\nFollow up to
https://github.com/elastic/kibana/pull/195174\n\nCloses
https://github.com/elastic/kibana/issues/212781","sha":"b542a760cf5c87900c87b3f5424749eec52366c6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217738","number":217738,"state":"MERGED","mergeCommit":{"sha":"28cc7e2d2484d35f5691fad2edcfc44998e41b9a","message":"[8.x]
[index mgmt] Fix preview of index templates which are used by data
streams (#217604) (#217738)\n\n# Backport\n\nThis will backport the
following commits from `main` to `8.x`:\n- [[index mgmt] Fix preview of
index templates which are used by data\nstreams
(#217604)](https://github.com/elastic/kibana/pull/217604)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Matthew Kime <matt@mattki.me>"}}]}] BACKPORT-->
2025-04-10 10:08:04 +02:00
Marco Vettorello
1cd15a12f3
[8.17] [Lens] Fix getIndexPatternsObjects for index-pattern only and minor cleanups (#215325) (#217624)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Lens] Fix getIndexPatternsObjects for index-pattern only and minor
cleanups (#215325)](https://github.com/elastic/kibana/pull/215325)

<!--- 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-04-08T16:31:56Z","message":"[Lens]
Fix getIndexPatternsObjects for index-pattern only and minor cleanups
(#215325)\n\n## Summary\n\nThis PR fixes the
https://github.com/elastic/kibana/issues/215323 issue\nand also provide
small cleanup on the code near the edited file, not\ndirectly correlated
but I was already there and the changes are
pretty\nminimal.\n\nCleanups:\n\n- the `SavedObjectReference` is
deprecated and needs to be imported from\n`core/server` instead\n-
Looking at the locator I've noticed a couple of non-null assertion\nthat
wasn't necessary\n- the locator readme was referencing the old `kibana
app services` team\n- cleaned up the
`x-pack/platform/plugins/shared/lens/public/utils.ts`\nto align all the
method to use the same form (or all functions or all\narrow function,
there was a pretty interesting mix there)\n- replaced usages of
exclusive OR with a more appropriate nullish\ncoalescing
operator","sha":"971edc124a9334ea79d8308864234d93c3e10f8c","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","v8.17.5"],"title":"[Lens]
Fix getIndexPatternsObjects for index-pattern only and minor
cleanups","number":215325,"url":"https://github.com/elastic/kibana/pull/215325","mergeCommit":{"message":"[Lens]
Fix getIndexPatternsObjects for index-pattern only and minor cleanups
(#215325)\n\n## Summary\n\nThis PR fixes the
https://github.com/elastic/kibana/issues/215323 issue\nand also provide
small cleanup on the code near the edited file, not\ndirectly correlated
but I was already there and the changes are
pretty\nminimal.\n\nCleanups:\n\n- the `SavedObjectReference` is
deprecated and needs to be imported from\n`core/server` instead\n-
Looking at the locator I've noticed a couple of non-null assertion\nthat
wasn't necessary\n- the locator readme was referencing the old `kibana
app services` team\n- cleaned up the
`x-pack/platform/plugins/shared/lens/public/utils.ts`\nto align all the
method to use the same form (or all functions or all\narrow function,
there was a pretty interesting mix there)\n- replaced usages of
exclusive OR with a more appropriate nullish\ncoalescing
operator","sha":"971edc124a9334ea79d8308864234d93c3e10f8c"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215325","number":215325,"mergeCommit":{"message":"[Lens]
Fix getIndexPatternsObjects for index-pattern only and minor cleanups
(#215325)\n\n## Summary\n\nThis PR fixes the
https://github.com/elastic/kibana/issues/215323 issue\nand also provide
small cleanup on the code near the edited file, not\ndirectly correlated
but I was already there and the changes are
pretty\nminimal.\n\nCleanups:\n\n- the `SavedObjectReference` is
deprecated and needs to be imported from\n`core/server` instead\n-
Looking at the locator I've noticed a couple of non-null assertion\nthat
wasn't necessary\n- the locator readme was referencing the old `kibana
app services` team\n- cleaned up the
`x-pack/platform/plugins/shared/lens/public/utils.ts`\nto align all the
method to use the same form (or all functions or all\narrow function,
there was a pretty interesting mix there)\n- replaced usages of
exclusive OR with a more appropriate nullish\ncoalescing
operator","sha":"971edc124a9334ea79d8308864234d93c3e10f8c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217565","number":217565,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217564","number":217564,"state":"OPEN"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217566","number":217566,"state":"OPEN"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-10 09:30:40 +02:00
Hannah Mudge
1b0d1f7623
[8.17] [Dashboard] Fix controls being overwritten on navigation (#217596)
Closes https://github.com/elastic/kibana/issues/208330

## Summary

Consider how we set `restoredRuntimeState` for controls in
`initializeDashboard`:


ce91dea75c/src/plugins/dashboard/public/dashboard_container/embeddable/create/create_dashboard.ts (L439-L445)

Now, consider the following scenario:

1. We have two dashboards - dashboard B has unsaved changes to its
control group, and dashboard A does not
2. We start in dashboard B and, since it has unsaved control changes,
`restoredRuntimeState[PANELS_CONTROL_GROUP_KEY]` (in
`DashboardContainer`) is populated with these changes
3. We navigate to Dashboard A via the `navigateToDashboard` method,
which calls `initializeDashboard`
4. In `initializeDashboard`, `overrideInput` does **not** have control
group state for dashboard A (since it does not have unsaved control
changes) - so, we skip calling `setRuntimeStateForChild` for dashboard A
5. This means that `DashboardContainer` still has
`restoredRuntimeState[PANELS_CONTROL_GROUP_KEY]` equal to the changes
from dashboard B, which results in Dashboard A's control group getting
overwritten with `restoredRuntimeState[PANELS_CONTROL_GROUP_KEY]` 🔥

If we clear `restoredRuntimeState` in `navigateToDashboard`, this is no
longer an issue - we will now start from a blank slate on navigation,
which is the desired behaviour.


**Before**


https://github.com/user-attachments/assets/d04fa41f-2603-4b64-963d-b59c6be6fa14

**After**


https://github.com/user-attachments/assets/ce42c204-4ed0-4c44-8c15-c2f49a60131b
2025-04-09 08:46:56 -06:00
Kibana Machine
963a242be4
[8.17] [UI] Search bar does not auto-expand for long queries (#217556) (#217642)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[UI] Search bar does not auto-expand for long queries
(#217556)](https://github.com/elastic/kibana/pull/217556)

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

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

<!--BACKPORT
[{"author":{"name":"Ola","email":"98127445+olapawlus@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T10:10:31Z","message":"[UI]
Search bar does not auto-expand for long queries (#217556)\n\n##
Summary\nUpdates search bar styles to wrap long text inputs while
preserving\nformatting.\n\nCloses:
#211071","sha":"df60cc93929f9dad507bf2ab3c7001cbe1840502","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Presentation","backport:version","v9.1.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[UI]
Search bar does not auto-expand for long
queries","number":217556,"url":"https://github.com/elastic/kibana/pull/217556","mergeCommit":{"message":"[UI]
Search bar does not auto-expand for long queries (#217556)\n\n##
Summary\nUpdates search bar styles to wrap long text inputs while
preserving\nformatting.\n\nCloses:
#211071","sha":"df60cc93929f9dad507bf2ab3c7001cbe1840502"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217556","number":217556,"mergeCommit":{"message":"[UI]
Search bar does not auto-expand for long queries (#217556)\n\n##
Summary\nUpdates search bar styles to wrap long text inputs while
preserving\nformatting.\n\nCloses:
#211071","sha":"df60cc93929f9dad507bf2ab3c7001cbe1840502"}},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ola <98127445+olapawlus@users.noreply.github.com>
2025-04-09 14:09:51 +02:00
elastic-vault-github-plugin-prod[bot]
073ec79b28
[8.17] Sync bundled packages with Package Storage (#217543)
Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2596

Co-authored-by: elasticmachine <elasticmachine@elastic.co>
2025-04-09 11:56:10 +02:00
Lisa Cawley
ce91dea75c
[8.17] [DOCS] Remove Upgrade Assistant add default field API (#217264) (#217429)
# Backport

This will backport the following commits from `8.x` to `8.17`:
- [[DOCS] Remove Upgrade Assistant add default field API
(#217264)](https://github.com/elastic/kibana/pull/216373)

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

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T16:31:35Z","message":"[DOCS]
Remove Upgrade Assistant add default field API
(#217264)","sha":"0391d970dbbcf402a7b4f469f4be908921604b76"},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:skip","ci:build-docker-fips"],"title":"Update
docker.elastic.co/wolfi/chainguard-base-fips:latest Docker digest to
22d75e2
(8.x)","number":216373,"url":"https://github.com/elastic/kibana/pull/216373"},"sourceBranch":"8.x","suggestedTargetBranches":[],"targetPullRequestStates":[]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-08 11:06:08 -04:00
Pierre HILBERT
d572dd7d97
[Fleet] Fix download URL for Agent Standalone (#217468)
## Summary

Closes https://github.com/elastic/elastic-agent/issues/7716

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
2025-04-08 09:41:54 -04:00
elastic-renovate-prod[bot]
a1f09554c7
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to c56628d (8.17) (#216562)
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base | digest | `c4e10ec` ->
`c56628d` |

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
2025-04-08 08:08:58 -05:00
Kibana Machine
8dee6a7414
[8.17] [SharedUX][A11y] Fix Share modal export icon focusable (#217313) (#217474)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[SharedUX][A11y] Fix Share modal export icon focusable
(#217313)](https://github.com/elastic/kibana/pull/217313)

<!--- 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-04-08T10:00:08Z","message":"[SharedUX][A11y]
Fix Share modal export icon focusable (#217313)\n\n## Summary\n\nThis PR
fixes [[Platform:Dashboards:DashboardViewMode] Tooltips on\nexport tab
on share panel are not announced because of lack of
focus\non](https://github.com/elastic/kibana/issues/214447) and fixes
[[a11y]\nIn the sharing menu the POST url info cannot be accessed with
the\nkeyboar](215991d)
issues.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/9c8c532d-1628-4f57-a2f0-2fe1d09e5cb6\n\nAfter:
\n\n\nhttps://github.com/user-attachments/assets/d7716469-ad73-4241-934d-f9f4d23a1279","sha":"0a3e1fa3d8ed4c5741c10c7485fd7c6eb04d3a03","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-major","a11y","v9.1.0"],"title":"[SharedUX][A11y]
Fix Share modal export icon
focusable","number":217313,"url":"https://github.com/elastic/kibana/pull/217313","mergeCommit":{"message":"[SharedUX][A11y]
Fix Share modal export icon focusable (#217313)\n\n## Summary\n\nThis PR
fixes [[Platform:Dashboards:DashboardViewMode] Tooltips on\nexport tab
on share panel are not announced because of lack of
focus\non](https://github.com/elastic/kibana/issues/214447) and fixes
[[a11y]\nIn the sharing menu the POST url info cannot be accessed with
the\nkeyboar](215991d)
issues.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/9c8c532d-1628-4f57-a2f0-2fe1d09e5cb6\n\nAfter:
\n\n\nhttps://github.com/user-attachments/assets/d7716469-ad73-4241-934d-f9f4d23a1279","sha":"0a3e1fa3d8ed4c5741c10c7485fd7c6eb04d3a03"}},"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/217313","number":217313,"mergeCommit":{"message":"[SharedUX][A11y]
Fix Share modal export icon focusable (#217313)\n\n## Summary\n\nThis PR
fixes [[Platform:Dashboards:DashboardViewMode] Tooltips on\nexport tab
on share panel are not announced because of lack of
focus\non](https://github.com/elastic/kibana/issues/214447) and fixes
[[a11y]\nIn the sharing menu the POST url info cannot be accessed with
the\nkeyboar](215991d)
issues.\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/9c8c532d-1628-4f57-a2f0-2fe1d09e5cb6\n\nAfter:
\n\n\nhttps://github.com/user-attachments/assets/d7716469-ad73-4241-934d-f9f4d23a1279","sha":"0a3e1fa3d8ed4c5741c10c7485fd7c6eb04d3a03"}}]}]
BACKPORT-->

Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co>
2025-04-08 14:19:15 +02:00
Francesco Fagnani
d568ede594
[8.17] [Synthetics] Fix save lens visualization on monitors overview (#216695) (#217349)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Synthetics] Fix save lens visualization on monitors overview
(#216695)](https://github.com/elastic/kibana/pull/216695)

<!--- 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-04-07T13:47:53Z","message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839","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","v9.0.1","v8.17.5"],"title":"[Synthetics]
Fix save lens visualization on monitors
overview","number":216695,"url":"https://github.com/elastic/kibana/pull/216695","mergeCommit":{"message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216695","number":216695,"mergeCommit":{"message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217329","number":217329,"state":"OPEN"},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2025-04-08 08:01:22 -04:00
Kibana Machine
cc42b2c35a
[8.17] [ci] Minor quick-checks updates (#215856) (#217443)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[ci] Minor quick-checks updates
(#215856)](https://github.com/elastic/kibana/pull/215856)

<!--- 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-04-08T07:26:14Z","message":"[ci]
Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node
scripts/prettier_topology_check` occasionally breaks with\n`.gitignore`
not being available, it's required for a globby
call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2
- some scripts are run together by `yarn kbn run-in-packages` -
this\nscript only logs AFTER a script finished successfully; when a
script\nlike this fails, the failing script is not logged. This change
logs\nbefore to see what the error is.
(ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[ci]
Minor quick-checks
updates","number":215856,"url":"https://github.com/elastic/kibana/pull/215856","mergeCommit":{"message":"[ci]
Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node
scripts/prettier_topology_check` occasionally breaks with\n`.gitignore`
not being available, it's required for a globby
call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2
- some scripts are run together by `yarn kbn run-in-packages` -
this\nscript only logs AFTER a script finished successfully; when a
script\nlike this fails, the failing script is not logged. This change
logs\nbefore to see what the error is.
(ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e"}},"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/215856","number":215856,"mergeCommit":{"message":"[ci]
Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node
scripts/prettier_topology_check` occasionally breaks with\n`.gitignore`
not being available, it's required for a globby
call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2
- some scripts are run together by `yarn kbn run-in-packages` -
this\nscript only logs AFTER a script finished successfully; when a
script\nlike this fails, the failing script is not logged. This change
logs\nbefore to see what the error is.
(ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
2025-04-08 11:22:27 +02:00
Kibana Machine
8e36d35b2e
[8.17] [Synthetics] Fixed alert count in monitor details (#216761) (#217336)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[Synthetics] Fixed alert count in monitor details
(#216761)](https://github.com/elastic/kibana/pull/216761)

<!--- 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-04-07T13:47:40Z","message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0","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","v9.0.1","v8.17.5"],"title":"[Synthetics]
Fixed alert count in monitor
details","number":216761,"url":"https://github.com/elastic/kibana/pull/216761","mergeCommit":{"message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216761","number":216761,"mergeCommit":{"message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
2025-04-07 18:01:42 +02:00
Robert Jaszczurek
815d7671eb
[8.17] [ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178) (#217315)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[ML] AIOps: Change Point Detection in Dashboards embeddable fix
(#217178)](https://github.com/elastic/kibana/pull/217178)

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

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

<!--BACKPORT [{"author":{"name":"Robert
Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-07T10:06:30Z","message":"[ML]
AIOps: Change Point Detection in Dashboards embeddable fix
(#217178)\n\nIt fixes an issue where adding the `Change Point Detection`
embeddable\ndidn't work properly.\nThe bug was introduced in
https://github.com/elastic/kibana/pull/197943\nThe main cause was the
use of `<ChangePointDetectionContextProvider>`\nwhich calls
`timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work,
`this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this
is not the case within dashboards.\nHowever, we do not actually need the
`ChangePointDetectionContext`\ninside the embeddable, so this PR removes
its usage.\nA functional test has been added to cover adding the Change
Point\nembeddable from the dashboards app. It's a very simple test that
does\nnot verify the embeddable's functionality, but it could be
improved in
a\nfollow-up.\n\n![image](https://github.com/user-attachments/assets/52b7f28b-87a0-423e-a923-d3e02300bf71)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:ML/AIOps","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[ML]
AIOps: Change Point Detection in Dashboards embeddable
fix","number":217178,"url":"https://github.com/elastic/kibana/pull/217178","mergeCommit":{"message":"[ML]
AIOps: Change Point Detection in Dashboards embeddable fix
(#217178)\n\nIt fixes an issue where adding the `Change Point Detection`
embeddable\ndidn't work properly.\nThe bug was introduced in
https://github.com/elastic/kibana/pull/197943\nThe main cause was the
use of `<ChangePointDetectionContextProvider>`\nwhich calls
`timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work,
`this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this
is not the case within dashboards.\nHowever, we do not actually need the
`ChangePointDetectionContext`\ninside the embeddable, so this PR removes
its usage.\nA functional test has been added to cover adding the Change
Point\nembeddable from the dashboards app. It's a very simple test that
does\nnot verify the embeddable's functionality, but it could be
improved in
a\nfollow-up.\n\n![image](https://github.com/user-attachments/assets/52b7f28b-87a0-423e-a923-d3e02300bf71)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217178","number":217178,"mergeCommit":{"message":"[ML]
AIOps: Change Point Detection in Dashboards embeddable fix
(#217178)\n\nIt fixes an issue where adding the `Change Point Detection`
embeddable\ndidn't work properly.\nThe bug was introduced in
https://github.com/elastic/kibana/pull/197943\nThe main cause was the
use of `<ChangePointDetectionContextProvider>`\nwhich calls
`timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work,
`this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this
is not the case within dashboards.\nHowever, we do not actually need the
`ChangePointDetectionContext`\ninside the embeddable, so this PR removes
its usage.\nA functional test has been added to cover adding the Change
Point\nembeddable from the dashboards app. It's a very simple test that
does\nnot verify the embeddable's functionality, but it could be
improved in
a\nfollow-up.\n\n![image](https://github.com/user-attachments/assets/52b7f28b-87a0-423e-a923-d3e02300bf71)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f"}},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-04-07 16:34:01 +02:00
Kibana Machine
3feee016da
[8.17] [ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979) (#217295)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[ResponseOps][Cases] Support horizontal scrolling for tables inside
the markdown editor
(#216979)](https://github.com/elastic/kibana/pull/216979)

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

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

<!--BACKPORT [{"author":{"name":"Georgiana-Andreea
Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T09:54:11Z","message":"[ResponseOps][Cases]
Support horizontal scrolling for tables inside the markdown editor
(#216979)\n\nCloses
https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n-
Applied changes to improve layout stability: removed the
`word-break\n`and limited the outer flex item to `max-width: 75%`, as
suggested in\nthe
ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[ResponseOps][Cases]
Support horizontal scrolling for tables inside the markdown
editor","number":216979,"url":"https://github.com/elastic/kibana/pull/216979","mergeCommit":{"message":"[ResponseOps][Cases]
Support horizontal scrolling for tables inside the markdown editor
(#216979)\n\nCloses
https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n-
Applied changes to improve layout stability: removed the
`word-break\n`and limited the outer flex item to `max-width: 75%`, as
suggested in\nthe
ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"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/216979","number":216979,"mergeCommit":{"message":"[ResponseOps][Cases]
Support horizontal scrolling for tables inside the markdown editor
(#216979)\n\nCloses
https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n-
Applied changes to improve layout stability: removed the
`word-break\n`and limited the outer flex item to `max-width: 75%`, as
suggested in\nthe
ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by:
Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>
2025-04-07 13:52:15 +02:00
Sid
bbb6a64691
[8.17] Additional prototype pollution protections (#206073) (#216286)
# Backport

This will backport the following commits from `main` to `8.17`:
- [Additional prototype pollution protections
(#206073)](https://github.com/elastic/kibana/pull/206073)

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

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

<!--BACKPORT [{"author":{"name":"Larry
Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T22:00:43Z","message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR
introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Hardening","v9.0.0","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-elasticsearch","backport:version","v8.17.0","v8.18.0","ci:all-gen-ai-suites","v9.1.0"],"title":"Additional
prototype pollution
protections","number":206073,"url":"https://github.com/elastic/kibana/pull/206073","mergeCommit":{"message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR
introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206073","number":206073,"mergeCommit":{"message":"Additional
prototype pollution protections (#206073)\n\n## Summary\n\n1. Extends
the server-side prototype pollution protections introduced
in\nhttps://github.com/elastic/kibana/pull/190716 to
include\n`Array.prototype`.\n2. Applies the same prototype pollution
protections to the client-side.\n\n\n### Identify risks\n\nDoes this PR
introduce any risks? For example, consider risks like hard\nto test
bugs, performance regression, potential of data loss.\n\nDescribe the
risk, its severity, and mitigation for each identified\nrisk. Invite
stakeholders and evaluate how to proceed before merging.\n\n- [ ]
Sealing prototypes on the client can lead to failures in\nthird-party
dependencies. I'm relying on sufficient functional test\ncoverage to
detect issues here. As a result, these protections are\ndisabled by
default for now, and can be controlled via
setting\n`server.prototypeHardening:
true/false`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9ce2dd8df9f2bd6c0ba1d089b69ddfd7fc1f4a02"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/208742","number":208742,"state":"MERGED","mergeCommit":{"sha":"24f82ee808ca45130b44e062aabbaf9475ca7a58","message":"[8.x]
Additional prototype pollution protections (#206073) (#208742)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.x`:\n- [Additional prototype pollution
protections\n(#206073)](https://github.com/elastic/kibana/pull/206073)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Larry Gregory <larry.gregory@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-04-04 20:52:26 +02:00
Kevin Delemme
7746e727fc
[8.17] fix(slo): group by with empty string (#217084) (#217208)
# Backport

This will backport the following commits from `main` to `8.17`:
- [fix(slo): group by with empty string
(#217084)](https://github.com/elastic/kibana/pull/217084)

<!--- 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-04-03T20:41:56Z","message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05","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","v9.0.1","v8.17.5"],"title":"fix(slo):
group by with empty
string","number":217084,"url":"https://github.com/elastic/kibana/pull/217084","mergeCommit":{"message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217110","number":217110,"state":"MERGED","mergeCommit":{"sha":"f5054deba36b1843262c64d27c8d0827f96b50bc","message":"[9.0]
fix(slo): group by with empty string (#217084) (#217110)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [fix(slo): group by with empty
string\n(#217084)](https://github.com/elastic/kibana/pull/217084)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Kevin Delemme
<kevin.delemme@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217084","number":217084,"mergeCommit":{"message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},{"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.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2025-04-04 17:44:25 +01:00
Aleh Zasypkin
5f0893c719
[8.17] chore(deps): upgrade tar-fs from 2.1.1 to 2.1.2 (#217173) (#217209)
# Backport

This will backport the following commits from `main` to `8.17`:
- [chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2`
(#217173)](https://github.com/elastic/kibana/pull/217173)

<!--- 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-04-04T14:18:38Z","message":"chore(deps):
upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n##
Summary\n\nUpgrade `tar-fs` from `2.1.1` to
`2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","backport:all-open","v9.1.0"],"title":"chore(deps):
upgrade `tar-fs` from `2.1.1` to
`2.1.2`","number":217173,"url":"https://github.com/elastic/kibana/pull/217173","mergeCommit":{"message":"chore(deps):
upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n##
Summary\n\nUpgrade `tar-fs` from `2.1.1` to
`2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81"}},"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/217173","number":217173,"mergeCommit":{"message":"chore(deps):
upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n##
Summary\n\nUpgrade `tar-fs` from `2.1.1` to
`2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81"}},{"url":"https://github.com/elastic/kibana/pull/217204","number":217204,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217205","number":217205,"branch":"9.0","state":"OPEN"}]}]
BACKPORT-->
2025-04-04 17:42:16 +01:00
Kibana Machine
8e64d29ffd
[8.17] [SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693) (#217191)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[SO migration] Move to previous step in update mappings wait when it
fails with search_phase_execution_exception
(#216693)](https://github.com/elastic/kibana/pull/216693)

<!--- 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-04-04T13:37:06Z","message":"[SO
migration] Move to previous step in update mappings wait when it fails
with search_phase_execution_exception (#216693)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana/issues/207096\n\nThis continues the
work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES
returns a 200 response containing an error field when we\nwait for the
update mappings task. This case wasn't being handled. This\nPR handles
that case, when we find a `search_phase_execution_exception`\nin the ES
response we return a retryable error that sends us back to the\nupdate
mappings state. It does it for both migration algorithms, the\npriority
is ZDT but seemed like a nice to have in both.\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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4","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":"[SO
migration] Move to previous step in update mappings wait when it fails
with
search_phase_execution_exception","number":216693,"url":"https://github.com/elastic/kibana/pull/216693","mergeCommit":{"message":"[SO
migration] Move to previous step in update mappings wait when it fails
with search_phase_execution_exception (#216693)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana/issues/207096\n\nThis continues the
work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES
returns a 200 response containing an error field when we\nwait for the
update mappings task. This case wasn't being handled. This\nPR handles
that case, when we find a `search_phase_execution_exception`\nin the ES
response we return a retryable error that sends us back to the\nupdate
mappings state. It does it for both migration algorithms, the\npriority
is ZDT but seemed like a nice to have in both.\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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}},"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/216693","number":216693,"mergeCommit":{"message":"[SO
migration] Move to previous step in update mappings wait when it fails
with search_phase_execution_exception (#216693)\n\n##
Summary\n\nResolves
https://github.com/elastic/kibana/issues/207096\n\nThis continues the
work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES
returns a 200 response containing an error field when we\nwait for the
update mappings task. This case wasn't being handled. This\nPR handles
that case, when we find a `search_phase_execution_exception`\nin the ES
response we return a retryable error that sends us back to the\nupdate
mappings state. It does it for both migration algorithms, the\npriority
is ZDT but seemed like a nice to have in both.\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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}}]}]
BACKPORT-->

Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>
2025-04-04 16:49:34 +01:00
Gonçalo Rica Pais da Silva
4e5a545a0b
[8.17] [APM] Do not rely on rendered items directly to update dependent requests (#216312) (#217162)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[APM] Do not rely on rendered items directly to update dependent
requests (#216312)](https://github.com/elastic/kibana/pull/216312)

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

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

<!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da
Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T18:23:09Z","message":"[APM]
Do not rely on rendered items directly to update dependent requests
(#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for
particular cases. In some\ncases, when the page updates with some new
criteria/filters, requests\nthat were being managed by `ManagedTable`
would fire at least twice,\nwith the first one getting aborted and then
resent. This PR removes that\nbehaviour by not storing the dependent
data in a `renderedItems` state\nand instead depending directly on the
request data itself and storing\ninstead the indices of the rendered
items. This removes the edge-case\nwhere `renderedItems` would cause the
affected requests from firing\nmultiple times, due to object equality
not being the same for the\nrendered items array between
renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability ->
Applications -> Service Inventory\n* Select a service with more than one
environment\n* Go to Errors tab and open the browser dev tools\n* Change
the environment on the service to update the errors tab\n\n**Expected
behaviour**: The `detailed_statistics` request should only\nfire once,
both on page load and on update (such as changing the
service\nenvironment).\n\nThis should apply to the Service Inventory
page as well, and anything\nmaking use of the `TransactionsTable`
component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","apm","backport:prev-major","Team:obs-ux-infra_services","v8.17.0","v9.1.0"],"title":"[APM]
Do not rely on rendered items directly to update dependent
requests","number":216312,"url":"https://github.com/elastic/kibana/pull/216312","mergeCommit":{"message":"[APM]
Do not rely on rendered items directly to update dependent requests
(#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for
particular cases. In some\ncases, when the page updates with some new
criteria/filters, requests\nthat were being managed by `ManagedTable`
would fire at least twice,\nwith the first one getting aborted and then
resent. This PR removes that\nbehaviour by not storing the dependent
data in a `renderedItems` state\nand instead depending directly on the
request data itself and storing\ninstead the indices of the rendered
items. This removes the edge-case\nwhere `renderedItems` would cause the
affected requests from firing\nmultiple times, due to object equality
not being the same for the\nrendered items array between
renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability ->
Applications -> Service Inventory\n* Select a service with more than one
environment\n* Go to Errors tab and open the browser dev tools\n* Change
the environment on the service to update the errors tab\n\n**Expected
behaviour**: The `detailed_statistics` request should only\nfire once,
both on page load and on update (such as changing the
service\nenvironment).\n\nThis should apply to the Service Inventory
page as well, and anything\nmaking use of the `TransactionsTable`
component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.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/216312","number":216312,"mergeCommit":{"message":"[APM]
Do not rely on rendered items directly to update dependent requests
(#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for
particular cases. In some\ncases, when the page updates with some new
criteria/filters, requests\nthat were being managed by `ManagedTable`
would fire at least twice,\nwith the first one getting aborted and then
resent. This PR removes that\nbehaviour by not storing the dependent
data in a `renderedItems` state\nand instead depending directly on the
request data itself and storing\ninstead the indices of the rendered
items. This removes the edge-case\nwhere `renderedItems` would cause the
affected requests from firing\nmultiple times, due to object equality
not being the same for the\nrendered items array between
renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability ->
Applications -> Service Inventory\n* Select a service with more than one
environment\n* Go to Errors tab and open the browser dev tools\n* Change
the environment on the service to update the errors tab\n\n**Expected
behaviour**: The `detailed_statistics` request should only\nfire once,
both on page load and on update (such as changing the
service\nenvironment).\n\nThis should apply to the Service Inventory
page as well, and anything\nmaking use of the `TransactionsTable`
component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f"}}]}]
BACKPORT-->
2025-04-04 14:23:23 +01:00
Kibana Machine
46091ee20b
[8.17] [CI] Allow using elastic-images-qa through PR label or env var (#216878) (#217139)
# Backport

This will backport the following commits from `main` to `8.17`:
- [[CI] Allow using `elastic-images-qa` through PR label or env var
(#216878)](https://github.com/elastic/kibana/pull/216878)

<!--- 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-04-04T08:05:30Z","message":"[CI]
Allow using `elastic-images-qa` through PR label or env var
(#216878)\n\n## Summary\nCurrently, if you'd like to test something on
Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite
all references to\n`elastic-images-qa` for the PR jobs; once done with
testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a
helpful tool for us to test with WIP VM images, we'd be able\nto add a
label to the PR, and it would automatically grab the QA images,\nwithout
any temporary commits.\n\nJobs in
https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave
ran with an elastic-qa image.
","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:use-qa-image","v9.1.0"],"title":"[CI]
Allow using `elastic-images-qa` through PR label or env
var","number":216878,"url":"https://github.com/elastic/kibana/pull/216878","mergeCommit":{"message":"[CI]
Allow using `elastic-images-qa` through PR label or env var
(#216878)\n\n## Summary\nCurrently, if you'd like to test something on
Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite
all references to\n`elastic-images-qa` for the PR jobs; once done with
testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a
helpful tool for us to test with WIP VM images, we'd be able\nto add a
label to the PR, and it would automatically grab the QA images,\nwithout
any temporary commits.\n\nJobs in
https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave
ran with an elastic-qa image.
","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1"}},"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/216878","number":216878,"mergeCommit":{"message":"[CI]
Allow using `elastic-images-qa` through PR label or env var
(#216878)\n\n## Summary\nCurrently, if you'd like to test something on
Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite
all references to\n`elastic-images-qa` for the PR jobs; once done with
testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a
helpful tool for us to test with WIP VM images, we'd be able\nto add a
label to the PR, and it would automatically grab the QA images,\nwithout
any temporary commits.\n\nJobs in
https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave
ran with an elastic-qa image.
","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1"}}]}] BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
2025-04-04 11:12:21 +01:00