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

83028 commits

This branch
This branch
All branches
Author SHA1 Message Date
Kibana Machine
d67cb8cec8
[8.18] [Stack connectors] Fix bedrock modelId encoding (#216915) (#217060) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Stack connectors] Fix bedrock `modelId` encoding
(#216915)](https://github.com/elastic/kibana/pull/216915)

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

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

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T15:56:14Z","message":"[Stack
connectors] Fix bedrock `modelId` encoding
(#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","sdh-linked","Team:Security Generative
AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Stack
connectors] Fix bedrock `modelId`
encoding","number":216915,"url":"https://github.com/elastic/kibana/pull/216915","mergeCommit":{"message":"[Stack
connectors] Fix bedrock `modelId` encoding
(#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a"}},"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/216915","number":216915,"mergeCommit":{"message":"[Stack
connectors] Fix bedrock `modelId` encoding
(#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a"}},{"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: Steph Milovic <stephanie.milovic@elastic.co>
 2025-04-03 18:44:11 +01:00
Nicolas Chaulet
177ad44060
[8.18] [Fleet] allow alpha, beta, rc suffixes in agent versions (#211787) (#217044) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Fleet] allow alpha, beta, rc suffixes in agent versions
(#211787)](https://github.com/elastic/kibana/pull/211787)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-19T20:37:28Z","message":"[Fleet]
allow alpha, beta, rc suffixes in agent versions (#211787)\n\n##
Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd
agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen
`9.0.0` comes out, that should show up as latest. For example,\n`8.0.0`
versions come back in this order:\n<img width=\"462\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:version","v9.1.0","v8.19.0","backport:8.18","v8.18.1"],"title":"[Fleet]
Do not allow alpha, beta, rc suffixes in agent
versions","number":211787,"url":"https://github.com/elastic/kibana/pull/211787","mergeCommit":{"message":"[Fleet]
allow alpha, beta, rc suffixes in agent versions (#211787)\n\n##
Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd
agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen
`9.0.0` comes out, that should show up as latest. For example,\n`8.0.0`
versions come back in this order:\n<img width=\"462\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211849","number":211849,"state":"MERGED","mergeCommit":{"sha":"1f98cbfdb28c12848820484a5ad4d51156f70136","message":"[9.0]
[Fleet] allow alpha, beta, rc suffixes in agent versions (#211787)
(#211849)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [[Fleet] allow alpha, beta, rc suffixes in agent
versions\n(#211787)](https://github.com/elastic/kibana/pull/211787)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Julia Bardi
<90178898+juliaElastic@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211787","number":211787,"mergeCommit":{"message":"[Fleet]
allow alpha, beta, rc suffixes in agent versions (#211787)\n\n##
Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd
agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen
`9.0.0` comes out, that should show up as latest. For example,\n`8.0.0`
versions come back in this order:\n<img width=\"462\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51"}},{"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"}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-04-03 17:36:36 +01:00
Kevin Delemme
81f21ca312
[8.18] [SLO]: Optional groupings for slo summary (#209910) (#217040) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[SLO]: Optional groupings for slo summary
(#209910)](https://github.com/elastic/kibana/pull/209910)

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

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

<!--BACKPORT [{"author":{"name":"Bailey
Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T23:18:56Z","message":"[SLO]:
Optional groupings for slo summary (#209910)\n\n##
Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO
summary optional to fix schema validation\r\nissues with SLOs without
groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with
loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n##
Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field.
All SLOs should\r\nstill be able to be grouped despite this
distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","Team:obs-ux-management","v9.1.0","v8.19.0"],"title":"[SLO]:
Optional groupings for slo
summary","number":209910,"url":"https://github.com/elastic/kibana/pull/209910","mergeCommit":{"message":"[SLO]:
Optional groupings for slo summary (#209910)\n\n##
Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO
summary optional to fix schema validation\r\nissues with SLOs without
groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with
loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n##
Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field.
All SLOs should\r\nstill be able to be grouped despite this
distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209934","number":209934,"state":"MERGED","mergeCommit":{"sha":"442136fc09962861c11ab8476813f6dccdf1fce7","message":"[9.0]
[SLO]: Optional groupings for slo summary (#209910) (#209934)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[SLO]: Optional groupings for slo
summary\n(#209910)](https://github.com/elastic/kibana/pull/209910)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by:
Bailey Cash
<bailey.cash@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209910","number":209910,"mergeCommit":{"message":"[SLO]:
Optional groupings for slo summary (#209910)\n\n##
Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO
summary optional to fix schema validation\r\nissues with SLOs without
groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with
loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n##
Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field.
All SLOs should\r\nstill be able to be grouped despite this
distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209933","number":209933,"state":"MERGED","mergeCommit":{"sha":"a37d63bf115a8f408fd91e6ef2da84a81e7b9abe","message":"[8.x]
[SLO]: Optional groupings for slo summary (#209910) (#209933)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.x`:\n- [[SLO]: Optional groupings for slo
summary\n(#209910)](https://github.com/elastic/kibana/pull/209910)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by:
Bailey Cash <bailey.cash@elastic.co>"}}]}] BACKPORT-->

Co-authored-by: Bailey Cash <bailey.cash@elastic.co>
 2025-04-03 17:28:30 +01:00
Kibana Machine
dd5db61860
[8.18] [ObsUx][A11y] Improve abbreviations spell for screen readers (#216954) (#217015) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUx][A11y] Improve abbreviations spell for screen readers
(#216954)](https://github.com/elastic/kibana/pull/216954)

<!--- 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-03T12:59:55Z","message":"[ObsUx][A11y]
Improve abbreviations spell for screen readers (#216954)\n\nCloses
https://github.com/elastic/kibana/issues/194983 \nCloses
https://github.com/elastic/kibana/issues/194982\n\n### What was done\n-
Add aria-label for elements in the table (links, buttons)\n- Improve the
spelling of some abbreviations for screen readers\n\n#### How to test\n-
Use any screen reader in Infrastructure inventory table view, and\nhosts
tables, navigate through the tables columns
titles\n\n\nfbd27a0b-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339","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]
Improve abbreviations spell for screen
readers","number":216954,"url":"https://github.com/elastic/kibana/pull/216954","mergeCommit":{"message":"[ObsUx][A11y]
Improve abbreviations spell for screen readers (#216954)\n\nCloses
https://github.com/elastic/kibana/issues/194983 \nCloses
https://github.com/elastic/kibana/issues/194982\n\n### What was done\n-
Add aria-label for elements in the table (links, buttons)\n- Improve the
spelling of some abbreviations for screen readers\n\n#### How to test\n-
Use any screen reader in Infrastructure inventory table view, and\nhosts
tables, navigate through the tables columns
titles\n\n\nfbd27a0b-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339"}},"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/216954","number":216954,"mergeCommit":{"message":"[ObsUx][A11y]
Improve abbreviations spell for screen readers (#216954)\n\nCloses
https://github.com/elastic/kibana/issues/194983 \nCloses
https://github.com/elastic/kibana/issues/194982\n\n### What was done\n-
Add aria-label for elements in the table (links, buttons)\n- Improve the
spelling of some abbreviations for screen readers\n\n#### How to test\n-
Use any screen reader in Infrastructure inventory table view, and\nhosts
tables, navigate through the tables columns
titles\n\n\nfbd27a0b-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339"}},{"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-03 16:21:51 +01:00
Miriam
99662f5f87
[8.18] [ObsUX][A11y] Add announcement keyboard elements improvements (#216592) (#216987) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUX][A11y] Add announcement keyboard elements improvements
(#216592)](https://github.com/elastic/kibana/pull/216592)

<!--- 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-02T11:24:26Z","message":"[ObsUX][A11y]
Add announcement keyboard elements improvements (#216592)\n\nCloses
https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome
elements on the Infrastructure Inventory were not accessible or\ntheir
interaction with the keyboard was not properly announced to the\nusers,
see issue for steps to reproduce, use a screen reader to test.\n\n###
What was done\n\n#### Groupby buttons \n\n- Replace link element by
button\n- Add announcement when interacting with the button, i.e.,
when\nclicking/selecting the `All` button nothing
changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n####
Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon,
the button didn't\nhave any action, it only shows the selected color for
minimum and\nmaximum for the selected color palette\n- Fix ui alignment
of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot
2025-04-01 at 08 58
40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img
width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54
31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX][A11y]
Add announcement keyboard elements
improvements","number":216592,"url":"https://github.com/elastic/kibana/pull/216592","mergeCommit":{"message":"[ObsUX][A11y]
Add announcement keyboard elements improvements (#216592)\n\nCloses
https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome
elements on the Infrastructure Inventory were not accessible or\ntheir
interaction with the keyboard was not properly announced to the\nusers,
see issue for steps to reproduce, use a screen reader to test.\n\n###
What was done\n\n#### Groupby buttons \n\n- Replace link element by
button\n- Add announcement when interacting with the button, i.e.,
when\nclicking/selecting the `All` button nothing
changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n####
Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon,
the button didn't\nhave any action, it only shows the selected color for
minimum and\nmaximum for the selected color palette\n- Fix ui alignment
of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot
2025-04-01 at 08 58
40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img
width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54
31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216800","number":216800,"state":"MERGED","mergeCommit":{"sha":"ae0c91447de0f4cc021be66dbd66751d3d0ead48","message":"[9.0]
[ObsUX][A11y] Add announcement keyboard elements improvements (#216592)
(#216800)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [[ObsUX][A11y] Add announcement keyboard elements
improvements\n(#216592)](https://github.com/elastic/kibana/pull/216592)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Miriam
<31922082+MiriamAparicio@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216592","number":216592,"mergeCommit":{"message":"[ObsUX][A11y]
Add announcement keyboard elements improvements (#216592)\n\nCloses
https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome
elements on the Infrastructure Inventory were not accessible or\ntheir
interaction with the keyboard was not properly announced to the\nusers,
see issue for steps to reproduce, use a screen reader to test.\n\n###
What was done\n\n#### Groupby buttons \n\n- Replace link element by
button\n- Add announcement when interacting with the button, i.e.,
when\nclicking/selecting the `All` button nothing
changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n####
Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon,
the button didn't\nhave any action, it only shows the selected color for
minimum and\nmaximum for the selected color palette\n- Fix ui alignment
of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot
2025-04-01 at 08 58
40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img
width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54
31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-03 13:43:34 +01:00
Kibana Machine
fb48a0196d
[8.18] [ObsUX][A11y] Add area label to comparison drop down (#215664) (#215715) 
# Backport

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

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

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

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

Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
 2025-04-03 13:28:22 +01:00
Kibana Machine
8a0d757fe4
[8.18] [APM] Span links: add tooltip explaining the reason for missing linked span details (#216487) (#216957) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM] Span links: add tooltip explaining the reason for missing
linked span details
(#216487)](https://github.com/elastic/kibana/pull/216487)

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

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

<!--BACKPORT [{"author":{"name":"Milosz
Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T14:39:00Z","message":"[APM]
Span links: add tooltip explaining the reason for missing linked span
details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching
details for the Span Links flyout, it is possible that the\nparent span
has not yet been ingested, resulting in an 'Unknown' service\nname which
might be misleading to users. To avoid confusion, we decided\nto add
tooltip to the icon with explanation.\n\n<img width=\"2558\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n###
How to test:\n- use edge-oblt data\n- in Applications go to
`accountingservice` service\n- select `orders receive` transaction\n- in
trace waterfall click `Span Links`
button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM]
Span links: add tooltip explaining the reason for missing linked span
details","number":216487,"url":"https://github.com/elastic/kibana/pull/216487","mergeCommit":{"message":"[APM]
Span links: add tooltip explaining the reason for missing linked span
details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching
details for the Span Links flyout, it is possible that the\nparent span
has not yet been ingested, resulting in an 'Unknown' service\nname which
might be misleading to users. To avoid confusion, we decided\nto add
tooltip to the icon with explanation.\n\n<img width=\"2558\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n###
How to test:\n- use edge-oblt data\n- in Applications go to
`accountingservice` service\n- select `orders receive` transaction\n- in
trace waterfall click `Span Links`
button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216660","number":216660,"state":"MERGED","mergeCommit":{"sha":"b587f643d0bcc489d7a11886a81296723da00616","message":"[9.0]
[APM] Span links: add tooltip explaining the reason for missing linked
span details (#216487) (#216660)\n\n# Backport\n\nThis will backport the
following commits from `main` to `9.0`:\n- [[APM] Span links: add
tooltip explaining the reason for missing\nlinked span
details\n(#216487)](https://github.com/elastic/kibana/pull/216487)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Milosz Marcinkowski
<38698566+miloszmarcinkowski@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216487","number":216487,"mergeCommit":{"message":"[APM]
Span links: add tooltip explaining the reason for missing linked span
details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching
details for the Span Links flyout, it is possible that the\nparent span
has not yet been ingested, resulting in an 'Unknown' service\nname which
might be misleading to users. To avoid confusion, we decided\nto add
tooltip to the icon with explanation.\n\n<img width=\"2558\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n###
How to test:\n- use edge-oblt data\n- in Applications go to
`accountingservice` service\n- select `orders receive` transaction\n- in
trace waterfall click `Span Links`
button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72"}}]}]
BACKPORT-->

Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>
 2025-04-03 10:19:00 +01:00
Kibana Machine
462fad4086
[8.18] [Usage collection] Replace agent.type with hard coded value to categorize monitoring type correctly. (#216391) (#216951) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Usage collection] Replace `agent.type` with hard coded value to
categorize monitoring type correctly.
(#216391)](https://github.com/elastic/kibana/pull/216391)

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

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

<!--BACKPORT
[{"author":{"name":"Mashhur","email":"99575341+mashhurs@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-03T07:06:38Z","message":"[Usage
collection] Replace `agent.type` with hard coded value to categorize
monitoring type correctly. (#216391)\n\n## Summary\nCollection type was
set with `agent.type` which conflicts on stack and\nmetricbeat
monitorings (same `metricbeat` value). For the stack\nmonitoring,
elastic-agent internally utilizes filebat or metricbeat.\nThis change
hard codes the `collection_types` corresponding on each\nmonitoring type
to categorize monitoring type correctly.\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- ~~[ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n-
~~[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials~~\n- [x] [Unit
or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- ~~[ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n-
~~[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.~~\n- ~~[ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed~~\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack
monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\":
{\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\":
\"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n
\"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n
\"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n
\"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n
\"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n
\"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n
\"batch_size_max\": 125,\n \"batch_size_min\": 125,\n
\"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\":
10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n
\"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\":
\"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n
\"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n
\"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n
}\n```\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736","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","v9.1.0"],"title":"[Usage
collection] Replace `agent.type` with hard coded value to categorize
monitoring type
correctly.","number":216391,"url":"https://github.com/elastic/kibana/pull/216391","mergeCommit":{"message":"[Usage
collection] Replace `agent.type` with hard coded value to categorize
monitoring type correctly. (#216391)\n\n## Summary\nCollection type was
set with `agent.type` which conflicts on stack and\nmetricbeat
monitorings (same `metricbeat` value). For the stack\nmonitoring,
elastic-agent internally utilizes filebat or metricbeat.\nThis change
hard codes the `collection_types` corresponding on each\nmonitoring type
to categorize monitoring type correctly.\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- ~~[ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n-
~~[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials~~\n- [x] [Unit
or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- ~~[ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n-
~~[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.~~\n- ~~[ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed~~\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack
monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\":
{\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\":
\"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n
\"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n
\"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n
\"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n
\"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n
\"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n
\"batch_size_max\": 125,\n \"batch_size_min\": 125,\n
\"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\":
10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n
\"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\":
\"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n
\"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n
\"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n
}\n```\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736"}},"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/216391","number":216391,"mergeCommit":{"message":"[Usage
collection] Replace `agent.type` with hard coded value to categorize
monitoring type correctly. (#216391)\n\n## Summary\nCollection type was
set with `agent.type` which conflicts on stack and\nmetricbeat
monitorings (same `metricbeat` value). For the stack\nmonitoring,
elastic-agent internally utilizes filebat or metricbeat.\nThis change
hard codes the `collection_types` corresponding on each\nmonitoring type
to categorize monitoring type correctly.\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- ~~[ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n-
~~[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials~~\n- [x] [Unit
or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- ~~[ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n-
~~[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.~~\n- ~~[ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed~~\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack
monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\":
{\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\":
\"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n
\"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n
\"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n
\"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n
\"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n
\"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n
\"batch_size_max\": 125,\n \"batch_size_min\": 125,\n
\"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\":
10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n
\"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\":
\"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\":
\"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n
\"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n
\"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n
\"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n
}\n```\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736"}}]}]
BACKPORT-->

Co-authored-by: Mashhur <99575341+mashhurs@users.noreply.github.com>
 2025-04-03 09:54:02 +01:00
Kibana Machine
bd8c979f98
[8.18] [dashboard] fix State being dropped when editing visualize embeddables (#216901) (#216924) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[dashboard] fix State being dropped when editing visualize
embeddables (#216901)](https://github.com/elastic/kibana/pull/216901)

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

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

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T20:12:27Z","message":"[dashboard]
fix State being dropped when editing visualize embeddables
(#216901)\n\nCloses
https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve
in branch specific
patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1)
Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add
new markdown panel. This takes you to visualize editor. On return\nto
dashboard, embeddable state transfer service contains the
markdown\nembeddable runtime state. `panels$.value` is `{
markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered
with empty\nserializedState and runtimeState from embeddable transfer
service.\n3) Click save dashboard. This is where the bug lies.
`panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput:
{ // serializedState\n}}}` but instead, remains unchanged.\n4) Click
duplicate panel. New panel is added to `panels$.value`. This\ntriggers
unsaved changes to be stored in session storage. Unsaved\nchanges store
`panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!!
}}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}`
is put into session storage\n5) Edit duplicated markdown panel. This
takes you to visualize editor.\nOn return to dashboard, embeddable state
transfer service contains the\nnew markdown embeddable runtime state for
the duplicated panel. This is\nwhere things start to fall apart. The
dashboard state is loaded from\nsaved object state and `panels` contains
the serialized state for both\n`markdownPanelId` and
`duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from
dashboard session and replaces dashboard saved\nstate. This causes the
first markdown panel to render with empty\nserializedState.\n\n\n###
Solution\nThe problem is resolved by updating `panels# Backport

This will backport the following commits from `main` to `8.18`:
{{{{raw}}}} - [[dashboard] fix State being dropped when editing
visualize embeddables
(#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}}

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

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

<!--BACKPORT on save. This causes step\n4 to store the current
serializedState in unsaved
changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","project:embeddableRebuild","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[dashboard]
fix State being dropped when editing visualize
embeddables","number":216901,"url":"https://github.com/elastic/kibana/pull/216901","mergeCommit":{"message":"[dashboard]
fix State being dropped when editing visualize embeddables
(#216901)\n\nCloses
https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve
in branch specific
patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1)
Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add
new markdown panel. This takes you to visualize editor. On return\nto
dashboard, embeddable state transfer service contains the
markdown\nembeddable runtime state. `panels$.value` is `{
markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered
with empty\nserializedState and runtimeState from embeddable transfer
service.\n3) Click save dashboard. This is where the bug lies.
`panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput:
{ // serializedState\n}}}` but instead, remains unchanged.\n4) Click
duplicate panel. New panel is added to `panels$.value`. This\ntriggers
unsaved changes to be stored in session storage. Unsaved\nchanges store
`panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!!
}}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}`
is put into session storage\n5) Edit duplicated markdown panel. This
takes you to visualize editor.\nOn return to dashboard, embeddable state
transfer service contains the\nnew markdown embeddable runtime state for
the duplicated panel. This is\nwhere things start to fall apart. The
dashboard state is loaded from\nsaved object state and `panels` contains
the serialized state for both\n`markdownPanelId` and
`duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from
dashboard session and replaces dashboard saved\nstate. This causes the
first markdown panel to render with empty\nserializedState.\n\n\n###
Solution\nThe problem is resolved by updating `panels# Backport

This will backport the following commits from `main` to `8.18`:
{{{{raw}}}} - [[dashboard] fix State being dropped when editing
visualize embeddables
(#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}}

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

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

<!--BACKPORT on save. This causes step\n4 to store the current
serializedState in unsaved
changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70"}},"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/216901","number":216901,"mergeCommit":{"message":"[dashboard]
fix State being dropped when editing visualize embeddables
(#216901)\n\nCloses
https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve
in branch specific
patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1)
Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add
new markdown panel. This takes you to visualize editor. On return\nto
dashboard, embeddable state transfer service contains the
markdown\nembeddable runtime state. `panels$.value` is `{
markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered
with empty\nserializedState and runtimeState from embeddable transfer
service.\n3) Click save dashboard. This is where the bug lies.
`panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput:
{ // serializedState\n}}}` but instead, remains unchanged.\n4) Click
duplicate panel. New panel is added to `panels$.value`. This\ntriggers
unsaved changes to be stored in session storage. Unsaved\nchanges store
`panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!!
}}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}`
is put into session storage\n5) Edit duplicated markdown panel. This
takes you to visualize editor.\nOn return to dashboard, embeddable state
transfer service contains the\nnew markdown embeddable runtime state for
the duplicated panel. This is\nwhere things start to fall apart. The
dashboard state is loaded from\nsaved object state and `panels` contains
the serialized state for both\n`markdownPanelId` and
`duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from
dashboard session and replaces dashboard saved\nstate. This causes the
first markdown panel to render with empty\nserializedState.\n\n\n###
Solution\nThe problem is resolved by updating `panels# Backport

This will backport the following commits from `main` to `8.18`:
{{{{raw}}}} - [[dashboard] fix State being dropped when editing
visualize embeddables
(#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}}

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

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

<!--BACKPORT on save. This causes step\n4 to store the current
serializedState in unsaved
changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70"}},{"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: Nathan Reese <reese.nathan@elastic.co>
 2025-04-02 23:01:47 +01:00
Kibana Machine
03589f4a90
[8.18] [Status logging] More performant throttling (#216534) (#216912) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Status logging] More performant throttling
(#216534)](https://github.com/elastic/kibana/pull/216534)

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

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

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T19:10:47Z","message":"[Status
logging] More performant throttling
(#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","performance","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Status
logging] More performant
throttling","number":216534,"url":"https://github.com/elastic/kibana/pull/216534","mergeCommit":{"message":"[Status
logging] More performant throttling
(#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6"}},"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/216534","number":216534,"mergeCommit":{"message":"[Status
logging] More performant throttling
(#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
 2025-04-02 22:00:32 +01:00
Kibana Machine
40e03461f0
[8.18] Add autocomplete support for all field types (#216765) (#216906) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Add autocomplete support for all field types
(#216765)](https://github.com/elastic/kibana/pull/216765)

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

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

<!--BACKPORT [{"author":{"name":"Ioana
Tagirta","email":"ioanatia@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T17:56:01Z","message":"Add
autocomplete support for all field types
(#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f","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","v9.1.0"],"title":"Add
autocomplete support for all field
types","number":216765,"url":"https://github.com/elastic/kibana/pull/216765","mergeCommit":{"message":"Add
autocomplete support for all field types
(#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f"}},"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/216765","number":216765,"mergeCommit":{"message":"Add
autocomplete support for all field types
(#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f"}}]}]
BACKPORT-->

Co-authored-by: Ioana Tagirta <ioanatia@users.noreply.github.com>
 2025-04-02 20:51:30 +01:00
Kibana Machine
5ae0c07bee
[8.18] Add default metrics dashboard for Node.js OTel (#215735) (#216895) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Add default metrics dashboard for Node.js OTel
(#215735)](https://github.com/elastic/kibana/pull/215735)

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

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

<!--BACKPORT [{"author":{"name":"David
Luna","email":"david.luna@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T17:00:46Z","message":"Add
default metrics dashboard for Node.js OTel
(#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","backport:prev-major","ci:cloud-redeploy","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"Add
default metrics dashboard for Node.js
OTel","number":215735,"url":"https://github.com/elastic/kibana/pull/215735","mergeCommit":{"message":"Add
default metrics dashboard for Node.js OTel
(#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb"}},"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/215735","number":215735,"mergeCommit":{"message":"Add
default metrics dashboard for Node.js OTel
(#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb"}}]}]
BACKPORT-->

Co-authored-by: David Luna <david.luna@elastic.co>
 2025-04-02 20:03:44 +01:00
Tiago Costa
241562a3d5
[8.18] chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715) (#216875) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [chore(NA): replaces native-hdr-histogram with hdr-histogram-js
(#216715)](https://github.com/elastic/kibana/pull/216715)

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

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

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T08:27:11Z","message":"chore(NA):
replaces native-hdr-histogram with hdr-histogram-js
(#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds
are failing\nthe bootstrap on macos machines during bootstrap since
early today.\n\nIts usage its contained in a single dev package and
therefore this PR\nattempts to port into
`hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","ci:collect-apm","ci:all-cypress-suites","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","ci:perf-check:start","v9.1.0"],"title":"chore(NA):
replaces native-hdr-histogram with
hdr-histogram-js","number":216715,"url":"https://github.com/elastic/kibana/pull/216715","mergeCommit":{"message":"chore(NA):
replaces native-hdr-histogram with hdr-histogram-js
(#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds
are failing\nthe bootstrap on macos machines during bootstrap since
early today.\n\nIts usage its contained in a single dev package and
therefore this PR\nattempts to port into
`hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993"}},"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/216715","number":216715,"mergeCommit":{"message":"chore(NA):
replaces native-hdr-histogram with hdr-histogram-js
(#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds
are failing\nthe bootstrap on macos machines during bootstrap since
early today.\n\nIts usage its contained in a single dev package and
therefore this PR\nattempts to port into
`hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993"}},{"url":"https://github.com/elastic/kibana/pull/216870","number":216870,"branch":"9.0","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/216874","number":216874,"branch":"8.x","state":"OPEN"}]}]
BACKPORT-->
 2025-04-02 18:46:08 +01:00
Steph Milovic
40db38b0f9
[8.18] [Security solution] Read config from preconfigured connectors in Assistant/Attack Discovery (#216700) (#216873) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security solution] Read `config` from preconfigured connectors in
Assistant/Attack Discovery
(#216700)](https://github.com/elastic/kibana/pull/216700)

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

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

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T15:04:06Z","message":"[Security
solution] Read `config` from preconfigured connectors in
Assistant/Attack Discovery
(#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","Team:Security Generative
AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
solution] Read `config` from preconfigured connectors in
Assistant/Attack
Discovery","number":216700,"url":"https://github.com/elastic/kibana/pull/216700","mergeCommit":{"message":"[Security
solution] Read `config` from preconfigured connectors in
Assistant/Attack Discovery
(#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},"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/216700","number":216700,"mergeCommit":{"message":"[Security
solution] Read `config` from preconfigured connectors in
Assistant/Attack Discovery
(#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216869","number":216869,"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-02 18:26:12 +01:00
Kibana Machine
fd9c9794eb
[8.18] Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927) (#216866) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Updates datafeeds for supplied security anomaly detection jobs to
exclude Elastic Agent and Beats processes
(#213927)](https://github.com/elastic/kibana/pull/213927)

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

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

<!--BACKPORT [{"author":{"name":"Miguel
Garzón","email":"mgarzon@uottawa.ca"},"sourceCommit":{"committedDate":"2025-03-21T09:32:14Z","message":"Updates
datafeeds for supplied security anomaly detection jobs to exclude
Elastic Agent and Beats processes (#213927)\n\nAs described in
https://github.com/elastic/security-team/issues/11532,\nwe have added
filters to exclude any processing related to the elastic\nendpoint
agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly
Detection","backport
missing","backport:prev-major","backport:version","v9.1.0","v8.19.0"],"title":"Updates
datafeeds for supplied security anomaly detection jobs to exclude
Elastic Agent and Beats
processes","number":213927,"url":"https://github.com/elastic/kibana/pull/213927","mergeCommit":{"message":"Updates
datafeeds for supplied security anomaly detection jobs to exclude
Elastic Agent and Beats processes (#213927)\n\nAs described in
https://github.com/elastic/security-team/issues/11532,\nwe have added
filters to exclude any processing related to the elastic\nendpoint
agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},"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/213927","number":213927,"mergeCommit":{"message":"Updates
datafeeds for supplied security anomaly detection jobs to exclude
Elastic Agent and Beats processes (#213927)\n\nAs described in
https://github.com/elastic/security-team/issues/11532,\nwe have added
filters to exclude any processing related to the elastic\nendpoint
agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Miguel Garzón <mgarzon@uottawa.ca>
 2025-04-02 17:45:46 +01:00
Kibana Machine
fb8150da8e
[8.18] [Discover] Fix getAdditionalCellActions FTR tests (#216540) (#216858) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Discover] Fix `getAdditionalCellActions` FTR tests
(#216540)](https://github.com/elastic/kibana/pull/216540)

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

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

<!--BACKPORT [{"author":{"name":"Davis
McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T14:45:08Z","message":"[Discover]
Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis
PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing
due to an issue dismissing alerts.\n\nResolves #213300.\nResolves
#213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Discover]
Fix `getAdditionalCellActions` FTR
tests","number":216540,"url":"https://github.com/elastic/kibana/pull/216540","mergeCommit":{"message":"[Discover]
Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis
PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing
due to an issue dismissing alerts.\n\nResolves #213300.\nResolves
#213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}},"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/216540","number":216540,"mergeCommit":{"message":"[Discover]
Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis
PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing
due to an issue dismissing alerts.\n\nResolves #213300.\nResolves
#213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}}]}]
BACKPORT-->

Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>
 2025-04-02 17:37:46 +01:00
Kibana Machine
dff8933d48
[8.18] [Security Solution] Fix alerts table grouping severity stats not showing badge (#216738) (#216845) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Fix alerts table grouping severity stats not
showing badge (#216738)](https://github.com/elastic/kibana/pull/216738)

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

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

<!--BACKPORT [{"author":{"name":"Philippe
Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:42:46Z","message":"[Security
Solution] Fix alerts table grouping severity stats not showing badge
(#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by
[this\nPR](https://github.com/elastic/kibana/pull/184635) back in
`8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the
PR linked above, the name of the property responsible to render\ncustom
components in the group stats section of the alerts table\ngrouping was
changed from `renderer` to `component` but there was (at\nleast) one
usage that had not been updated. Because that usage wasn't\ncorrectly
typed and there was no unit tests to verify the behavior, the\nissue
went unnoticed...\n\n### Notes\n\nThis whole code should be refactored
eventually. This is not the purpose\nof this PR. This only focuses on
fixing the issue, adding proper types\nand unit tests.\n\n| Before |
After |\n| ------------- | ------------- |\n| ![Screenshot 2025-04-01 at
5
00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n|
![Screenshot 2025-04-01 at 5
05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n|\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting:Investigations","Team:Security Generative
AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5","v8.16.7"],"title":"[Security
Solution] Fix alerts table grouping severity stats not showing
badge","number":216738,"url":"https://github.com/elastic/kibana/pull/216738","mergeCommit":{"message":"[Security
Solution] Fix alerts table grouping severity stats not showing badge
(#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by
[this\nPR](https://github.com/elastic/kibana/pull/184635) back in
`8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the
PR linked above, the name of the property responsible to render\ncustom
components in the group stats section of the alerts table\ngrouping was
changed from `renderer` to `component` but there was (at\nleast) one
usage that had not been updated. Because that usage wasn't\ncorrectly
typed and there was no unit tests to verify the behavior, the\nissue
went unnoticed...\n\n### Notes\n\nThis whole code should be refactored
eventually. This is not the purpose\nof this PR. This only focuses on
fixing the issue, adding proper types\nand unit tests.\n\n| Before |
After |\n| ------------- | ------------- |\n| ![Screenshot 2025-04-01 at
5
00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n|
![Screenshot 2025-04-01 at 5
05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n|\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216738","number":216738,"mergeCommit":{"message":"[Security
Solution] Fix alerts table grouping severity stats not showing badge
(#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by
[this\nPR](https://github.com/elastic/kibana/pull/184635) back in
`8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the
PR linked above, the name of the property responsible to render\ncustom
components in the group stats section of the alerts table\ngrouping was
changed from `renderer` to `component` but there was (at\nleast) one
usage that had not been updated. Because that usage wasn't\ncorrectly
typed and there was no unit tests to verify the behavior, the\nissue
went unnoticed...\n\n### Notes\n\nThis whole code should be refactored
eventually. This is not the purpose\nof this PR. This only focuses on
fixing the issue, adding proper types\nand unit tests.\n\n| Before |
After |\n| ------------- | ------------- |\n| ![Screenshot 2025-04-01 at
5
00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n|
![Screenshot 2025-04-01 at 5
05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n|\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},{"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"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>
 2025-04-02 16:46:31 +01:00
Kibana Machine
65df0cb8da
[8.18] Dev console - improve autocomplete for ES|QL _query API (#216795) (#216833) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Dev console - improve autocomplete for ES|QL _query API
(#216795)](https://github.com/elastic/kibana/pull/216795)

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

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

<!--BACKPORT [{"author":{"name":"Ioana
Tagirta","email":"ioanatia@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T13:20:44Z","message":"Dev
console - improve autocomplete for ES|QL _query API
(#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f","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","v9.1.0"],"title":"Dev
console - improve autocomplete for ES|QL _query
API","number":216795,"url":"https://github.com/elastic/kibana/pull/216795","mergeCommit":{"message":"Dev
console - improve autocomplete for ES|QL _query API
(#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f"}},"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/216795","number":216795,"mergeCommit":{"message":"Dev
console - improve autocomplete for ES|QL _query API
(#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f"}}]}]
BACKPORT-->

Co-authored-by: Ioana Tagirta <ioanatia@users.noreply.github.com>
 2025-04-02 16:30:58 +01:00
Hannah Mudge
dad960ba36
[8.18] [controls] remove id from explicit input (#211851) (#216702) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[controls] remove id from explicit input
(#211851)](https://github.com/elastic/kibana/pull/211851)

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

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

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T21:31:42Z","message":"[controls]
remove id from explicit input (#211851)\n\nPart of `EmbeddableInput`
type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part
of this effort\nis removing `id` key from
`controlConfig/explicitInput`.\n\nWhile investigating this PR, I found
it odd that\n`ControlGroupApi.serializeState` returned controls in shape
`[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected
to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason
this works\nis
that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut`
adds `id` to each object in `controls`. This PR\nalso resolves this and
updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[
{ id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","project:embeddableRebuild","backport:version","v9.1.0","v8.19.0"],"title":"[controls]
remove id from explicit
input","number":211851,"url":"https://github.com/elastic/kibana/pull/211851","mergeCommit":{"message":"[controls]
remove id from explicit input (#211851)\n\nPart of `EmbeddableInput`
type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part
of this effort\nis removing `id` key from
`controlConfig/explicitInput`.\n\nWhile investigating this PR, I found
it odd that\n`ControlGroupApi.serializeState` returned controls in shape
`[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected
to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason
this works\nis
that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut`
adds `id` to each object in `controls`. This PR\nalso resolves this and
updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[
{ id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e"}},"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/211851","number":211851,"mergeCommit":{"message":"[controls]
remove id from explicit input (#211851)\n\nPart of `EmbeddableInput`
type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part
of this effort\nis removing `id` key from
`controlConfig/explicitInput`.\n\nWhile investigating this PR, I found
it odd that\n`ControlGroupApi.serializeState` returned controls in shape
`[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected
to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason
this works\nis
that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut`
adds `id` to each object in `controls`. This PR\nalso resolves this and
updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[
{ id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212994","number":212994,"state":"MERGED","mergeCommit":{"sha":"8cea348178264f1e994ac2e71814c2ec63bc7fd7","message":"[8.x]
[controls] remove id from explicit input (#211851) (#212994)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.x`:\n- [[controls] remove id from explicit
input\n(#211851)](https://github.com/elastic/kibana/pull/211851)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Nathan Reese <reese.nathan@elastic.co>"}}]}] BACKPORT-->

---------

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-02 08:30:00 -06:00
Kibana Machine
efa90a360d
[8.18] [Vega] Fix update vega spec in functional tests (#216620) (#216673) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Vega] Fix update vega spec in functional tests
(#216620)](https://github.com/elastic/kibana/pull/216620)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T15:26:17Z","message":"[Vega]
Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis
PR fixes a flaky test practice that was causing issues in
7.17\nbranch.\nThe flakiness was introduced long ago when the choosen
method to\nupdate/add more content to the Vega Spec was done by manually
clicking\nin the Vega spec editor the left border (where the editor
shows the line\nnumbers) to select all the text in the editor and go to
the last line\nbut a char before the end of the text (right before the
closing\nbracket).\n\nThe failure highlighted
by\nhttps://github.com/elastic/kibana/issues/213646 where caused the
added\n`config` text positioned in the wrong line/column due to the
Konami Code\nlike type of functional test operation.\n\n\nThe fix
instead provides a more robust method: it takes the written text\nin the
editor, parse it to JSON, update the JSON and write it back again\nto
the editor.\n\nWill fix the issue
https://github.com/elastic/kibana/issues/213646 when\nbackported to
7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Visualizations","release_note:skip","backport:all-open","v9.1.0"],"title":"[Vega]
Fix update vega spec in functional
tests","number":216620,"url":"https://github.com/elastic/kibana/pull/216620","mergeCommit":{"message":"[Vega]
Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis
PR fixes a flaky test practice that was causing issues in
7.17\nbranch.\nThe flakiness was introduced long ago when the choosen
method to\nupdate/add more content to the Vega Spec was done by manually
clicking\nin the Vega spec editor the left border (where the editor
shows the line\nnumbers) to select all the text in the editor and go to
the last line\nbut a char before the end of the text (right before the
closing\nbracket).\n\nThe failure highlighted
by\nhttps://github.com/elastic/kibana/issues/213646 where caused the
added\n`config` text positioned in the wrong line/column due to the
Konami Code\nlike type of functional test operation.\n\n\nThe fix
instead provides a more robust method: it takes the written text\nin the
editor, parse it to JSON, update the JSON and write it back again\nto
the editor.\n\nWill fix the issue
https://github.com/elastic/kibana/issues/213646 when\nbackported to
7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}},"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/216620","number":216620,"mergeCommit":{"message":"[Vega]
Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis
PR fixes a flaky test practice that was causing issues in
7.17\nbranch.\nThe flakiness was introduced long ago when the choosen
method to\nupdate/add more content to the Vega Spec was done by manually
clicking\nin the Vega spec editor the left border (where the editor
shows the line\nnumbers) to select all the text in the editor and go to
the last line\nbut a char before the end of the text (right before the
closing\nbracket).\n\nThe failure highlighted
by\nhttps://github.com/elastic/kibana/issues/213646 where caused the
added\n`config` text positioned in the wrong line/column due to the
Konami Code\nlike type of functional test operation.\n\n\nThe fix
instead provides a more robust method: it takes the written text\nin the
editor, parse it to JSON, update the JSON and write it back again\nto
the editor.\n\nWill fix the issue
https://github.com/elastic/kibana/issues/213646 when\nbackported to
7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}}]}] BACKPORT-->

Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co>
 2025-04-02 09:56:26 +01:00
Kibana Machine
b9e6f3d0e6
[8.18] [FIPS] Skips license check test for FIPS test suite (#216056) (#216728) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[FIPS] Skips license check test for FIPS test suite
(#216056)](https://github.com/elastic/kibana/pull/216056)

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

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

<!--BACKPORT
[{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T21:23:35Z","message":"[FIPS]
Skips license check test for FIPS test suite (#216056)\n\n##
Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the
platinum\nlicense so having a test which asserts `basic` causes the CI
to fail.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Core","release_note:skip","v9.0.0","Feature:FIPS","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[FIPS]
Skips license check test for FIPS test
suite","number":216056,"url":"https://github.com/elastic/kibana/pull/216056","mergeCommit":{"message":"[FIPS]
Skips license check test for FIPS test suite (#216056)\n\n##
Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the
platinum\nlicense so having a test which asserts `basic` causes the CI
to fail.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},"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/216056","number":216056,"mergeCommit":{"message":"[FIPS]
Skips license check test for FIPS test suite (#216056)\n\n##
Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the
platinum\nlicense so having a test which asserts `basic` causes the CI
to fail.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sid <siddharthmantri1@gmail.com>
 2025-04-02 00:11:32 +01:00
Cauê Marcondes
3f72e2f823
[8.18] [APM] Fix query for transaction marks (#215819) (#216679) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM] Fix query for transaction marks
(#215819)](https://github.com/elastic/kibana/pull/215819)

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

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

<!--BACKPORT [{"author":{"name":"Sunghyun
Kim","email":"cqbqdd11519@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T15:05:42Z","message":"[APM]
Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a
bug in kibana 8.17, where no transaction marks are shown in\nthe APM's
transaction waterfall ui.\nThe marks are stored in the field
`transaction.marks.agent` of\ndocuments, but kibana apm server is
querying `transaction.agent.marks`.\n\nThis PR fixes the field
name.\n\n\nI also added `span.id` in the query source to include the
marks in the\nresponse, even if there is no `span.links` in the
transaction info.\n(I found the case from RUM data with
`transaction.marks.agent` but\nwithout `span.links`, so that the
response does not include marks\nbecause there is no `source` field in
the query result)\n\nI am not sure if it's the right way to fix it, as i
have no\nunderstanding about the relationsip between
`transaction.marks.agent`\nand `span.links`, so this PR is more like a
bug report.\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- [ ] 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-
[ ]
...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","💝community","backport:all-open","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM]
Fix query for transaction
marks","number":215819,"url":"https://github.com/elastic/kibana/pull/215819","mergeCommit":{"message":"[APM]
Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a
bug in kibana 8.17, where no transaction marks are shown in\nthe APM's
transaction waterfall ui.\nThe marks are stored in the field
`transaction.marks.agent` of\ndocuments, but kibana apm server is
querying `transaction.agent.marks`.\n\nThis PR fixes the field
name.\n\n\nI also added `span.id` in the query source to include the
marks in the\nresponse, even if there is no `span.links` in the
transaction info.\n(I found the case from RUM data with
`transaction.marks.agent` but\nwithout `span.links`, so that the
response does not include marks\nbecause there is no `source` field in
the query result)\n\nI am not sure if it's the right way to fix it, as i
have no\nunderstanding about the relationsip between
`transaction.marks.agent`\nand `span.links`, so this PR is more like a
bug report.\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- [ ] 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-
[ ]
...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}},"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/215819","number":215819,"mergeCommit":{"message":"[APM]
Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a
bug in kibana 8.17, where no transaction marks are shown in\nthe APM's
transaction waterfall ui.\nThe marks are stored in the field
`transaction.marks.agent` of\ndocuments, but kibana apm server is
querying `transaction.agent.marks`.\n\nThis PR fixes the field
name.\n\n\nI also added `span.id` in the query source to include the
marks in the\nresponse, even if there is no `span.links` in the
transaction info.\n(I found the case from RUM data with
`transaction.marks.agent` but\nwithout `span.links`, so that the
response does not include marks\nbecause there is no `source` field in
the query result)\n\nI am not sure if it's the right way to fix it, as i
have no\nunderstanding about the relationsip between
`transaction.marks.agent`\nand `span.links`, so this PR is more like a
bug report.\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- [ ] 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-
[ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}}]}]
BACKPORT-->

---------

Co-authored-by: Sunghyun Kim <cqbqdd11519@gmail.com>
 2025-04-01 20:42:45 +01:00
jennypavlova
71bbb4774e
[8.18] [APM][OTel] Add url.full fallback (#215397) (#216639) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM][OTel] Add url.full fallback
(#215397)](https://github.com/elastic/kibana/pull/215397)

<!--- 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-01T09:50:28Z","message":"[APM][OTel]
Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the
missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n-
[SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create
a\nserverless instance from this PR and it should make it easier)~~\n-
Testing on serverless (the env linked in the PR) \n - EDOT service (I
run locally in Docker and connect to the env): \n<img width=\"1904\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n
- Other generated service (from the
env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n
\n- In the meantime \n - using synthtrace: Case to run/expectation\n-
`node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary
should be visible\n
\n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n-
`node scripts/synthtrace simple_trace.ts` / The trace summary
should\nstill be visible (using `url.full` in this case)\n
\n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04","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","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","ci:project-redeploy","v9.1.0"],"title":"[APM][OTel]
Add url.full
fallback","number":215397,"url":"https://github.com/elastic/kibana/pull/215397","mergeCommit":{"message":"[APM][OTel]
Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the
missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n-
[SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create
a\nserverless instance from this PR and it should make it easier)~~\n-
Testing on serverless (the env linked in the PR) \n - EDOT service (I
run locally in Docker and connect to the env): \n<img width=\"1904\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n
- Other generated service (from the
env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n
\n- In the meantime \n - using synthtrace: Case to run/expectation\n-
`node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary
should be visible\n
\n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n-
`node scripts/synthtrace simple_trace.ts` / The trace summary
should\nstill be visible (using `url.full` in this case)\n
\n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}},"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/215397","number":215397,"mergeCommit":{"message":"[APM][OTel]
Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the
missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n-
[SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create
a\nserverless instance from this PR and it should make it easier)~~\n-
Testing on serverless (the env linked in the PR) \n - EDOT service (I
run locally in Docker and connect to the env): \n<img width=\"1904\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n
- Other generated service (from the
env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n
\n- In the meantime \n - using synthtrace: Case to run/expectation\n-
`node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary
should be visible\n
\n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n-
`node scripts/synthtrace simple_trace.ts` / The trace summary
should\nstill be visible (using `url.full` in this case)\n
\n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}}]}]
BACKPORT-->
 2025-04-01 18:50:40 +01:00
florent-leborgne
89ab8e4aff
[8.18] [Docs] Add note about runtime fields and data views (#216617) (#216669) 
# Backport

This will backport the following commits from `8.x` to `8.18`:
- [[Docs] Add note about runtime fields and data views
(#216617)](https://github.com/elastic/kibana/pull/216617)

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

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

<!--BACKPORT
[{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T15:37:58Z","message":"[Docs]
Add note about runtime fields and data views (#216617)\n\nReproduce
https://github.com/elastic/kibana/pull/159636","sha":"2d7bbd76f621b42457ddbf1c2377a6e4f6a717db","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.16.0","backport:version","v8.17.0","v8.18.0","v8.19.0"],"title":"[Docs]
Add note about runtime fields and data
views","number":216617,"url":"https://github.com/elastic/kibana/pull/216617","mergeCommit":{"message":"[Docs]
Add note about runtime fields and data views (#216617)\n\nReproduce
https://github.com/elastic/kibana/pull/159636","sha":"2d7bbd76f621b42457ddbf1c2377a6e4f6a717db"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.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":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-01 16:12:54 +00:00
Julia Bardi
0c716056b3
[8.18][Fleet] Update inputs_with_standalone_docker_agent.ts (#216622) 
Related to https://github.com/elastic/kibana/pull/216589
Fix docker image
 2025-04-01 16:44:05 +02:00
Kibana Machine
43968cbe58
[8.18] [APM][OTel] Fix spanlink invalid filter (#215322) (#216607) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM][OTel] Fix spanlink invalid filter
(#215322)](https://github.com/elastic/kibana/pull/215322)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:43:19Z","message":"[APM][OTel]
Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an
optional check for `span.id` (this value is always\npopulated) when
redirecting to an error within a span
link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.5"],"title":"[APM][OTel]
Fix spanlink invalid
filter","number":215322,"url":"https://github.com/elastic/kibana/pull/215322","mergeCommit":{"message":"[APM][OTel]
Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an
optional check for `span.id` (this value is always\npopulated) when
redirecting to an error within a span
link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215322","number":215322,"mergeCommit":{"message":"[APM][OTel]
Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an
optional check for `span.id` (this value is always\npopulated) when
redirecting to an error within a span
link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-01 12:43:54 +01:00
Sergi Romeu
1b05004fd6
[8.18] [APM] Prevent getChildrenGroupedByParentId to include the parent in the children list (#214957) (#216579) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM] Prevent `getChildrenGroupedByParentId` to include the parent in
the children list
(#214957)](https://github.com/elastic/kibana/pull/214957)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T12:28:20Z","message":"[APM]
Prevent `getChildrenGroupedByParentId` to include the parent in the
children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR
prevents `getChildrenGroupedByParentId` to include the parent\nitem in
the children list, as this was causing some duplication.\n\n| Before |
After
|\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img
width=\"1433\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img
width=\"858\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img
width=\"1372\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img
width=\"844\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1","v8.17.5"],"title":"[APM]
Prevent `getChildrenGroupedByParentId` to include the parent in the
children
list","number":214957,"url":"https://github.com/elastic/kibana/pull/214957","mergeCommit":{"message":"[APM]
Prevent `getChildrenGroupedByParentId` to include the parent in the
children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR
prevents `getChildrenGroupedByParentId` to include the parent\nitem in
the children list, as this was causing some duplication.\n\n| Before |
After
|\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img
width=\"1433\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img
width=\"858\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img
width=\"1372\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img
width=\"844\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215153","number":215153,"state":"MERGED","mergeCommit":{"sha":"6c0c502e8e15bea18d8c96408f28b11e7f1a535f","message":"[9.0]
[APM] Prevent `getChildrenGroupedByParentId` to include the parent in
the children list (#214957) (#215153)\n\n# Backport\n\nThis will
backport the following commits from `main` to `9.0`:\n- [[APM] Prevent
`getChildrenGroupedByParentId` to include the parent in\nthe children
list\n(#214957)](https://github.com/elastic/kibana/pull/214957)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>"}},{"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/214957","number":214957,"mergeCommit":{"message":"[APM]
Prevent `getChildrenGroupedByParentId` to include the parent in the
children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR
prevents `getChildrenGroupedByParentId` to include the parent\nitem in
the children list, as this was causing some duplication.\n\n| Before |
After
|\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img
width=\"1433\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img
width=\"858\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img
width=\"1372\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img
width=\"844\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215152","number":215152,"state":"MERGED","mergeCommit":{"sha":"42e65b516782cb2895a5ee7e832885ed608cd4b9","message":"[8.x]
[APM] Prevent `getChildrenGroupedByParentId` to include the parent in
the children list (#214957) (#215152)\n\n# Backport\n\nThis will
backport the following commits from `main` to `8.x`:\n- [[APM] Prevent
`getChildrenGroupedByParentId` to include the parent in\nthe children
list\n(#214957)](https://github.com/elastic/kibana/pull/214957)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>"}},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-01 12:32:40 +01:00
Kibana Machine
8065eb640a
[8.18] [Fleet] enable flaky test (#216460) (#216589) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Fleet] enable flaky test
(#216460)](https://github.com/elastic/kibana/pull/216460)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T08:29:23Z","message":"[Fleet]
enable flaky test (#216460)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n-
[x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet]
enable flaky
test","number":216460,"url":"https://github.com/elastic/kibana/pull/216460","mergeCommit":{"message":"[Fleet]
enable flaky test (#216460)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n-
[x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}},"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/216460","number":216460,"mergeCommit":{"message":"[Fleet]
enable flaky test (#216460)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n-
[x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-04-01 11:30:06 +01:00
Kibana Machine
e9836788d1
[8.18] [ObsUX][A11y] Change button for link in Pod context menu (#216022) (#216065) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUX][A11y] Change button for link in Pod context menu
(#216022)](https://github.com/elastic/kibana/pull/216022)

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

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

<!--BACKPORT
[{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-26T15:17:15Z","message":"[ObsUX][A11y]
Change button for link in Pod context menu (#216022)\n\nCloses
https://github.com/elastic/kibana/issues/194971\n\n## Summary\n\nThe
context menu for Kubernetes Pod includes several links to other\nviews,
some of these links were converted to a button because the\n`onClick`
prop was added.\n\n`EuiListGroupItemProps`\n\n<img width=\"852\"
alt=\"Screenshot 2025-03-26 at 11 04
02\"\nsrc=\"https://github.com/user-attachments/assets/b7fb43b4-1fff-4605-9509-d894ece18e81\"\n/>\n\n<img
width=\"852\" alt=\"Screenshot 2025-03-26 at 11 03
40\"\nsrc=\"https://github.com/user-attachments/assets/5a7e831d-3bce-42ce-a7f0-46d5556e8a41\"\n/>\n\n###
What was done\n\n- Remove the `onClick` prop\n- Hide links when they are
not available instead of marking them as\ndisabled\n- The `Create
inventory rule` button wasn't changed to a link as it's\nopening a
flyout\n\n### How to test\n\n- Open the Infrastructure Inventory view
and select Kubernetes Pods\n- Click on a pod to open the popover\n-
Review the items' markup or use a screen reader to listen to each
item\nin the popover\n- On advance settings we can enable or disable
legacy Uptime, when\ndisabled link should be
hidden\n\nBEFORE\n\n\n![image](https://github.com/user-attachments/assets/ac590116-e168-4a70-90e1-62f4b5df2d95)\n\nAFTER\n\n<img
width=\"1566\" alt=\"Screenshot 2025-03-26 at 10 59
48\"\nsrc=\"https://github.com/user-attachments/assets/08e8be52-cf8b-424b-aec4-a65246660878\"\n/>\n\n<img
width=\"815\" alt=\"Screenshot 2025-03-26 at 11 00
51\"\nsrc=\"https://github.com/user-attachments/assets/1df50949-fc98-49b9-88ac-1de956ffbfd8\"\n/>","sha":"a0dfe46b843ca2d1ca744316e0b14acd64a4494b","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]
Change button for link in Pod context
menu","number":216022,"url":"https://github.com/elastic/kibana/pull/216022","mergeCommit":{"message":"[ObsUX][A11y]
Change button for link in Pod context menu (#216022)\n\nCloses
https://github.com/elastic/kibana/issues/194971\n\n## Summary\n\nThe
context menu for Kubernetes Pod includes several links to other\nviews,
some of these links were converted to a button because the\n`onClick`
prop was added.\n\n`EuiListGroupItemProps`\n\n<img width=\"852\"
alt=\"Screenshot 2025-03-26 at 11 04
02\"\nsrc=\"https://github.com/user-attachments/assets/b7fb43b4-1fff-4605-9509-d894ece18e81\"\n/>\n\n<img
width=\"852\" alt=\"Screenshot 2025-03-26 at 11 03
40\"\nsrc=\"https://github.com/user-attachments/assets/5a7e831d-3bce-42ce-a7f0-46d5556e8a41\"\n/>\n\n###
What was done\n\n- Remove the `onClick` prop\n- Hide links when they are
not available instead of marking them as\ndisabled\n- The `Create
inventory rule` button wasn't changed to a link as it's\nopening a
flyout\n\n### How to test\n\n- Open the Infrastructure Inventory view
and select Kubernetes Pods\n- Click on a pod to open the popover\n-
Review the items' markup or use a screen reader to listen to each
item\nin the popover\n- On advance settings we can enable or disable
legacy Uptime, when\ndisabled link should be
hidden\n\nBEFORE\n\n\n![image](https://github.com/user-attachments/assets/ac590116-e168-4a70-90e1-62f4b5df2d95)\n\nAFTER\n\n<img
width=\"1566\" alt=\"Screenshot 2025-03-26 at 10 59
48\"\nsrc=\"https://github.com/user-attachments/assets/08e8be52-cf8b-424b-aec4-a65246660878\"\n/>\n\n<img
width=\"815\" alt=\"Screenshot 2025-03-26 at 11 00
51\"\nsrc=\"https://github.com/user-attachments/assets/1df50949-fc98-49b9-88ac-1de956ffbfd8\"\n/>","sha":"a0dfe46b843ca2d1ca744316e0b14acd64a4494b"}},"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/216022","number":216022,"mergeCommit":{"message":"[ObsUX][A11y]
Change button for link in Pod context menu (#216022)\n\nCloses
https://github.com/elastic/kibana/issues/194971\n\n## Summary\n\nThe
context menu for Kubernetes Pod includes several links to other\nviews,
some of these links were converted to a button because the\n`onClick`
prop was added.\n\n`EuiListGroupItemProps`\n\n<img width=\"852\"
alt=\"Screenshot 2025-03-26 at 11 04
02\"\nsrc=\"https://github.com/user-attachments/assets/b7fb43b4-1fff-4605-9509-d894ece18e81\"\n/>\n\n<img
width=\"852\" alt=\"Screenshot 2025-03-26 at 11 03
40\"\nsrc=\"https://github.com/user-attachments/assets/5a7e831d-3bce-42ce-a7f0-46d5556e8a41\"\n/>\n\n###
What was done\n\n- Remove the `onClick` prop\n- Hide links when they are
not available instead of marking them as\ndisabled\n- The `Create
inventory rule` button wasn't changed to a link as it's\nopening a
flyout\n\n### How to test\n\n- Open the Infrastructure Inventory view
and select Kubernetes Pods\n- Click on a pod to open the popover\n-
Review the items' markup or use a screen reader to listen to each
item\nin the popover\n- On advance settings we can enable or disable
legacy Uptime, when\ndisabled link should be
hidden\n\nBEFORE\n\n\n![image](https://github.com/user-attachments/assets/ac590116-e168-4a70-90e1-62f4b5df2d95)\n\nAFTER\n\n<img
width=\"1566\" alt=\"Screenshot 2025-03-26 at 10 59
48\"\nsrc=\"https://github.com/user-attachments/assets/08e8be52-cf8b-424b-aec4-a65246660878\"\n/>\n\n<img
width=\"815\" alt=\"Screenshot 2025-03-26 at 11 00
51\"\nsrc=\"https://github.com/user-attachments/assets/1df50949-fc98-49b9-88ac-1de956ffbfd8\"\n/>","sha":"a0dfe46b843ca2d1ca744316e0b14acd64a4494b"}},{"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-01 10:54:27 +01:00
Sergi Romeu
c3b5889133
[8.18] [APM] Fix entry item in waterfall shouldn't be orphan (#214700) (#216577) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM] Fix entry item in waterfall shouldn't be orphan
(#214700)](https://github.com/elastic/kibana/pull/214700)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T10:02:30Z","message":"[APM]
Fix entry item in waterfall shouldn't be orphan (#214700)\n\n##
Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry
waterfall transaction is\ntreated as an orphan, causing it to reparent
itself and be duplicated\nmultiple
times.\n\n---------\n\nCo-authored-by: Cauê Marcondes
<55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1","v8.17.5"],"title":"[APM]
Fix entry item in waterfall shouldn't be
orphan","number":214700,"url":"https://github.com/elastic/kibana/pull/214700","mergeCommit":{"message":"[APM]
Fix entry item in waterfall shouldn't be orphan (#214700)\n\n##
Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry
waterfall transaction is\ntreated as an orphan, causing it to reparent
itself and be duplicated\nmultiple
times.\n\n---------\n\nCo-authored-by: Cauê Marcondes
<55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214928","number":214928,"state":"MERGED","mergeCommit":{"sha":"a0aebf185976baa6b9a11549876b16e5c752d95a","message":"[9.0]
[APM] Fix entry item in waterfall shouldn't be orphan (#214700)
(#214928)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [[APM] Fix entry item in waterfall shouldn't be
orphan\n(#214700)](https://github.com/elastic/kibana/pull/214700)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>"}},{"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/214700","number":214700,"mergeCommit":{"message":"[APM]
Fix entry item in waterfall shouldn't be orphan (#214700)\n\n##
Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry
waterfall transaction is\ntreated as an orphan, causing it to reparent
itself and be duplicated\nmultiple
times.\n\n---------\n\nCo-authored-by: Cauê Marcondes
<55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214927","number":214927,"state":"MERGED","mergeCommit":{"sha":"ccc2c36864ea68a4823c2239b39eb08e4d636ee2","message":"[8.x]
[APM] Fix entry item in waterfall shouldn't be orphan (#214700)
(#214927)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[APM] Fix entry item in waterfall shouldn't be
orphan\n(#214700)](https://github.com/elastic/kibana/pull/214700)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Sergi Romeu
<sergi.romeu@elastic.co>"}},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-01 09:43:39 +01:00
Drew Tate
3f3e5dd1c5
[8.18] [ES|QL] Hide "not" operators from suggestions menu (#216355) (#216548) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ES|QL] Hide "not" operators from suggestions menu
(#216355)](https://github.com/elastic/kibana/pull/216355)

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

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

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T19:25:08Z","message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin https://github.com/elastic/kibana/pull/205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL]
Hide \"not\" operators from suggestions
menu","number":216355,"url":"https://github.com/elastic/kibana/pull/216355","mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin https://github.com/elastic/kibana/pull/205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216355","number":216355,"mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin https://github.com/elastic/kibana/pull/205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216533","number":216533,"state":"OPEN"}]}]
BACKPORT-->
 2025-04-01 07:37:02 +02:00
Kibana Machine
4d99120a39
[8.18] [Controls] Fix control styles and invalid selection icon for Borealis (#213851) (#216567) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Controls] Fix control styles and invalid selection icon for Borealis
(#213851)](https://github.com/elastic/kibana/pull/213851)

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

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

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T00:04:43Z","message":"[Controls]
Fix control styles and invalid selection icon for Borealis
(#213851)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210614.\nCloses
https://github.com/elastic/kibana/issues/210615.\nCloses
https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up
to the Borealis updates to fix controls\ncolors/styles. This also fixes
the text color of the range slider number\ninputs to match the invalid
state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5
54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n####
Dark mode\n![Screenshot 2025-03-10 at 5
33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n####
Options List control with selection that results in no
data\n\n![Screenshot 2025-03-10 at 5
49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n####
Range Slider control with valid selection that results in no
data\n![Screenshot 2025-03-10 at 5
49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n####
Range Slider control with invalid selection\n![Screenshot 2025-03-10 at
5
48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] 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":"96598fc01956c0762ac50d8636c3e78ae5735863","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Platform-Design","Feature:Dashboard","Team:Presentation","loe:small","release_note:skip","impact:medium","backport:version","EUI
Visual
Refresh","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Controls] Fix
control styles and invalid selection icon for
Borealis","number":213851,"url":"https://github.com/elastic/kibana/pull/213851","mergeCommit":{"message":"[Controls]
Fix control styles and invalid selection icon for Borealis
(#213851)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210614.\nCloses
https://github.com/elastic/kibana/issues/210615.\nCloses
https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up
to the Borealis updates to fix controls\ncolors/styles. This also fixes
the text color of the range slider number\ninputs to match the invalid
state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5
54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n####
Dark mode\n![Screenshot 2025-03-10 at 5
33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n####
Options List control with selection that results in no
data\n\n![Screenshot 2025-03-10 at 5
49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n####
Range Slider control with valid selection that results in no
data\n![Screenshot 2025-03-10 at 5
49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n####
Range Slider control with invalid selection\n![Screenshot 2025-03-10 at
5
48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] 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":"96598fc01956c0762ac50d8636c3e78ae5735863"}},"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/213851","number":213851,"mergeCommit":{"message":"[Controls]
Fix control styles and invalid selection icon for Borealis
(#213851)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/210614.\nCloses
https://github.com/elastic/kibana/issues/210615.\nCloses
https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up
to the Borealis updates to fix controls\ncolors/styles. This also fixes
the text color of the range slider number\ninputs to match the invalid
state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5
54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n####
Dark mode\n![Screenshot 2025-03-10 at 5
33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n####
Options List control with selection that results in no
data\n\n![Screenshot 2025-03-10 at 5
49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n####
Range Slider control with valid selection that results in no
data\n![Screenshot 2025-03-10 at 5
49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n####
Range Slider control with invalid selection\n![Screenshot 2025-03-10 at
5
48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] 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":"96598fc01956c0762ac50d8636c3e78ae5735863"}},{"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: Catherine Liu <catherine.liu@elastic.co>
 2025-04-01 02:50:16 +01:00
Kibana Machine
f4ea86120f
[8.18] Update dependency @types/diff to ^7.0.2 (main) (#216427) (#216564) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Update dependency @types/diff to ^7.0.2 (main)
(#216427)](https://github.com/elastic/kibana/pull/216427)

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

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

<!--BACKPORT
[{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-31T22:16:59Z","message":"Update
dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n|
devDependencies | patch | [`^7.0.1`
->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2)
|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At
any time (no schedule defined),\nAutomerge - At any time (no schedule
defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes
conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**:
Close this PR and you won't be reminded about this
update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR,
check\nthis box\n\n---\n\nThis PR has been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"Update
dependency @types/diff to ^7.0.2
(main)","number":216427,"url":"https://github.com/elastic/kibana/pull/216427","mergeCommit":{"message":"Update
dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n|
devDependencies | patch | [`^7.0.1`
->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2)
|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At
any time (no schedule defined),\nAutomerge - At any time (no schedule
defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes
conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**:
Close this PR and you won't be reminded about this
update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR,
check\nthis box\n\n---\n\nThis PR has been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535"}},"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/216427","number":216427,"mergeCommit":{"message":"Update
dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains
the following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n|
devDependencies | patch | [`^7.0.1`
->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2)
|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At
any time (no schedule defined),\nAutomerge - At any time (no schedule
defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes
conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**:
Close this PR and you won't be reminded about this
update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR,
check\nthis box\n\n---\n\nThis PR has been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-01 01:45:29 +01:00
Kibana Machine
f62aed6daf
[8.18] Update dependency lru-cache to ^11.1.0 (main) (#216517) (#216554) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Update dependency lru-cache to ^11.1.0 (main)
(#216517)](https://github.com/elastic/kibana/pull/216517)

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

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

<!--BACKPORT
[{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-31T21:58:09Z","message":"Update
dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[lru-cache](https://redirect.github.com/isaacs/node-lru-cache)
|\ndependencies | minor | [`^11.0.2`
->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>isaacs/node-lru-cache
(lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:all-open","v9.1.0"],"title":"Update
dependency lru-cache to ^11.1.0
(main)","number":216517,"url":"https://github.com/elastic/kibana/pull/216517","mergeCommit":{"message":"Update
dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[lru-cache](https://redirect.github.com/isaacs/node-lru-cache)
|\ndependencies | minor | [`^11.0.2`
->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>isaacs/node-lru-cache
(lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6"}},"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/216517","number":216517,"mergeCommit":{"message":"Update
dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the
following updates:\n\n| Package | Type | Update | Change
|\n|---|---|---|---|\n|
[lru-cache](https://redirect.github.com/isaacs/node-lru-cache)
|\ndependencies | minor | [`^11.0.2`
->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0)
|\n\n---\n\n### Release
Notes\n\n<details>\n<summary>isaacs/node-lru-cache
(lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n</details>\n\n---\n\n###
Configuration\n\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦
**Automerge**: Disabled by config. Please merge this manually once
you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted,
or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR
and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If
you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has
been generated by
[Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by:
elastic-renovate-prod[bot]
<174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6"}}]}]
BACKPORT-->

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
 2025-04-01 00:52:24 +01:00
seanrathier
912d79089c
[8.18] [Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239) (#216547) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Cloud Security] Hide agentless traffic filtering callout in
Serverless (#216239)](https://github.com/elastic/kibana/pull/216239)

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

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

<!--BACKPORT
[{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-03-31T15:04:28Z","message":"[Cloud
Security] Hide agentless traffic filtering callout in Serverless
(#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76","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:Cloud
Security","backport:prev-minor","v9.1.0","backport:8.18"],"title":"[Cloud
Security] Hide agentless traffic filtering callout in
Serverless","number":216239,"url":"https://github.com/elastic/kibana/pull/216239","mergeCommit":{"message":"[Cloud
Security] Hide agentless traffic filtering callout in Serverless
(#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216496","number":216496,"state":"MERGED","mergeCommit":{"sha":"bb3ac40a5cf5cb62248f8ae25562064af8ea3330","message":"[9.0]
[Cloud Security] Hide agentless traffic filtering callout in Serverless
(#216239) (#216496)\n\n# Backport\n\nThis will backport the following
commits from `main` to `9.0`:\n- [[Cloud Security] Hide agentless
traffic filtering callout in\nServerless
(#216239)](https://github.com/elastic/kibana/pull/216239)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
seanrathier
<sean.rathier@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216239","number":216239,"mergeCommit":{"message":"[Cloud
Security] Hide agentless traffic filtering callout in Serverless
(#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}}]}]
BACKPORT-->
 2025-03-31 23:56:02 +01:00
Kibana Machine
b558d4df69
[8.18] [embeddable] fix race condition in useBatchedPublishingSubjects (#216399) (#216525) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[embeddable] fix race condition in useBatchedPublishingSubjects
(#216399)](https://github.com/elastic/kibana/pull/216399)

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

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

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T17:21:56Z","message":"[embeddable]
fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses
https://github.com/elastic/kibana/issues/214176
and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from
chrome 134 to 135 in functional
test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed
a race\ncondition in `useBatchedPublishingSubjects` where batched
observables\ncould emit new values before `useEffect` sets up the
subscription. This\nPR resolves this issue by setting up subscription in
useRef, which has\nno timing delays.\n\nIn chrome 134,
`useBatchedPublishingSubjects` `useEffect` gets called\n(setting up
subscription) before lens embeddable emits any changes to\nbatched
observables.\n<img width=\"300\"
alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn
chrome 135, `useBatchedPublishingSubjects` `useEffect` gets
called\nafter lens embeddable emits changes to batched observables. This
causes\nthe lens embeddable to not render since the
`LensEmbeddableComponent`\nhas a stale value for
`expressionParams`.\n<img width=\"300\"
alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1","v8.17.5","v8.16.7"],"title":"[embeddable]
fix race condition in
useBatchedPublishingSubjects","number":216399,"url":"https://github.com/elastic/kibana/pull/216399","mergeCommit":{"message":"[embeddable]
fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses
https://github.com/elastic/kibana/issues/214176
and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from
chrome 134 to 135 in functional
test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed
a race\ncondition in `useBatchedPublishingSubjects` where batched
observables\ncould emit new values before `useEffect` sets up the
subscription. This\nPR resolves this issue by setting up subscription in
useRef, which has\nno timing delays.\n\nIn chrome 134,
`useBatchedPublishingSubjects` `useEffect` gets called\n(setting up
subscription) before lens embeddable emits any changes to\nbatched
observables.\n<img width=\"300\"
alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn
chrome 135, `useBatchedPublishingSubjects` `useEffect` gets
called\nafter lens embeddable emits changes to batched observables. This
causes\nthe lens embeddable to not render since the
`LensEmbeddableComponent`\nhas a stale value for
`expressionParams`.\n<img width=\"300\"
alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0","8.17","8.16"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216399","number":216399,"mergeCommit":{"message":"[embeddable]
fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses
https://github.com/elastic/kibana/issues/214176
and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from
chrome 134 to 135 in functional
test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed
a race\ncondition in `useBatchedPublishingSubjects` where batched
observables\ncould emit new values before `useEffect` sets up the
subscription. This\nPR resolves this issue by setting up subscription in
useRef, which has\nno timing delays.\n\nIn chrome 134,
`useBatchedPublishingSubjects` `useEffect` gets called\n(setting up
subscription) before lens embeddable emits any changes to\nbatched
observables.\n<img width=\"300\"
alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn
chrome 135, `useBatchedPublishingSubjects` `useEffect` gets
called\nafter lens embeddable emits changes to batched observables. This
causes\nthe lens embeddable to not render since the
`LensEmbeddableComponent`\nhas a stale value for
`expressionParams`.\n<img width=\"300\"
alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b"}},{"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"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
 2025-03-31 20:36:32 +01:00
Kibana Machine
44261a9338
[8.18] Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283) (#216480) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Fix unenroll inactive agent tasks if first set of agents returned is
equal to UNENROLLMENT_BATCH_SIZE
(#216283)](https://github.com/elastic/kibana/pull/216283)

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

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

<!--BACKPORT [{"author":{"name":"Mario Rodriguez
Molins","email":"mario.rodriguez@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T13:55:14Z","message":"Fix
unenroll inactive agent tasks if first set of agents returned is equal
to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the
unenrollment inactive agent task to be able to unenroll some\nagents
when the number of agents returned by the first\n`getAgentsByKuery`
trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Fix
unenroll inactive agent tasks if first set of agents returned is equal
to
UNENROLLMENT_BATCH_SIZE","number":216283,"url":"https://github.com/elastic/kibana/pull/216283","mergeCommit":{"message":"Fix
unenroll inactive agent tasks if first set of agents returned is equal
to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the
unenrollment inactive agent task to be able to unenroll some\nagents
when the number of agents returned by the first\n`getAgentsByKuery`
trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d"}},"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/216283","number":216283,"mergeCommit":{"message":"Fix
unenroll inactive agent tasks if first set of agents returned is equal
to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the
unenrollment inactive agent task to be able to unenroll some\nagents
when the number of agents returned by the first\n`getAgentsByKuery`
trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d"}}]}]
BACKPORT-->

Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>
 2025-03-31 16:54:42 +01:00
natasha-moore-elastic
54c16eb883
[8.18] [DOCS] Deletes asciidoc Osquery API docs (#216269) (#216431) 
{defaultPrDescription}

<!--BACKPORT {commits} BACKPORT-->
 2025-03-31 11:22:13 -04:00
Kibana Machine
b1c52174e5
[8.18] [APM][OTel] Service inventory icons should be visible if the agentName is returned (#216220) (#216466) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM][OTel] Service inventory icons should be visible if the
`agentName` is returned
(#216220)](https://github.com/elastic/kibana/pull/216220)

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

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

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T13:07:17Z","message":"[APM][OTel]
Service inventory icons should be visible if the `agentName` is returned
(#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue
with the service icons overridden by the merge\nof the service
stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of
refreshing /\nchanging the time range, etc. to reproduce\nThe way to
verify the fix is to check the service overview - every\nservice that
has an icon there should have an icon in the
service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel]
Service inventory icons should be visible if the `agentName` is
returned","number":216220,"url":"https://github.com/elastic/kibana/pull/216220","mergeCommit":{"message":"[APM][OTel]
Service inventory icons should be visible if the `agentName` is returned
(#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue
with the service icons overridden by the merge\nof the service
stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of
refreshing /\nchanging the time range, etc. to reproduce\nThe way to
verify the fix is to check the service overview - every\nservice that
has an icon there should have an icon in the
service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}},"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/216220","number":216220,"mergeCommit":{"message":"[APM][OTel]
Service inventory icons should be visible if the `agentName` is returned
(#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue
with the service icons overridden by the merge\nof the service
stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of
refreshing /\nchanging the time range, etc. to reproduce\nThe way to
verify the fix is to check the service overview - every\nservice that
has an icon there should have an icon in the
service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}}]}]
BACKPORT-->

Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
 2025-03-31 16:00:15 +01:00
Aleh Zasypkin
09be537547
[8.18] chore(deps): upgrade vega from 5.31.0 to 5.33.0 (#216284) (#216353) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [chore(deps): upgrade `vega` from `5.31.0` to `5.33.0`
(#216284)](https://github.com/elastic/kibana/pull/216284)

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

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

<!--BACKPORT [{"author":{"name":"Aleh
Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-03-28T15:07:14Z","message":"chore(deps):
upgrade `vega` from `5.31.0` to `5.33.0` (#216284)\n\n##
Summary\n\nUpgrade `vega` from `5.31.0` to `5.33.0`:\n*
https://github.com/vega/vega/releases/tag/v5.32.0\n*
https://github.com/vega/vega/releases/tag/v5.33.0","sha":"69bd83e69e933999402c7ba28260f14a4b3dc3bf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","dependencies","backport:all-open","v9.1.0"],"title":"chore(deps):
upgrade `vega` from `5.31.0` to
`5.33.0`","number":216284,"url":"https://github.com/elastic/kibana/pull/216284","mergeCommit":{"message":"chore(deps):
upgrade `vega` from `5.31.0` to `5.33.0` (#216284)\n\n##
Summary\n\nUpgrade `vega` from `5.31.0` to `5.33.0`:\n*
https://github.com/vega/vega/releases/tag/v5.32.0\n*
https://github.com/vega/vega/releases/tag/v5.33.0","sha":"69bd83e69e933999402c7ba28260f14a4b3dc3bf"}},"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/216284","number":216284,"mergeCommit":{"message":"chore(deps):
upgrade `vega` from `5.31.0` to `5.33.0` (#216284)\n\n##
Summary\n\nUpgrade `vega` from `5.31.0` to `5.33.0`:\n*
https://github.com/vega/vega/releases/tag/v5.32.0\n*
https://github.com/vega/vega/releases/tag/v5.33.0","sha":"69bd83e69e933999402c7ba28260f14a4b3dc3bf"}},{"url":"https://github.com/elastic/kibana/pull/216314","number":216314,"branch":"9.0","state":"OPEN"}]}]
BACKPORT-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2025-03-31 15:08:30 +01:00
Kibana Machine
ac1b5337e8
[8.18] [Response Ops][Cases] Makes find user action an internal endpoint (#216264) (#216442) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Response Ops][Cases] Makes find user action an internal endpoint
(#216264)](https://github.com/elastic/kibana/pull/216264)

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

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

<!--BACKPORT [{"author":{"name":"Julian
Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-31T10:47:01Z","message":"[Response
Ops][Cases] Makes find user action an internal endpoint (#216264)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/216261","sha":"d4318afbaadcfea577a11f50b27f132e652623ed","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"],"title":"[Response
Ops][Cases] Makes find user action an internal
endpoint","number":216264,"url":"https://github.com/elastic/kibana/pull/216264","mergeCommit":{"message":"[Response
Ops][Cases] Makes find user action an internal endpoint (#216264)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/216261","sha":"d4318afbaadcfea577a11f50b27f132e652623ed"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216264","number":216264,"mergeCommit":{"message":"[Response
Ops][Cases] Makes find user action an internal endpoint (#216264)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/216261","sha":"d4318afbaadcfea577a11f50b27f132e652623ed"}}]}]
BACKPORT-->

Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
 2025-03-31 14:15:24 +01:00
Khristinin Nikita
558d11af76
[8.18] Clear gap filters after unmounting component (#211588) (#216133) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Clear gap filters after unmounting component
(#211588)](https://github.com/elastic/kibana/pull/211588)

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

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

<!--BACKPORT [{"author":{"name":"Khristinin
Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T09:22:57Z","message":"Clear
gap filters after unmounting component (#211588)\n\n## When we move out
monitoring tab we reset filters to show only rule\nwith
gaps\n\n\n\n\nhttps://github.com/user-attachments/assets/d86b248e-62e1-41c7-9873-8140a8d86b81\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"24d948db43cd55e4a25836ba3d227aaffbd08891","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","backport:prev-minor","backport:version","v8.18.0","v9.1.0"],"title":"Clear
gap filters after unmounting
component","number":211588,"url":"https://github.com/elastic/kibana/pull/211588","mergeCommit":{"message":"Clear
gap filters after unmounting component (#211588)\n\n## When we move out
monitoring tab we reset filters to show only rule\nwith
gaps\n\n\n\n\nhttps://github.com/user-attachments/assets/d86b248e-62e1-41c7-9873-8140a8d86b81\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"24d948db43cd55e4a25836ba3d227aaffbd08891"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212020","number":212020,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211588","number":211588,"mergeCommit":{"message":"Clear
gap filters after unmounting component (#211588)\n\n## When we move out
monitoring tab we reset filters to show only rule\nwith
gaps\n\n\n\n\nhttps://github.com/user-attachments/assets/d86b248e-62e1-41c7-9873-8140a8d86b81\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"24d948db43cd55e4a25836ba3d227aaffbd08891"}},{"url":"https://github.com/elastic/kibana/pull/212021","number":212021,"branch":"9.0","state":"OPEN"}]}]
BACKPORT-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2025-03-31 08:01:25 +00:00
Kibana Machine
0316dab7a4
[8.18] [Fleet] disable unenroll action on agentless agents (#216299) (#216333) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Fleet] disable unenroll action on agentless agents
(#216299)](https://github.com/elastic/kibana/pull/216299)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T15:51:02Z","message":"[Fleet]
disable unenroll action on agentless agents (#216299)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll
agent action on agentless agents\n\n<img width=\"1124\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img
width=\"1126\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet]
disable unenroll action on agentless
agents","number":216299,"url":"https://github.com/elastic/kibana/pull/216299","mergeCommit":{"message":"[Fleet]
disable unenroll action on agentless agents (#216299)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll
agent action on agentless agents\n\n<img width=\"1124\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img
width=\"1126\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234"}},"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/216299","number":216299,"mergeCommit":{"message":"[Fleet]
disable unenroll action on agentless agents (#216299)\n\n##
Summary\n\nCloses
https://github.com/elastic/kibana/issues/209173\n\nDisable Unenroll
agent action on agentless agents\n\n<img width=\"1124\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/6603bac5-b0b1-4a20-8b16-f121bd69e969\"\n/>\n<img
width=\"1126\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e41bca5b-f73d-44bc-b095-9970a25f6322\"\n/>","sha":"6914495033b75d80af64a247768223547f501234"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2025-03-28 18:59:09 +01:00
Kibana Machine
15b5519963
[8.18] [Dataset Quality] Fix brittle test which was failing in the midnight job (#216260) (#216318) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Dataset Quality] Fix brittle test which was failing in the midnight
job (#216260)](https://github.com/elastic/kibana/pull/216260)

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

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

<!--BACKPORT [{"author":{"name":"Achyut
Jhunjhunwala","email":"achyut.jhunjhunwala@elastic.co"},"sourceCommit":{"committedDate":"2025-03-28T15:13:05Z","message":"[Dataset
Quality] Fix brittle test which was failing in the midnight job
(#216260)\n\nThis PR fixes a bug where the test would run at midnight
and due to the\nodd timing, the index which gets created is asserted for
a different\ndate than expected.\n\nWith this fix, we don't check the
complete index name now by replacing\nthe date assertion part with
startWith and endsWith
assertions.","sha":"0f0ee3a0b8be0182e136f4bb75765d469917ee3b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","backport:prev-major","Feature:Dataset
Health","v9.1.0","Team:Obs UX Logs"],"title":"[Dataset Quality] Fix
brittle test which was failing in the midnight
job","number":216260,"url":"https://github.com/elastic/kibana/pull/216260","mergeCommit":{"message":"[Dataset
Quality] Fix brittle test which was failing in the midnight job
(#216260)\n\nThis PR fixes a bug where the test would run at midnight
and due to the\nodd timing, the index which gets created is asserted for
a different\ndate than expected.\n\nWith this fix, we don't check the
complete index name now by replacing\nthe date assertion part with
startWith and endsWith
assertions.","sha":"0f0ee3a0b8be0182e136f4bb75765d469917ee3b"}},"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/216260","number":216260,"mergeCommit":{"message":"[Dataset
Quality] Fix brittle test which was failing in the midnight job
(#216260)\n\nThis PR fixes a bug where the test would run at midnight
and due to the\nodd timing, the index which gets created is asserted for
a different\ndate than expected.\n\nWith this fix, we don't check the
complete index name now by replacing\nthe date assertion part with
startWith and endsWith
assertions.","sha":"0f0ee3a0b8be0182e136f4bb75765d469917ee3b"}}]}]
BACKPORT-->

Co-authored-by: Achyut Jhunjhunwala <achyut.jhunjhunwala@elastic.co>
 2025-03-28 18:15:42 +01:00
Kibana Machine
24c65a5dcc
[8.18] [Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145) (#216280) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Response Ops][Flaky Tests] Remove duplicated click creating
connector (#216145)](https://github.com/elastic/kibana/pull/216145)

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

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

<!--BACKPORT [{"author":{"name":"Julian
Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T11:43:25Z","message":"[Response
Ops][Flaky Tests] Remove duplicated click creating connector
(#216145)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/202328\n\nThe test itself
wasn't failing but the setup was. The test failing does\nso because it's
the first one in the test suite. We are trying to click\non the flyout
save button twice one right after the other. What I think\nis happening
is that the first one manages to close the flyout before\nthe second
click gets the chance to trigger.\n\nAlso the image in CI is this where
we can see the flyout is closed\nalready but it's still trying to close
it\n\n![image](https://github.com/user-attachments/assets/c606f776-aab4-4884-94e2-a2c258a30546)","sha":"e16ba346e39df1843b45017137d4c894c357bb13","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"],"title":"[Response
Ops][Flaky Tests] Remove duplicated click creating
connector","number":216145,"url":"https://github.com/elastic/kibana/pull/216145","mergeCommit":{"message":"[Response
Ops][Flaky Tests] Remove duplicated click creating connector
(#216145)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/202328\n\nThe test itself
wasn't failing but the setup was. The test failing does\nso because it's
the first one in the test suite. We are trying to click\non the flyout
save button twice one right after the other. What I think\nis happening
is that the first one manages to close the flyout before\nthe second
click gets the chance to trigger.\n\nAlso the image in CI is this where
we can see the flyout is closed\nalready but it's still trying to close
it\n\n![image](https://github.com/user-attachments/assets/c606f776-aab4-4884-94e2-a2c258a30546)","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216145","number":216145,"mergeCommit":{"message":"[Response
Ops][Flaky Tests] Remove duplicated click creating connector
(#216145)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/202328\n\nThe test itself
wasn't failing but the setup was. The test failing does\nso because it's
the first one in the test suite. We are trying to click\non the flyout
save button twice one right after the other. What I think\nis happening
is that the first one manages to close the flyout before\nthe second
click gets the chance to trigger.\n\nAlso the image in CI is this where
we can see the flyout is closed\nalready but it's still trying to close
it\n\n![image](https://github.com/user-attachments/assets/c606f776-aab4-4884-94e2-a2c258a30546)","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}}]}]
BACKPORT-->

Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
 2025-03-28 15:09:38 +01:00
Kibana Machine
0bc14342fb
[8.18] [Security Solution][Entity Analytics][Bug]Adding code to get spaceId dynamically (#216063) (#216254) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution][Entity Analytics][Bug]Adding code to get spaceId
dynamically (#216063)](https://github.com/elastic/kibana/pull/216063)

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

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

<!--BACKPORT [{"author":{"name":"Abhishek
Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T06:59:27Z","message":"[Security
Solution][Entity Analytics][Bug]Adding code to get spaceId dynamically
(#216063)\n\n## Summary\n\nThe Risk Summary in the Entity Flyout was
displaying an incorrect risk\nscore due to the space name not being
accounted for in the risk score\nindex query.\n\nThis update ensures
that the namespace is properly considered while\nquerying the risk
score, providing accurate results across different\nspaces.\n\nScreen
recording :
\n\n\n\nhttps://github.com/user-attachments/assets/91df526c-1c22-4d53-aa0c-d74abb54920a\n\n\nTesting
Steps : \n1. Navigate to Entity Risk Score page.\n2. Add data in the
`default` space\n3. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n4. The Risk score in the Entities
table and the flyout should be same\n5. Create a new space\n6. Add data
in the new space\n7. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n8. The Risk score in the Entities
table and the flyout should be same\n\n\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [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":"ffb196f8e6f04db25b2b9ce12213d3cb8267173f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Entity
Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution][Entity Analytics][Bug]Adding code to get spaceId
dynamically","number":216063,"url":"https://github.com/elastic/kibana/pull/216063","mergeCommit":{"message":"[Security
Solution][Entity Analytics][Bug]Adding code to get spaceId dynamically
(#216063)\n\n## Summary\n\nThe Risk Summary in the Entity Flyout was
displaying an incorrect risk\nscore due to the space name not being
accounted for in the risk score\nindex query.\n\nThis update ensures
that the namespace is properly considered while\nquerying the risk
score, providing accurate results across different\nspaces.\n\nScreen
recording :
\n\n\n\nhttps://github.com/user-attachments/assets/91df526c-1c22-4d53-aa0c-d74abb54920a\n\n\nTesting
Steps : \n1. Navigate to Entity Risk Score page.\n2. Add data in the
`default` space\n3. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n4. The Risk score in the Entities
table and the flyout should be same\n5. Create a new space\n6. Add data
in the new space\n7. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n8. The Risk score in the Entities
table and the flyout should be same\n\n\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [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":"ffb196f8e6f04db25b2b9ce12213d3cb8267173f"}},"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/216063","number":216063,"mergeCommit":{"message":"[Security
Solution][Entity Analytics][Bug]Adding code to get spaceId dynamically
(#216063)\n\n## Summary\n\nThe Risk Summary in the Entity Flyout was
displaying an incorrect risk\nscore due to the space name not being
accounted for in the risk score\nindex query.\n\nThis update ensures
that the namespace is properly considered while\nquerying the risk
score, providing accurate results across different\nspaces.\n\nScreen
recording :
\n\n\n\nhttps://github.com/user-attachments/assets/91df526c-1c22-4d53-aa0c-d74abb54920a\n\n\nTesting
Steps : \n1. Navigate to Entity Risk Score page.\n2. Add data in the
`default` space\n3. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n4. The Risk score in the Entities
table and the flyout should be same\n5. Create a new space\n6. Add data
in the new space\n7. Check for Risk score in the Risk Summary for any of
the entities in\nthe Entity Flyout.\n8. The Risk score in the Entities
table and the flyout should be same\n\n\n\n### Checklist\n\nCheck the PR
satisfies following conditions. \n\nReviewers should verify this PR
satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [x] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [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":"ffb196f8e6f04db25b2b9ce12213d3cb8267173f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com>
 2025-03-28 11:00:07 +02:00
Efe Gürkan YALAMAN
3af1098ba3
[8.18] [Synonyms] Update Synonyms Text and Enable (#215618) (#215833) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Efe Gürkan
YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T23:30:55Z","message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Synonyms]
Update Synonyms Text and
Enable","number":215618,"url":"https://github.com/elastic/kibana/pull/215618","mergeCommit":{"message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/215814","number":215814,"state":"MERGED","mergeCommit":{"sha":"5f3a62c004a3ea2a4879b9bc3f82e3ae5f02f4b0","message":"[9.0]
[Synonyms] Update Synonyms Text and Enable (#215618) (#215814)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[Synonyms] Update Synonyms Text and
Enable\n(#215618)](https://github.com/elastic/kibana/pull/215618)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Efe Gürkan YALAMAN
<efeguerkan.yalaman@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215618","number":215618,"mergeCommit":{"message":"[Synonyms]
Update Synonyms Text and Enable (#215618)\n\n## Summary\n\nText in
various places updated.\nAdded some telemetry that was decided.\nSmall
visual changes on empty prompt page.\nAdded a new example in a
collapsible accordion.\nAlso enables the synonyms plugin by
default.\n\n<img width=\"1637\" alt=\"Screenshot 2025-03-24 at 10 36
26\"\nsrc=\"https://github.com/user-attachments/assets/b02ef4a7-a18f-44b5-a845-d2566102e8ea\"\n/>\n<img
width=\"1627\" alt=\"Screenshot 2025-03-24 at 10 36
40\"\nsrc=\"https://github.com/user-attachments/assets/f7ea1c5e-d82e-497a-b215-5eab7190f041\"\n/>\n<img
width=\"1634\" alt=\"Screenshot 2025-03-24 at 10 36
52\"\nsrc=\"https://github.com/user-attachments/assets/d410bcc1-c075-4b5a-bcb7-11f97c64ffb9\"\n/>\n<img
width=\"825\" alt=\"Screenshot 2025-03-24 at 10 37
00\"\nsrc=\"https://github.com/user-attachments/assets/8a9e7567-5dbd-4238-8f8b-297b78a4dcac\"\n/>\n\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"01a4ff72e73c1d31b0aeed76f3a9ec4b5393deb8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Kathleen DeRusso <kathleen.derusso@elastic.co>
Co-authored-by: Samiul Monir <samiul.monir@elastic.co>
 2025-03-28 02:42:15 +02:00
Kibana Machine
a002e9b3c9
[8.18] fix: [Analytics:Visualize Library page]Incorrect aria label used for Tags list (#215658) (#216187) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [fix: [Analytics:Visualize Library page]Incorrect aria label used for
Tags list (#215658)](https://github.com/elastic/kibana/pull/215658)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-27T14:14:11Z","message":"fix:
[Analytics:Visualize Library page]Incorrect aria label used for Tags
list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements
has to be clear and descriptive for user to know what\nelement is
currently active, how to interact with it. Same with
aria\nlabels.\nEspecially for the users using assistive technology.\n\n#
Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed
translations\n\n\n# Screen: \n<img width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Analytics:Visualize Library page]Incorrect aria label used for Tags
list","number":215658,"url":"https://github.com/elastic/kibana/pull/215658","mergeCommit":{"message":"fix:
[Analytics:Visualize Library page]Incorrect aria label used for Tags
list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements
has to be clear and descriptive for user to know what\nelement is
currently active, how to interact with it. Same with
aria\nlabels.\nEspecially for the users using assistive technology.\n\n#
Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed
translations\n\n\n# Screen: \n<img width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e"}},"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/215658","number":215658,"mergeCommit":{"message":"fix:
[Analytics:Visualize Library page]Incorrect aria label used for Tags
list (#215658)\n\nCloses: #215004\n\n# Description\nNames of elements
has to be clear and descriptive for user to know what\nelement is
currently active, how to interact with it. Same with
aria\nlabels.\nEspecially for the users using assistive technology.\n\n#
Changes made? \n1. Fixed mentioned a11y concerns\n2. Fixed
translations\n\n\n# Screen: \n<img width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d5b1b404-5a4a-4499-8a1c-59528c866bf9\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"418e328b9d25fde0743fa569c5b0c8a41669319e"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
 2025-03-27 18:56:59 +02:00
Kibana Machine
6016065bfd
[8.18] fix: [Analytics:Maps page]Duplication of elements announcement (#215684) (#216186) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [fix: [Analytics:Maps page]Duplication of elements announcement
(#215684)](https://github.com/elastic/kibana/pull/215684)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-27T14:13:56Z","message":"fix:
[Analytics:Maps page]Duplication of elements announcement
(#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to
hear the same information once upon reaching\nelement.\nEspecially for
the users using assistive technology.\n\n### Changes made: \n\n1.
Partially fix #215647. Only list page related part! Text
for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img
width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix:
[Analytics:Maps page]Duplication of elements
announcement","number":215684,"url":"https://github.com/elastic/kibana/pull/215684","mergeCommit":{"message":"fix:
[Analytics:Maps page]Duplication of elements announcement
(#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to
hear the same information once upon reaching\nelement.\nEspecially for
the users using assistive technology.\n\n### Changes made: \n\n1.
Partially fix #215647. Only list page related part! Text
for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img
width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846"}},"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/215684","number":215684,"mergeCommit":{"message":"fix:
[Analytics:Maps page]Duplication of elements announcement
(#215684)\n\nPart of: #215647\n\n## Summary\n\nIt is enough for user to
hear the same information once upon reaching\nelement.\nEspecially for
the users using assistive technology.\n\n### Changes made: \n\n1.
Partially fix #215647. Only list page related part! Text
for\n'aria-label' attribute were updated\n\n### Screen:\n\n<img
width=\"1408\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/be4f6166-238e-484e-bbc2-cbb6bf5de162\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ef5a2c9adba43f849eda3a3134371461fee7c846"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
 2025-03-27 18:19:04 +02:00
Nick Partridge
306c26eff7
[8.18] [Lens][Datatable] Fix color by value for Last value array mode (#213917) (#216118) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Lens][Datatable] Fix color by value for Last value array mode
(#213917)](https://github.com/elastic/kibana/pull/213917)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T09:09:03Z","message":"[Lens][Datatable]
Fix color by value for Last value array mode (#213917)\n\n##
Summary\n\nFixes the table side of #188263 \n\nThe [fix used
for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has
been\ngeneralized and re-used for the datatable
visualization.\n\n\n![color_by_value_table](https://github.com/user-attachments/assets/b347dba2-24d7-4233-8c0c-3236f5212f35)\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"0b9df094d1770065f79c05272a41175396caa27b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","v9.0.0","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Lens][Datatable]
Fix color by value for Last value array
mode","number":213917,"url":"https://github.com/elastic/kibana/pull/213917","mergeCommit":{"message":"[Lens][Datatable]
Fix color by value for Last value array mode (#213917)\n\n##
Summary\n\nFixes the table side of #188263 \n\nThe [fix used
for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has
been\ngeneralized and re-used for the datatable
visualization.\n\n\n![color_by_value_table](https://github.com/user-attachments/assets/b347dba2-24d7-4233-8c0c-3236f5212f35)\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"0b9df094d1770065f79c05272a41175396caa27b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214919","number":214919,"state":"MERGED","mergeCommit":{"sha":"ce776eca54a3b56d07d2404486162d5050098d26","message":"[9.0]
[Lens][Datatable] Fix color by value for Last value array mode (#213917)
(#214919)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [[Lens][Datatable] Fix color by value for Last value
array
mode\n(#213917)](https://github.com/elastic/kibana/pull/213917)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Marco Liberati
<dej611@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213917","number":213917,"mergeCommit":{"message":"[Lens][Datatable]
Fix color by value for Last value array mode (#213917)\n\n##
Summary\n\nFixes the table side of #188263 \n\nThe [fix used
for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has
been\ngeneralized and re-used for the datatable
visualization.\n\n\n![color_by_value_table](https://github.com/user-attachments/assets/b347dba2-24d7-4233-8c0c-3236f5212f35)\n\n\n###
Checklist\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"0b9df094d1770065f79c05272a41175396caa27b"}},{"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"}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2025-03-27 15:59:29 +01:00