github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity
83047 commits 431 branches 496 tags 22 GiB
Commit graph

819 commits

Author SHA1 Message Date
Sergi Massaneda
c3cdc7cd56
[8.18] [Security Solution] fix security dashboards timerange issue (#218825) (#218930) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] fix security dashboards timerange issue
(#218825)](https://github.com/elastic/kibana/pull/218825)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-04-22T17:49:32Z","message":"[Security
Solution] fix security dashboards timerange issue (#218825)\n\n##
Summary\n\nFix for
https://github.com/elastic/kibana/issues/211984\n\nSends only the
`timeRange` properties the dashboard API needs, removing\n`fromStr` and
`toStr` that cause the dashboard to crash\n\n###
Screenshots\n\nbefore\n\n![before](5db42dd6-8095-4f56-9a1f-b9261d01fbb1)\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"0e3fab9d0df0c9e165876d33a5f0541b84ca8d83","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting:Explore","backport:prev-major","v9.1.0"],"title":"[Security
Solution] fix security dashboards timerange
issue","number":218825,"url":"https://github.com/elastic/kibana/pull/218825","mergeCommit":{"message":"[Security
Solution] fix security dashboards timerange issue (#218825)\n\n##
Summary\n\nFix for
https://github.com/elastic/kibana/issues/211984\n\nSends only the
`timeRange` properties the dashboard API needs, removing\n`fromStr` and
`toStr` that cause the dashboard to crash\n\n###
Screenshots\n\nbefore\n\n![before](5db42dd6-8095-4f56-9a1f-b9261d01fbb1)\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"0e3fab9d0df0c9e165876d33a5f0541b84ca8d83"}},"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/218825","number":218825,"mergeCommit":{"message":"[Security
Solution] fix security dashboards timerange issue (#218825)\n\n##
Summary\n\nFix for
https://github.com/elastic/kibana/issues/211984\n\nSends only the
`timeRange` properties the dashboard API needs, removing\n`fromStr` and
`toStr` that cause the dashboard to crash\n\n###
Screenshots\n\nbefore\n\n![before](5db42dd6-8095-4f56-9a1f-b9261d01fbb1)\n\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"0e3fab9d0df0c9e165876d33a5f0541b84ca8d83"}},{"url":"https://github.com/elastic/kibana/pull/218871","number":218871,"branch":"8.19","state":"OPEN"}]}]
BACKPORT-->
 2025-04-23 13:31:27 +02:00
