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

84501 commits

This branch
This branch
All branches
Author SHA1 Message Date
Kibana Machine
e9c10d757c
[9.0] Improve accessibility in create connector flyout (#218426) (#218683) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [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-18 23:55:20 +02:00
elastic-renovate-prod[bot]
d308405d88
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 5ffa55a (9.0) (#218623) 
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-18 23:26:29 +02:00
elastic-renovate-prod[bot]
78cc90cdea
Update docker.elastic.co/wolfi/chainguard-base-fips:latest Docker digest to 88dc781 (9.0) (#218592) 
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base-fips | digest | `b6d3d24` ->
`88dc781` |

---

### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJjaTpidWlsZC1kb2NrZXItZmlwcyIsInJlbGVhc2Vfbm90ZTpza2lwIl19-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: Brad White <Ikuni17@users.noreply.github.com>
 2025-04-18 22:25:55 +02:00
Kibana Machine
01d7f190db
[9.0] [Security Solution] Fixes related integrations render performance on rule editing pages (#217254) (#218671) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Fixes related integrations render performance on
rule editing pages
(#217254)](https://github.com/elastic/kibana/pull/217254)

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

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

<!--BACKPORT [{"author":{"name":"Davis
Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-18T18:47:20Z","message":"[Security
Solution] Fixes related integrations render performance on rule editing
pages (#217254)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the
re-render performance issues caused by the related\nintegrations
component on the rule edit and creation pages. This copies\na strategy
used in https://github.com/elastic/kibana/pull/180682 to fix\na similar
issue with required fields. Related integrations component now\ndoesn't
re-render when there are updates to components that don't
affect\nit.\n\n#### React Profile while typing in query field
component\n![Screenshot 2025-04-04 at 8
12\n38 PM](https://github.com/user-attachments/assets/9d3edcaa-4856-42df-9e6d-59bcc4785b5d)\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection Rule
Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution] Fixes related integrations render performance on rule editing
pages","number":217254,"url":"https://github.com/elastic/kibana/pull/217254","mergeCommit":{"message":"[Security
Solution] Fixes related integrations render performance on rule editing
pages (#217254)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the
re-render performance issues caused by the related\nintegrations
component on the rule edit and creation pages. This copies\na strategy
used in https://github.com/elastic/kibana/pull/180682 to fix\na similar
issue with required fields. Related integrations component now\ndoesn't
re-render when there are updates to components that don't
affect\nit.\n\n#### React Profile while typing in query field
component\n![Screenshot 2025-04-04 at 8
12\n38 PM](https://github.com/user-attachments/assets/9d3edcaa-4856-42df-9e6d-59bcc4785b5d)\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217254","number":217254,"mergeCommit":{"message":"[Security
Solution] Fixes related integrations render performance on rule editing
pages (#217254)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the
re-render performance issues caused by the related\nintegrations
component on the rule edit and creation pages. This copies\na strategy
used in https://github.com/elastic/kibana/pull/180682 to fix\na similar
issue with required fields. Related integrations component now\ndoesn't
re-render when there are updates to components that don't
affect\nit.\n\n#### React Profile while typing in query field
component\n![Screenshot 2025-04-04 at 8
12\n38 PM](https://github.com/user-attachments/assets/9d3edcaa-4856-42df-9e6d-59bcc4785b5d)\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca"}},{"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"}]}]
BACKPORT-->

Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>
 2025-04-18 22:12:44 +02:00
Kibana Machine
f9f11a5e4b
[9.0] [SB] Fix graph layout stories (#217766) (#218476) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[SB] Fix graph layout stories
(#217766)](https://github.com/elastic/kibana/pull/217766)

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

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

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T16:59:08Z","message":"[SB]
Fix graph layout stories (#217766)\n\n## Summary\n\nThis fixes the graph
layout stories not rendering properly after\n#214684. Open to a better
or preferred fix as I'm not familiar with\nthese components.\n\nThere
was a console warning:\n```js\n[React Flow]: The React Flow parent
container needs a width and a height to render the graph. Help:
https://reactflow.dev/error#004\n```\n\n[Storybook
preview\nlink](https://ci-artifacts.kibana.dev/storybooks/pr-217766/cloud_security_posture_graph/index.html?path=/story/components-graph-components-graph-layout--simple-api-mock)\n\n---------\n\nCo-authored-by:
Kfir Peled
<61654899+kfirpeled@users.noreply.github.com>","sha":"a7796cd0d00453f67d0f5c4366352c53d6c63131","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:build-storybooks","backport:version","v9.1.0","v8.19.0"],"title":"[SB]
Fix graph layout
stories","number":217766,"url":"https://github.com/elastic/kibana/pull/217766","mergeCommit":{"message":"[SB]
Fix graph layout stories (#217766)\n\n## Summary\n\nThis fixes the graph
layout stories not rendering properly after\n#214684. Open to a better
or preferred fix as I'm not familiar with\nthese components.\n\nThere
was a console warning:\n```js\n[React Flow]: The React Flow parent
container needs a width and a height to render the graph. Help:
https://reactflow.dev/error#004\n```\n\n[Storybook
preview\nlink](https://ci-artifacts.kibana.dev/storybooks/pr-217766/cloud_security_posture_graph/index.html?path=/story/components-graph-components-graph-layout--simple-api-mock)\n\n---------\n\nCo-authored-by:
Kfir Peled
<61654899+kfirpeled@users.noreply.github.com>","sha":"a7796cd0d00453f67d0f5c4366352c53d6c63131"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217766","number":217766,"mergeCommit":{"message":"[SB]
Fix graph layout stories (#217766)\n\n## Summary\n\nThis fixes the graph
layout stories not rendering properly after\n#214684. Open to a better
or preferred fix as I'm not familiar with\nthese components.\n\nThere
was a console warning:\n```js\n[React Flow]: The React Flow parent
container needs a width and a height to render the graph. Help:
https://reactflow.dev/error#004\n```\n\n[Storybook
preview\nlink](https://ci-artifacts.kibana.dev/storybooks/pr-217766/cloud_security_posture_graph/index.html?path=/story/components-graph-components-graph-layout--simple-api-mock)\n\n---------\n\nCo-authored-by:
Kfir Peled
<61654899+kfirpeled@users.noreply.github.com>","sha":"a7796cd0d00453f67d0f5c4366352c53d6c63131"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Brad White <Ikuni17@users.noreply.github.com>
 2025-04-18 19:24:41 +00:00
Kibana Machine
02dc9ab14e
[9.0] SKA: Relocate ai assistant management (#218129) (#218555) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [SKA: Relocate ai assistant management
(#218129)](https://github.com/elastic/kibana/pull/218129)

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

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

<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T11:55:02Z","message":"SKA:
Relocate ai assistant management (#218129)\n\n##
Summary\n\nPre-requisite for
https://github.com/elastic/kibana/pull/216088, as the\n`AI Assistant
Management` configuration settings should be available for\nSearch
too.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cf94c2fe0f572e52edf379b91a61128a33912c17","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v9.1.0"],"title":"SKA:
Relocate ai assistant
management","number":218129,"url":"https://github.com/elastic/kibana/pull/218129","mergeCommit":{"message":"SKA:
Relocate ai assistant management (#218129)\n\n##
Summary\n\nPre-requisite for
https://github.com/elastic/kibana/pull/216088, as the\n`AI Assistant
Management` configuration settings should be available for\nSearch
too.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cf94c2fe0f572e52edf379b91a61128a33912c17"}},"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/218129","number":218129,"mergeCommit":{"message":"SKA:
Relocate ai assistant management (#218129)\n\n##
Summary\n\nPre-requisite for
https://github.com/elastic/kibana/pull/216088, as the\n`AI Assistant
Management` configuration settings should be available for\nSearch
too.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cf94c2fe0f572e52edf379b91a61128a33912c17"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co>
 2025-04-18 16:09:54 +02:00
Kibana Machine
3fdbb83968
[9.0] Update dependency @launchdarkly/node-server-sdk to ^9.8.0 (main) (#218366) (#218650) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Update dependency @launchdarkly/node-server-sdk to ^9.8.0 (main)
(#218366)](https://github.com/elastic/kibana/pull/218366)

<!--- 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-18T12:21:32Z","message":"Update
dependency @launchdarkly/node-server-sdk to ^9.8.0 (main)
(#218366)\n\nThis PR contains the following updates:\n\n| Package | Type
| Update | Change
|\n|---|---|---|---|\n|\n[@launchdarkly/node-server-sdk](https://redirect.github.com/launchdarkly/js-core/tree/main/packages/sdk/server-node)\n([source](https://redirect.github.com/launchdarkly/js-core))
|\ndependencies | minor | [`^9.7.7`
->\n`^9.8.0`](https://renovatebot.com/diffs/npm/@launchdarkly%2fnode-server-sdk/9.7.7/9.8.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":"b1887104c179354011046e4db685a4663d817c73","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Security","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update
dependency @launchdarkly/node-server-sdk to ^9.8.0
(main)","number":218366,"url":"https://github.com/elastic/kibana/pull/218366","mergeCommit":{"message":"Update
dependency @launchdarkly/node-server-sdk to ^9.8.0 (main)
(#218366)\n\nThis PR contains the following updates:\n\n| Package | Type
| Update | Change
|\n|---|---|---|---|\n|\n[@launchdarkly/node-server-sdk](https://redirect.github.com/launchdarkly/js-core/tree/main/packages/sdk/server-node)\n([source](https://redirect.github.com/launchdarkly/js-core))
|\ndependencies | minor | [`^9.7.7`
->\n`^9.8.0`](https://renovatebot.com/diffs/npm/@launchdarkly%2fnode-server-sdk/9.7.7/9.8.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":"b1887104c179354011046e4db685a4663d817c73"}},"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/218366","number":218366,"mergeCommit":{"message":"Update
dependency @launchdarkly/node-server-sdk to ^9.8.0 (main)
(#218366)\n\nThis PR contains the following updates:\n\n| Package | Type
| Update | Change
|\n|---|---|---|---|\n|\n[@launchdarkly/node-server-sdk](https://redirect.github.com/launchdarkly/js-core/tree/main/packages/sdk/server-node)\n([source](https://redirect.github.com/launchdarkly/js-core))
|\ndependencies | minor | [`^9.7.7`
->\n`^9.8.0`](https://renovatebot.com/diffs/npm/@launchdarkly%2fnode-server-sdk/9.7.7/9.8.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":"b1887104c179354011046e4db685a4663d817c73"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-18 15:51:46 +02:00
Kibana Machine
8f1ca120f1
[9.0] [Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540) (#218596) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Show banner to promote prebuilt rule
customization in both Serverless and ESS
(#218540)](https://github.com/elastic/kibana/pull/218540)

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

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

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T17:11:47Z","message":"[Security
Solution] Show banner to promote prebuilt rule customization in both
Serverless and ESS (#218540)\n\n**Resolves:
https://github.com/elastic/kibana/issues/209000**\n**Related PR:
https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR
updates the code to show a promo banner in the rules table. With\nthis
change, this banner will be shown in both ESS (8.18+) and\nServerless.
Previously it was shown only in ESS. In both ESS and\nServerless the
blog link is the same – this is expected and correct.\n\nWe couldn't add
a banner for Serverless earlier, because the blog post\nwas published on
the 8.18/9.0 release day. If we would have added it\nearlier, Serverless
users would click on a link at get a 404 page.\n\nExpected behaviour for
both ESS and Serverless:\n - Banner is visible above the rules table\n-
The link leads
to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img
width=\"1006\" alt=\"Scherm­afbeelding 2025-03-11 om 12 25
45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n-
Adds a rule management table banner to promote prebuilt
rule\ncustomization in Serverless. Previously this banner was only shown
in\nESS. Banner is dismissible. Its state is stored in localStorage.\n-
Tweaks banner wording a bit as per docs
suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution] Show banner to promote prebuilt rule customization in both
Serverless and
ESS","number":218540,"url":"https://github.com/elastic/kibana/pull/218540","mergeCommit":{"message":"[Security
Solution] Show banner to promote prebuilt rule customization in both
Serverless and ESS (#218540)\n\n**Resolves:
https://github.com/elastic/kibana/issues/209000**\n**Related PR:
https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR
updates the code to show a promo banner in the rules table. With\nthis
change, this banner will be shown in both ESS (8.18+) and\nServerless.
Previously it was shown only in ESS. In both ESS and\nServerless the
blog link is the same – this is expected and correct.\n\nWe couldn't add
a banner for Serverless earlier, because the blog post\nwas published on
the 8.18/9.0 release day. If we would have added it\nearlier, Serverless
users would click on a link at get a 404 page.\n\nExpected behaviour for
both ESS and Serverless:\n - Banner is visible above the rules table\n-
The link leads
to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img
width=\"1006\" alt=\"Scherm­afbeelding 2025-03-11 om 12 25
45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n-
Adds a rule management table banner to promote prebuilt
rule\ncustomization in Serverless. Previously this banner was only shown
in\nESS. Banner is dismissible. Its state is stored in localStorage.\n-
Tweaks banner wording a bit as per docs
suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218540","number":218540,"mergeCommit":{"message":"[Security
Solution] Show banner to promote prebuilt rule customization in both
Serverless and ESS (#218540)\n\n**Resolves:
https://github.com/elastic/kibana/issues/209000**\n**Related PR:
https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR
updates the code to show a promo banner in the rules table. With\nthis
change, this banner will be shown in both ESS (8.18+) and\nServerless.
Previously it was shown only in ESS. In both ESS and\nServerless the
blog link is the same – this is expected and correct.\n\nWe couldn't add
a banner for Serverless earlier, because the blog post\nwas published on
the 8.18/9.0 release day. If we would have added it\nearlier, Serverless
users would click on a link at get a 404 page.\n\nExpected behaviour for
both ESS and Serverless:\n - Banner is visible above the rules table\n-
The link leads
to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img
width=\"1006\" alt=\"Scherm­afbeelding 2025-03-11 om 12 25
45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n-
Adds a rule management table banner to promote prebuilt
rule\ncustomization in Serverless. Previously this banner was only shown
in\nESS. Banner is dismissible. Its state is stored in localStorage.\n-
Tweaks banner wording a bit as per docs
suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf"}},{"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"}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
 2025-04-18 09:24:05 +00:00
Elena Stoeva
de1b09a732
[9.0] [Console] Fix test for opening documentation (#218318) (#218552) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Console] Fix test for opening documentation
(#218318)](https://github.com/elastic/kibana/pull/218318)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T09:28:01Z","message":"[Console]
Fix test for opening documentation (#218318)\n\nFixes
https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR
fixes the Console tests for opening documentation which were\nfailing
because the doc
link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis
now redirecting
to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v9.0.1"],"title":"[Console]
Fix test for opening
documentation","number":218318,"url":"https://github.com/elastic/kibana/pull/218318","mergeCommit":{"message":"[Console]
Fix test for opening documentation (#218318)\n\nFixes
https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR
fixes the Console tests for opening documentation which were\nfailing
because the doc
link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis
now redirecting
to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218318","number":218318,"mergeCommit":{"message":"[Console]
Fix test for opening documentation (#218318)\n\nFixes
https://github.com/elastic/kibana/issues/218255\n\n## Summary\n\nThis PR
fixes the Console tests for opening documentation which were\nfailing
because the doc
link\nhttps://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html\nis
now redirecting
to\nhttps://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search.","sha":"5ce6ce575f25fa93a89234e1a5431627209d989b"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-17 20:45:46 -05:00
Ersin Erdal
74a6d1b837
[9.0] Auto increase fields limit of the alert indices (#216719) (#218202) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Auto increase fields limit of the alert indices
(#216719)](https://github.com/elastic/kibana/pull/216719)

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

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

<!--BACKPORT [{"author":{"name":"Ersin
Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T07:38:27Z","message":"Auto
increase fields limit of the alert indices (#216719)\n\nThis PR adds the
auto-increase the fields limit on startup when an\nalerts index reaches
its limits because of the dynamic fields.\n\n# To verify:\nTo be able to
test this PR we need a rule type that adds dynamic fields.\nI used the
custom threshold rule for this:\n\nGo to the custom threshold rule type
definition and change its\nalerts.mappings to:\n```\n mappings: {\n //
dynamic: true,\n fieldMap: {\n 'kibana.alerting.grouping': {\n type:
'object',\n dynamic: true,\n array: false,\n required: false,\n },\n
...legacyExperimentalFieldMap,\n ...Array(412)\n .fill(0)\n
.reduce((acc, val, i) => {\n acc[`${i + 1}`] = { type: 'keyword', array:
false, required: false };\n return acc;\n }, {}),\n },\n
dynamicTemplates: [\n {\n strings_as_keywords: {\n path_match:
'kibana.alert.grouping.*',\n match_mapping_type: 'string',\n mapping:
{\n type: 'keyword',\n ignore_above: 1024,\n },\n },\n },\n ],\n },\n
```\n \n Above changes adds 412 dummy fields to the alerts index to make
it close to reach its fields limit (default: 2500).\n And makes
everything under `kibana.alert.grouping` path to be added to the index
as dynamic fields.\n \n Then apply the below changes to the custom
threshold rule executor:\n ```\n const grouping: Record<string, string>
= {};\n groups?.forEach((groupObj) => (grouping[groupObj.field] =
groupObj.value));\n \n const { uuid, start } = alertsClient.report({\n
id: `${group}`,\n actionGroup: actionGroupId,\n payload: {\n
[ALERT_REASON]: reason,\n [ALERT_EVALUATION_VALUES]: evaluationValues,\n
[ALERT_EVALUATION_THRESHOLD]: threshold,\n [ALERT_GROUP]: groups,\n //
@ts-ignore\n ['kibana.alerting.grouping']: grouping,\n
...flattenAdditionalContext(additionalContext),\n
...getEcsGroups(groups),\n },\n }); \n ```\n \nAbove changes add the
selected groups under `kibana.alerting.grouping` path.\n \nThen: \n- Run
ES with ` path.data=../your-local-data-path` to keep the data for the
next start.\n- Run Kibana\n- Create a custom threshold rule that
generates an alert and has at least 2 groups.\n- Let the rule run.\n- Go
to `Stack Management` > `Index Management` and search for observability
threshold index.\n- Check its mappings, it should show the dummy fields
you have added to the rule type and the first grouping you have selected
while you were creating the rule type.\n- Go to the Dev Tools and find
your alert in the
`.internal.alerts-observability.threshold.alerts-default-000001`
index.\nThe other groups you have selected should be saved under
`_ignored` field:\n```\n\"_ignored\": [\n
\"kibana.alerting.grouping.host.name\"\n],\n```\n- Stop Kibana\n-
increase the number of dummy fields you have added to the rule type
definition:\n```\n ...Array(412) <-- make this greater than 412\n
.fill(0)\n```\n- Start kibana again.\n- The new fields should be added
to the mappings. Check them on `Stack Management` > `Index Management`
\n- Check also the index settings: `Stack Management` > `Index
Management` >
`.internal.alerts-observability.threshold.alerts-default-000001` >
settings tab.\n- `\"mapping\" > \"total_fields\" > \"limit\" ` should be
greater than 2500\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f6c30d6b9ad1a46a73cc5c084a5e70051d78a7cb","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","v9.1.0","v8.19.0"],"title":"Auto
increase fields limit of the alert
indices","number":216719,"url":"https://github.com/elastic/kibana/pull/216719","mergeCommit":{"message":"Auto
increase fields limit of the alert indices (#216719)\n\nThis PR adds the
auto-increase the fields limit on startup when an\nalerts index reaches
its limits because of the dynamic fields.\n\n# To verify:\nTo be able to
test this PR we need a rule type that adds dynamic fields.\nI used the
custom threshold rule for this:\n\nGo to the custom threshold rule type
definition and change its\nalerts.mappings to:\n```\n mappings: {\n //
dynamic: true,\n fieldMap: {\n 'kibana.alerting.grouping': {\n type:
'object',\n dynamic: true,\n array: false,\n required: false,\n },\n
...legacyExperimentalFieldMap,\n ...Array(412)\n .fill(0)\n
.reduce((acc, val, i) => {\n acc[`${i + 1}`] = { type: 'keyword', array:
false, required: false };\n return acc;\n }, {}),\n },\n
dynamicTemplates: [\n {\n strings_as_keywords: {\n path_match:
'kibana.alert.grouping.*',\n match_mapping_type: 'string',\n mapping:
{\n type: 'keyword',\n ignore_above: 1024,\n },\n },\n },\n ],\n },\n
```\n \n Above changes adds 412 dummy fields to the alerts index to make
it close to reach its fields limit (default: 2500).\n And makes
everything under `kibana.alert.grouping` path to be added to the index
as dynamic fields.\n \n Then apply the below changes to the custom
threshold rule executor:\n ```\n const grouping: Record<string, string>
= {};\n groups?.forEach((groupObj) => (grouping[groupObj.field] =
groupObj.value));\n \n const { uuid, start } = alertsClient.report({\n
id: `${group}`,\n actionGroup: actionGroupId,\n payload: {\n
[ALERT_REASON]: reason,\n [ALERT_EVALUATION_VALUES]: evaluationValues,\n
[ALERT_EVALUATION_THRESHOLD]: threshold,\n [ALERT_GROUP]: groups,\n //
@ts-ignore\n ['kibana.alerting.grouping']: grouping,\n
...flattenAdditionalContext(additionalContext),\n
...getEcsGroups(groups),\n },\n }); \n ```\n \nAbove changes add the
selected groups under `kibana.alerting.grouping` path.\n \nThen: \n- Run
ES with ` path.data=../your-local-data-path` to keep the data for the
next start.\n- Run Kibana\n- Create a custom threshold rule that
generates an alert and has at least 2 groups.\n- Let the rule run.\n- Go
to `Stack Management` > `Index Management` and search for observability
threshold index.\n- Check its mappings, it should show the dummy fields
you have added to the rule type and the first grouping you have selected
while you were creating the rule type.\n- Go to the Dev Tools and find
your alert in the
`.internal.alerts-observability.threshold.alerts-default-000001`
index.\nThe other groups you have selected should be saved under
`_ignored` field:\n```\n\"_ignored\": [\n
\"kibana.alerting.grouping.host.name\"\n],\n```\n- Stop Kibana\n-
increase the number of dummy fields you have added to the rule type
definition:\n```\n ...Array(412) <-- make this greater than 412\n
.fill(0)\n```\n- Start kibana again.\n- The new fields should be added
to the mappings. Check them on `Stack Management` > `Index Management`
\n- Check also the index settings: `Stack Management` > `Index
Management` >
`.internal.alerts-observability.threshold.alerts-default-000001` >
settings tab.\n- `\"mapping\" > \"total_fields\" > \"limit\" ` should be
greater than 2500\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f6c30d6b9ad1a46a73cc5c084a5e70051d78a7cb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216719","number":216719,"mergeCommit":{"message":"Auto
increase fields limit of the alert indices (#216719)\n\nThis PR adds the
auto-increase the fields limit on startup when an\nalerts index reaches
its limits because of the dynamic fields.\n\n# To verify:\nTo be able to
test this PR we need a rule type that adds dynamic fields.\nI used the
custom threshold rule for this:\n\nGo to the custom threshold rule type
definition and change its\nalerts.mappings to:\n```\n mappings: {\n //
dynamic: true,\n fieldMap: {\n 'kibana.alerting.grouping': {\n type:
'object',\n dynamic: true,\n array: false,\n required: false,\n },\n
...legacyExperimentalFieldMap,\n ...Array(412)\n .fill(0)\n
.reduce((acc, val, i) => {\n acc[`${i + 1}`] = { type: 'keyword', array:
false, required: false };\n return acc;\n }, {}),\n },\n
dynamicTemplates: [\n {\n strings_as_keywords: {\n path_match:
'kibana.alert.grouping.*',\n match_mapping_type: 'string',\n mapping:
{\n type: 'keyword',\n ignore_above: 1024,\n },\n },\n },\n ],\n },\n
```\n \n Above changes adds 412 dummy fields to the alerts index to make
it close to reach its fields limit (default: 2500).\n And makes
everything under `kibana.alert.grouping` path to be added to the index
as dynamic fields.\n \n Then apply the below changes to the custom
threshold rule executor:\n ```\n const grouping: Record<string, string>
= {};\n groups?.forEach((groupObj) => (grouping[groupObj.field] =
groupObj.value));\n \n const { uuid, start } = alertsClient.report({\n
id: `${group}`,\n actionGroup: actionGroupId,\n payload: {\n
[ALERT_REASON]: reason,\n [ALERT_EVALUATION_VALUES]: evaluationValues,\n
[ALERT_EVALUATION_THRESHOLD]: threshold,\n [ALERT_GROUP]: groups,\n //
@ts-ignore\n ['kibana.alerting.grouping']: grouping,\n
...flattenAdditionalContext(additionalContext),\n
...getEcsGroups(groups),\n },\n }); \n ```\n \nAbove changes add the
selected groups under `kibana.alerting.grouping` path.\n \nThen: \n- Run
ES with ` path.data=../your-local-data-path` to keep the data for the
next start.\n- Run Kibana\n- Create a custom threshold rule that
generates an alert and has at least 2 groups.\n- Let the rule run.\n- Go
to `Stack Management` > `Index Management` and search for observability
threshold index.\n- Check its mappings, it should show the dummy fields
you have added to the rule type and the first grouping you have selected
while you were creating the rule type.\n- Go to the Dev Tools and find
your alert in the
`.internal.alerts-observability.threshold.alerts-default-000001`
index.\nThe other groups you have selected should be saved under
`_ignored` field:\n```\n\"_ignored\": [\n
\"kibana.alerting.grouping.host.name\"\n],\n```\n- Stop Kibana\n-
increase the number of dummy fields you have added to the rule type
definition:\n```\n ...Array(412) <-- make this greater than 412\n
.fill(0)\n```\n- Start kibana again.\n- The new fields should be added
to the mappings. Check them on `Stack Management` > `Index Management`
\n- Check also the index settings: `Stack Management` > `Index
Management` >
`.internal.alerts-observability.threshold.alerts-default-000001` >
settings tab.\n- `\"mapping\" > \"total_fields\" > \"limit\" ` should be
greater than 2500\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f6c30d6b9ad1a46a73cc5c084a5e70051d78a7cb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-17 18:52:40 -04:00
Kibana Machine
ddc4bbcb53
[9.0] [ftr] split x-pack discover config (#217483) (#218589) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[ftr] split x-pack discover config
(#217483)](https://github.com/elastic/kibana/pull/217483)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T16:51:17Z","message":"[ftr]
split x-pack discover config (#217483)\n\n## Summary\n\nSplit
`x-pack/test/functional/apps/discover/config.ts: 41.1
minutes`\ninto:\n\n -
x-pack/test/functional/apps/discover/group1/config.ts\n -
x-pack/test/functional/apps/discover/group2/config.ts\n -
x-pack/test/functional/apps/discover/group3/config.ts","sha":"2cc56f827b1e19c595ac6c0aae8e295e850e636f","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","FTR","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[ftr]
split x-pack discover
config","number":217483,"url":"https://github.com/elastic/kibana/pull/217483","mergeCommit":{"message":"[ftr]
split x-pack discover config (#217483)\n\n## Summary\n\nSplit
`x-pack/test/functional/apps/discover/config.ts: 41.1
minutes`\ninto:\n\n -
x-pack/test/functional/apps/discover/group1/config.ts\n -
x-pack/test/functional/apps/discover/group2/config.ts\n -
x-pack/test/functional/apps/discover/group3/config.ts","sha":"2cc56f827b1e19c595ac6c0aae8e295e850e636f"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217483","number":217483,"mergeCommit":{"message":"[ftr]
split x-pack discover config (#217483)\n\n## Summary\n\nSplit
`x-pack/test/functional/apps/discover/config.ts: 41.1
minutes`\ninto:\n\n -
x-pack/test/functional/apps/discover/group1/config.ts\n -
x-pack/test/functional/apps/discover/group2/config.ts\n -
x-pack/test/functional/apps/discover/group3/config.ts","sha":"2cc56f827b1e19c595ac6c0aae8e295e850e636f"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2025-04-17 20:23:36 +02:00
Kibana Machine
ebee03ab4c
[9.0] Update dependency @redocly/cli to ^1.34.2 (main) (#218400) (#218586) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Update dependency @redocly/cli to ^1.34.2 (main)
(#218400)](https://github.com/elastic/kibana/pull/218400)

<!--- 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-17T15:46:38Z","message":"Update
dependency @redocly/cli to ^1.34.2 (main) (#218400)\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"7a5b5534f846e77084fd4648eb0e2dddd6fc4f7b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update
dependency @redocly/cli to ^1.34.2
(main)","number":218400,"url":"https://github.com/elastic/kibana/pull/218400","mergeCommit":{"message":"Update
dependency @redocly/cli to ^1.34.2 (main) (#218400)\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"7a5b5534f846e77084fd4648eb0e2dddd6fc4f7b"}},"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/218400","number":218400,"mergeCommit":{"message":"Update
dependency @redocly/cli to ^1.34.2 (main) (#218400)\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"7a5b5534f846e77084fd4648eb0e2dddd6fc4f7b"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-17 19:53:39 +02:00
Maryam Saeidi
c725d4beff
[9.0] Track toast errors using apm-rum (#217948) (#218581) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Track toast errors using apm-rum
(#217948)](https://github.com/elastic/kibana/pull/217948)

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

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

<!--BACKPORT [{"author":{"name":"Maryam
Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T07:49:11Z","message":"Track
toast errors using apm-rum (#217948)\n\nCloses
https://github.com/elastic/observability-dev/issues/4022\n\n##
Summary\n\nIn this PR, we are capturing toast errors using
apm-rum:\n\n\nhttps://github.com/user-attachments/assets/b61529f9-ab8e-4171-9042-0884e11eb385\n\n\nErrorType
is available in labels which this feature was added to the rum\nagent in
this\n[PR](https://github.com/elastic/apm-agent-rum-js/pull/1594).\n\n\n###
🧪 How to test\n\nAdd the following to your kibana.yml
file:\n\n```\nelastic.apm.active:
true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment:
yourName <-- Change to your name\n```\n<details>\n<summary>Throw a toast
error</summary>\n\nAdd this code to a page as
[alerts\npage](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/observability/public/pages/alerts/alerts.tsx)\nand
visit
http://localhost:5601/kibana/app/observability/alerts\n\n```\nuseEffect(()
=> {\n const error = new Error('Mary test error > toasts.addError');\n
toasts.addError(error, { title: 'Testing error toast', toastMessage:
error.message });\n toasts.addDanger('Testing danger toast');\n },
[]);\n```\n\n</details>\n\nThen
visit\n[kibana-cloud-apm.elastic.dev](https://kibana-cloud-apm.elastic.dev/app/apm/services/kibana-frontend/errors?comparisonEnabled=true&environment=ENVIRONMENT_ALL&kuery=&latencyAggregationType=avg&offset=1d&rangeFrom=now-1h&rangeTo=now&serviceGroup=&transactionType=page-load)\nfiltered
for `yourName` in the
environment.","sha":"ae9e5d679ce1ace883ec7bae432b46f9c77f2758","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"Track
toast errors using
apm-rum","number":217948,"url":"https://github.com/elastic/kibana/pull/217948","mergeCommit":{"message":"Track
toast errors using apm-rum (#217948)\n\nCloses
https://github.com/elastic/observability-dev/issues/4022\n\n##
Summary\n\nIn this PR, we are capturing toast errors using
apm-rum:\n\n\nhttps://github.com/user-attachments/assets/b61529f9-ab8e-4171-9042-0884e11eb385\n\n\nErrorType
is available in labels which this feature was added to the rum\nagent in
this\n[PR](https://github.com/elastic/apm-agent-rum-js/pull/1594).\n\n\n###
🧪 How to test\n\nAdd the following to your kibana.yml
file:\n\n```\nelastic.apm.active:
true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment:
yourName <-- Change to your name\n```\n<details>\n<summary>Throw a toast
error</summary>\n\nAdd this code to a page as
[alerts\npage](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/observability/public/pages/alerts/alerts.tsx)\nand
visit
http://localhost:5601/kibana/app/observability/alerts\n\n```\nuseEffect(()
=> {\n const error = new Error('Mary test error > toasts.addError');\n
toasts.addError(error, { title: 'Testing error toast', toastMessage:
error.message });\n toasts.addDanger('Testing danger toast');\n },
[]);\n```\n\n</details>\n\nThen
visit\n[kibana-cloud-apm.elastic.dev](https://kibana-cloud-apm.elastic.dev/app/apm/services/kibana-frontend/errors?comparisonEnabled=true&environment=ENVIRONMENT_ALL&kuery=&latencyAggregationType=avg&offset=1d&rangeFrom=now-1h&rangeTo=now&serviceGroup=&transactionType=page-load)\nfiltered
for `yourName` in the
environment.","sha":"ae9e5d679ce1ace883ec7bae432b46f9c77f2758"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217948","number":217948,"mergeCommit":{"message":"Track
toast errors using apm-rum (#217948)\n\nCloses
https://github.com/elastic/observability-dev/issues/4022\n\n##
Summary\n\nIn this PR, we are capturing toast errors using
apm-rum:\n\n\nhttps://github.com/user-attachments/assets/b61529f9-ab8e-4171-9042-0884e11eb385\n\n\nErrorType
is available in labels which this feature was added to the rum\nagent in
this\n[PR](https://github.com/elastic/apm-agent-rum-js/pull/1594).\n\n\n###
🧪 How to test\n\nAdd the following to your kibana.yml
file:\n\n```\nelastic.apm.active:
true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment:
yourName <-- Change to your name\n```\n<details>\n<summary>Throw a toast
error</summary>\n\nAdd this code to a page as
[alerts\npage](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/observability/public/pages/alerts/alerts.tsx)\nand
visit
http://localhost:5601/kibana/app/observability/alerts\n\n```\nuseEffect(()
=> {\n const error = new Error('Mary test error > toasts.addError');\n
toasts.addError(error, { title: 'Testing error toast', toastMessage:
error.message });\n toasts.addDanger('Testing danger toast');\n },
[]);\n```\n\n</details>\n\nThen
visit\n[kibana-cloud-apm.elastic.dev](https://kibana-cloud-apm.elastic.dev/app/apm/services/kibana-frontend/errors?comparisonEnabled=true&environment=ENVIRONMENT_ALL&kuery=&latencyAggregationType=avg&offset=1d&rangeFrom=now-1h&rangeTo=now&serviceGroup=&transactionType=page-load)\nfiltered
for `yourName` in the
environment.","sha":"ae9e5d679ce1ace883ec7bae432b46f9c77f2758"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/218531","number":218531,"branch":"8.19","state":"MERGED","mergeCommit":{"sha":"caa2fbb25501b65fa704c8f9cf2821cc4e18ea34","message":"[8.19]
Track toast errors using apm-rum (#217948) (#218531)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.19`:\n- [Track toast errors using
apm-rum\n(#217948)](https://github.com/elastic/kibana/pull/217948)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}]
BACKPORT-->
 2025-04-17 19:42:06 +02:00
Vitalii Dmyterko
99531c2900
[9.0] [Security Solution][Detection Engine] adds async ES|QL query (#216667) (#218583) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution][Detection Engine] adds async ES|QL query
(#216667)](https://github.com/elastic/kibana/pull/216667)

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

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

<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T14:23:07Z","message":"[Security
Solution][Detection Engine] adds async ES|QL query (#216667)\n\n##
Summary\n\n- addresses
https://github.com/elastic/security-team/issues/11116 (list\nitem
2)\n\nIntroducing async query would allow to overcome ES request timeout
for\nlong running rules and queries.\n\nTimeout for ES request is
[defined in
alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand
is smaller value out of rule execution timeout or default ES
request\ntimeout(which is 5m and
hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf
ES|QL rule performs a single long-running ES query, it can time
out\nafter 5m due to this ES request timeout. This value can't be
changed,\nunlike rule execution timeout. It can be overwritten in Kibana
config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n
ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we
can encounter situations when rule fails execution after 5m due\nto ES
request timeout, despite a fact it configured with longer timeout\nof
15m\n\nBy using async query, we can overcome this limitation and can
poll async\nquery results until it completes or rule timeouts\n\nMore
details in
internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Detection
Engine","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution][Detection Engine] adds async ES|QL
query","number":216667,"url":"https://github.com/elastic/kibana/pull/216667","mergeCommit":{"message":"[Security
Solution][Detection Engine] adds async ES|QL query (#216667)\n\n##
Summary\n\n- addresses
https://github.com/elastic/security-team/issues/11116 (list\nitem
2)\n\nIntroducing async query would allow to overcome ES request timeout
for\nlong running rules and queries.\n\nTimeout for ES request is
[defined in
alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand
is smaller value out of rule execution timeout or default ES
request\ntimeout(which is 5m and
hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf
ES|QL rule performs a single long-running ES query, it can time
out\nafter 5m due to this ES request timeout. This value can't be
changed,\nunlike rule execution timeout. It can be overwritten in Kibana
config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n
ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we
can encounter situations when rule fails execution after 5m due\nto ES
request timeout, despite a fact it configured with longer timeout\nof
15m\n\nBy using async query, we can overcome this limitation and can
poll async\nquery results until it completes or rule timeouts\n\nMore
details in
internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216667","number":216667,"mergeCommit":{"message":"[Security
Solution][Detection Engine] adds async ES|QL query (#216667)\n\n##
Summary\n\n- addresses
https://github.com/elastic/security-team/issues/11116 (list\nitem
2)\n\nIntroducing async query would allow to overcome ES request timeout
for\nlong running rules and queries.\n\nTimeout for ES request is
[defined in
alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand
is smaller value out of rule execution timeout or default ES
request\ntimeout(which is 5m and
hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf
ES|QL rule performs a single long-running ES query, it can time
out\nafter 5m due to this ES request timeout. This value can't be
changed,\nunlike rule execution timeout. It can be overwritten in Kibana
config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n
ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we
can encounter situations when rule fails execution after 5m due\nto ES
request timeout, despite a fact it configured with longer timeout\nof
15m\n\nBy using async query, we can overcome this limitation and can
poll async\nquery results until it completes or rule timeouts\n\nMore
details in
internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by:
Ryland Herrick
<ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218567","number":218567,"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"}]}]
BACKPORT-->
 2025-04-17 19:17:32 +02:00
Kibana Machine
cb022879a9
[9.0] [Unzyme] Migrates status_table of enzyme completely (#218361) (#218491) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Unzyme] Migrates status_table of enzyme completely
(#218361)](https://github.com/elastic/kibana/pull/218361)

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

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

<!--BACKPORT [{"author":{"name":"Christiane (Tina)
Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T20:23:28Z","message":"[Unzyme]
Migrates status_table of enzyme completely (#218361)\n\n## Summary\nfix
https://github.com/elastic/kibana/issues/217589 again\nThe
implementation in https://github.com/elastic/kibana/pull/217599 for\nthe
status table still relied on enzyme indirectly by
using\n`mountWithI18n`.\n\nThis PR refactors the test from implementing
the enzyme-reliant helper\nto using `renderReactTestingLibraryWithI18n`
that doesn't.\n\n## Note to reviewers:\nIf
`renderReactTestingLibraryWithI18n` becomes the standard, renaming
it\nto something shorter (e.g. `renderWithI18n`) would be nicer. ATM,
the\nhelper's only used in 13 files and it would be better to do so now
that\nwhen adoption becomes wide-spread.\n\nThe package is owned by
`shared-ux` and renaming the function would\nrequire code-reviews from
too many teams to justify doing so in this PR.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"c45f791ddb3917fb13d978fc53a3a440bf9505b5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v9.1.0"],"title":"[Unzyme]
Migrates status_table of enzyme
completely","number":218361,"url":"https://github.com/elastic/kibana/pull/218361","mergeCommit":{"message":"[Unzyme]
Migrates status_table of enzyme completely (#218361)\n\n## Summary\nfix
https://github.com/elastic/kibana/issues/217589 again\nThe
implementation in https://github.com/elastic/kibana/pull/217599 for\nthe
status table still relied on enzyme indirectly by
using\n`mountWithI18n`.\n\nThis PR refactors the test from implementing
the enzyme-reliant helper\nto using `renderReactTestingLibraryWithI18n`
that doesn't.\n\n## Note to reviewers:\nIf
`renderReactTestingLibraryWithI18n` becomes the standard, renaming
it\nto something shorter (e.g. `renderWithI18n`) would be nicer. ATM,
the\nhelper's only used in 13 files and it would be better to do so now
that\nwhen adoption becomes wide-spread.\n\nThe package is owned by
`shared-ux` and renaming the function would\nrequire code-reviews from
too many teams to justify doing so in this PR.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"c45f791ddb3917fb13d978fc53a3a440bf9505b5"}},"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/218361","number":218361,"mergeCommit":{"message":"[Unzyme]
Migrates status_table of enzyme completely (#218361)\n\n## Summary\nfix
https://github.com/elastic/kibana/issues/217589 again\nThe
implementation in https://github.com/elastic/kibana/pull/217599 for\nthe
status table still relied on enzyme indirectly by
using\n`mountWithI18n`.\n\nThis PR refactors the test from implementing
the enzyme-reliant helper\nto using `renderReactTestingLibraryWithI18n`
that doesn't.\n\n## Note to reviewers:\nIf
`renderReactTestingLibraryWithI18n` becomes the standard, renaming
it\nto something shorter (e.g. `renderWithI18n`) would be nicer. ATM,
the\nhelper's only used in 13 files and it would be better to do so now
that\nwhen adoption becomes wide-spread.\n\nThe package is owned by
`shared-ux` and renaming the function would\nrequire code-reviews from
too many teams to justify doing so in this PR.\n\n### Checklist\n\nCheck
the PR satisfies following conditions. \n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"c45f791ddb3917fb13d978fc53a3a440bf9505b5"}}]}]
BACKPORT-->

Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
 2025-04-17 12:10:37 -05:00
Kibana Machine
0afff0c441
[9.0] [ML] Fix vCPU usage message in the Start deployment dialog (#218557) (#218580) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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 18:56:51 +02:00
Kibana Machine
3429d039c6
[9.0] Fix placeholder in monaco editor dissapear when value is set (#217828) (#218562) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Fix placeholder in monaco editor dissapear when value is set
(#217828)](https://github.com/elastic/kibana/pull/217828)

<!--- 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-17T12:49:05Z","message":"Fix
placeholder in monaco editor dissapear when value is set (#217828)\n\n##
Summary\n\nThis PR fixes [[Bug] Setting text in the placeholder property
does not\nclear when value is set with
onChange\naction](https://github.com/elastic/kibana/issues/149882)
issue.","sha":"ea3dead452cc9d5db9626237bb60cd5c509b08a9","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:SharedUX","backport:prev-minor","v9.1.0"],"title":"Fix
placeholder in monaco editor dissapear when value is
set","number":217828,"url":"https://github.com/elastic/kibana/pull/217828","mergeCommit":{"message":"Fix
placeholder in monaco editor dissapear when value is set (#217828)\n\n##
Summary\n\nThis PR fixes [[Bug] Setting text in the placeholder property
does not\nclear when value is set with
onChange\naction](https://github.com/elastic/kibana/issues/149882)
issue.","sha":"ea3dead452cc9d5db9626237bb60cd5c509b08a9"}},"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/217828","number":217828,"mergeCommit":{"message":"Fix
placeholder in monaco editor dissapear when value is set (#217828)\n\n##
Summary\n\nThis PR fixes [[Bug] Setting text in the placeholder property
does not\nclear when value is set with
onChange\naction](https://github.com/elastic/kibana/issues/149882)
issue.","sha":"ea3dead452cc9d5db9626237bb60cd5c509b08a9"}}]}]
BACKPORT-->

Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co>
 2025-04-17 16:50:31 +02:00
jennypavlova
4b50e48d24
[9.0] [APM][OTel] Encode service name in the APM URLs (#217092) (#218474) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[APM][OTel] Encode service name in the APM URLs
(#217092)](https://github.com/elastic/kibana/pull/217092)

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

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

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T15:52:33Z","message":"[APM][OTel]
Encode service name in the APM URLs (#217092)\n\nCloses #213943\n\n##
Summary\n\nThis PR ensures the service name is always encoded in the APM
UIs. It's\na follow-up of https://github.com/elastic/kibana/pull/215031
and aims to\nfind a better solution to the problem:\n- Add the encoding
directly to `formatRequest` as suggested there\n- I saw that there are
many places where we use legacy Url builders, so\nI will try to replace
them where possible and use\napm router link method where the path is
encoded\n([ref](7158e0201b/src/platform/packages/shared/kbn-typed-react-router-config/src/create_router.ts (L184-L185)))\n-
The PR includes the changes to address the issue above:\n - Replaced and
removed `LegacyAPMLink`\n- Refactored `useAPMHref` to support encoding
(and extracted and test\nthe encoding logic)\n - Example usage: \n -
Before: \n ```js\n useAPMHref({\n path:
`/services/${serviceName}/.....`,\n persistedFilters,\n });\n ```\n -
After:\n ```js\n useAPMHref({\n path:
'/services/{serviceName}/.......}',\n pathParams: { serviceName },\n
persistedFilters,\n });\n ```\n - Used the APM router link method as
much as possible\n\n\n## Testing\n- Run `node scripts/synthtrace
trace_with_service_names_with_slashes.ts\n--clean --live --uniqueIds
--live`\n- Go to service inventory and click the
links:\n\n\nhttps://github.com/user-attachments/assets/fcd4fbfc-4125-4cc8-9b00-53c5f375423f","sha":"f816e7b84f94d9af8d3fffb85dc83512f31c55e9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:prev-minor","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[APM][OTel]
Encode service name in the APM
URLs","number":217092,"url":"https://github.com/elastic/kibana/pull/217092","mergeCommit":{"message":"[APM][OTel]
Encode service name in the APM URLs (#217092)\n\nCloses #213943\n\n##
Summary\n\nThis PR ensures the service name is always encoded in the APM
UIs. It's\na follow-up of https://github.com/elastic/kibana/pull/215031
and aims to\nfind a better solution to the problem:\n- Add the encoding
directly to `formatRequest` as suggested there\n- I saw that there are
many places where we use legacy Url builders, so\nI will try to replace
them where possible and use\napm router link method where the path is
encoded\n([ref](7158e0201b/src/platform/packages/shared/kbn-typed-react-router-config/src/create_router.ts (L184-L185)))\n-
The PR includes the changes to address the issue above:\n - Replaced and
removed `LegacyAPMLink`\n- Refactored `useAPMHref` to support encoding
(and extracted and test\nthe encoding logic)\n - Example usage: \n -
Before: \n ```js\n useAPMHref({\n path:
`/services/${serviceName}/.....`,\n persistedFilters,\n });\n ```\n -
After:\n ```js\n useAPMHref({\n path:
'/services/{serviceName}/.......}',\n pathParams: { serviceName },\n
persistedFilters,\n });\n ```\n - Used the APM router link method as
much as possible\n\n\n## Testing\n- Run `node scripts/synthtrace
trace_with_service_names_with_slashes.ts\n--clean --live --uniqueIds
--live`\n- Go to service inventory and click the
links:\n\n\nhttps://github.com/user-attachments/assets/fcd4fbfc-4125-4cc8-9b00-53c5f375423f","sha":"f816e7b84f94d9af8d3fffb85dc83512f31c55e9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217092","number":217092,"mergeCommit":{"message":"[APM][OTel]
Encode service name in the APM URLs (#217092)\n\nCloses #213943\n\n##
Summary\n\nThis PR ensures the service name is always encoded in the APM
UIs. It's\na follow-up of https://github.com/elastic/kibana/pull/215031
and aims to\nfind a better solution to the problem:\n- Add the encoding
directly to `formatRequest` as suggested there\n- I saw that there are
many places where we use legacy Url builders, so\nI will try to replace
them where possible and use\napm router link method where the path is
encoded\n([ref](7158e0201b/src/platform/packages/shared/kbn-typed-react-router-config/src/create_router.ts (L184-L185)))\n-
The PR includes the changes to address the issue above:\n - Replaced and
removed `LegacyAPMLink`\n- Refactored `useAPMHref` to support encoding
(and extracted and test\nthe encoding logic)\n - Example usage: \n -
Before: \n ```js\n useAPMHref({\n path:
`/services/${serviceName}/.....`,\n persistedFilters,\n });\n ```\n -
After:\n ```js\n useAPMHref({\n path:
'/services/{serviceName}/.......}',\n pathParams: { serviceName },\n
persistedFilters,\n });\n ```\n - Used the APM router link method as
much as possible\n\n\n## Testing\n- Run `node scripts/synthtrace
trace_with_service_names_with_slashes.ts\n--clean --live --uniqueIds
--live`\n- Go to service inventory and click the
links:\n\n\nhttps://github.com/user-attachments/assets/fcd4fbfc-4125-4cc8-9b00-53c5f375423f","sha":"f816e7b84f94d9af8d3fffb85dc83512f31c55e9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-17 14:44:16 +02:00
Kibana Machine
a7361cfc9a
[9.0] [Console] Fix output for empty response body (#218104) (#218185) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Console] Fix output for empty response body
(#218104)](https://github.com/elastic/kibana/pull/218104)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-14T22:06:14Z","message":"[Console]
Fix output for empty response body (#218104)\n\nFixes
https://github.com/elastic/kibana/issues/217433\n\n## Summary\n\nThis PR
fixes the Console output when the response body is an
empty\nstring.\n\nIn https://github.com/elastic/kibana/pull/199975, we
made Console to\ndisplay an `OK` output if the status code is 200 but
response body is\n`null`. Previously,
`POST\n/_cluster/voting_config_exclusions?node_names=node` returned
`null` and\nso the output was correctly set to `OK` but now the response
is an empty\nstring and this case isn't covered correctly. In this PR,
we make sure\nto perform the right check at the right point so that both
`null` and\nempty strings are covered.\n\nThe test that covers this
scenario and had
failures:\n7092e79157/src/platform/test/functional/apps/console/_console.ts (L258)\n\n\nTo
run the failing test with the new Es
snapshots:\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/8.19.0/archives/20250414-022022_f16f4ce6/manifest.json\"
node scripts/functional_tests_server.js --config
./src/platform/test/functional/apps/console/config.ts\n```\n\nand
\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/9.1.0/archives/20250414-021844_4ed1a000/manifest.json\"
node scripts/functional_test_runner.js --config
./src/platform/test/functional/apps/console/config.ts --grep=\"Shows OK
when status code is 200 but body is
empty\"\n```","sha":"170651ac78595f6fe8e2ab4924fd5300b8a4f14e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console]
Fix output for empty response
body","number":218104,"url":"https://github.com/elastic/kibana/pull/218104","mergeCommit":{"message":"[Console]
Fix output for empty response body (#218104)\n\nFixes
https://github.com/elastic/kibana/issues/217433\n\n## Summary\n\nThis PR
fixes the Console output when the response body is an
empty\nstring.\n\nIn https://github.com/elastic/kibana/pull/199975, we
made Console to\ndisplay an `OK` output if the status code is 200 but
response body is\n`null`. Previously,
`POST\n/_cluster/voting_config_exclusions?node_names=node` returned
`null` and\nso the output was correctly set to `OK` but now the response
is an empty\nstring and this case isn't covered correctly. In this PR,
we make sure\nto perform the right check at the right point so that both
`null` and\nempty strings are covered.\n\nThe test that covers this
scenario and had
failures:\n7092e79157/src/platform/test/functional/apps/console/_console.ts (L258)\n\n\nTo
run the failing test with the new Es
snapshots:\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/8.19.0/archives/20250414-022022_f16f4ce6/manifest.json\"
node scripts/functional_tests_server.js --config
./src/platform/test/functional/apps/console/config.ts\n```\n\nand
\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/9.1.0/archives/20250414-021844_4ed1a000/manifest.json\"
node scripts/functional_test_runner.js --config
./src/platform/test/functional/apps/console/config.ts --grep=\"Shows OK
when status code is 200 but body is
empty\"\n```","sha":"170651ac78595f6fe8e2ab4924fd5300b8a4f14e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218104","number":218104,"mergeCommit":{"message":"[Console]
Fix output for empty response body (#218104)\n\nFixes
https://github.com/elastic/kibana/issues/217433\n\n## Summary\n\nThis PR
fixes the Console output when the response body is an
empty\nstring.\n\nIn https://github.com/elastic/kibana/pull/199975, we
made Console to\ndisplay an `OK` output if the status code is 200 but
response body is\n`null`. Previously,
`POST\n/_cluster/voting_config_exclusions?node_names=node` returned
`null` and\nso the output was correctly set to `OK` but now the response
is an empty\nstring and this case isn't covered correctly. In this PR,
we make sure\nto perform the right check at the right point so that both
`null` and\nempty strings are covered.\n\nThe test that covers this
scenario and had
failures:\n7092e79157/src/platform/test/functional/apps/console/_console.ts (L258)\n\n\nTo
run the failing test with the new Es
snapshots:\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/8.19.0/archives/20250414-022022_f16f4ce6/manifest.json\"
node scripts/functional_tests_server.js --config
./src/platform/test/functional/apps/console/config.ts\n```\n\nand
\n\n```\nES_SNAPSHOT_MANIFEST=\"https://storage.googleapis.com/kibana-ci-es-snapshots-daily/9.1.0/archives/20250414-021844_4ed1a000/manifest.json\"
node scripts/functional_test_runner.js --config
./src/platform/test/functional/apps/console/config.ts --grep=\"Shows OK
when status code is 200 but body is
empty\"\n```","sha":"170651ac78595f6fe8e2ab4924fd5300b8a4f14e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
Co-authored-by: Elena Stoeva <elenastoeva99@gmail.com>
 2025-04-17 13:51:50 +02:00
jennypavlova
b6bca1b6da
[9.0] [APM][OTel] EDOT error summary fix (#217885) (#218390) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[APM][OTel] EDOT error summary fix
(#217885)](https://github.com/elastic/kibana/pull/217885)

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

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

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T19:44:11Z","message":"[APM][OTel]
EDOT error summary fix (#217885)\n\n## Summary\n\nThis PR fixes the
issue with the error summary missing items using edot.\nIt includes e2e
tests with synthtrace for both edot and otel services.\n\nTODO \n\n- [x]
Test with serverless (waiting for the PR to be deployed)\nTested on
serverless works as expected: \n\n<img width=\"2560\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dd7962e-7d66-482d-97fb-0b08882bd04f\"\n/>","sha":"7c9a3ee1f2a7f4599cd294ef2890e7c1b9cefd27","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","ci:cloud-redeploy","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[APM][OTel]
EDOT error summary
fix","number":217885,"url":"https://github.com/elastic/kibana/pull/217885","mergeCommit":{"message":"[APM][OTel]
EDOT error summary fix (#217885)\n\n## Summary\n\nThis PR fixes the
issue with the error summary missing items using edot.\nIt includes e2e
tests with synthtrace for both edot and otel services.\n\nTODO \n\n- [x]
Test with serverless (waiting for the PR to be deployed)\nTested on
serverless works as expected: \n\n<img width=\"2560\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dd7962e-7d66-482d-97fb-0b08882bd04f\"\n/>","sha":"7c9a3ee1f2a7f4599cd294ef2890e7c1b9cefd27"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217885","number":217885,"mergeCommit":{"message":"[APM][OTel]
EDOT error summary fix (#217885)\n\n## Summary\n\nThis PR fixes the
issue with the error summary missing items using edot.\nIt includes e2e
tests with synthtrace for both edot and otel services.\n\nTODO \n\n- [x]
Test with serverless (waiting for the PR to be deployed)\nTested on
serverless works as expected: \n\n<img width=\"2560\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8dd7962e-7d66-482d-97fb-0b08882bd04f\"\n/>","sha":"7c9a3ee1f2a7f4599cd294ef2890e7c1b9cefd27"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-17 12:38:27 +02:00
Kibana Machine
267bb614aa
[9.0] [Discover] Stop keydown event propagation when unified doc tabs are focused (#218131) (#218300) (#218539) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Discover] Stop keydown event propagation when unified doc tabs are
focused (#218131)
(#218300)](https://github.com/elastic/kibana/pull/218300)

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

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

<!--BACKPORT [{"author":{"name":"Alejandro García
Parrondo","email":"31973472+AlexGPlay@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T09:02:50Z","message":"[Discover]
Stop keydown event propagation when unified doc tabs are focused
(#218131) (#218300)\n\n## Summary\n\nWhen a tab was focused and the
right or left arrow keys were used it was\nchanging the focused tab and
the selected document, it should only\nchange the selected tab.\n\nFixes
https://github.com/elastic/kibana/issues/218131\n\n\n![chrome-capture-2025-4-15](https://github.com/user-attachments/assets/052313e1-aa1e-4d60-9b48-2a22f9b0d90b)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"41ccdb70da28959a9025dab4dfbf36c58228eb67","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","v9.0.0","Team:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover]
Stop keydown event propagation when unified doc tabs are focused
(#218131)","number":218300,"url":"https://github.com/elastic/kibana/pull/218300","mergeCommit":{"message":"[Discover]
Stop keydown event propagation when unified doc tabs are focused
(#218131) (#218300)\n\n## Summary\n\nWhen a tab was focused and the
right or left arrow keys were used it was\nchanging the focused tab and
the selected document, it should only\nchange the selected tab.\n\nFixes
https://github.com/elastic/kibana/issues/218131\n\n\n![chrome-capture-2025-4-15](https://github.com/user-attachments/assets/052313e1-aa1e-4d60-9b48-2a22f9b0d90b)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"41ccdb70da28959a9025dab4dfbf36c58228eb67"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"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/218300","number":218300,"mergeCommit":{"message":"[Discover]
Stop keydown event propagation when unified doc tabs are focused
(#218131) (#218300)\n\n## Summary\n\nWhen a tab was focused and the
right or left arrow keys were used it was\nchanging the focused tab and
the selected document, it should only\nchange the selected tab.\n\nFixes
https://github.com/elastic/kibana/issues/218131\n\n\n![chrome-capture-2025-4-15](https://github.com/user-attachments/assets/052313e1-aa1e-4d60-9b48-2a22f9b0d90b)\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"41ccdb70da28959a9025dab4dfbf36c58228eb67"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Alejandro García Parrondo <31973472+AlexGPlay@users.noreply.github.com>
 2025-04-17 12:35:13 +02:00
Maryam Saeidi
199eda6ef7
[9.0] Update apm-rum packages (#217800) (#218534) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Update apm-rum packages
(#217800)](https://github.com/elastic/kibana/pull/217800)

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

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

<!--BACKPORT [{"author":{"name":"Maryam
Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T14:57:06Z","message":"Update
apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages
mostly to use this
feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous
version|Current version|Change
log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version
bump only for
package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"Update
apm-rum
packages","number":217800,"url":"https://github.com/elastic/kibana/pull/217800","mergeCommit":{"message":"Update
apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages
mostly to use this
feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous
version|Current version|Change
log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version
bump only for
package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217800","number":217800,"mergeCommit":{"message":"Update
apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages
mostly to use this
feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous
version|Current version|Change
log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add
support for adding labels to\ncaptured
errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version
bump only for
package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218145","number":218145,"state":"MERGED","mergeCommit":{"sha":"a32b7835a1c6a2e9aab0cf681a3fd20039eb385c","message":"[8.x]
Update apm-rum packages (#217800) (#218145)\n\n# Backport\n\nThis will
backport the following commits from `main` to `8.x`:\n- [Update apm-rum
packages\n(#217800)](https://github.com/elastic/kibana/pull/217800)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-17 12:10:40 +02:00
Kibana Machine
25cef6d35b
[9.0] [Security Solution] Allow disabling experimental features via config (#217363) (#218429) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Allow disabling experimental features via config
(#217363)](https://github.com/elastic/kibana/pull/217363)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T12:09:28Z","message":"[Security
Solution] Allow disabling experimental features via config
(#217363)\n\n## Summary\n\nThis PR adds support for disabling
experimental features using the\nexisting
`xpack.securitySolution.enableExperimental` configuration.\n\nThis
solves the problem of not being able to disable a feature by
config\nonce the feature has been enabled by default.\n\n### The
Challenge \n\nWhen we start developing a feature under an experimental
flag we always\nfollow the same steps:\n\n1 - Create the experimental
flag disabled by default + enable it via\nconfig for testing\n2 -
Implement the feature\n3 - Enable the experimental flag by default when
we want to release the\nfeature.\n4 - Deployments can disable the
feature via config (as a safety\nmeasure).\n5 - Remove the experimental
flag after some time.\n\nWe start by creating the flag disabled by
default while we implement it.\nIn
`experimental_features.ts`:\n```ts\nexport const
allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n
[...]\n```\nAnd enable it via config
with:\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureEnabled\n```\n\nOnce the implementation is done and the
experimental flag can be enabled\nby default, we have to do a
trick:\nSince the `xpack.securitySolution.enableExperimental` config can
only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`,
what\nwe have to do is rename the flag to `myFeatureDisabled` and keep
the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also
need to do a code refactor to update all the places in the\ncode where
the flag was checked: `if (myFeatureEnabled)` ->
`if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling
the feature via config (in\ncase something goes
wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the
possibility to turn a flag to _false_ using the\nsame
`xpack.securitySolution.enableExperimental` config. This was\npreferable
to introducing a new config since this one is already\nwhitelisted in
Cloud UI, can be easily overritten in deployments, and\nalso because
people are used to it.\n\nWith these changes, the first two steps would
be the same, with the\ndifference that we won't need to have the
_Enabled_ or _Disabled_ word\nat the end of the flag name. It could be
just the feature name, in\n`experimental_features.ts`:\n```ts\nexport
const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n
[...]\n```\n\nAnd when we need to enable the feature by default, we can
just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor
or confusing naming would be required. \n\nThen, in case we need to
disable the feature in a production deployment\nfor some reason, we
could just do this via config
:\n```yml\nxpack.securitySolution.enableExperimental:\n -
disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e","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:
SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[Security
Solution] Allow disabling experimental features via
config","number":217363,"url":"https://github.com/elastic/kibana/pull/217363","mergeCommit":{"message":"[Security
Solution] Allow disabling experimental features via config
(#217363)\n\n## Summary\n\nThis PR adds support for disabling
experimental features using the\nexisting
`xpack.securitySolution.enableExperimental` configuration.\n\nThis
solves the problem of not being able to disable a feature by
config\nonce the feature has been enabled by default.\n\n### The
Challenge \n\nWhen we start developing a feature under an experimental
flag we always\nfollow the same steps:\n\n1 - Create the experimental
flag disabled by default + enable it via\nconfig for testing\n2 -
Implement the feature\n3 - Enable the experimental flag by default when
we want to release the\nfeature.\n4 - Deployments can disable the
feature via config (as a safety\nmeasure).\n5 - Remove the experimental
flag after some time.\n\nWe start by creating the flag disabled by
default while we implement it.\nIn
`experimental_features.ts`:\n```ts\nexport const
allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n
[...]\n```\nAnd enable it via config
with:\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureEnabled\n```\n\nOnce the implementation is done and the
experimental flag can be enabled\nby default, we have to do a
trick:\nSince the `xpack.securitySolution.enableExperimental` config can
only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`,
what\nwe have to do is rename the flag to `myFeatureDisabled` and keep
the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also
need to do a code refactor to update all the places in the\ncode where
the flag was checked: `if (myFeatureEnabled)` ->
`if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling
the feature via config (in\ncase something goes
wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the
possibility to turn a flag to _false_ using the\nsame
`xpack.securitySolution.enableExperimental` config. This was\npreferable
to introducing a new config since this one is already\nwhitelisted in
Cloud UI, can be easily overritten in deployments, and\nalso because
people are used to it.\n\nWith these changes, the first two steps would
be the same, with the\ndifference that we won't need to have the
_Enabled_ or _Disabled_ word\nat the end of the flag name. It could be
just the feature name, in\n`experimental_features.ts`:\n```ts\nexport
const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n
[...]\n```\n\nAnd when we need to enable the feature by default, we can
just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor
or confusing naming would be required. \n\nThen, in case we need to
disable the feature in a production deployment\nfor some reason, we
could just do this via config
:\n```yml\nxpack.securitySolution.enableExperimental:\n -
disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217363","number":217363,"mergeCommit":{"message":"[Security
Solution] Allow disabling experimental features via config
(#217363)\n\n## Summary\n\nThis PR adds support for disabling
experimental features using the\nexisting
`xpack.securitySolution.enableExperimental` configuration.\n\nThis
solves the problem of not being able to disable a feature by
config\nonce the feature has been enabled by default.\n\n### The
Challenge \n\nWhen we start developing a feature under an experimental
flag we always\nfollow the same steps:\n\n1 - Create the experimental
flag disabled by default + enable it via\nconfig for testing\n2 -
Implement the feature\n3 - Enable the experimental flag by default when
we want to release the\nfeature.\n4 - Deployments can disable the
feature via config (as a safety\nmeasure).\n5 - Remove the experimental
flag after some time.\n\nWe start by creating the flag disabled by
default while we implement it.\nIn
`experimental_features.ts`:\n```ts\nexport const
allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n
[...]\n```\nAnd enable it via config
with:\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureEnabled\n```\n\nOnce the implementation is done and the
experimental flag can be enabled\nby default, we have to do a
trick:\nSince the `xpack.securitySolution.enableExperimental` config can
only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`,
what\nwe have to do is rename the flag to `myFeatureDisabled` and keep
the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also
need to do a code refactor to update all the places in the\ncode where
the flag was checked: `if (myFeatureEnabled)` ->
`if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling
the feature via config (in\ncase something goes
wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n -
myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the
possibility to turn a flag to _false_ using the\nsame
`xpack.securitySolution.enableExperimental` config. This was\npreferable
to introducing a new config since this one is already\nwhitelisted in
Cloud UI, can be easily overritten in deployments, and\nalso because
people are used to it.\n\nWith these changes, the first two steps would
be the same, with the\ndifference that we won't need to have the
_Enabled_ or _Disabled_ word\nat the end of the flag name. It could be
just the feature name, in\n`experimental_features.ts`:\n```ts\nexport
const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n
[...]\n```\n\nAnd when we need to enable the feature by default, we can
just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues
= Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor
or confusing naming would be required. \n\nThen, in case we need to
disable the feature in a production deployment\nfor some reason, we
could just do this via config
:\n```yml\nxpack.securitySolution.enableExperimental:\n -
disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2025-04-17 11:19:10 +02:00
Kibana Machine
3fc06a8092
[9.0] [Synthetics] Fixed test run logs per page (#218458) (#218526) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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:15:54 +02:00
Kibana Machine
fa0eecbca9
[9.0] [Security Solution][Rules Management] Separate actions import logic from rules import (#216380) (#218467) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution][Rules Management] Separate actions import logic
from rules import
(#216380)](https://github.com/elastic/kibana/pull/216380)

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

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

<!--BACKPORT [{"author":{"name":"Marshall
Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T15:47:26Z","message":"[Security
Solution][Rules Management] Separate actions import logic from rules
import (#216380)\n\n## Summary\n\nRedo of
https://github.com/elastic/kibana/pull/193471\nCloses
https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug
where importing a rule fails with a connector into a space\nwhere (1)
the connector already exists, and (2) the existing connector\nwas
exported and re-imported from another space. The import logic in\nthis
scenario effectively tries to convert the action ID on the rule\nimport
twice. The second conversion attempt tries to use the old action\nID to
look up the correct new action ID in a map, however, in this
test\nscenario the action ID has already been updated by legacy SO
ID\nmigration logic and there is no map entry with the new ID as a key.
The\nresult is that the second attempt sets the action ID to
undefined,\nresulting in an import failure.\n\nThe root cause of the bug
is that we have two different places in the\nrule import logic where
action IDs are migrated. The first ID migration\nwas done by
`migrateLegacyActionsIds` prior to importing rule actions,\nand the
second migration was done by `importRuleActionConnectors`
after\nimporting the actions. `importRuleActionConnectors` used a lookup
table\nto convert old IDs to new IDs, but if the connector already
existed and\nhad an `originId` then the rule action would already be
migrated by\n`migrateLegacyActionsIds`. The lookup table used
by\n`importRuleActionConnectors` does not have entries for migrated
IDs,\nonly the original IDs, so in that case the result of the lookup
is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the
logic to create a clean separation between action\nand rule import. We
now import the connectors first, ignoring the rules,\nthen migrate
action IDs on the rules afterwards. This handles connectors\nchanging
IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs
changing on import if there are ID conflicts. Only after the\nconnectors
are imported and rule actions are migrated do we then verify\nif each
rule action references a connector ID that actually exists with\nthe new
`checkRuleActions` function,
replacing\n`checkIfActionsHaveMissingConnectors` and related functions
that were\nalso buggy.\n\nFinally, as a nice side effect this rework
removes \"rule action\nconnector missing\" errors out of the
`action_connector_errors` part of\nthe response.
`action_connector_errors` is reserved for errors importing\nconnectors
specifically. If a rule action is missing a connector and\ntherefore we
don't import the rule, that's a rule error and it's\nrepresented in the
`errors` part of the response. Since the shape of the\nresponse is not
changing, I don't consider this a breaking change but\nrather a bug
fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below
and change the extension back to\n.ndjson from .json (github does not
allow .ndjson
files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2.
Import the rule and connector into a space (default is fine)\n3. Create
a new space\n4. Import the rule and connector into the new space\n5.
Import the rule and connector into the new space again, but check
the\n`Overwrite existing connectors with conflicting action \"id\"`
box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection
Rule
Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution][Rules Management] Separate actions import logic from rules
import","number":216380,"url":"https://github.com/elastic/kibana/pull/216380","mergeCommit":{"message":"[Security
Solution][Rules Management] Separate actions import logic from rules
import (#216380)\n\n## Summary\n\nRedo of
https://github.com/elastic/kibana/pull/193471\nCloses
https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug
where importing a rule fails with a connector into a space\nwhere (1)
the connector already exists, and (2) the existing connector\nwas
exported and re-imported from another space. The import logic in\nthis
scenario effectively tries to convert the action ID on the rule\nimport
twice. The second conversion attempt tries to use the old action\nID to
look up the correct new action ID in a map, however, in this
test\nscenario the action ID has already been updated by legacy SO
ID\nmigration logic and there is no map entry with the new ID as a key.
The\nresult is that the second attempt sets the action ID to
undefined,\nresulting in an import failure.\n\nThe root cause of the bug
is that we have two different places in the\nrule import logic where
action IDs are migrated. The first ID migration\nwas done by
`migrateLegacyActionsIds` prior to importing rule actions,\nand the
second migration was done by `importRuleActionConnectors`
after\nimporting the actions. `importRuleActionConnectors` used a lookup
table\nto convert old IDs to new IDs, but if the connector already
existed and\nhad an `originId` then the rule action would already be
migrated by\n`migrateLegacyActionsIds`. The lookup table used
by\n`importRuleActionConnectors` does not have entries for migrated
IDs,\nonly the original IDs, so in that case the result of the lookup
is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the
logic to create a clean separation between action\nand rule import. We
now import the connectors first, ignoring the rules,\nthen migrate
action IDs on the rules afterwards. This handles connectors\nchanging
IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs
changing on import if there are ID conflicts. Only after the\nconnectors
are imported and rule actions are migrated do we then verify\nif each
rule action references a connector ID that actually exists with\nthe new
`checkRuleActions` function,
replacing\n`checkIfActionsHaveMissingConnectors` and related functions
that were\nalso buggy.\n\nFinally, as a nice side effect this rework
removes \"rule action\nconnector missing\" errors out of the
`action_connector_errors` part of\nthe response.
`action_connector_errors` is reserved for errors importing\nconnectors
specifically. If a rule action is missing a connector and\ntherefore we
don't import the rule, that's a rule error and it's\nrepresented in the
`errors` part of the response. Since the shape of the\nresponse is not
changing, I don't consider this a breaking change but\nrather a bug
fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below
and change the extension back to\n.ndjson from .json (github does not
allow .ndjson
files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2.
Import the rule and connector into a space (default is fine)\n3. Create
a new space\n4. Import the rule and connector into the new space\n5.
Import the rule and connector into the new space again, but check
the\n`Overwrite existing connectors with conflicting action \"id\"`
box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216380","number":216380,"mergeCommit":{"message":"[Security
Solution][Rules Management] Separate actions import logic from rules
import (#216380)\n\n## Summary\n\nRedo of
https://github.com/elastic/kibana/pull/193471\nCloses
https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug
where importing a rule fails with a connector into a space\nwhere (1)
the connector already exists, and (2) the existing connector\nwas
exported and re-imported from another space. The import logic in\nthis
scenario effectively tries to convert the action ID on the rule\nimport
twice. The second conversion attempt tries to use the old action\nID to
look up the correct new action ID in a map, however, in this
test\nscenario the action ID has already been updated by legacy SO
ID\nmigration logic and there is no map entry with the new ID as a key.
The\nresult is that the second attempt sets the action ID to
undefined,\nresulting in an import failure.\n\nThe root cause of the bug
is that we have two different places in the\nrule import logic where
action IDs are migrated. The first ID migration\nwas done by
`migrateLegacyActionsIds` prior to importing rule actions,\nand the
second migration was done by `importRuleActionConnectors`
after\nimporting the actions. `importRuleActionConnectors` used a lookup
table\nto convert old IDs to new IDs, but if the connector already
existed and\nhad an `originId` then the rule action would already be
migrated by\n`migrateLegacyActionsIds`. The lookup table used
by\n`importRuleActionConnectors` does not have entries for migrated
IDs,\nonly the original IDs, so in that case the result of the lookup
is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the
logic to create a clean separation between action\nand rule import. We
now import the connectors first, ignoring the rules,\nthen migrate
action IDs on the rules afterwards. This handles connectors\nchanging
IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs
changing on import if there are ID conflicts. Only after the\nconnectors
are imported and rule actions are migrated do we then verify\nif each
rule action references a connector ID that actually exists with\nthe new
`checkRuleActions` function,
replacing\n`checkIfActionsHaveMissingConnectors` and related functions
that were\nalso buggy.\n\nFinally, as a nice side effect this rework
removes \"rule action\nconnector missing\" errors out of the
`action_connector_errors` part of\nthe response.
`action_connector_errors` is reserved for errors importing\nconnectors
specifically. If a rule action is missing a connector and\ntherefore we
don't import the rule, that's a rule error and it's\nrepresented in the
`errors` part of the response. Since the shape of the\nresponse is not
changing, I don't consider this a breaking change but\nrather a bug
fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below
and change the extension back to\n.ndjson from .json (github does not
allow .ndjson
files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2.
Import the rule and connector into a space (default is fine)\n3. Create
a new space\n4. Import the rule and connector into the new space\n5.
Import the rule and connector into the new space again, but check
the\n`Overwrite existing connectors with conflicting action \"id\"`
box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com>
 2025-04-17 07:34:26 +02:00
Tiago Costa
f32483dbe6
skip flaky suite (#216815) 2025-04-17 04:10:46 +01:00
Kibana Machine
91b43cf280 skip failing test suite (#143229) 2025-04-17 05:08:54 +02:00
Kibana Machine
41b029d2b1 skip failing test suite (#213784) 2025-04-16 14:15:04 +02:00
Tiago Costa
ccc46ae28f
chore(NA): bump version to 9.0.1 (#218309) 
Usually bump from 9.0.0 to 9.0.1
 2025-04-16 06:43:31 +01:00
elastic-renovate-prod[bot]
57d0fc8a1e
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 1c7f5aa (9.0) (#218040) 
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-15 19:49:13 -06:00
elastic-renovate-prod[bot]
965e2d7363
Update docker.elastic.co/wolfi/chainguard-base-fips:latest Docker digest to b6d3d24 (9.0) (#218039) 
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base-fips | digest | `0135014` ->
`b6d3d24` |

---

### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJjaTpidWlsZC1kb2NrZXItZmlwcyIsInJlbGVhc2Vfbm90ZTpza2lwIl19-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-15 17:13:38 -06:00
Kibana Machine
24f351bf0b
[9.0] [docs] Fix image paths for docs-assembler (#218344) (#218359) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[docs] Fix image paths for docs-assembler
(#218344)](https://github.com/elastic/kibana/pull/218344)

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

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

<!--BACKPORT [{"author":{"name":"Colleen
McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T21:59:57Z","message":"[docs]
Fix image paths for docs-assembler (#218344)\n\nFixes image paths to
work with docs-assembler.\n\nNotes for the reviewer:\n* I was not able
to get images in reference, extend, or release-notes to\nwork using the
`:::{image}` syntax because it seems to resolve\ndifferently than the
Markdown `![]()` syntax. We should address this in\ndocs-builder, but in
order to get images working as soon as possible,\nI've used Markdown
syntax and left us a `TO DO` in a code comment to add\nback the
`screenshot` class where applicable.\n* Can you please add the
appropriate labels needed for
backporting?","sha":"907cd5904b3328d5c89da31fb19c0528a6acdd50","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","documentation","backport:version","v9.1.0","v9.0.1"],"title":"[docs]
Fix image paths for
docs-assembler","number":218344,"url":"https://github.com/elastic/kibana/pull/218344","mergeCommit":{"message":"[docs]
Fix image paths for docs-assembler (#218344)\n\nFixes image paths to
work with docs-assembler.\n\nNotes for the reviewer:\n* I was not able
to get images in reference, extend, or release-notes to\nwork using the
`:::{image}` syntax because it seems to resolve\ndifferently than the
Markdown `![]()` syntax. We should address this in\ndocs-builder, but in
order to get images working as soon as possible,\nI've used Markdown
syntax and left us a `TO DO` in a code comment to add\nback the
`screenshot` class where applicable.\n* Can you please add the
appropriate labels needed for
backporting?","sha":"907cd5904b3328d5c89da31fb19c0528a6acdd50"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218344","number":218344,"mergeCommit":{"message":"[docs]
Fix image paths for docs-assembler (#218344)\n\nFixes image paths to
work with docs-assembler.\n\nNotes for the reviewer:\n* I was not able
to get images in reference, extend, or release-notes to\nwork using the
`:::{image}` syntax because it seems to resolve\ndifferently than the
Markdown `![]()` syntax. We should address this in\ndocs-builder, but in
order to get images working as soon as possible,\nI've used Markdown
syntax and left us a `TO DO` in a code comment to add\nback the
`screenshot` class where applicable.\n* Can you please add the
appropriate labels needed for
backporting?","sha":"907cd5904b3328d5c89da31fb19c0528a6acdd50"}}]}]
BACKPORT-->

Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co>
 2025-04-15 22:33:11 +00:00
Kibana Machine
b0f9319f34
[9.0] [Custom threshold rule] Allow group for ip type fields !! (#216062) (#218338) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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 21:46:36 +02:00
Cristina Amico
54ba9dae86
[9.0] [Fleet] Update deb and rpm install commands (#218068) (#218236) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Fleet] Update deb and rpm install commands
(#218068)](https://github.com/elastic/kibana/pull/218068)

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

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

<!--BACKPORT [{"author":{"name":"Cristina
Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T10:14:40Z","message":"[Fleet]
Update deb and rpm install commands (#218068)\n\nFixes
https://github.com/elastic/kibana/issues/212609\n\n## Summary\n\nThe
`--install-servers` flag present in the enroll commands for
fleet\nservers and elastic agents doesn't work in case of `deb` and
`rpm`\ninstallers. It should be used `ELASTIC_AGENT_FLAVOR` instead (see
[this\ncomment](https://github.com/elastic/kibana/issues/212609#issuecomment-2752335880)\nexplaining
it).\n\nI fixed the command in those cases and also added some unit
tests (that\nweren't present in some cases).\n\n### Testing \n- try to
enroll a fleet server or elastic agent\n- check that `rpm` and `deb`
commands don't have `--install-servers` in\nthe enroll commands
but\n\n```\nsudo ELASTIC_AGENT_FLAVOR=servers dpkg -i
$path_to_deb\n```\n\n### screenshots\n<img width=\"780\"
alt=\"Screenshot 2025-04-14 at 16 40 39\" src=\"http\n<img width=\"743\"
alt=\"Screenshot 2025-04-14 at 16 40
30\"\nsrc=\"https://github.com/user-attachments/assets/0bb405a7-7682-44ed-959e-b81832fd84af\"\n/>\n\ns://github.com/user-attachments/assets/f693f830-7e7f-43bd-a0ac-f378352cda93\"\n/>\n\n\n###
Checklist\n\n- [
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"7ffe810fc4d4189c285bdb2c08e8736f8ae27354","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","v9.1.0"],"title":"[Fleet]
Update deb and rpm install
commands","number":218068,"url":"https://github.com/elastic/kibana/pull/218068","mergeCommit":{"message":"[Fleet]
Update deb and rpm install commands (#218068)\n\nFixes
https://github.com/elastic/kibana/issues/212609\n\n## Summary\n\nThe
`--install-servers` flag present in the enroll commands for
fleet\nservers and elastic agents doesn't work in case of `deb` and
`rpm`\ninstallers. It should be used `ELASTIC_AGENT_FLAVOR` instead (see
[this\ncomment](https://github.com/elastic/kibana/issues/212609#issuecomment-2752335880)\nexplaining
it).\n\nI fixed the command in those cases and also added some unit
tests (that\nweren't present in some cases).\n\n### Testing \n- try to
enroll a fleet server or elastic agent\n- check that `rpm` and `deb`
commands don't have `--install-servers` in\nthe enroll commands
but\n\n```\nsudo ELASTIC_AGENT_FLAVOR=servers dpkg -i
$path_to_deb\n```\n\n### screenshots\n<img width=\"780\"
alt=\"Screenshot 2025-04-14 at 16 40 39\" src=\"http\n<img width=\"743\"
alt=\"Screenshot 2025-04-14 at 16 40
30\"\nsrc=\"https://github.com/user-attachments/assets/0bb405a7-7682-44ed-959e-b81832fd84af\"\n/>\n\ns://github.com/user-attachments/assets/f693f830-7e7f-43bd-a0ac-f378352cda93\"\n/>\n\n\n###
Checklist\n\n- [
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"7ffe810fc4d4189c285bdb2c08e8736f8ae27354"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218068","number":218068,"mergeCommit":{"message":"[Fleet]
Update deb and rpm install commands (#218068)\n\nFixes
https://github.com/elastic/kibana/issues/212609\n\n## Summary\n\nThe
`--install-servers` flag present in the enroll commands for
fleet\nservers and elastic agents doesn't work in case of `deb` and
`rpm`\ninstallers. It should be used `ELASTIC_AGENT_FLAVOR` instead (see
[this\ncomment](https://github.com/elastic/kibana/issues/212609#issuecomment-2752335880)\nexplaining
it).\n\nI fixed the command in those cases and also added some unit
tests (that\nweren't present in some cases).\n\n### Testing \n- try to
enroll a fleet server or elastic agent\n- check that `rpm` and `deb`
commands don't have `--install-servers` in\nthe enroll commands
but\n\n```\nsudo ELASTIC_AGENT_FLAVOR=servers dpkg -i
$path_to_deb\n```\n\n### screenshots\n<img width=\"780\"
alt=\"Screenshot 2025-04-14 at 16 40 39\" src=\"http\n<img width=\"743\"
alt=\"Screenshot 2025-04-14 at 16 40
30\"\nsrc=\"https://github.com/user-attachments/assets/0bb405a7-7682-44ed-959e-b81832fd84af\"\n/>\n\ns://github.com/user-attachments/assets/f693f830-7e7f-43bd-a0ac-f378352cda93\"\n/>\n\n\n###
Checklist\n\n- [
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"7ffe810fc4d4189c285bdb2c08e8736f8ae27354"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2025-04-15 18:16:36 +02:00
Matthias Wilhelm
33e094fdaf
[9.0] [Data view] Fix allow_hidden usage in the request for fields (#217628) (#218246) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Data view] Fix allow_hidden usage in the request for fields
(#217628)](https://github.com/elastic/kibana/pull/217628)

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

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

<!--BACKPORT [{"author":{"name":"Matthias
Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T10:11:00Z","message":"[Data
view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis
PR fixes the missing allowHidden/allow_hidden usage for data views using
the \"allow hidden and system indices\" functionality when creating a
data view. There are 2 endpoints being requested in Discover: `/fields`
& `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields`
ignored this parameter internally. This was
fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data
Views","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Data
view] Fix allow_hidden usage in the request for
fields","number":217628,"url":"https://github.com/elastic/kibana/pull/217628","mergeCommit":{"message":"[Data
view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis
PR fixes the missing allowHidden/allow_hidden usage for data views using
the \"allow hidden and system indices\" functionality when creating a
data view. There are 2 endpoints being requested in Discover: `/fields`
& `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields`
ignored this parameter internally. This was
fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4"}},"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/217628","number":217628,"mergeCommit":{"message":"[Data
view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis
PR fixes the missing allowHidden/allow_hidden usage for data views using
the \"allow hidden and system indices\" functionality when creating a
data view. There are 2 endpoints being requested in Discover: `/fields`
& `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields`
ignored this parameter internally. This was
fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4"}}]}]
BACKPORT-->
 2025-04-15 18:04:30 +02:00
Kibana Machine
2ea36d1f49
[9.0] Console/fix folding with script (#216817) (#218278) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [Console/fix folding with script
(#216817)](https://github.com/elastic/kibana/pull/216817)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T13:45:23Z","message":"Console/fix
folding with script (#216817)\n\nFixes
https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR
fixes the logic for finding folding ranges by ignoring\nopening/closing
markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that
the `script` field in the following request is
folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n
\"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n
\"\"\"\n for (field in params['fields']){\n if (!$(field,
'').isEmpty()){\n def value = $(field, '');\n def hash =
value.sha256();\n\n // Now we need to traverse as deep as needed\n //
and write to that field\n // because we do not have a simple\n // set
operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n
\n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n
\"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n
]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the
ranges is best-effort without\ncompromising performance. We currently
iterate through each line in the\ntext and use regex, but there are some
cases which are not covered by\nthis logic; for example, opening
parenthesis, followed by a string in\nthe same line would not be
foldable. In order to cover all cases\ncorrectly, we would need to
iterate through every single character, but\nthat would make the logic
much more complex and might affect performance\nif we have a lot of text
in the editor, as these folding ranges are\ncomputed on every change in
the
editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"Console/fix
folding with
script","number":216817,"url":"https://github.com/elastic/kibana/pull/216817","mergeCommit":{"message":"Console/fix
folding with script (#216817)\n\nFixes
https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR
fixes the logic for finding folding ranges by ignoring\nopening/closing
markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that
the `script` field in the following request is
folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n
\"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n
\"\"\"\n for (field in params['fields']){\n if (!$(field,
'').isEmpty()){\n def value = $(field, '');\n def hash =
value.sha256();\n\n // Now we need to traverse as deep as needed\n //
and write to that field\n // because we do not have a simple\n // set
operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n
\n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n
\"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n
]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the
ranges is best-effort without\ncompromising performance. We currently
iterate through each line in the\ntext and use regex, but there are some
cases which are not covered by\nthis logic; for example, opening
parenthesis, followed by a string in\nthe same line would not be
foldable. In order to cover all cases\ncorrectly, we would need to
iterate through every single character, but\nthat would make the logic
much more complex and might affect performance\nif we have a lot of text
in the editor, as these folding ranges are\ncomputed on every change in
the
editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216817","number":216817,"mergeCommit":{"message":"Console/fix
folding with script (#216817)\n\nFixes
https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR
fixes the logic for finding folding ranges by ignoring\nopening/closing
markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that
the `script` field in the following request is
folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n
\"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n
\"\"\"\n for (field in params['fields']){\n if (!$(field,
'').isEmpty()){\n def value = $(field, '');\n def hash =
value.sha256();\n\n // Now we need to traverse as deep as needed\n //
and write to that field\n // because we do not have a simple\n // set
operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n
\n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n
\"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n
]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the
ranges is best-effort without\ncompromising performance. We currently
iterate through each line in the\ntext and use regex, but there are some
cases which are not covered by\nthis logic; for example, opening
parenthesis, followed by a string in\nthe same line would not be
foldable. In order to cover all cases\ncorrectly, we would need to
iterate through every single character, but\nthat would make the logic
much more complex and might affect performance\nif we have a lot of text
in the editor, as these folding ranges are\ncomputed on every change in
the
editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2025-04-15 17:16:05 +02:00
Kibana Machine
b10ac896f3
[9.0] [Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123) (#218249) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Security Solution] Suppress prebuilt rule SO duplicates in review
install endpoint
(#218123)](https://github.com/elastic/kibana/pull/218123)

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

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

<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T11:45:08Z","message":"[Security
Solution] Suppress prebuilt rule SO duplicates in review install
endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy
`security_detection_engine` package doesn't affect a preview
installation endpoint. Older security detection rules package versions
contain saved object rule duplicates affecting the endpoint.\n\nHaving
`security_detection_engine` v`8.17.1` package installed
`/internal/detection_engine/prebuilt_rules/status` and
`/internal/detection_engine/prebuilt_rules/installation/_review`
endpoints return a different number of rules available to install.\n\n##
Details\n\nOlder `security_detection_engine` package versions contain
rule saved objects duplicates representing the latest version. For
example, `8.17.1` version has a rule `Microsoft 365 User Restricted from
Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16`
and the latest version `206`. Since a package may contain multiple
historical rule versions it sticks to the following format
`<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and
`<version>` it's version. Some older package versions omit `<version>`
for the latest rule version. `Microsoft 365 User Restricted from Sending
Email` rule mentioned above has two equal assets corresponding to the
latest version with the only difference in the saved object id
`0136b315-b566-482f-866c-1d8e2477ba16` and
`0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview
endpoint was designed to handle `<rule_id>_<version>` format only.
Consequently, it improperly handles older prebuilt rules package
version.\n\nThis bug manifested in
https://github.com/elastic/kibana/pull/217544 where
`security_detection_engine` version has been bumped to `8.18.1`. It
resulted in a failed integration test. Further investigation has shown
that the test installs an older package version `8.17.1` to assert
prebuilt rules upgrade workflow works correctly.\n\nThe fix is
implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by
using `Map` to deduplicate prebuilt rule
assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution] Suppress prebuilt rule SO duplicates in review install
endpoint","number":218123,"url":"https://github.com/elastic/kibana/pull/218123","mergeCommit":{"message":"[Security
Solution] Suppress prebuilt rule SO duplicates in review install
endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy
`security_detection_engine` package doesn't affect a preview
installation endpoint. Older security detection rules package versions
contain saved object rule duplicates affecting the endpoint.\n\nHaving
`security_detection_engine` v`8.17.1` package installed
`/internal/detection_engine/prebuilt_rules/status` and
`/internal/detection_engine/prebuilt_rules/installation/_review`
endpoints return a different number of rules available to install.\n\n##
Details\n\nOlder `security_detection_engine` package versions contain
rule saved objects duplicates representing the latest version. For
example, `8.17.1` version has a rule `Microsoft 365 User Restricted from
Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16`
and the latest version `206`. Since a package may contain multiple
historical rule versions it sticks to the following format
`<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and
`<version>` it's version. Some older package versions omit `<version>`
for the latest rule version. `Microsoft 365 User Restricted from Sending
Email` rule mentioned above has two equal assets corresponding to the
latest version with the only difference in the saved object id
`0136b315-b566-482f-866c-1d8e2477ba16` and
`0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview
endpoint was designed to handle `<rule_id>_<version>` format only.
Consequently, it improperly handles older prebuilt rules package
version.\n\nThis bug manifested in
https://github.com/elastic/kibana/pull/217544 where
`security_detection_engine` version has been bumped to `8.18.1`. It
resulted in a failed integration test. Further investigation has shown
that the test installs an older package version `8.17.1` to assert
prebuilt rules upgrade workflow works correctly.\n\nThe fix is
implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by
using `Map` to deduplicate prebuilt rule
assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218123","number":218123,"mergeCommit":{"message":"[Security
Solution] Suppress prebuilt rule SO duplicates in review install
endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy
`security_detection_engine` package doesn't affect a preview
installation endpoint. Older security detection rules package versions
contain saved object rule duplicates affecting the endpoint.\n\nHaving
`security_detection_engine` v`8.17.1` package installed
`/internal/detection_engine/prebuilt_rules/status` and
`/internal/detection_engine/prebuilt_rules/installation/_review`
endpoints return a different number of rules available to install.\n\n##
Details\n\nOlder `security_detection_engine` package versions contain
rule saved objects duplicates representing the latest version. For
example, `8.17.1` version has a rule `Microsoft 365 User Restricted from
Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16`
and the latest version `206`. Since a package may contain multiple
historical rule versions it sticks to the following format
`<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and
`<version>` it's version. Some older package versions omit `<version>`
for the latest rule version. `Microsoft 365 User Restricted from Sending
Email` rule mentioned above has two equal assets corresponding to the
latest version with the only difference in the saved object id
`0136b315-b566-482f-866c-1d8e2477ba16` and
`0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview
endpoint was designed to handle `<rule_id>_<version>` format only.
Consequently, it improperly handles older prebuilt rules package
version.\n\nThis bug manifested in
https://github.com/elastic/kibana/pull/217544 where
`security_detection_engine` version has been bumped to `8.18.1`. It
resulted in a failed integration test. Further investigation has shown
that the test installs an older package version `8.17.1` to assert
prebuilt rules upgrade workflow works correctly.\n\nThe fix is
implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by
using `Map` to deduplicate prebuilt rule
assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
 2025-04-15 15:23:37 +02:00
Kibana Machine
35ef891f3f
[9.0] [Console] Fix nested sql lexer rules (#217571) (#218239) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Console] Fix nested sql lexer rules
(#217571)](https://github.com/elastic/kibana/pull/217571)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T10:59:27Z","message":"[Console]
Fix nested sql lexer rules (#217571)\n\nFixes
https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR
fixes the SQL lexer rules which, previously, recognized a single\n`/` as
a start of comment, which is not a valid SQL syntax. According to\nthe
[SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere
are only two types of comments - the single-line one that starts\nwith
`--` and the multi-line one that starts with `/*` and ends
with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that
contains the `/` character was\nincorrectly highlighted as a comment and
was messing up the highlighting\nof the rest of the request.\n\nTest
with the following request. Make sure that the SQL script in
the\n`\"query\"` object is highlighted correctly as well as the rest of
the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n
\"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n
\"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\":
{\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n
\"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n
\"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\":
1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n
{\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n
\"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\":
[\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\":
999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n
{{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n
{{#service.name}}({{.}}) OR
{{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}}
({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n
\"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n
}\n },\n \"condition\": {\n \"compare\": {\n
\"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n
\"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found
related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n
}\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console]
Fix nested sql lexer
rules","number":217571,"url":"https://github.com/elastic/kibana/pull/217571","mergeCommit":{"message":"[Console]
Fix nested sql lexer rules (#217571)\n\nFixes
https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR
fixes the SQL lexer rules which, previously, recognized a single\n`/` as
a start of comment, which is not a valid SQL syntax. According to\nthe
[SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere
are only two types of comments - the single-line one that starts\nwith
`--` and the multi-line one that starts with `/*` and ends
with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that
contains the `/` character was\nincorrectly highlighted as a comment and
was messing up the highlighting\nof the rest of the request.\n\nTest
with the following request. Make sure that the SQL script in
the\n`\"query\"` object is highlighted correctly as well as the rest of
the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n
\"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n
\"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\":
{\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n
\"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n
\"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\":
1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n
{\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n
\"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\":
[\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\":
999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n
{{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n
{{#service.name}}({{.}}) OR
{{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}}
({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n
\"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n
}\n },\n \"condition\": {\n \"compare\": {\n
\"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n
\"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found
related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n
}\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217571","number":217571,"mergeCommit":{"message":"[Console]
Fix nested sql lexer rules (#217571)\n\nFixes
https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR
fixes the SQL lexer rules which, previously, recognized a single\n`/` as
a start of comment, which is not a valid SQL syntax. According to\nthe
[SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere
are only two types of comments - the single-line one that starts\nwith
`--` and the multi-line one that starts with `/*` and ends
with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that
contains the `/` character was\nincorrectly highlighted as a comment and
was messing up the highlighting\nof the rest of the request.\n\nTest
with the following request. Make sure that the SQL script in
the\n`\"query\"` object is highlighted correctly as well as the rest of
the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n
\"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n
\"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\":
{\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n
\"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n
\"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\":
1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n
{\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n
\"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\":
[\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\":
999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n
{{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n
{{#service.name}}({{.}}) OR
{{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}}
({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n
\"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n
}\n },\n \"condition\": {\n \"compare\": {\n
\"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n
\"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found
related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n
}\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2025-04-15 14:55:41 +02:00
Kibana Machine
98b209d765
[9.0] [Infra] Check ML permissions before requesting ML data (#218069) (#218230) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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 13:43:42 +02:00
Kibana Machine
f9d26b45b6
[9.0] [Console] Fix a11y overlay test (#218130) (#218220) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Console] Fix a11y overlay test
(#218130)](https://github.com/elastic/kibana/pull/218130)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T09:07:06Z","message":"[Console]
Fix a11y overlay test (#218130)\n\nFixes
https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR
fixes the flaky test for the a11y overlay by adding a `retry`\nand
allowing more time for the overlay element to be detected.\n\nFlaky test
runner
build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console]
Fix a11y overlay
test","number":218130,"url":"https://github.com/elastic/kibana/pull/218130","mergeCommit":{"message":"[Console]
Fix a11y overlay test (#218130)\n\nFixes
https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR
fixes the flaky test for the a11y overlay by adding a `retry`\nand
allowing more time for the overlay element to be detected.\n\nFlaky test
runner
build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218130","number":218130,"mergeCommit":{"message":"[Console]
Fix a11y overlay test (#218130)\n\nFixes
https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR
fixes the flaky test for the a11y overlay by adding a `retry`\nand
allowing more time for the overlay element to be detected.\n\nFlaky test
runner
build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2025-04-15 13:17:02 +02:00
Kibana Machine
51682db9a8
[9.0] [Console] Finishing design touches (#217887) (#218222) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[Console] Finishing design touches
(#217887)](https://github.com/elastic/kibana/pull/217887)

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

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

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T09:08:32Z","message":"[Console]
Finishing design touches (#217887)\n\nFixes
https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR
adds the following small design improvements:\n\n### 1. Ensures that the
bottom border of the selection doesn't overlap\nwith the next line by
shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot
2025-04-10 at 17 50
35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe
also increase the line height a little to ensure that the action\npanel
box fits inside a single-line request selection box:\n\n\n<img
width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00
07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n###
2. Ensures that the left border of the selection doesn't overlap\nwith
the line numbers by shifting the border to the right.\n\nBefore:\n<img
width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49
30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img
width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50
01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n###
3. Increases the contrast between the selected text and the\nselection
blue box by increasing the transparency of the blue
selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot
2025-04-10 at 17 51
43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana
Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console]
Finishing design
touches","number":217887,"url":"https://github.com/elastic/kibana/pull/217887","mergeCommit":{"message":"[Console]
Finishing design touches (#217887)\n\nFixes
https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR
adds the following small design improvements:\n\n### 1. Ensures that the
bottom border of the selection doesn't overlap\nwith the next line by
shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot
2025-04-10 at 17 50
35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe
also increase the line height a little to ensure that the action\npanel
box fits inside a single-line request selection box:\n\n\n<img
width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00
07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n###
2. Ensures that the left border of the selection doesn't overlap\nwith
the line numbers by shifting the border to the right.\n\nBefore:\n<img
width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49
30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img
width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50
01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n###
3. Increases the contrast between the selected text and the\nselection
blue box by increasing the transparency of the blue
selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot
2025-04-10 at 17 51
43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217887","number":217887,"mergeCommit":{"message":"[Console]
Finishing design touches (#217887)\n\nFixes
https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR
adds the following small design improvements:\n\n### 1. Ensures that the
bottom border of the selection doesn't overlap\nwith the next line by
shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot
2025-04-10 at 17 50
35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe
also increase the line height a little to ensure that the action\npanel
box fits inside a single-line request selection box:\n\n\n<img
width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00
07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n###
2. Ensures that the left border of the selection doesn't overlap\nwith
the line numbers by shifting the border to the right.\n\nBefore:\n<img
width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49
30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img
width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50
01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n###
3. Increases the contrast between the selected text and the\nselection
blue box by increasing the transparency of the blue
selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot
2025-04-10 at 17 51
43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img
width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51
14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by:
Matthew Kime
<matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2025-04-15 13:16:13 +02:00
Kibana Machine
972d62ec1a
[9.0] [ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107) (#218219) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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:13:12 +02:00
Jeramy Soucy
fcdff43eac
[9.0] Fixes bulk re-encryption for encrypted objects located in all spaces (#217625) (#218177) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [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:22:59 -04:00
elastic-renovate-prod[bot]
ef80ad851e
Update dependency selenium-webdriver to ^4.31.0 (9.0) (#216403) 
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-14 22:22:25 +02:00
Kibana Machine
086804391a
[9.0] [FTR] unify custom role name with Scout (#217882) (#218152) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[FTR] unify custom role name with Scout
(#217882)](https://github.com/elastic/kibana/pull/217882)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:21:49Z","message":"[FTR]
unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF
David added a possibility to spin up MKI project with custom role\nset
and ready to use.\n\nOriginally FTR was using reserved name
`'customRole'` for internal\nKibana role to be mapped with native custom
role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate
SAML authentication, but\nthe new framework will allow to run the tests
in parallel. That said, we\nneed to support multiple custom role
credentials (one pair per worker)\nand for simplicity we decided to use
the same keys:\n\nTo run your tests locally against MKI you need to add
a new Cloud user\nentry in
`user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\":
..., \"password\": ... }, // FTR requires only the first
entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ...
},\n...\n```\n\nThe test change is minimal:\n<img width=\"559\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by:
Cesare de Cal
<cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","FTR","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[FTR]
unify custom role name with
Scout","number":217882,"url":"https://github.com/elastic/kibana/pull/217882","mergeCommit":{"message":"[FTR]
unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF
David added a possibility to spin up MKI project with custom role\nset
and ready to use.\n\nOriginally FTR was using reserved name
`'customRole'` for internal\nKibana role to be mapped with native custom
role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate
SAML authentication, but\nthe new framework will allow to run the tests
in parallel. That said, we\nneed to support multiple custom role
credentials (one pair per worker)\nand for simplicity we decided to use
the same keys:\n\nTo run your tests locally against MKI you need to add
a new Cloud user\nentry in
`user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\":
..., \"password\": ... }, // FTR requires only the first
entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ...
},\n...\n```\n\nThe test change is minimal:\n<img width=\"559\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by:
Cesare de Cal
<cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217882","number":217882,"mergeCommit":{"message":"[FTR]
unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF
David added a possibility to spin up MKI project with custom role\nset
and ready to use.\n\nOriginally FTR was using reserved name
`'customRole'` for internal\nKibana role to be mapped with native custom
role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate
SAML authentication, but\nthe new framework will allow to run the tests
in parallel. That said, we\nneed to support multiple custom role
credentials (one pair per worker)\nand for simplicity we decided to use
the same keys:\n\nTo run your tests locally against MKI you need to add
a new Cloud user\nentry in
`user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\":
..., \"password\": ... }, // FTR requires only the first
entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ...
},\n...\n```\n\nThe test change is minimal:\n<img width=\"559\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by:
Cesare de Cal
<cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2025-04-14 21:23:01 +02:00
Kibana Machine
06e5e580eb
[9.0] [Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959) (#218155) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[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","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","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.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/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,"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: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>
 2025-04-14 20:46:32 +02:00
Lisa Cawley
85f32f93e1
[9.0] [DOCS] Add minimal synthetic APIs (#214518) (#217900) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[DOCS] Add minimal synthetic APIs
(#214518)](https://github.com/elastic/kibana/pull/214518)

<!--- 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-10T17:26:49Z","message":"[DOCS]
Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis
<colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[DOCS]
Add minimal synthetic
APIs","number":214518,"url":"https://github.com/elastic/kibana/pull/214518","mergeCommit":{"message":"[DOCS]
Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis
<colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214518","number":214518,"mergeCommit":{"message":"[DOCS]
Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis
<colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-14 19:58:03 +02:00
Lisa Cawley
1d08c30c53
[9.0] [DOCS] Use new responseOps URLs in doc link service and APIs (#217601) (#217928) 2025-04-14 13:43:05 -04:00
Kibana Machine
02a41598f9
[9.0] [ObsUX][A11y] Fix focus for popover in details flyout (#218095) (#218127) 
# Backport

This will backport the following commits from `main` to `9.0`:
- [[ObsUX][A11y] Fix focus for popover in details flyout
(#218095)](https://github.com/elastic/kibana/pull/218095)

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

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

<!--BACKPORT
[{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-14T14:15:25Z","message":"[ObsUX][A11y]
Fix focus for popover in details flyout (#218095)\n\nCloses
https://github.com/elastic/kibana/issues/212633\n\n## Summary\n\nFixed
navigation by keeping focus on Popover opener element\n\n### How to
test\nObservability -> Infrastructure -> Infrastructure inventory
page.\n1. Navigate to any square below All button.\n2. Press Enter.\n3.
Navigate to infographic for Host IP.\n4. Press Enter.\n5. Press
Esc.\n\nExpected result: Navigation continues to next element when Tab
key is\npressed.\n\nBEFORE
\n\n\nhttps://github.com/user-attachments/assets/e9ee6ff6-895d-408f-b165-0f8edd4eb197\n\nAFTER\n\n\nhttps://github.com/user-attachments/assets/b01e6955-b659-4d9a-abcf-1ece48adc161","sha":"26d9f5f7d0d24eaa8fdefc9a92747de4e3cc5a66","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX][A11y]
Fix focus for popover in details
flyout","number":218095,"url":"https://github.com/elastic/kibana/pull/218095","mergeCommit":{"message":"[ObsUX][A11y]
Fix focus for popover in details flyout (#218095)\n\nCloses
https://github.com/elastic/kibana/issues/212633\n\n## Summary\n\nFixed
navigation by keeping focus on Popover opener element\n\n### How to
test\nObservability -> Infrastructure -> Infrastructure inventory
page.\n1. Navigate to any square below All button.\n2. Press Enter.\n3.
Navigate to infographic for Host IP.\n4. Press Enter.\n5. Press
Esc.\n\nExpected result: Navigation continues to next element when Tab
key is\npressed.\n\nBEFORE
\n\n\nhttps://github.com/user-attachments/assets/e9ee6ff6-895d-408f-b165-0f8edd4eb197\n\nAFTER\n\n\nhttps://github.com/user-attachments/assets/b01e6955-b659-4d9a-abcf-1ece48adc161","sha":"26d9f5f7d0d24eaa8fdefc9a92747de4e3cc5a66"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218095","number":218095,"mergeCommit":{"message":"[ObsUX][A11y]
Fix focus for popover in details flyout (#218095)\n\nCloses
https://github.com/elastic/kibana/issues/212633\n\n## Summary\n\nFixed
navigation by keeping focus on Popover opener element\n\n### How to
test\nObservability -> Infrastructure -> Infrastructure inventory
page.\n1. Navigate to any square below All button.\n2. Press Enter.\n3.
Navigate to infographic for Host IP.\n4. Press Enter.\n5. Press
Esc.\n\nExpected result: Navigation continues to next element when Tab
key is\npressed.\n\nBEFORE
\n\n\nhttps://github.com/user-attachments/assets/e9ee6ff6-895d-408f-b165-0f8edd4eb197\n\nAFTER\n\n\nhttps://github.com/user-attachments/assets/b01e6955-b659-4d9a-abcf-1ece48adc161","sha":"26d9f5f7d0d24eaa8fdefc9a92747de4e3cc5a66"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
 2025-04-14 18:06:11 +02:00
Milosz Marcinkowski
1b5224cd3f
[9.0] [APM][UI] Sort environment dropdown alphabetically (#217710) (#218093) 
# Backport

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

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/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:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v8.18.0","v9.1.0","v8.19.0","v8.17.5","v8.16.7"],"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":"8.18","label":"v8.18.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217880","number":217880,"state":"MERGED","mergeCommit":{"sha":"6d7097d6be890bac0896fe67d04b84e65cbe2c7c","message":"[8.18]
[APM][UI] Sort environment dropdown alphabetically (#217710)
(#217880)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.18`:\n- [[APM][UI] Sort environment dropdown
alphabetically\n(#217710)](https://github.com/elastic/kibana/pull/217710)\n\n<!---
Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Milosz\nMarcinkowski\",\"email\":\"38698566+miloszmarcinkowski@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-04-10T15:38:20Z\",\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment
dropdown\nalphabetically\",\"number\":217710,\"url\":\"https://github.com/elastic/kibana/pull/217710\",\"mergeCommit\":{\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\\\"\\n/>|\",\"sha\":\"23cbaa6d55de4e331ce180f6857db94ca11c209a\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","labelRegex":"^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"}},{"branch":"8.x","label":"v8.19.0","labelRegex":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217878","number":217878,"state":"MERGED","mergeCommit":{"sha":"22cb96803f4b8533d7e3c82981afb75b8112da11","message":"[8.x]
[APM][UI] Sort environment dropdown alphabetically (#217710)
(#217878)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[APM][UI] Sort environment dropdown
alphabetically\n(#217710)](https://github.com/elastic/kibana/pull/217710)\n\n<!---
Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Milosz\nMarcinkowski\",\"email\":\"38698566+miloszmarcinkowski@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-04-10T15:38:20Z\",\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment
dropdown\nalphabetically\",\"number\":217710,\"url\":\"https://github.com/elastic/kibana/pull/217710\",\"mergeCommit\":{\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\\\"\\n/>|\",\"sha\":\"23cbaa6d55de4e331ce180f6857db94ca11c209a\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"8.17","label":"v8.17.5","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217881","number":217881,"state":"MERGED","mergeCommit":{"sha":"0fe80714cb1d0b7f73543f303c7224aa66741605","message":"[8.17]
[APM][UI] Sort environment dropdown alphabetically (#217710)
(#217881)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.17`:\n- [[APM][UI] Sort environment dropdown
alphabetically\n(#217710)](https://github.com/elastic/kibana/pull/217710)\n\n<!---
Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Milosz\nMarcinkowski\",\"email\":\"38698566+miloszmarcinkowski@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-04-10T15:38:20Z\",\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment
dropdown\nalphabetically\",\"number\":217710,\"url\":\"https://github.com/elastic/kibana/pull/217710\",\"mergeCommit\":{\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\\\"\\n/>|\",\"sha\":\"23cbaa6d55de4e331ce180f6857db94ca11c209a\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"8.16","label":"v8.16.7","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217883","number":217883,"state":"MERGED","mergeCommit":{"sha":"8ea1340a099d0db7aec11f9f0849cd11ea25a589","message":"[8.16]
[APM][UI] Sort environment dropdown alphabetically (#217710)
(#217883)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.16`:\n- [[APM][UI] Sort environment dropdown
alphabetically\n(#217710)](https://github.com/elastic/kibana/pull/217710)\n\n<!---
Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Milosz\nMarcinkowski\",\"email\":\"38698566+miloszmarcinkowski@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-04-10T15:38:20Z\",\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment
dropdown\nalphabetically\",\"number\":217710,\"url\":\"https://github.com/elastic/kibana/pull/217710\",\"mergeCommit\":{\"message\":\"[APM][UI]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\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]\nSort
environment dropdown alphabetically
(#217710)\\n\\nCloses\n#217814\\n\\n### Summary\\n\\nSort environment
list\nalphabetically.\\n\\n|Before|After|\\n|-|-|\\n|<img
width=\\\"1724\\\"\nalt=\\\"Screenshot 2025-04-10 at 12
01\n15\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\\\"\\n/>|<img\nwidth=\\\"1722\\\"
alt=\\\"Screenshot 2025-04-10 at 11
58\n27\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\\\"\\n/>|\",\"sha\":\"23cbaa6d55de4e331ce180f6857db94ca11c209a\"}}]}]\nBACKPORT-->"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-14 15:54:40 +02:00