Update preconfigured connector name #217570#217712
Closed
alvarezmelissa87 wants to merge 4694 commits intoelastic:mainfrom
Closed
Update preconfigured connector name #217570#217712alvarezmelissa87 wants to merge 4694 commits intoelastic:mainfrom
alvarezmelissa87 wants to merge 4694 commits intoelastic:mainfrom
Conversation
# Backport This will backport the following commits from `main` to `8.18`: - [[Chore] Remove unused module (elastic#214018)](elastic#214018) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Thomas Neirynck","email":"thomas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T14:25:36Z","message":"[Chore] Remove unused module (elastic#214018)\n\n## Summary\n\nRemove unused module.\n\nI noticed this doing some investigations, and thought to tidy this up.\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]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"bac2f0c6bdf386ce9bdced2f95f2ab4bcf67f1ce","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","backport:prev-major","v9.1.0"],"title":"[Chore] Remove unused module","number":214018,"url":"https://github.com/elastic/kibana/pull/214018","mergeCommit":{"message":"[Chore] Remove unused module (elastic#214018)\n\n## Summary\n\nRemove unused module.\n\nI noticed this doing some investigations, and thought to tidy this up.\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]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"bac2f0c6bdf386ce9bdced2f95f2ab4bcf67f1ce"}},"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/214018","number":214018,"mergeCommit":{"message":"[Chore] Remove unused module (elastic#214018)\n\n## Summary\n\nRemove unused module.\n\nI noticed this doing some investigations, and thought to tidy this up.\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]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"bac2f0c6bdf386ce9bdced2f95f2ab4bcf67f1ce"}}]}] BACKPORT--> Co-authored-by: Thomas Neirynck <thomas@elastic.co>
…ing callout message (elastic#213995) (elastic#214197) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Adds check for license level for rule editing callout message (elastic#213995)](elastic#213995) <!--- 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-03-12T15:03:38Z","message":"[Security Solution] Adds check for license level for rule editing callout message (elastic#213995)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213983\n\nAdds gating logic to only display the rule upgrade related warning\ncallout on the rule editing page if the user has the appropriate license\nlevel, otherwise the message is irrelevant as the user wouldn't be able\nto edit a prebuilt rule in the way the message refers to\n\n### Testing\n\n**Steps to reproduce:**\n\n1. Use a Platinum license or any tier that does not allow prebuilt rule\nupdates.\n2. Navigate to the Rule Management page and select a prebuilt rule with\nan available update.\n3. Open Rule Details page -> Edit rule settings\n4. Observe the callout message is not displayed at the top of the page\n\nNOTE: When using the enterprise license, the callout should still be\ndisplayed","sha":"0485578022006a183c5d0db1dd3a404ba2bff015","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","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Adds check for license level for rule editing callout message","number":213995,"url":"https://github.com/elastic/kibana/pull/213995","mergeCommit":{"message":"[Security Solution] Adds check for license level for rule editing callout message (elastic#213995)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213983\n\nAdds gating logic to only display the rule upgrade related warning\ncallout on the rule editing page if the user has the appropriate license\nlevel, otherwise the message is irrelevant as the user wouldn't be able\nto edit a prebuilt rule in the way the message refers to\n\n### Testing\n\n**Steps to reproduce:**\n\n1. Use a Platinum license or any tier that does not allow prebuilt rule\nupdates.\n2. Navigate to the Rule Management page and select a prebuilt rule with\nan available update.\n3. Open Rule Details page -> Edit rule settings\n4. Observe the callout message is not displayed at the top of the page\n\nNOTE: When using the enterprise license, the callout should still be\ndisplayed","sha":"0485578022006a183c5d0db1dd3a404ba2bff015"}},"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/213995","number":213995,"mergeCommit":{"message":"[Security Solution] Adds check for license level for rule editing callout message (elastic#213995)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213983\n\nAdds gating logic to only display the rule upgrade related warning\ncallout on the rule editing page if the user has the appropriate license\nlevel, otherwise the message is irrelevant as the user wouldn't be able\nto edit a prebuilt rule in the way the message refers to\n\n### Testing\n\n**Steps to reproduce:**\n\n1. Use a Platinum license or any tier that does not allow prebuilt rule\nupdates.\n2. Navigate to the Rule Management page and select a prebuilt rule with\nan available update.\n3. Open Rule Details page -> Edit rule settings\n4. Observe the callout message is not displayed at the top of the page\n\nNOTE: When using the enterprise license, the callout should still be\ndisplayed","sha":"0485578022006a183c5d0db1dd3a404ba2bff015"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>
…tic#213834) (elastic#214221) # Backport This will backport the following commits from `main` to `8.18`: - [[Logs UI] Make logs ui categories page tests more robust (elastic#213834)](elastic#213834) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T16:08:11Z","message":"[Logs UI] Make logs ui categories page tests more robust (elastic#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Logs UI","release_note:skip","backport:all-open","Team:obs-ux-logs","v9.1.0"],"title":"[Logs UI] Make logs ui categories page tests more robust","number":213834,"url":"https://github.com/elastic/kibana/pull/213834","mergeCommit":{"message":"[Logs UI] Make logs ui categories page tests more robust (elastic#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e"}},"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/213834","number":213834,"mergeCommit":{"message":"[Logs UI] Make logs ui categories page tests more robust (elastic#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e"}}]}] BACKPORT--> Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com>
…options (elastic#213970) (elastic#214206) # Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Update description on data reduction advanced options (elastic#213970)](elastic#213970) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T15:42:27Z","message":"[EDR Workflows] Update description on data reduction advanced options (elastic#213970)\n\n## Summary\n\n- refines description for\n- 9 `(win|mac|linux).advanced.events.hash.(md5|sha1|sha256)`:\n9e7bbcf767a47795ef1e791ba4f88045526ac90d\n> Compute and include (MD5|SHA-1|SHA-256) hashes for processes and\nlibraries in events? This will increase CPU usage and event sizes. If\nany user event filter or trustlists reference this hash type, Endpoint\nwill ignore this setting and automatically enable this hash type.\n- 6 `(win|mac|linux).advanced.alerts.hash.(md5|sha1)`:\n8fc0f51ab45ffc2430683f0b05773a91e0a63717\n> Compute and include (MD5|SHA-1) hashes for processes and libraries in\nalerts? This will increase CPU usage and alert sizes. If any user\nexceptionlist, trustlist, or blocklists reference this hash type,\nEndpoint will ignore this setting and automatically enable this hash\ntype.\n- provides a 'history' for default behavior changes (e.g. `<=8.17\ndefault: true, >=8.18 default: false`) for\n- 12 `(win|mac|linux).advanced.(events|alerts).hash.(md5|sha1)`:\n05b0ebe8eab1a5f010f8a995454ffb05dfd502d8\n (note that events sha256 is not changed)\n > <=8.17 default: true, >=8.18 default: false\n- 3 `(win|mac|linux).advanced.events.aggregate_process`:\n5984d8e90a43127c93c367286d727c489612c90e\n > <=8.17 default: false, >=8.18 default: true\n- 3 `(win|mac|linux).advanced.events.set_extended_host_information`:\n5da25a3592409b5bfbc7b7256312f2b3f67fe1b5\n > <=8.17 default: true, >=8.18 default: false\n\n> [!IMPORTANT]\n> The plan is to backport this PR to all open branches:\n> - `8.18`/`8.x`/`9.0`/`main` will contain all modifications,\n> - but `8.16`/`8.17` manual backports will only contain the description\nrefinement\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)","sha":"ad3b7fce112d8dc0e28c847937458bf2d455fba2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Update description on data reduction advanced options","number":213970,"url":"https://github.com/elastic/kibana/pull/213970","mergeCommit":{"message":"[EDR Workflows] Update description on data reduction advanced options (elastic#213970)\n\n## Summary\n\n- refines description for\n- 9 `(win|mac|linux).advanced.events.hash.(md5|sha1|sha256)`:\n9e7bbcf767a47795ef1e791ba4f88045526ac90d\n> Compute and include (MD5|SHA-1|SHA-256) hashes for processes and\nlibraries in events? This will increase CPU usage and event sizes. If\nany user event filter or trustlists reference this hash type, Endpoint\nwill ignore this setting and automatically enable this hash type.\n- 6 `(win|mac|linux).advanced.alerts.hash.(md5|sha1)`:\n8fc0f51ab45ffc2430683f0b05773a91e0a63717\n> Compute and include (MD5|SHA-1) hashes for processes and libraries in\nalerts? This will increase CPU usage and alert sizes. If any user\nexceptionlist, trustlist, or blocklists reference this hash type,\nEndpoint will ignore this setting and automatically enable this hash\ntype.\n- provides a 'history' for default behavior changes (e.g. `<=8.17\ndefault: true, >=8.18 default: false`) for\n- 12 `(win|mac|linux).advanced.(events|alerts).hash.(md5|sha1)`:\n05b0ebe8eab1a5f010f8a995454ffb05dfd502d8\n (note that events sha256 is not changed)\n > <=8.17 default: true, >=8.18 default: false\n- 3 `(win|mac|linux).advanced.events.aggregate_process`:\n5984d8e90a43127c93c367286d727c489612c90e\n > <=8.17 default: false, >=8.18 default: true\n- 3 `(win|mac|linux).advanced.events.set_extended_host_information`:\n5da25a3592409b5bfbc7b7256312f2b3f67fe1b5\n > <=8.17 default: true, >=8.18 default: false\n\n> [!IMPORTANT]\n> The plan is to backport this PR to all open branches:\n> - `8.18`/`8.x`/`9.0`/`main` will contain all modifications,\n> - but `8.16`/`8.17` manual backports will only contain the description\nrefinement\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)","sha":"ad3b7fce112d8dc0e28c847937458bf2d455fba2"}},"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/213970","number":213970,"mergeCommit":{"message":"[EDR Workflows] Update description on data reduction advanced options (elastic#213970)\n\n## Summary\n\n- refines description for\n- 9 `(win|mac|linux).advanced.events.hash.(md5|sha1|sha256)`:\n9e7bbcf767a47795ef1e791ba4f88045526ac90d\n> Compute and include (MD5|SHA-1|SHA-256) hashes for processes and\nlibraries in events? This will increase CPU usage and event sizes. If\nany user event filter or trustlists reference this hash type, Endpoint\nwill ignore this setting and automatically enable this hash type.\n- 6 `(win|mac|linux).advanced.alerts.hash.(md5|sha1)`:\n8fc0f51ab45ffc2430683f0b05773a91e0a63717\n> Compute and include (MD5|SHA-1) hashes for processes and libraries in\nalerts? This will increase CPU usage and alert sizes. If any user\nexceptionlist, trustlist, or blocklists reference this hash type,\nEndpoint will ignore this setting and automatically enable this hash\ntype.\n- provides a 'history' for default behavior changes (e.g. `<=8.17\ndefault: true, >=8.18 default: false`) for\n- 12 `(win|mac|linux).advanced.(events|alerts).hash.(md5|sha1)`:\n05b0ebe8eab1a5f010f8a995454ffb05dfd502d8\n (note that events sha256 is not changed)\n > <=8.17 default: true, >=8.18 default: false\n- 3 `(win|mac|linux).advanced.events.aggregate_process`:\n5984d8e90a43127c93c367286d727c489612c90e\n > <=8.17 default: false, >=8.18 default: true\n- 3 `(win|mac|linux).advanced.events.set_extended_host_information`:\n5da25a3592409b5bfbc7b7256312f2b3f67fe1b5\n > <=8.17 default: true, >=8.18 default: false\n\n> [!IMPORTANT]\n> The plan is to backport this PR to all open branches:\n> - `8.18`/`8.x`/`9.0`/`main` will contain all modifications,\n> - but `8.16`/`8.17` manual backports will only contain the description\nrefinement\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)","sha":"ad3b7fce112d8dc0e28c847937458bf2d455fba2"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
…erence URLs" when base version is missing (elastic#214161) (elastic#214252) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Force upgrading to target version for "Reference URLs" when base version is missing (elastic#214161)](elastic#214161) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:41:32Z","message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (elastic#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing","number":214161,"url":"https://github.com/elastic/kibana/pull/214161","mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (elastic#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},"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/214161","number":214161,"mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (elastic#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
Integrating latest translations extracted from 8.18 branch. Skipping backports from main to target branches since the `i18n_check` might trim unused translations that are still used in different branches. Integration script is ran against each target branch separately.
…stic#212560) (elastic#213967) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Siem migrations Onboarding UI changes (elastic#212560)](elastic#212560) <!--- 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-03-11T15:51:30Z","message":"[Security Solution] Siem migrations Onboarding UI changes (elastic#212560)\n\n## Summary\n\n1/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n\n**Pending**\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\n**Processing**\n\nOld\n\n\n\nNew\n\n\n\n**Results**\n\nOld\n\n\n\nNew\n\n\n\n**Connectors**\n\nText changes when the EIS connector is selected\n\n\nhttps://github.com/user-attachments/assets/f819c379-42a1-4dc8-b320-aa5fd5b7639a","sha":"b7412d94e76407477250cec38c01242f9e771000","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","ci:cloud-deploy","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Siem migrations Onboarding UI changes ","number":212560,"url":"https://github.com/elastic/kibana/pull/212560","mergeCommit":{"message":"[Security Solution] Siem migrations Onboarding UI changes (elastic#212560)\n\n## Summary\n\n1/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n\n**Pending**\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\n**Processing**\n\nOld\n\n\n\nNew\n\n\n\n**Results**\n\nOld\n\n\n\nNew\n\n\n\n**Connectors**\n\nText changes when the EIS connector is selected\n\n\nhttps://github.com/user-attachments/assets/f819c379-42a1-4dc8-b320-aa5fd5b7639a","sha":"b7412d94e76407477250cec38c01242f9e771000"}},"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/213963","number":213963,"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/212560","number":212560,"mergeCommit":{"message":"[Security Solution] Siem migrations Onboarding UI changes (elastic#212560)\n\n## Summary\n\n1/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n\n**Pending**\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\n**Processing**\n\nOld\n\n\n\nNew\n\n\n\n**Results**\n\nOld\n\n\n\nNew\n\n\n\n**Connectors**\n\nText changes when the EIS connector is selected\n\n\nhttps://github.com/user-attachments/assets/f819c379-42a1-4dc8-b320-aa5fd5b7639a","sha":"b7412d94e76407477250cec38c01242f9e771000"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…tic#214028) (elastic#214272) # Backport This will backport the following commits from `main` to `8.18`: - [Alerts table in Rule Preview panel fills container width (elastic#214028)](elastic#214028) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-12T19:21:33Z","message":"Alerts table in Rule Preview panel fills container width (elastic#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when elastic#206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Feature:Detection Rule Preview","backport:prev-minor","backport:prev-major","Team:Detection Engine","v8.18.0","v9.1.0"],"title":"Alerts table in Rule Preview panel fills container width","number":214028,"url":"https://github.com/elastic/kibana/pull/214028","mergeCommit":{"message":"Alerts table in Rule Preview panel fills container width (elastic#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when elastic#206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"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/214028","number":214028,"mergeCommit":{"message":"Alerts table in Rule Preview panel fills container width (elastic#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when elastic#206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com>
…o 69a0542 (8.18) (elastic#214064) This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `a37e513` -> `69a0542` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://github.com/giggio/node-chromedriver) | devDependencies | major | [`^133.0.2` -> `^134.0.0`](https://renovatebot.com/diffs/npm/chromedriver/133.0.3/134.0.0) | `134.0.2` (+1) | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v134.0.0`](https://github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) [Compare Source](https://github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
… flyout (elastic#213975) (elastic#214316) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Siem migrations copy changes in the upload flyout (elastic#213975)](elastic#213975) <!--- 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-03-12T14:58:33Z","message":"[Security Solution] Siem migrations copy changes in the upload flyout (elastic#213975)\n\n## Summary\n\n## Summary\n\n2/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n\n**Pending**\n- UI changes in the translated rules page\n\n### Screenshots\n\n\n\n\n\n\n\n\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"065790e20a335f049a51b928e0bdc67e3da01984","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","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Siem migrations copy changes in the upload flyout","number":213975,"url":"https://github.com/elastic/kibana/pull/213975","mergeCommit":{"message":"[Security Solution] Siem migrations copy changes in the upload flyout (elastic#213975)\n\n## Summary\n\n## Summary\n\n2/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n\n**Pending**\n- UI changes in the translated rules page\n\n### Screenshots\n\n\n\n\n\n\n\n\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"065790e20a335f049a51b928e0bdc67e3da01984"}},"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/214194","number":214194,"state":"MERGED","mergeCommit":{"sha":"7e0b240a4c0768d8496d1f0963e780fb14586cfe","message":"[9.0] [Security Solution] Siem migrations copy changes in the upload flyout (elastic#213975) (elastic#214194)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Security Solution] Siem migrations copy changes in the upload flyout\n(elastic#213975)](https://github.com/elastic/kibana/pull/213975)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213975","number":213975,"mergeCommit":{"message":"[Security Solution] Siem migrations copy changes in the upload flyout (elastic#213975)\n\n## Summary\n\n## Summary\n\n2/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n\n**Pending**\n- UI changes in the translated rules page\n\n### Screenshots\n\n\n\n\n\n\n\n\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"065790e20a335f049a51b928e0bdc67e3da01984"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214281","number":214281,"state":"OPEN"}]}] BACKPORT-->
…#214295) # Backport This will backport the following commits from `main` to `8.18`: - [[Feature Flags] Retry provider setup (elastic#214200)](elastic#214200) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T21:45:38Z","message":"[Feature Flags] Retry provider setup (elastic#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] Retry provider setup","number":214200,"url":"https://github.com/elastic/kibana/pull/214200","mergeCommit":{"message":"[Feature Flags] Retry provider setup (elastic#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}},"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/214200","number":214200,"mergeCommit":{"message":"[Feature Flags] Retry provider setup (elastic#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}},{"url":"https://github.com/elastic/kibana/pull/214288","number":214288,"branch":"9.0","state":"OPEN"}]}] BACKPORT-->
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2436 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
) (elastic#214168) # Backport This will backport the following commits from `main` to `8.18`: - [[Siem Migrations] Add Translated Rules Empty Page (elastic#213438)](elastic#213438) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T13:59:12Z","message":"[Siem Migrations] Add Translated Rules Empty Page (elastic#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ExpressionLanguage","release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migrations] Add Translated Rules Empty Page","number":213438,"url":"https://github.com/elastic/kibana/pull/213438","mergeCommit":{"message":"[Siem Migrations] Add Translated Rules Empty Page (elastic#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25"}},"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/213438","number":213438,"mergeCommit":{"message":"[Siem Migrations] Add Translated Rules Empty Page (elastic#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>
…#214344) # Backport This will backport the following commits from `main` to `8.18`: - [[Feature Flags] ECS-compliant logger (elastic#214231)](elastic#214231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T23:24:40Z","message":"[Feature Flags] ECS-compliant logger (elastic#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] ECS-compliant logger","number":214231,"url":"https://github.com/elastic/kibana/pull/214231","mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (elastic#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214304","number":214304,"state":"MERGED","mergeCommit":{"sha":"fa04dc0e0536ced502e3eb8993aa7ba227f7299d","message":"[9.0] [Feature Flags] ECS-compliant logger (elastic#214231) (elastic#214304)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Feature Flags] ECS-compliant logger\n(elastic#214231)](https://github.com/elastic/kibana/pull/214231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214231","number":214231,"mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (elastic#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}}]}] BACKPORT-->
…dal on basic license (elastic#214340) (elastic#214383) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Avoid showing rules update confirmation modal on basic license (elastic#214340)](elastic#214340) <!--- 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-03-13T13:47:30Z","message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (elastic#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](elastic#214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Avoid showing rules update confirmation modal on basic license","number":214340,"url":"https://github.com/elastic/kibana/pull/214340","mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (elastic#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](elastic#214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},"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/214340","number":214340,"mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (elastic#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](elastic#214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
…lastic#214033) # Backport This will backport the following commits from `main` to `8.18`: - [Add minimal user session management API docs (elastic#212576)](elastic#212576) <!--- 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-03-11T22:47:07Z","message":"Add minimal user session management API docs (elastic#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"Add minimal user session management API docs","number":212576,"url":"https://github.com/elastic/kibana/pull/212576","mergeCommit":{"message":"Add minimal user session management API docs (elastic#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"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/212576","number":212576,"mergeCommit":{"message":"Add minimal user session management API docs (elastic#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43"}},{"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,"url":"https://github.com/elastic/kibana/pull/214030","number":214030,"state":"OPEN"}]}] BACKPORT-->
…ic#214394) # Backport This will backport the following commits from `main` to `8.18`: - [[Security solution] Bedrock region fix (elastic#214251)](elastic#214251) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:01:03Z","message":"[Security solution] Bedrock region fix (elastic#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[Security solution] Bedrock region fix","number":214251,"url":"https://github.com/elastic/kibana/pull/214251","mergeCommit":{"message":"[Security solution] Bedrock region fix (elastic#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214251","number":214251,"mergeCommit":{"message":"[Security solution] Bedrock region fix (elastic#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214388","number":214388,"state":"OPEN"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…) (elastic#214289) # Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Never delete @Custom component templates (elastic#214232)](elastic#214232) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T19:58:40Z","message":"[Fleet] Never delete @Custom component templates (elastic#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:version","v9.1.0","backport:8.18","v8.18.1"],"title":"[Fleet] Never delete @Custom component templates","number":214232,"url":"https://github.com/elastic/kibana/pull/214232","mergeCommit":{"message":"[Fleet] Never delete @Custom component templates (elastic#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}},"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/214279","number":214279,"state":"MERGED","mergeCommit":{"sha":"ffc575724f73009d5d564b7c896ab162e7880c4e","message":"[9.0] [Fleet] Never delete @Custom component templates (elastic#214232) (elastic#214279)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Never delete @Custom component templates\n(elastic#214232)](https://github.com/elastic/kibana/pull/214232)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214232","number":214232,"mergeCommit":{"message":"[Fleet] Never delete @Custom component templates (elastic#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>
…on is not enabled (elastic#214365) (elastic#214407) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Hide conflict badges when rule customization is not enabled (elastic#214365)](elastic#214365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:52:48Z","message":"[Security Solution] Hide conflict badges when rule customization is not enabled (elastic#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37","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","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Hide conflict badges when rule customization is not enabled","number":214365,"url":"https://github.com/elastic/kibana/pull/214365","mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (elastic#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},"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/214365","number":214365,"mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (elastic#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
…use case header (elastic#214269) (elastic#214429) # Backport This will backport the following commits from `main` to `8.18`: - [[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (elastic#214269)](elastic#214269) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:44:06Z","message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (elastic#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e","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","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header","number":214269,"url":"https://github.com/elastic/kibana/pull/214269","mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (elastic#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},"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/214269","number":214269,"mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (elastic#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
…oard (elastic#214356) (elastic#214419) # Backport This will backport the following commits from `main` to `8.18`: - [[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (elastic#214356)](elastic#214356) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:20:17Z","message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (elastic#214356)\n\nCloses elastic#214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n-⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard","number":214356,"url":"https://github.com/elastic/kibana/pull/214356","mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (elastic#214356)\n\nCloses elastic#214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n-⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}},"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/214356","number":214356,"mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (elastic#214356)\n\nCloses elastic#214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n-⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
…stic#214360) (elastic#214451) # Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] fix UI bug displaying default agent binary source (elastic#214360)](elastic#214360) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T17:01:08Z","message":"[Fleet] fix UI bug displaying default agent binary source (elastic#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] fix UI bug displaying default agent binary source","number":214360,"url":"https://github.com/elastic/kibana/pull/214360","mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (elastic#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}},"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/214360","number":214360,"mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (elastic#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
… (elastic#214296) # Backport This will backport the following commits from `main` to `8.18`: - [[Stack Monitoring] New FTR for "view logs" link (elastic#208351)](elastic#208351) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T22:35:28Z","message":"[Stack Monitoring] New FTR for \"view logs\" link (elastic#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](elastic#199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","FTR","v8.18.0","v8.17.2","v9.1.0"],"title":"[Stack Monitoring] New FTR for \"view logs\" link","number":208351,"url":"https://github.com/elastic/kibana/pull/208351","mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (elastic#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](elastic#199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/208351","number":208351,"mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (elastic#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](elastic#199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co>
… for Cloud Environments (elastic#214404) (elastic#214460) # Backport This will backport the following commits from `8.x` to `8.18`: - [[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (elastic#214404)](elastic#214404) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark J. Hoy","email":"mark.hoy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T17:34:45Z","message":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (elastic#214404)\n\n## Summary\n\nUpdates the text for the flyout for the Enterprise Search node\ndeprecation. The text includes verbiage asking the user to remove the\nconfiguration variables for Enterprise Search - in Cloud environments,\nthis is taken care of already for the user when the node is removed from\nthe deployment. This PR just hides that text (it will still show in\nnon-Cloud environments)\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] 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.","sha":"e7e92547656be37e1b4725e39f0d174717f57e95","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Upgrade Assistant","Team:EnterpriseSearch","v8.19.0","backport:8.18","v8.18.1"],"title":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments","number":214404,"url":"https://github.com/elastic/kibana/pull/214404","mergeCommit":{"message":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (elastic#214404)\n\n## Summary\n\nUpdates the text for the flyout for the Enterprise Search node\ndeprecation. The text includes verbiage asking the user to remove the\nconfiguration variables for Enterprise Search - in Cloud environments,\nthis is taken care of already for the user when the node is removed from\nthe deployment. This PR just hides that text (it will still show in\nnon-Cloud environments)\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] 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.","sha":"e7e92547656be37e1b4725e39f0d174717f57e95"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"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"}]}] BACKPORT-->
…al (elastic#213981) (elastic#214462) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] UI copy for Upgrade rules confirmation modal (elastic#213981)](elastic#213981) <!--- 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-03-13T18:36:35Z","message":"[Security Solution] UI copy for Upgrade rules confirmation modal (elastic#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","ui-copy","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] UI copy for Upgrade rules confirmation modal ","number":213981,"url":"https://github.com/elastic/kibana/pull/213981","mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (elastic#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},"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/213981","number":213981,"mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (elastic#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
…preview and add preview banner (elastic#213455) (elastic#214467) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix session view navigation when in alert preview and add preview banner (elastic#213455)](elastic#213455) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T18:43:18Z","message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (elastic#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] 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":"a6ceafc8916a8f6c121fcad88f9057f92523feb3","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:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fix session view navigation when in alert preview and add preview banner","number":213455,"url":"https://github.com/elastic/kibana/pull/213455","mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (elastic#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] 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":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},"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/213455","number":213455,"mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (elastic#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] 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":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
…lastic#214178) (elastic#214471) # Backport This will backport the following commits from `main` to `8.18`: - [[Threat Hunting Investigations] Fix timeline column width bug (elastic#214178)](elastic#214178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:49:16Z","message":"[Threat Hunting Investigations] Fix timeline column width bug (elastic#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Fix timeline column width bug","number":214178,"url":"https://github.com/elastic/kibana/pull/214178","mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (elastic#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}},"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/214178","number":214178,"mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (elastic#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co>
…elastic#217325) (elastic#217613) # Backport This will backport the following commits from `main` to `8.18`: - [[A11y][APM] Add missing `aria-label` for some services buttons (elastic#217325)](elastic#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 (elastic#217325)\n\n## Summary\n\nFixes elastic#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 (elastic#217325)\n\n## Summary\n\nFixes elastic#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 (elastic#217325)\n\n## Summary\n\nFixes elastic#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>
…ic#216483) (elastic#217611) # Backport This will backport the following commits from `main` to `8.18`: - [[A11y][APM] Add `aria-label` to technical preview badge (elastic#216483)](elastic#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 (elastic#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","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 (elastic#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","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 (elastic#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","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 (elastic#216483) (elastic#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(elastic#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>
…fix accidental config backup file (elastic#216978) (elastic#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 (elastic#216978)](elastic#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 (elastic#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 (elastic#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 (elastic#216978) (elastic#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(elastic#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 (elastic#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>
…ic#216470) (elastic#217495) # Backport This will backport the following commits from `main` to `8.18`: - [[Oblt Onboarding] Add breadcrumbs for quick start flows (elastic#216470)](elastic#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 (elastic#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| \n| \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 (elastic#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| \n| \n|","sha":"fcc7244da2b801ce5e59017a00e3ce19a20b01ce"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[]}] BACKPORT-->
…6628) (elastic#216777) # Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX] [A11y] Fix focus on metadata table content (elastic#216628)](elastic#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 (elastic#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\nhttps://github.com/user-attachments/assets/13a0f7a2-2f24-4304-a6ad-cc46e3bbfc1c\n\nAfter\n\n\nhttps://github.com/user-attachments/assets/7993abdc-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 (elastic#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\nhttps://github.com/user-attachments/assets/13a0f7a2-2f24-4304-a6ad-cc46e3bbfc1c\n\nAfter\n\n\nhttps://github.com/user-attachments/assets/7993abdc-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 (elastic#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\nhttps://github.com/user-attachments/assets/13a0f7a2-2f24-4304-a6ad-cc46e3bbfc1c\n\nAfter\n\n\nhttps://github.com/user-attachments/assets/7993abdc-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>
Contributor
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
Contributor
💔 Build Failed
Failed CI StepsHistory |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto8.18:- Update preconfigured connector name (#217570)
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.