Kibana Machine
2ae62a46c4
[8.18] [Infra] Check ML permissions before requesting ML data (#218069) (#218228) 
# Backport

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

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

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

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

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
Co-authored-by: Irene Blanco <irene.blanco@elastic.co>
 2025-04-23 11:37:16 +02:00
Agustina Nahir Ruidiaz
91c373eb49
[8.18] [Security Solution][Onboarding] Adding telemetry to video selectors (#217280) (#218831) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution][Onboarding] Adding telemetry to video selectors
(#217280)](https://github.com/elastic/kibana/pull/217280)

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

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

<!--BACKPORT [{"author":{"name":"Agustina Nahir
Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T13:42:30Z","message":"[Security
Solution][Onboarding] Adding telemetry to video selectors
(#217280)\n\n## Summary\n\nNew event created for the video selectors
inside rules, dashboards and\nalerts cards.\n\n```\nexport interface
OnboardingHubSelectorCardClickedParams {\n originStepId: string;\n
selectorId: string;\n}\n```\n\nTo verify:\n\nAdd these lines to
kibana.dev.yml\n\n```\nlogging.browser.root.level:
debug\ntelemetry.optIn: true\n```\n\n1. In the onboarding hub, expand
the rules card\n2. It should log `Report event \"Onboarding Hub Step
Selector
Clicked\"`.\n\n\nhttps://github.com/user-attachments/assets/c1b1084e-4917-4412-93ed-984a74b6b6b4\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\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\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f00f83715c8787033c7904c0794350f847900bfe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","v9.0.0","Team:Threat
Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution][Onboarding] Adding telemetry to video
selectors","number":217280,"url":"https://github.com/elastic/kibana/pull/217280","mergeCommit":{"message":"[Security
Solution][Onboarding] Adding telemetry to video selectors
(#217280)\n\n## Summary\n\nNew event created for the video selectors
inside rules, dashboards and\nalerts cards.\n\n```\nexport interface
OnboardingHubSelectorCardClickedParams {\n originStepId: string;\n
selectorId: string;\n}\n```\n\nTo verify:\n\nAdd these lines to
kibana.dev.yml\n\n```\nlogging.browser.root.level:
debug\ntelemetry.optIn: true\n```\n\n1. In the onboarding hub, expand
the rules card\n2. It should log `Report event \"Onboarding Hub Step
Selector
Clicked\"`.\n\n\nhttps://github.com/user-attachments/assets/c1b1084e-4917-4412-93ed-984a74b6b6b4\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\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\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f00f83715c8787033c7904c0794350f847900bfe"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218829","number":218829,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217280","number":217280,"mergeCommit":{"message":"[Security
Solution][Onboarding] Adding telemetry to video selectors
(#217280)\n\n## Summary\n\nNew event created for the video selectors
inside rules, dashboards and\nalerts cards.\n\n```\nexport interface
OnboardingHubSelectorCardClickedParams {\n originStepId: string;\n
selectorId: string;\n}\n```\n\nTo verify:\n\nAdd these lines to
kibana.dev.yml\n\n```\nlogging.browser.root.level:
debug\ntelemetry.optIn: true\n```\n\n1. In the onboarding hub, expand
the rules card\n2. It should log `Report event \"Onboarding Hub Step
Selector
Clicked\"`.\n\n\nhttps://github.com/user-attachments/assets/c1b1084e-4917-4412-93ed-984a74b6b6b4\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\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\n---------\n\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f00f83715c8787033c7904c0794350f847900bfe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/218830","number":218830,"branch":"8.19","state":"OPEN"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-23 10:43:11 +02:00
Kibana Machine
5642748856
[8.18] [ObsUX][Infra] Filter out null values from sourceDataStreams (#218772) (#218798) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUX][Infra] Filter out null values from `sourceDataStreams`
(#218772)](https://github.com/elastic/kibana/pull/218772)

<!--- 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-22T10:37:09Z","message":"[ObsUX][Infra]
Filter out null values from `sourceDataStreams` (#218772)\n\n##
Summary\n\nPart of #213045\n\nThis PR fixes an issue when the
`observability:entityCentricExperience`\nflag is enabled.\nBy some
reason, we may get null values in `sourceDataStreams` and when\nwe try
to validate it with the zod schema, it
breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[ObsUX][Infra]
Filter out null values from
`sourceDataStreams`","number":218772,"url":"https://github.com/elastic/kibana/pull/218772","mergeCommit":{"message":"[ObsUX][Infra]
Filter out null values from `sourceDataStreams` (#218772)\n\n##
Summary\n\nPart of #213045\n\nThis PR fixes an issue when the
`observability:entityCentricExperience`\nflag is enabled.\nBy some
reason, we may get null values in `sourceDataStreams` and when\nwe try
to validate it with the zod schema, it
breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218772","number":218772,"mergeCommit":{"message":"[ObsUX][Infra]
Filter out null values from `sourceDataStreams` (#218772)\n\n##
Summary\n\nPart of #213045\n\nThis PR fixes an issue when the
`observability:entityCentricExperience`\nflag is enabled.\nBy some
reason, we may get null values in `sourceDataStreams` and when\nwe try
to validate it with the zod schema, it
breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-22 14:46:55 +02:00
Kibana Machine
317dbd86c8
[8.18] [Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426) (#218775) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Synthetics] When changing condition type of a monitor status rule
other conditions are not changed
(#216426)](https://github.com/elastic/kibana/pull/216426)

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-22T08:21:48Z","message":"[Synthetics]
When changing condition type of a monitor status rule other conditions
are not changed (#216426)\n\nThis PR closes #197786
.\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics]
When changing condition type of a monitor status rule other conditions
are not
changed","number":216426,"url":"https://github.com/elastic/kibana/pull/216426","mergeCommit":{"message":"[Synthetics]
When changing condition type of a monitor status rule other conditions
are not changed (#216426)\n\nThis PR closes #197786
.\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216426","number":216426,"mergeCommit":{"message":"[Synthetics]
When changing condition type of a monitor status rule other conditions
are not changed (#216426)\n\nThis PR closes #197786
.\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
 2025-04-22 12:12:53 +02:00
Kibana Machine
1e15aed03c
[8.18] [Synthetics] Fixed monitor history histogram and group by location issue (#218550) (#218761) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Synthetics] Fixed monitor history histogram and group by location
issue (#218550)](https://github.com/elastic/kibana/pull/218550)

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-22T07:28:35Z","message":"[Synthetics]
Fixed monitor history histogram and group by location issue
(#218550)\n\nThis PR closes #217105 and closes #217118
\n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics]
Fixed monitor history histogram and group by location
issue","number":218550,"url":"https://github.com/elastic/kibana/pull/218550","mergeCommit":{"message":"[Synthetics]
Fixed monitor history histogram and group by location issue
(#218550)\n\nThis PR closes #217105 and closes #217118
\n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218550","number":218550,"mergeCommit":{"message":"[Synthetics]
Fixed monitor history histogram and group by location issue
(#218550)\n\nThis PR closes #217105 and closes #217118
\n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
 2025-04-22 11:18:54 +02:00
Kibana Machine
f83f7de27e
[8.18] [Security Solution][Telemetry] Add index metadata EBT event (#218546) (#218600) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution][Telemetry] Add index metadata EBT event
(#218546)](https://github.com/elastic/kibana/pull/218546)

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

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

<!--BACKPORT [{"author":{"name":"Sebastián
Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T18:00:26Z","message":"[Security
Solution][Telemetry] Add index metadata EBT event (#218546)\n\n##
Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n-
Add a new EBT event collecting index template info\n ```typescript\n
export interface IndexTemplateInfo {\n template_name: string;\n
index_mode: Nullable<string>;\n datastream: boolean;\n package_name:
Nullable<string>;\n managed_by: Nullable<string>;\n beat:
Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of:
string[];\n source_enabled: Nullable<boolean>;\n source_includes:
string[];\n source_excludes: string[];\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- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","ci:build-cloud-image","v9.1.0"],"title":"[Security
Solution][Telemetry] Add index metadata EBT
event","number":218546,"url":"https://github.com/elastic/kibana/pull/218546","mergeCommit":{"message":"[Security
Solution][Telemetry] Add index metadata EBT event (#218546)\n\n##
Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n-
Add a new EBT event collecting index template info\n ```typescript\n
export interface IndexTemplateInfo {\n template_name: string;\n
index_mode: Nullable<string>;\n datastream: boolean;\n package_name:
Nullable<string>;\n managed_by: Nullable<string>;\n beat:
Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of:
string[];\n source_enabled: Nullable<boolean>;\n source_includes:
string[];\n source_excludes: string[];\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- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511"}},"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/218546","number":218546,"mergeCommit":{"message":"[Security
Solution][Telemetry] Add index metadata EBT event (#218546)\n\n##
Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n-
Add a new EBT event collecting index template info\n ```typescript\n
export interface IndexTemplateInfo {\n template_name: string;\n
index_mode: Nullable<string>;\n datastream: boolean;\n package_name:
Nullable<string>;\n managed_by: Nullable<string>;\n beat:
Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of:
string[];\n source_enabled: Nullable<boolean>;\n source_includes:
string[];\n source_excludes: string[];\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- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests
changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511"}}]}]
BACKPORT-->

Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
 2025-04-22 10:48:32 +02:00
Kibana Machine
025cff5840
[8.18] Advanced policy opt-out for scan-on-event (#218354) (#218612) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [Advanced policy opt-out for scan-on-event
(#218354)](https://github.com/elastic/kibana/pull/218354)

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

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

<!--BACKPORT [{"author":{"name":"Gabriel
Landau","email":"42078554+gabriellandau@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T19:00:15Z","message":"Advanced
policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users
to opt out of scan-on-event to help troubleshoot and
resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend}
users can now opt out of event-driven Memory Protection\nscanning via
advanced policy.\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-
[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:
Konrad Szwarc
<konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Defend
Workflows","backport:version","v9.1.0","v8.18.1","v9.0.1","v8.17.6"],"title":"Advanced
policy opt-out for
scan-on-event","number":218354,"url":"https://github.com/elastic/kibana/pull/218354","mergeCommit":{"message":"Advanced
policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users
to opt out of scan-on-event to help troubleshoot and
resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend}
users can now opt out of event-driven Memory Protection\nscanning via
advanced policy.\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-
[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:
Konrad Szwarc
<konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218354","number":218354,"mergeCommit":{"message":"Advanced
policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users
to opt out of scan-on-event to help troubleshoot and
resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend}
users can now opt out of event-driven Memory Protection\nscanning via
advanced policy.\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-
[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:
Konrad Szwarc
<konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Gabriel Landau <42078554+gabriellandau@users.noreply.github.com>
 2025-04-21 18:41:04 +02:00
Kibana Machine
1af5b2556a
[8.18] [Security Solution] Fixes related integrations render performance on rule editing pages (#217254) (#218669) 
# Backport

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

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

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

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

Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>
 2025-04-18 22:31:43 +02:00
Kibana Machine
8c1a846ef9
[8.18] [Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540) (#218594) 
# Backport

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

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

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

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

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
 2025-04-18 09:25:09 +00:00
Vitalii Dmyterko
d8e5155c84
[8.18] [Security Solution][Detection Engine] adds async ES|QL query (#216667) (#218585) 
# Backport

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

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

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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-17 20:50:45 +02:00
Marshall Main
a2630eb4ab
[8.18] [Security Solution][Rules Management] Separate actions import logic from rules import (#216380) (#218484) 
# Backport

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

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

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

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

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

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-17T05:34:38Z","message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics]
Fixed test run logs per
page","number":218458,"url":"https://github.com/elastic/kibana/pull/218458","mergeCommit":{"message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218458","number":218458,"mergeCommit":{"message":"[Synthetics]
Fixed test run logs per page
(#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
 2025-04-17 09:23:48 +02:00
Kibana Machine
0b4badc7d1
[8.18] [Custom threshold rule] Allow group for ip type fields !! (#216062) (#218336) 
# Backport

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

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

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

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

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
 2025-04-17 09:14:25 +02:00
jennypavlova
906ff07331
[8.18] [APM][OTel] Encode service name in the APM URLs (#217092) (#218477) 
# Backport

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

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

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

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

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Fix redux action being fired because of unused
react-router value
(#217055)](https://github.com/elastic/kibana/pull/217055)

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

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

<!--BACKPORT [{"author":{"name":"Kevin
Qualters","email":"56408403+kqualters-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T14:13:44Z","message":"[Security
Solution] Fix redux action being fired because of unused react-router
value (#217055)\n\n## Summary\n\nThis pr fixes a bug with the
RouteCapture component, used at a high\nlevel in the security solution
component tree, to reflect url changes\ninto redux. The code previously
used the full result of\n'react-router-dom' 's useLocation hook as the
payload, which contains 4\nparameters, pathname, search, hash that we
make use of, and a 4th that\nwas added sometime later by the library
that is essentially a random id\ngenerated every time the hook is
called, called key. We have never used\nthis, and it was being
inadvertently copied into the redux state, and\nalso causing some other
actions or hooks based listeners to run I think\nas well.\n\nBelow is
the contrived example of going from the home page to an empty\nalerts
page, and you can see 4 actions in the after, and 5 in the\nbefore, with
1 updating only the key. May reduce more unneeded actions\nwith more
going on in the page, but exactly how many is not
known.\nBefore:\n\n![image](ebd75055-4e17-497b-bed2-a5fd58c5c92f)\n\n\n###
Checklist\n\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c277812ffe3e74eb9bc0733a538bd78ea9b95f58","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","backport:all-open","v9.1.0"],"title":"[Security
Solution] Fix redux action being fired because of unused react-router
value","number":217055,"url":"https://github.com/elastic/kibana/pull/217055","mergeCommit":{"message":"[Security
Solution] Fix redux action being fired because of unused react-router
value (#217055)\n\n## Summary\n\nThis pr fixes a bug with the
RouteCapture component, used at a high\nlevel in the security solution
component tree, to reflect url changes\ninto redux. The code previously
used the full result of\n'react-router-dom' 's useLocation hook as the
payload, which contains 4\nparameters, pathname, search, hash that we
make use of, and a 4th that\nwas added sometime later by the library
that is essentially a random id\ngenerated every time the hook is
called, called key. We have never used\nthis, and it was being
inadvertently copied into the redux state, and\nalso causing some other
actions or hooks based listeners to run I think\nas well.\n\nBelow is
the contrived example of going from the home page to an empty\nalerts
page, and you can see 4 actions in the after, and 5 in the\nbefore, with
1 updating only the key. May reduce more unneeded actions\nwith more
going on in the page, but exactly how many is not
known.\nBefore:\n\n![image](ebd75055-4e17-497b-bed2-a5fd58c5c92f)\n\n\n###
Checklist\n\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c277812ffe3e74eb9bc0733a538bd78ea9b95f58"}},"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/217055","number":217055,"mergeCommit":{"message":"[Security
Solution] Fix redux action being fired because of unused react-router
value (#217055)\n\n## Summary\n\nThis pr fixes a bug with the
RouteCapture component, used at a high\nlevel in the security solution
component tree, to reflect url changes\ninto redux. The code previously
used the full result of\n'react-router-dom' 's useLocation hook as the
payload, which contains 4\nparameters, pathname, search, hash that we
make use of, and a 4th that\nwas added sometime later by the library
that is essentially a random id\ngenerated every time the hook is
called, called key. We have never used\nthis, and it was being
inadvertently copied into the redux state, and\nalso causing some other
actions or hooks based listeners to run I think\nas well.\n\nBelow is
the contrived example of going from the home page to an empty\nalerts
page, and you can see 4 actions in the after, and 5 in the\nbefore, with
1 updating only the key. May reduce more unneeded actions\nwith more
going on in the page, but exactly how many is not
known.\nBefore:\n\n![image](ebd75055-4e17-497b-bed2-a5fd58c5c92f)\n\n\n###
Checklist\n\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"c277812ffe3e74eb9bc0733a538bd78ea9b95f58"}}]}]
BACKPORT-->

Co-authored-by: Kevin Qualters <56408403+kqualters-elastic@users.noreply.github.com>
 2025-04-16 18:49:49 +02:00
Kibana Machine
9556de5d7e
[8.18] [Security Solution] Allow disabling experimental features via config (#217363) (#218427) 
# Backport

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

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

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

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

Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
 2025-04-16 15:56:22 +02:00
Kibana Machine
39e48f126d
[8.18] [Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123) (#218247) 
# Backport

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

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

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

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

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
 2025-04-16 15:21:39 +02:00
Francesco Fagnani
a5f832e6cd
[8.18] [Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197) (#218292) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T14:53:14Z","message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global
params","number":216197,"url":"https://github.com/elastic/kibana/pull/216197","mergeCommit":{"message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216197","number":216197,"mergeCommit":{"message":"[Synthetics]
Sync global parameters is called in the endpoints to add, edit or delete
global params (#216197)\n\nThis PR closes #215668.\n\nThe global
parameters are synched in the endpoints where they are\ncreated, edited
or deleted.\n\n---------\n\nCo-authored-by: Shahzad
<shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218290","number":218290,"state":"OPEN"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-16 10:04:38 +02:00
Kibana Machine
fc87edd906
[8.18] [Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959) (#218153) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Dmitrii
Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:22:38Z","message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:high","Feature:Endpoint","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy
creation","number":217959,"url":"https://github.com/elastic/kibana/pull/217959","mergeCommit":{"message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217959","number":217959,"mergeCommit":{"message":"[Security
Solution] Fix prebuilt rules force upgrade on Endpoint policy creation
(#217959)\n\n**Resolves:
https://github.com/elastic/security-team/issues/7216**\n\n##
Summary\n\nThis PR updates the Endpoint policy callback to: \n\n-
**Install only the Elastic Defend rule if it's missing**,
without\nupgrading it to the latest version. Previously, the rule was
both\ninstalled and updated whenever an Endpoint policy was created,
which\nconflicted with rule customization. Automatic upgrades could
erase\nexisting user customizations.\n\n- **Avoid triggering the
installation or upgrade of any other prebuilt\nrules** as part of this
flow. The Endpoint package policy
creation\ncallback\n([source](f7d8bc3c25/x-pack/solutions/security/plugins/security_solution/server/fleet_integration/fleet_integration.ts (L181-L187)))\npreviously
installed and upgraded **all** prebuilt detection rules to\ntheir target
versions whenever an Endpoint policy was created.\n\nThis logic relied
on the legacy rule upgrade method, which has a known\nissue that causes
all configured rule actions and exceptions to be lost.\nBy removing the
upgrade logic, this PR eliminates that
incorrect\nbehavior.","sha":"9f5425f061e6fff8579f7db1117af075b1b6ca1b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>
 2025-04-14 21:06:42 +02:00
Kibana Machine
4dd7c79ecf
[8.18] [ObsUX][A11y] Fix focus for popover in details flyout (#218095) (#218125) 
# Backport

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

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

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

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

Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
 2025-04-14 18:12:16 +02:00
Milosz Marcinkowski
6d7097d6be
[8.18] [APM][UI] Sort environment dropdown alphabetically (#217710) (#217880) 
# Backport

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

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

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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-14 11:44:24 +02:00
Lisa Cawley
c3769d1c0b
[8.18] [DOCS] Add minimal synthetic APIs (#214518) (#217902) 
# Backport

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

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

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

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

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-11 10:53:31 -04:00
Sergi Romeu
dd276315fb
[8.18] [APM][Cypress] Attempt to fix mobile transactions test (#217648) (#217954) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-11T08:28:49Z","message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","apm:mobile","backport:all-open","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][Cypress]
Attempt to fix mobile transactions
test","number":217648,"url":"https://github.com/elastic/kibana/pull/217648","mergeCommit":{"message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217648","number":217648,"mergeCommit":{"message":"[APM][Cypress]
Attempt to fix mobile transactions test (#217648)\n\n##
Summary\n\nCloses
#207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}}]}]
BACKPORT-->
 2025-04-11 13:11:21 +02:00
Georgii Gorbachev
6bedafe4c0
[8.18] [Security Solution] Improving documentations for bulk_actions (#216852) (#217824) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Improving documentations for bulk_actions
(#216852)](https://github.com/elastic/kibana/pull/216852)

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

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

<!--BACKPORT [{"author":{"name":"Jacek
Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-09T16:03:19Z","message":"[Security
Solution] Improving documentations for bulk_actions
(#216852)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn
this PR I am improving documentation for the bulk_actions endpoint.\nThe
focus is on improving descriptions of parameters and providing\nexamples
for all important situations, especially setting / adding\nactions.\n\n#
Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2.
yarn openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77","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:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","APIDocs","Team:Detection Rule
Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security
Solution] Improving documentations for
bulk_actions","number":216852,"url":"https://github.com/elastic/kibana/pull/216852","mergeCommit":{"message":"[Security
Solution] Improving documentations for bulk_actions
(#216852)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn
this PR I am improving documentation for the bulk_actions endpoint.\nThe
focus is on improving descriptions of parameters and providing\nexamples
for all important situations, especially setting / adding\nactions.\n\n#
Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2.
yarn openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217717","number":217717,"state":"MERGED","mergeCommit":{"sha":"91cdba78ba8586974f5cb317fb33e8c0cbf32e60","message":"[9.0]
[Security Solution] Improving documentations for bulk_actions (#216852)
(#217717)\n\n# Backport\n\nThis will backport the following commits from
`main` to `9.0`:\n- [[Security Solution] Improving documentations for
bulk_actions\n(#216852)](https://github.com/elastic/kibana/pull/216852)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Jacek Kolezynski
<jacek.kolezynski@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216852","number":216852,"mergeCommit":{"message":"[Security
Solution] Improving documentations for bulk_actions
(#216852)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn
this PR I am improving documentation for the bulk_actions endpoint.\nThe
focus is on improving descriptions of parameters and providing\nexamples
for all important situations, especially setting / adding\nactions.\n\n#
Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2.
yarn openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by:
Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217716","number":217716,"state":"MERGED","mergeCommit":{"sha":"3fa939ea4d4b7e3ec59009782c638ccb3dda95ac","message":"[8.x]
[Security Solution] Improving documentations for bulk_actions (#216852)
(#217716)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[Security Solution] Improving documentations for
bulk_actions\n(#216852)](https://github.com/elastic/kibana/pull/216852)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by:
Jacek Kolezynski
<jacek.kolezynski@elastic.co>"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>
 2025-04-11 09:20:46 +02:00
Kevin Delemme
bc9f967272
[8.18] fix(slo): search bar filters (#217702) (#217869) 2025-04-10 13:46:39 -04:00
Kibana Machine
9001dd9290
[8.18] [Obs AI Assistant] Fix navigating to the search connectors page (#217749) (#217861) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Obs AI Assistant] Fix navigating to the search connectors page
(#217749)](https://github.com/elastic/kibana/pull/217749)

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

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

<!--BACKPORT [{"author":{"name":"Viduni
Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T14:27:54Z","message":"[Obs
AI Assistant] Fix navigating to the search connectors page
(#217749)\n\nCloses
https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n###
Problem\n\nClicking on connectors in the Search connectors tab in the AI
Assistant\nsettings navigates the user to a blank
page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis
happens because `enterprise_search` URLs are deprecated and
it's\nrenamed to `elasticsearch`.\nRelated to
https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs
-\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n###
Solution\n\nReplace the URL path from `enterpriseSearch` to
`elasticsearch`\n\nAfter the
fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n###
Checklist\n\n- [x] The PR description includes the appropriate Release
Notes section,\nand the correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1","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
AI
Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1"],"title":"[Obs
AI Assistant] Fix navigating to the search connectors
page","number":217749,"url":"https://github.com/elastic/kibana/pull/217749","mergeCommit":{"message":"[Obs
AI Assistant] Fix navigating to the search connectors page
(#217749)\n\nCloses
https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n###
Problem\n\nClicking on connectors in the Search connectors tab in the AI
Assistant\nsettings navigates the user to a blank
page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis
happens because `enterprise_search` URLs are deprecated and
it's\nrenamed to `elasticsearch`.\nRelated to
https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs
-\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n###
Solution\n\nReplace the URL path from `enterpriseSearch` to
`elasticsearch`\n\nAfter the
fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n###
Checklist\n\n- [x] The PR description includes the appropriate Release
Notes section,\nand the correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1"}},"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/217749","number":217749,"mergeCommit":{"message":"[Obs
AI Assistant] Fix navigating to the search connectors page
(#217749)\n\nCloses
https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n###
Problem\n\nClicking on connectors in the Search connectors tab in the AI
Assistant\nsettings navigates the user to a blank
page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis
happens because `enterprise_search` URLs are deprecated and
it's\nrenamed to `elasticsearch`.\nRelated to
https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs
-\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n###
Solution\n\nReplace the URL path from `enterpriseSearch` to
`elasticsearch`\n\nAfter the
fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n###
Checklist\n\n- [x] The PR description includes the appropriate Release
Notes section,\nand the correct `release_note:*` label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co>
 2025-04-10 18:52:24 +02:00
Carlos Crespo
cf9e5ce9b7
[8.18] [APM] Treat "links" field as array (#215906) (#217662) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T07:10:15Z","message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM]
Treat \"links\" field as
array","number":215906,"url":"https://github.com/elastic/kibana/pull/215906","mergeCommit":{"message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215906","number":215906,"mergeCommit":{"message":"[APM]
Treat \"links\" field as array (#215906)\n\nFixes
[#215706](https://github.com/elastic/kibana/issues/215706)\n\n##
Summary\n\nThis fixes the problem where Otel span links were not
considered a\ncollection of links.\n\n\n<img width=\"1721\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n###
How to test\n\nRun: `node scripts/synthtrace span_links.ts --live
--uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel`
and wait a few\nminutes\n\nNavigate to Services Inventory -> product
consumer -> Transactions and\ninspect the span links from `Span
B`\n\nRun the query below to confirm that there are `links` with a
collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n
\"exists\": {\n \"field\": \"links*\"\n }\n
}\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}}]}]
BACKPORT-->
 2025-04-10 15:36:51 +02:00
Kibana Machine
70ed457075
[8.18] [A11y][APM] Improve aria-label for correlations (#217512) (#217808) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[A11y][APM] Improve `aria-label` for correlations
(#217512)](https://github.com/elastic/kibana/pull/217512)

<!--- 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-10T09:52:11Z","message":"[A11y][APM]
Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the
`aria-label` attributes in the latency correlations\npage to add more
context about the selected
field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[A11y][APM]
Improve `aria-label` for
correlations","number":217512,"url":"https://github.com/elastic/kibana/pull/217512","mergeCommit":{"message":"[A11y][APM]
Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the
`aria-label` attributes in the latency correlations\npage to add more
context about the selected
field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217512","number":217512,"mergeCommit":{"message":"[A11y][APM]
Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses
https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the
`aria-label` attributes in the latency correlations\npage to add more
context about the selected
field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-10 14:10:47 +02:00
Miriam
3bdc2d40c3
[8.18] [ObsUx][A11y] Add unique accessible lables to metadata table (#217496) (#217813) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUx][A11y] Add unique accessible lables to metadata table
(#217496)](https://github.com/elastic/kibana/pull/217496)

<!--- 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-09T07:41:30Z","message":"[ObsUx][A11y]
Add unique accessible lables to metadata table (#217496)\n\nCloses
https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd
unique accessible labels to metadata table\n\n### How to test\n\nUse a
screen reader to navigate the table\n\nOn Host details, Metadata
tab\n\n1. Verify the first column in the table header announces Pin
Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12
38
28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2.
Verify the Pin column row announces which field pins\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38
45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3.
Verify the \"+ x more\" does announce more of which field\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb","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 unique accessible lables to metadata
table","number":217496,"url":"https://github.com/elastic/kibana/pull/217496","mergeCommit":{"message":"[ObsUx][A11y]
Add unique accessible lables to metadata table (#217496)\n\nCloses
https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd
unique accessible labels to metadata table\n\n### How to test\n\nUse a
screen reader to navigate the table\n\nOn Host details, Metadata
tab\n\n1. Verify the first column in the table header announces Pin
Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12
38
28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2.
Verify the Pin column row announces which field pins\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38
45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3.
Verify the \"+ x more\" does announce more of which field\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217621","number":217621,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217496","number":217496,"mergeCommit":{"message":"[ObsUx][A11y]
Add unique accessible lables to metadata table (#217496)\n\nCloses
https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd
unique accessible labels to metadata table\n\n### How to test\n\nUse a
screen reader to navigate the table\n\nOn Host details, Metadata
tab\n\n1. Verify the first column in the table header announces Pin
Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12
38
28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2.
Verify the Pin column row announces which field pins\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38
45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3.
Verify the \"+ x more\" does announce more of which field\n\n<img
width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39
35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217657","number":217657,"state":"MERGED","mergeCommit":{"sha":"3b5e43ab47a19264d60771b161202ac677060a3b","message":"[8.x]
[ObsUx][A11y] Add unique accessible lables to metadata table (#217496)
(#217657)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[ObsUx][A11y] Add unique accessible lables to
metadata
table\n(#217496)](https://github.com/elastic/kibana/pull/217496)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}]
BACKPORT-->
 2025-04-10 13:59:41 +02:00
Mykola Harmash
c220d2938c
Revert "[8.18] [Oblt Onboarding] Add breadcrumbs for quick start flow… (#217686) 
Revert of the
5c5d8e3638
because it's a non-essential change and it was merged too close to the
BC.
 2025-04-10 12:50:01 +02:00
Sergi Romeu
0f8fe7f1aa
[8.18] [A11y][APM] Improve aria-label for EuiCodeBlock on onboarding page (#217292) (#217691) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[A11y][APM] Improve `aria-label` for `EuiCodeBlock` on onboarding
page (#217292)](https://github.com/elastic/kibana/pull/217292)

<!--- 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-09T13:55:12Z","message":"[A11y][APM]
Improve `aria-label` for `EuiCodeBlock` on onboarding page
(#217292)\n\n## Summary\n\nFixes #195030\n\nThis PR adds `aria-label`
with language context for `EuiCodeBlock` in\nthe APM onboarding
page.","sha":"a49dc033306931b83facd68b062b30339ec895ed","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[A11y][APM]
Improve `aria-label` for `EuiCodeBlock` on onboarding
page","number":217292,"url":"https://github.com/elastic/kibana/pull/217292","mergeCommit":{"message":"[A11y][APM]
Improve `aria-label` for `EuiCodeBlock` on onboarding page
(#217292)\n\n## Summary\n\nFixes #195030\n\nThis PR adds `aria-label`
with language context for `EuiCodeBlock` in\nthe APM onboarding
page.","sha":"a49dc033306931b83facd68b062b30339ec895ed"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217292","number":217292,"mergeCommit":{"message":"[A11y][APM]
Improve `aria-label` for `EuiCodeBlock` on onboarding page
(#217292)\n\n## Summary\n\nFixes #195030\n\nThis PR adds `aria-label`
with language context for `EuiCodeBlock` in\nthe APM onboarding
page.","sha":"a49dc033306931b83facd68b062b30339ec895ed"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-09 19:26:22 +02:00
Kibana Machine
5fdc5279ba
[8.18] [ObsUX] [A11y] Fix focus on metadata table content (#216628) (#216777) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUX] [A11y] Fix focus on metadata table content
(#216628)](https://github.com/elastic/kibana/pull/216628)

<!--- 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-02T09:25:05Z","message":"[ObsUX]
[A11y] Fix focus on metadata table content (#216628)\n\nCloses
https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost
Detail page has a Metadata tab with expandable table rows. These\nrows
add content to the page in an unexpected reading order. Content\nshould
be expanded underneath the show more / less trigger. Focus should\nstay
on the
toggle.\n\nBefore\n\n\n7993abdc-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX]
[A11y] Fix focus on metadata table
content","number":216628,"url":"https://github.com/elastic/kibana/pull/216628","mergeCommit":{"message":"[ObsUX]
[A11y] Fix focus on metadata table content (#216628)\n\nCloses
https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost
Detail page has a Metadata tab with expandable table rows. These\nrows
add content to the page in an unexpected reading order. Content\nshould
be expanded underneath the show more / less trigger. Focus should\nstay
on the
toggle.\n\nBefore\n\n\n7993abdc-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265"}},"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/216628","number":216628,"mergeCommit":{"message":"[ObsUX]
[A11y] Fix focus on metadata table content (#216628)\n\nCloses
https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost
Detail page has a Metadata tab with expandable table rows. These\nrows
add content to the page in an unexpected reading order. Content\nshould
be expanded underneath the show more / less trigger. Focus should\nstay
on the
toggle.\n\nBefore\n\n\n7993abdc-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265"}},{"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-09 14:53:42 +02:00
Mykola Harmash
5c5d8e3638
[8.18] [Oblt Onboarding] Add breadcrumbs for quick start flows (#216470) (#217495) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Oblt Onboarding] Add breadcrumbs for quick start flows
(#216470)](https://github.com/elastic/kibana/pull/216470)

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

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

<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T11:49:09Z","message":"[Oblt
Onboarding] Add breadcrumbs for quick start flows (#216470)\n\nCloses
https://github.com/elastic/kibana/issues/191646\n\nThis change adds
breadcrumbs to the project navigation bar for every\nquickstart
flow.\n\n| Classic Navigation | Solution Navigation |\n| --- | --- |\n|
![CleanShot 2025-03-31 at 15
32\n08@2x](https://github.com/user-attachments/assets/d9489e9c-1df1-43f2-99ec-b82128a1be85)\n|
![CleanShot 2025-03-31 at 15
31\n13@2x](https://github.com/user-attachments/assets/28180e0b-da00-4773-b9e5-a4d7e1c97424)\n|","sha":"fcc7244da2b801ce5e59017a00e3ce19a20b01ce","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","ci:project-deploy-observability","Feature:
Observability Onboarding"],"title":"[Oblt Onboarding] Add breadcrumbs
for quick start
flows","number":216470,"url":"https://github.com/elastic/kibana/pull/216470","mergeCommit":{"message":"[Oblt
Onboarding] Add breadcrumbs for quick start flows (#216470)\n\nCloses
https://github.com/elastic/kibana/issues/191646\n\nThis change adds
breadcrumbs to the project navigation bar for every\nquickstart
flow.\n\n| Classic Navigation | Solution Navigation |\n| --- | --- |\n|
![CleanShot 2025-03-31 at 15
32\n08@2x](https://github.com/user-attachments/assets/d9489e9c-1df1-43f2-99ec-b82128a1be85)\n|
![CleanShot 2025-03-31 at 15
31\n13@2x](https://github.com/user-attachments/assets/28180e0b-da00-4773-b9e5-a4d7e1c97424)\n|","sha":"fcc7244da2b801ce5e59017a00e3ce19a20b01ce"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[]}]
BACKPORT-->
 2025-04-09 14:35:24 +02:00
Mykola Harmash
b0906caf93
[8.18] [Oblt Onboarding][Auto Detect] Filter out httpjson inputs and fix accidental config backup file (#216978) (#217497) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Oblt Onboarding][Auto Detect] Filter out httpjson inputs and fix
accidental config backup file
(#216978)](https://github.com/elastic/kibana/pull/216978)

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

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

<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-04-07T13:57:33Z","message":"[Oblt
Onboarding][Auto Detect] Filter out httpjson inputs and fix accidental
config backup file (#216978)\n\nCloses
https://github.com/elastic/kibana/issues/199744\n\n* Adds a separate
`sed` commands for Linux and macOS when replacing API\nkey within the
Agent config. GNU and BSD versions of `sed` treat `-i`\n(in-place
editing) argument differently, GNU version allows `-i` without\na value
while BSD version requires a backup file extension even when\nit's empty
🫠\n* Adds filtering of unsupported input types inside the
integration\npolicies. For now it only filters out `httpjson`.\n\n## How
to test\n1. Go through the auto-detect flow\n2. Make sure there is no
`'elastic-agent.yml='` file in the Agent\ndirectory, or any other weird
artifacts\n3. Inspect individual integration config files, make sure
they don't\nhave `httpjson` inputs\n\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>","sha":"ec72d4a880cc7c396fc0376bb33bdb2821bc6db5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Feature:
Observability
Onboarding","backport:version","v9.1.0","v8.18.1","v9.0.1"],"title":"[Oblt
Onboarding][Auto Detect] Filter out httpjson inputs and fix accidental
config backup
file","number":216978,"url":"https://github.com/elastic/kibana/pull/216978","mergeCommit":{"message":"[Oblt
Onboarding][Auto Detect] Filter out httpjson inputs and fix accidental
config backup file (#216978)\n\nCloses
https://github.com/elastic/kibana/issues/199744\n\n* Adds a separate
`sed` commands for Linux and macOS when replacing API\nkey within the
Agent config. GNU and BSD versions of `sed` treat `-i`\n(in-place
editing) argument differently, GNU version allows `-i` without\na value
while BSD version requires a backup file extension even when\nit's empty
🫠\n* Adds filtering of unsupported input types inside the
integration\npolicies. For now it only filters out `httpjson`.\n\n## How
to test\n1. Go through the auto-detect flow\n2. Make sure there is no
`'elastic-agent.yml='` file in the Agent\ndirectory, or any other weird
artifacts\n3. Inspect individual integration config files, make sure
they don't\nhave `httpjson` inputs\n\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>","sha":"ec72d4a880cc7c396fc0376bb33bdb2821bc6db5"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217334","number":217334,"state":"MERGED","mergeCommit":{"sha":"5ea5a88198dc9bf1a5d235764596ab3914b328e1","message":"[9.0]
[Oblt Onboarding][Auto Detect] Filter out httpjson inputs and fix
accidental config backup file (#216978) (#217334)\n\n# Backport\n\nThis
will backport the following commits from `main` to `9.0`:\n- [[Oblt
Onboarding][Auto Detect] Filter out httpjson inputs and fix\naccidental
config backup
file\n(#216978)](https://github.com/elastic/kibana/pull/216978)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Mykola Harmash
<mykola.harmash@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216978","number":216978,"mergeCommit":{"message":"[Oblt
Onboarding][Auto Detect] Filter out httpjson inputs and fix accidental
config backup file (#216978)\n\nCloses
https://github.com/elastic/kibana/issues/199744\n\n* Adds a separate
`sed` commands for Linux and macOS when replacing API\nkey within the
Agent config. GNU and BSD versions of `sed` treat `-i`\n(in-place
editing) argument differently, GNU version allows `-i` without\na value
while BSD version requires a backup file extension even when\nit's empty
🫠\n* Adds filtering of unsupported input types inside the
integration\npolicies. For now it only filters out `httpjson`.\n\n## How
to test\n1. Go through the auto-detect flow\n2. Make sure there is no
`'elastic-agent.yml='` file in the Agent\ndirectory, or any other weird
artifacts\n3. Inspect individual integration config files, make sure
they don't\nhave `httpjson` inputs\n\nCo-authored-by: Joe Reuter
<johannes.reuter@elastic.co>","sha":"ec72d4a880cc7c396fc0376bb33bdb2821bc6db5"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-09 14:35:02 +02:00
Kibana Machine
22cd3ad345
[8.18] [A11y][APM] Add aria-label to technical preview badge (#216483) (#217611) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[A11y][APM] Add `aria-label` to technical preview badge
(#216483)](https://github.com/elastic/kibana/pull/216483)

<!--- 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:08:27Z","message":"[A11y][APM]
Add `aria-label` to technical preview badge (#216483)\n\n##
Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis
PR adds the `aria-label` prop so screen readers work with this\ntooltip
text.\n\n![image](https://github.com/user-attachments/assets/8c3d345d-68be-42cb-ab6f-addafd0d7683)","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[A11y][APM]
Add `aria-label` to technical preview
badge","number":216483,"url":"https://github.com/elastic/kibana/pull/216483","mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to technical preview badge (#216483)\n\n##
Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis
PR adds the `aria-label` prop so screen readers work with this\ntooltip
text.\n\n![image](https://github.com/user-attachments/assets/8c3d345d-68be-42cb-ab6f-addafd0d7683)","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216483","number":216483,"mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to technical preview badge (#216483)\n\n##
Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis
PR adds the `aria-label` prop so screen readers work with this\ntooltip
text.\n\n![image](https://github.com/user-attachments/assets/8c3d345d-68be-42cb-ab6f-addafd0d7683)","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216601","number":216601,"state":"MERGED","mergeCommit":{"sha":"5561abe7fcaf697171e4d494ad5db7863e9b7fe4","message":"[8.x]
[A11y][APM] Add `aria-label` to technical preview badge (#216483)
(#216601)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[A11y][APM] Add `aria-label` to technical preview
badge\n(#216483)](https://github.com/elastic/kibana/pull/216483)\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":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-09 14:01:13 +02:00
Kibana Machine
b7da508e2e
[8.18] [A11y][APM] Add missing aria-label for some services buttons (#217325) (#217613) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[A11y][APM] Add missing `aria-label` for some services buttons
(#217325)](https://github.com/elastic/kibana/pull/217325)

<!--- 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-09T07:02:15Z","message":"[A11y][APM]
Add missing `aria-label` for some services buttons (#217325)\n\n##
Summary\n\nFixes #212264\n\nThis PR adds a couple of `aria-label`
attributes to buttons that do not\nhave a screen-reader announcement
under the Services and Services
Groups\npages.","sha":"749f57c12f685eee1f380644a39732773dcd7ab7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[A11y][APM]
Add missing `aria-label` for some services
buttons","number":217325,"url":"https://github.com/elastic/kibana/pull/217325","mergeCommit":{"message":"[A11y][APM]
Add missing `aria-label` for some services buttons (#217325)\n\n##
Summary\n\nFixes #212264\n\nThis PR adds a couple of `aria-label`
attributes to buttons that do not\nhave a screen-reader announcement
under the Services and Services
Groups\npages.","sha":"749f57c12f685eee1f380644a39732773dcd7ab7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217325","number":217325,"mergeCommit":{"message":"[A11y][APM]
Add missing `aria-label` for some services buttons (#217325)\n\n##
Summary\n\nFixes #212264\n\nThis PR adds a couple of `aria-label`
attributes to buttons that do not\nhave a screen-reader announcement
under the Services and Services
Groups\npages.","sha":"749f57c12f685eee1f380644a39732773dcd7ab7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-09 14:00:58 +02:00
Kibana Machine
1bb180276c
[8.18] [A11y][APM] Add aria-label to fold traces button (#216485) (#217609) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[A11y][APM] Add `aria-label` to fold traces button
(#216485)](https://github.com/elastic/kibana/pull/216485)

<!--- 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:06:55Z","message":"[A11y][APM]
Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes
#212228\n\nThis PR adds `aria-label` to the fold/unfold traces
button.\n\n\n![image](https://github.com/user-attachments/assets/7c14d3d1-c246-4b85-a80c-4fb51dd1f305)","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[A11y][APM]
Add `aria-label` to fold traces
button","number":216485,"url":"https://github.com/elastic/kibana/pull/216485","mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes
#212228\n\nThis PR adds `aria-label` to the fold/unfold traces
button.\n\n\n![image](https://github.com/user-attachments/assets/7c14d3d1-c246-4b85-a80c-4fb51dd1f305)","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba"}},"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/216485","number":216485,"mergeCommit":{"message":"[A11y][APM]
Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes
#212228\n\nThis PR adds `aria-label` to the fold/unfold traces
button.\n\n\n![image](https://github.com/user-attachments/assets/7c14d3d1-c246-4b85-a80c-4fb51dd1f305)","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216600","number":216600,"state":"MERGED","mergeCommit":{"sha":"20425bc726d7cb6442f273c25f24ebaaafee4892","message":"[8.x]
[A11y][APM] Add `aria-label` to fold traces button (#216485)
(#216600)\n\n# Backport\n\nThis will backport the following commits from
`main` to `8.x`:\n- [[A11y][APM] Add `aria-label` to fold traces
button\n(#216485)](https://github.com/elastic/kibana/pull/216485)\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.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: Sergi Romeu <sergi.romeu@elastic.co>
 2025-04-09 13:58:15 +02:00
Francesco Fagnani
42f9afd320
[8.18] [Synthetics] Fix save lens visualization on monitors overview (#216695) (#217347) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-07T13:47:53Z","message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics]
Fix save lens visualization on monitors
overview","number":216695,"url":"https://github.com/elastic/kibana/pull/216695","mergeCommit":{"message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216695","number":216695,"mergeCommit":{"message":"[Synthetics]
Fix save lens visualization on monitors overview (#216695)\n\nThis PR
closes #212490 by fixing the save lens
visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217329","number":217329,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-08 08:01:06 -04:00
Miriam
d2b827b1a1
[8.18] [ObsUX][A11y] Add aria-label to group by count (#217302) (#217449) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[ObsUX][A11y] Add aria-label to group by count
(#217302)](https://github.com/elastic/kibana/pull/217302)

<!--- 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-07T13:42:12Z","message":"[ObsUX][A11y]
Add aria-label to group by count (#217302)\n\nCloses
https://github.com/elastic/kibana/issues/194974\n\n### What was
done\n\n- for the `All` button a description and spell out was done
in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to
count number so it spells out the number of type\nof node\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25
51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24
47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572","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 aria-label to group by
count","number":217302,"url":"https://github.com/elastic/kibana/pull/217302","mergeCommit":{"message":"[ObsUX][A11y]
Add aria-label to group by count (#217302)\n\nCloses
https://github.com/elastic/kibana/issues/194974\n\n### What was
done\n\n- for the `All` button a description and spell out was done
in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to
count number so it spells out the number of type\nof node\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25
51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24
47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572"}},"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/217328","number":217328,"state":"MERGED","mergeCommit":{"sha":"7fb23f119491bb83b61773c4621c1f380ac3f90f","message":"[9.0]
[ObsUX][A11y] Add aria-label to group by count (#217302) (#217328)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[ObsUX][A11y] Add aria-label to group by
count\n(#217302)](https://github.com/elastic/kibana/pull/217302)\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/217302","number":217302,"mergeCommit":{"message":"[ObsUX][A11y]
Add aria-label to group by count (#217302)\n\nCloses
https://github.com/elastic/kibana/issues/194974\n\n### What was
done\n\n- for the `All` button a description and spell out was done
in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to
count number so it spells out the number of type\nof node\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26
15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25
51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img
width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24
47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-08 12:08:14 +02:00
Abdul Wahab Zahid
ca96f071c3
[8.18] [Onboarding] Hide card labels in search results (#213417) (#216666) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Onboarding] Hide card labels in search results
(#213417)](https://github.com/elastic/kibana/pull/213417)

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

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

<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-07T14:40:39Z","message":"[Onboarding]
Hide card labels in search results (#213417)\n\nCloses
https://github.com/elastic/kibana/issues/200917\n\nLooking at the code
in Fleet search results screen, cards would also\nhave the `Unverified`
badges.
([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould
return `true` because this specific page doesn't
provides\n`packageVerificationKeyId` to the `isPackageUnverified()`
function, this\nonly happens on the individual integration details page.
Fleet search\njust [hides
the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor
cards in search results.\n\nThis change aligns Onboarding search results
with Fleet search results\nand hides the card labels which fixes the
issue with `Unverified` badge\nappearing for installed
integrations.\n\n| Before | After |\n| --- | ---
|\n|\n![388110694-bd6abaf4-15ac-4d56-b556-fddb11c85ba7](https://github.com/user-attachments/assets/751a6572-192c-45f6-bfa8-82433b73398d)\n|
![CleanShot 2025-03-07 at 14
35\n53@2x](https://github.com/user-attachments/assets/d1588d7d-eec8-4207-a1e6-9a53272bbddf)\n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Feature:
Observability
Onboarding","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Onboarding]
Hide card labels in search
results","number":213417,"url":"https://github.com/elastic/kibana/pull/213417","mergeCommit":{"message":"[Onboarding]
Hide card labels in search results (#213417)\n\nCloses
https://github.com/elastic/kibana/issues/200917\n\nLooking at the code
in Fleet search results screen, cards would also\nhave the `Unverified`
badges.
([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould
return `true` because this specific page doesn't
provides\n`packageVerificationKeyId` to the `isPackageUnverified()`
function, this\nonly happens on the individual integration details page.
Fleet search\njust [hides
the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor
cards in search results.\n\nThis change aligns Onboarding search results
with Fleet search results\nand hides the card labels which fixes the
issue with `Unverified` badge\nappearing for installed
integrations.\n\n| Before | After |\n| --- | ---
|\n|\n![388110694-bd6abaf4-15ac-4d56-b556-fddb11c85ba7](https://github.com/user-attachments/assets/751a6572-192c-45f6-bfa8-82433b73398d)\n|
![CleanShot 2025-03-07 at 14
35\n53@2x](https://github.com/user-attachments/assets/d1588d7d-eec8-4207-a1e6-9a53272bbddf)\n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d"}},"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/213579","number":213579,"state":"MERGED","mergeCommit":{"sha":"ff5042eb811c5eb1eb6bccc797feec06f52e1e32","message":"[9.0]
[Onboarding] Hide card labels in search results (#213417) (#213579)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [[Onboarding] Hide card labels in search
results\n(#213417)](https://github.com/elastic/kibana/pull/213417)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Mykola Harmash
<mykola.harmash@gmail.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213417","number":213417,"mergeCommit":{"message":"[Onboarding]
Hide card labels in search results (#213417)\n\nCloses
https://github.com/elastic/kibana/issues/200917\n\nLooking at the code
in Fleet search results screen, cards would also\nhave the `Unverified`
badges.
([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould
return `true` because this specific page doesn't
provides\n`packageVerificationKeyId` to the `isPackageUnverified()`
function, this\nonly happens on the individual integration details page.
Fleet search\njust [hides
the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor
cards in search results.\n\nThis change aligns Onboarding search results
with Fleet search results\nand hides the card labels which fixes the
issue with `Unverified` badge\nappearing for installed
integrations.\n\n| Before | After |\n| --- | ---
|\n|\n![388110694-bd6abaf4-15ac-4d56-b556-fddb11c85ba7](https://github.com/user-attachments/assets/751a6572-192c-45f6-bfa8-82433b73398d)\n|
![CleanShot 2025-03-07 at 14
35\n53@2x](https://github.com/user-attachments/assets/d1588d7d-eec8-4207-a1e6-9a53272bbddf)\n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
 2025-04-08 12:07:20 +02:00
Abdul Wahab Zahid
406ef5cb98
[8.18] [Obs Onboarding] Add page rendering performance monitoring (#213769) (#216762) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Obs Onboarding] Add page rendering performance monitoring
(#213769)](https://github.com/elastic/kibana/pull/213769)

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

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

<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-18T08:50:38Z","message":"[Obs
Onboarding] Add page rendering performance monitoring
(#213769)\n\nCloses
https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses
https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis
change add logic for triggering [the page rendering
performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n*
Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n*
Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1.
Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the
above mentioned onboarding screens\n4. Observe
`kibana:plugin_render_time` EBT event emitted in the Network\ntab of the
dev tools\n\nEvents emitted from local Kibana end up in the Staging
Telemetry\ncluster, there is a [dedicated rendering
performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding
events can be filtered using `observabilityOnboarding`\napplication ID.
(note that it takes some time for events to be indexed\nand they appear
in the cluster with a significant
delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","Feature: Observability
Onboarding","backport:version","v9.1.0"],"title":"[Obs Onboarding] Add
page rendering performance
monitoring","number":213769,"url":"https://github.com/elastic/kibana/pull/213769","mergeCommit":{"message":"[Obs
Onboarding] Add page rendering performance monitoring
(#213769)\n\nCloses
https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses
https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis
change add logic for triggering [the page rendering
performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n*
Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n*
Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1.
Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the
above mentioned onboarding screens\n4. Observe
`kibana:plugin_render_time` EBT event emitted in the Network\ntab of the
dev tools\n\nEvents emitted from local Kibana end up in the Staging
Telemetry\ncluster, there is a [dedicated rendering
performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding
events can be filtered using `observabilityOnboarding`\napplication ID.
(note that it takes some time for events to be indexed\nand they appear
in the cluster with a significant
delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4"}},"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/213769","number":213769,"mergeCommit":{"message":"[Obs
Onboarding] Add page rendering performance monitoring
(#213769)\n\nCloses
https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses
https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis
change add logic for triggering [the page rendering
performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n*
Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n*
Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1.
Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the
above mentioned onboarding screens\n4. Observe
`kibana:plugin_render_time` EBT event emitted in the Network\ntab of the
dev tools\n\nEvents emitted from local Kibana end up in the Staging
Telemetry\ncluster, there is a [dedicated rendering
performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding
events can be filtered using `observabilityOnboarding`\napplication ID.
(note that it takes some time for events to be indexed\nand they appear
in the cluster with a significant
delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4"}}]}]
BACKPORT-->

---------

Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-08 12:06:54 +02:00
Kibana Machine
b59647e5ef
[8.18] [Security Assistant] Don't cache MLClient (#217408) (#217416) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Assistant] Don't cache MLClient
(#217408)](https://github.com/elastic/kibana/pull/217408)

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

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

<!--BACKPORT [{"author":{"name":"Patryk
Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-04-07T23:25:45Z","message":"[Security
Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize
your PR. If it involves visual changes include a screenshot
or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Security
Assistant] Don't cache
MLClient","number":217408,"url":"https://github.com/elastic/kibana/pull/217408","mergeCommit":{"message":"[Security
Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize
your PR. If it involves visual changes include a screenshot
or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0"}},"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/217408","number":217408,"mergeCommit":{"message":"[Security
Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize
your PR. If it involves visual changes include a screenshot
or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0"}}]}]
BACKPORT-->

Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>
 2025-04-08 03:10:18 +02:00
Georgii Gorbachev
78a86c6f03
[8.18] [Security Solution] Improve documentation for version and revision fields (#216074) (#217341) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Improve documentation for `version` and
`revision` fields
(#216074)](https://github.com/elastic/kibana/pull/216074)

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

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

<!--BACKPORT [{"author":{"name":"Jacek
Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T18:06:13Z","message":"[Security
Solution] Improve documentation for `version` and `revision` fields
(#216074)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3545**\n\n##
Summary\n\nI am fixing documentation for the version and revision
fields.\nI used this page as the base
documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe
changes:\n- by marking the RuleVersion as read-only I am making sure we
are\nproperly documenting that this field is not to be used in the
request.\nIt is only returned in the response.\n- by introducing
RuleRevision type and marking it as read-only, I am\ndoing the same for
this field, saying that this field is not supposed to\nbe used in the
request.\n- I am not changing any code in the app, as the ticket says we
shouldn't\ndo any breaking changes and the update of the version should
not cause\n400 error. Basically current behavior is kept: users can
still update\nthe version to whatever value they want, including going
backwards, and\nthe changes to revision field is completely ignored.\n-
I am adding a condensed description of these fields.\n\nI wanted to
introduce an internal link between these two fields, but I\ncouldn't
make it work in Bump.sh (even though this should work, normal\nMarkdown
links) so I abandoned this idea.\n\nYou can also use this
[link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the
generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img
width=\"660\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","APIDocs","Team:Detection Rule Management","Feature:Prebuilt
Detection Rules","backport:version","9.1
candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Improve
documentation for `version` and `revision`
fields","number":216074,"url":"https://github.com/elastic/kibana/pull/216074","mergeCommit":{"message":"[Security
Solution] Improve documentation for `version` and `revision` fields
(#216074)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3545**\n\n##
Summary\n\nI am fixing documentation for the version and revision
fields.\nI used this page as the base
documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe
changes:\n- by marking the RuleVersion as read-only I am making sure we
are\nproperly documenting that this field is not to be used in the
request.\nIt is only returned in the response.\n- by introducing
RuleRevision type and marking it as read-only, I am\ndoing the same for
this field, saying that this field is not supposed to\nbe used in the
request.\n- I am not changing any code in the app, as the ticket says we
shouldn't\ndo any breaking changes and the update of the version should
not cause\n400 error. Basically current behavior is kept: users can
still update\nthe version to whatever value they want, including going
backwards, and\nthe changes to revision field is completely ignored.\n-
I am adding a condensed description of these fields.\n\nI wanted to
introduce an internal link between these two fields, but I\ncouldn't
make it work in Bump.sh (even though this should work, normal\nMarkdown
links) so I abandoned this idea.\n\nYou can also use this
[link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the
generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img
width=\"660\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},"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/216074","number":216074,"mergeCommit":{"message":"[Security
Solution] Improve documentation for `version` and `revision` fields
(#216074)\n\n**Resolves:
https://github.com/elastic/security-docs/issues/3545**\n\n##
Summary\n\nI am fixing documentation for the version and revision
fields.\nI used this page as the base
documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe
changes:\n- by marking the RuleVersion as read-only I am making sure we
are\nproperly documenting that this field is not to be used in the
request.\nIt is only returned in the response.\n- by introducing
RuleRevision type and marking it as read-only, I am\ndoing the same for
this field, saying that this field is not supposed to\nbe used in the
request.\n- I am not changing any code in the app, as the ticket says we
shouldn't\ndo any breaking changes and the update of the version should
not cause\n400 error. Basically current behavior is kept: users can
still update\nthe version to whatever value they want, including going
backwards, and\nthe changes to revision field is completely ignored.\n-
I am adding a condensed description of these fields.\n\nI wanted to
introduce an internal link between these two fields, but I\ncouldn't
make it work in Bump.sh (even though this should work, normal\nMarkdown
links) so I abandoned this idea.\n\nYou can also use this
[link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the
generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img
width=\"660\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216531","number":216531,"state":"MERGED","mergeCommit":{"sha":"a75155043b5f8cfd97907734b49ccd3ea1f9bca3","message":"[8.x]
[Security Solution] Improve documentation for `version` and `revision`
fields (#216074) (#216531)\n\n# Backport\n\nThis will backport the
following commits from `main` to `8.x`:\n- [[Security Solution] Improve
documentation for `version` and\n`revision`
fields\n(#216074)](https://github.com/elastic/kibana/pull/216074)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Jacek Kolezynski <jacek.kolezynski@elastic.co>"}}]}] BACKPORT-->

Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>
 2025-04-07 18:17:27 +02:00
Sergi Massaneda
dd7dae0f16
[8.18] [Security Solution] Onboarding check inference endpoint (#217150) (#217335) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Onboarding check inference endpoint
(#217150)](https://github.com/elastic/kibana/pull/217150)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T13:43:39Z","message":"[Security
Solution] Onboarding check inference endpoint (#217150)\n\n##
Summary\n\nThis PR checks that the inference endpoint exists before
showing the\ninference connector in the list of selectable
connectors.\n\nAlso, it removes code duplication by centralizing the
implementation in\nthe /common/connectors directory of the onboarding
cards\n\n\n![siem_migrations_connector_card](99ddd69d-18c7-41be-bec0-45524d718d08)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting","Team:Threat
Hunting:Explore","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security
Solution] Onboarding check inference
endpoint","number":217150,"url":"https://github.com/elastic/kibana/pull/217150","mergeCommit":{"message":"[Security
Solution] Onboarding check inference endpoint (#217150)\n\n##
Summary\n\nThis PR checks that the inference endpoint exists before
showing the\ninference connector in the list of selectable
connectors.\n\nAlso, it removes code duplication by centralizing the
implementation in\nthe /common/connectors directory of the onboarding
cards\n\n\n![siem_migrations_connector_card](99ddd69d-18c7-41be-bec0-45524d718d08)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c"}},"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/217150","number":217150,"mergeCommit":{"message":"[Security
Solution] Onboarding check inference endpoint (#217150)\n\n##
Summary\n\nThis PR checks that the inference endpoint exists before
showing the\ninference connector in the list of selectable
connectors.\n\nAlso, it removes code duplication by centralizing the
implementation in\nthe /common/connectors directory of the onboarding
cards\n\n\n![siem_migrations_connector_card](99ddd69d-18c7-41be-bec0-45524d718d08)\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-07 17:59:41 +02:00
Kibana Machine
2334c67609
[8.18] [Synthetics] Fixed alert count in monitor details (#216761) (#217337) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Francesco
Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-07T13:47:40Z","message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics]
Fixed alert count in monitor
details","number":216761,"url":"https://github.com/elastic/kibana/pull/216761","mergeCommit":{"message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216761","number":216761,"mergeCommit":{"message":"[Synthetics]
Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328
\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38
42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img
width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38
21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
 2025-04-07 17:52:06 +02:00
Abdul Wahab Zahid
1ffaddb6a8
[8.18] [Performance] Refactor TTFMP query from, to fields (#213911) (#217091) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Performance] Refactor TTFMP query `from`, `to` fields
(#213911)](https://github.com/elastic/kibana/pull/213911)

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

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

<!--BACKPORT [{"author":{"name":"Abdul Wahab
Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-03-20T10:40:24Z","message":"[Performance]
Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana
forwards `query_range_secs` and `query_offset_secs` to\nmark the
selected time range when reporting TTFMP event. This format\ncaused some
challenges to identify `from`, `to` date offsets
in\nvisualizations.\n\nTo simplify, the PR renames and sends the three
fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with
-ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset
to `0` (now), with -ve for past and +ve\nfor future dates\n-
`query_range_secs` same as previously sent\n\n_This approach is followed
after a discussion, and based on
the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest
date -> QueryFrom\nNewest date -> QueryTo\nDuration ->
QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in
the EBT indexer to ingest in the\ntop level of the document, eventually
removing the need to create\nruntime fields in data views for
visualizations.\n\nAlso, runtime fields in data views should be updated
to reflect this\nchange. For backward compatibility, the runtime fields
can cater both\nthe old and new field names conditionally.\n\n###
Testing\n- Ensure that the TTFMP events are correctly reporting the date
ranges.\n\n###
Example\n\n![image](https://github.com/user-attachments/assets/529507fc-66f7-440a-8bbb-b34176e8d093)","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","v9.1.0","v8.19.0"],"title":"[Performance] Refactor TTFMP query
`from`, `to`
fields","number":213911,"url":"https://github.com/elastic/kibana/pull/213911","mergeCommit":{"message":"[Performance]
Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana
forwards `query_range_secs` and `query_offset_secs` to\nmark the
selected time range when reporting TTFMP event. This format\ncaused some
challenges to identify `from`, `to` date offsets
in\nvisualizations.\n\nTo simplify, the PR renames and sends the three
fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with
-ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset
to `0` (now), with -ve for past and +ve\nfor future dates\n-
`query_range_secs` same as previously sent\n\n_This approach is followed
after a discussion, and based on
the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest
date -> QueryFrom\nNewest date -> QueryTo\nDuration ->
QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in
the EBT indexer to ingest in the\ntop level of the document, eventually
removing the need to create\nruntime fields in data views for
visualizations.\n\nAlso, runtime fields in data views should be updated
to reflect this\nchange. For backward compatibility, the runtime fields
can cater both\nthe old and new field names conditionally.\n\n###
Testing\n- Ensure that the TTFMP events are correctly reporting the date
ranges.\n\n###
Example\n\n![image](https://github.com/user-attachments/assets/529507fc-66f7-440a-8bbb-b34176e8d093)","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e"}},"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/213911","number":213911,"mergeCommit":{"message":"[Performance]
Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana
forwards `query_range_secs` and `query_offset_secs` to\nmark the
selected time range when reporting TTFMP event. This format\ncaused some
challenges to identify `from`, `to` date offsets
in\nvisualizations.\n\nTo simplify, the PR renames and sends the three
fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with
-ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset
to `0` (now), with -ve for past and +ve\nfor future dates\n-
`query_range_secs` same as previously sent\n\n_This approach is followed
after a discussion, and based on
the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest
date -> QueryFrom\nNewest date -> QueryTo\nDuration ->
QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in
the EBT indexer to ingest in the\ntop level of the document, eventually
removing the need to create\nruntime fields in data views for
visualizations.\n\nAlso, runtime fields in data views should be updated
to reflect this\nchange. For backward compatibility, the runtime fields
can cater both\nthe old and new field names conditionally.\n\n###
Testing\n- Ensure that the TTFMP events are correctly reporting the date
ranges.\n\n###
Example\n\n![image](https://github.com/user-attachments/assets/529507fc-66f7-440a-8bbb-b34176e8d093)","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217090","number":217090,"state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217089","number":217089,"branch":"9.0","state":"OPEN"}]}]
BACKPORT-->
 2025-04-07 18:46:29 +03:00
Kibana Machine
b5d0c87af1
[8.18] [APM][OTel] Fix layers issue for ESQL visualization by adding textBased layers (#216358) (#217321) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[APM][OTel] Fix layers issue for ESQL visualization by adding
`textBased` layers
(#216358)](https://github.com/elastic/kibana/pull/216358)

<!--- 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-07T13:20:12Z","message":"[APM][OTel]
Fix layers issue for ESQL visualization by adding `textBased` layers
(#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue
with the ESQL visualization by supporting\n`textBased` layers. For
testing, there is a link to the serverless env\nof this PR and it should
be tested EDOT Java SDK as shown in [the\nscreenshot in
this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by:
Jonas Kunz
<j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd","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:cloud-redeploy","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel]
Fix layers issue for ESQL visualization by adding `textBased`
layers","number":216358,"url":"https://github.com/elastic/kibana/pull/216358","mergeCommit":{"message":"[APM][OTel]
Fix layers issue for ESQL visualization by adding `textBased` layers
(#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue
with the ESQL visualization by supporting\n`textBased` layers. For
testing, there is a link to the serverless env\nof this PR and it should
be tested EDOT Java SDK as shown in [the\nscreenshot in
this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by:
Jonas Kunz
<j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd"}},"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/216358","number":216358,"mergeCommit":{"message":"[APM][OTel]
Fix layers issue for ESQL visualization by adding `textBased` layers
(#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue
with the ESQL visualization by supporting\n`textBased` layers. For
testing, there is a link to the serverless env\nof this PR and it should
be tested EDOT Java SDK as shown in [the\nscreenshot in
this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by:
Jonas Kunz
<j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd"}}]}]
BACKPORT-->

Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
 2025-04-07 17:27:25 +02:00
Georgii Gorbachev
0e90f2d2f2
[8.18] [Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367) (#217305) 
# Backport

This will backport the following commits from `main` to `8.18`:
- [[Security Solution] Migrate legacy Detections API docs to OpenAPI
specs (#212367)](https://github.com/elastic/kibana/pull/212367)

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

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

<!--BACKPORT [{"author":{"name":"Jacek
Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T13:43:02Z","message":"[Security
Solution] Migrate legacy Detections API docs to OpenAPI specs
(#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is
the first part of the migration effort, containing changes for:\n- CRUD
endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List
Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the
description of the fields. Some of the\nfields contained description
that was very similar to the legacy, then I\ndidn't change it. I only
modified the descriptions where it was\nvaluable.\n\nI also discovered
some problems. For example the value for the 'query'\nfield, always
shows 'EQL query to execute'. I reported this to the docs\nteam, in the
'next-api-reference' channel.\n\nAnother issue was with
'related_integrations field', which also didn't\nshow the long
description. I also wrote about it to the docs
team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn
this PR I decided to try moving the description one level up, where\nit
renders properly.\n\n\n# Testing\n1. cd
x-pack/solutions/security/plugins/security_solution\n2. yarn
openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","APIDocs","Team:Detection Rule
Management","backport:version","8.18
candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Migrate
legacy Detections API docs to OpenAPI
specs","number":212367,"url":"https://github.com/elastic/kibana/pull/212367","mergeCommit":{"message":"[Security
Solution] Migrate legacy Detections API docs to OpenAPI specs
(#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is
the first part of the migration effort, containing changes for:\n- CRUD
endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List
Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the
description of the fields. Some of the\nfields contained description
that was very similar to the legacy, then I\ndidn't change it. I only
modified the descriptions where it was\nvaluable.\n\nI also discovered
some problems. For example the value for the 'query'\nfield, always
shows 'EQL query to execute'. I reported this to the docs\nteam, in the
'next-api-reference' channel.\n\nAnother issue was with
'related_integrations field', which also didn't\nshow the long
description. I also wrote about it to the docs
team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn
this PR I decided to try moving the description one level up, where\nit
renders properly.\n\n\n# Testing\n1. cd
x-pack/solutions/security/plugins/security_solution\n2. yarn
openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},"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/212367","number":212367,"mergeCommit":{"message":"[Security
Solution] Migrate legacy Detections API docs to OpenAPI specs
(#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is
the first part of the migration effort, containing changes for:\n- CRUD
endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List
Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the
description of the fields. Some of the\nfields contained description
that was very similar to the legacy, then I\ndidn't change it. I only
modified the descriptions where it was\nvaluable.\n\nI also discovered
some problems. For example the value for the 'query'\nfield, always
shows 'EQL query to execute'. I reported this to the docs\nteam, in the
'next-api-reference' channel.\n\nAnother issue was with
'related_integrations field', which also didn't\nshow the long
description. I also wrote about it to the docs
team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn
this PR I decided to try moving the description one level up, where\nit
renders properly.\n\n\n# Testing\n1. cd
x-pack/solutions/security/plugins/security_solution\n2. yarn
openapi:bundle:detections \n3. Take the bundled
file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand
load it into bump.sh console to see the changes.\n4. Compare the changes
with the
[Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou
can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere
I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216734","number":216734,"state":"MERGED","mergeCommit":{"sha":"9c8b23ad7b5cf5025506e1d51fa22d7de7194305","message":"[8.x]
[Security Solution] Migrate legacy Detections API docs to OpenAPI specs
(#212367) (#216734)\n\n# Backport\n\nThis will backport the following
commits from `main` to `8.x`:\n- [[Security Solution] Migrate legacy
Detections API docs to OpenAPI\nspecs
(#212367)](https://github.com/elastic/kibana/pull/212367)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Jacek Kolezynski <jacek.kolezynski@elastic.co>"}}]}] BACKPORT-->

---------

Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2025-04-07 15:55:08 +02:00
Kevin Delemme
a0f92a2a00
[8.18] fix(slo): group by with empty string (#217084) (#217206) 
# Backport

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

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

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

<!--BACKPORT [{"author":{"name":"Kevin
Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T20:41:56Z","message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"fix(slo):
group by with empty
string","number":217084,"url":"https://github.com/elastic/kibana/pull/217084","mergeCommit":{"message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217110","number":217110,"state":"MERGED","mergeCommit":{"sha":"f5054deba36b1843262c64d27c8d0827f96b50bc","message":"[9.0]
fix(slo): group by with empty string (#217084) (#217110)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`9.0`:\n- [fix(slo): group by with empty
string\n(#217084)](https://github.com/elastic/kibana/pull/217084)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Kevin Delemme
<kevin.delemme@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217084","number":217084,"mergeCommit":{"message":"fix(slo):
group by with empty string
(#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2025-04-04 17:13:07 +01:00