mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
82357 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
0eb1a283c2
|
[8.18] [Discover] Add "All logs" data view to classic nav (#209042) (#210483)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Add "All logs" data view to classic nav (#209042)](https://github.com/elastic/kibana/pull/209042) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T01:18:26Z","message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","Team:DataDiscovery","Team:obs-ux-logs","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Add \"All logs\" data view to classic nav","number":209042,"url":"https://github.com/elastic/kibana/pull/209042","mergeCommit":{"message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe"}},"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/209042","number":209042,"mergeCommit":{"message":"[Discover] Add \"All logs\" data view to classic nav (#209042)\n\n## Summary\r\n\r\nThis PR adds the default \"All logs\" data view introduced in #205991 to\r\nthe classic nav in addition to Observability nav.\r\n\r\nResolves #209013.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"37465f43d2eb8428a8cc2e845df686c10abe8abe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
christineweng
|
ee07395957
|
[8.18] [Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287) (#210475)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287)](https://github.com/elastic/kibana/pull/208287) <!--- Backport version: 9.6.4 --> ### 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-02-10T22:11:13Z","message":"[Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287)\n\n## Summary\r\n\r\nThis PR updates the cloud insights in entity section to open to entity\r\nflyout. When examining the insights (for example, the host is shown to\r\nhave 50 alerts, instead of opening the preview, and user click on the\r\ndetails and go to respective tabs, this PR updated the behavior to open\r\nthe details tab via 1 click. The goal is to reduce friction for users\r\nduring investigation.\r\n\r\nFeature flag: `newExpandableFlyoutNavigationEnabled`\r\n\r\nWhen flag is off:\r\n- Click on alert count should open timeline (if user has timeline\r\nprivileage)\r\n- Click on misconfigurations and vulnerabilities badge should open\r\nhost/user preview\r\n\r\n\r\nhttps://github.com/user-attachments/assets/23e0cc40-129d-4e75-b5be-26a49dcad710\r\n\r\n\r\nWhen flag is on:\r\n- Click on count badges should open the respective entity flyout and the\r\ninsights details tab\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5dfc39b7-edae-4b76-9a3a-79326337cb3b\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6e61f526a75de7a654fbb0760edf2efec3a611bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts","number":208287,"url":"https://github.com/elastic/kibana/pull/208287","mergeCommit":{"message":"[Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287)\n\n## Summary\r\n\r\nThis PR updates the cloud insights in entity section to open to entity\r\nflyout. When examining the insights (for example, the host is shown to\r\nhave 50 alerts, instead of opening the preview, and user click on the\r\ndetails and go to respective tabs, this PR updated the behavior to open\r\nthe details tab via 1 click. The goal is to reduce friction for users\r\nduring investigation.\r\n\r\nFeature flag: `newExpandableFlyoutNavigationEnabled`\r\n\r\nWhen flag is off:\r\n- Click on alert count should open timeline (if user has timeline\r\nprivileage)\r\n- Click on misconfigurations and vulnerabilities badge should open\r\nhost/user preview\r\n\r\n\r\nhttps://github.com/user-attachments/assets/23e0cc40-129d-4e75-b5be-26a49dcad710\r\n\r\n\r\nWhen flag is on:\r\n- Click on count badges should open the respective entity flyout and the\r\ninsights details tab\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5dfc39b7-edae-4b76-9a3a-79326337cb3b\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6e61f526a75de7a654fbb0760edf2efec3a611bb"}},"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/210472","number":210472,"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/208287","number":208287,"mergeCommit":{"message":"[Security Solution][Alert Flyout] Update entity insight badge to open entity flyouts (#208287)\n\n## Summary\r\n\r\nThis PR updates the cloud insights in entity section to open to entity\r\nflyout. When examining the insights (for example, the host is shown to\r\nhave 50 alerts, instead of opening the preview, and user click on the\r\ndetails and go to respective tabs, this PR updated the behavior to open\r\nthe details tab via 1 click. The goal is to reduce friction for users\r\nduring investigation.\r\n\r\nFeature flag: `newExpandableFlyoutNavigationEnabled`\r\n\r\nWhen flag is off:\r\n- Click on alert count should open timeline (if user has timeline\r\nprivileage)\r\n- Click on misconfigurations and vulnerabilities badge should open\r\nhost/user preview\r\n\r\n\r\nhttps://github.com/user-attachments/assets/23e0cc40-129d-4e75-b5be-26a49dcad710\r\n\r\n\r\nWhen flag is on:\r\n- Click on count badges should open the respective entity flyout and the\r\ninsights details tab\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5dfc39b7-edae-4b76-9a3a-79326337cb3b\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6e61f526a75de7a654fbb0760edf2efec3a611bb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
86adb758f9
|
[8.18] Fix alignment issues with badges on inference endpoints table (#210423) (#210459)
# Backport This will backport the following commits from `main` to `8.18`: - [Fix alignment issues with badges on inference endpoints table (#210423)](https://github.com/elastic/kibana/pull/210423) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Michael DeFazio","email":"michael.defazio@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T20:50:18Z","message":"Fix alignment issues with badges on inference endpoints table (#210423)\n\n## Summary\r\n\r\n- Aligns preconfigured and tech preview badges. \r\n- Adds wrapping to the column\r\n- Moves preconfigured to be next to the name: help remove an extra flex\r\nitem for non-preconfigured items\r\n\r\n\r\nPrevious:\r\n\r\n\r\n\r\n\r\n\r\n- - - \r\n \r\nUpdate:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] ~Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\r\n- [ ]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials~\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] ~If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\r\n- [ ] ~This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.~\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nLow risk—just small UI flexbox changes.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"75694a122814000df42063a8356a908ba1b186eb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Fix alignment issues with badges on inference endpoints table","number":210423,"url":"https://github.com/elastic/kibana/pull/210423","mergeCommit":{"message":"Fix alignment issues with badges on inference endpoints table (#210423)\n\n## Summary\r\n\r\n- Aligns preconfigured and tech preview badges. \r\n- Adds wrapping to the column\r\n- Moves preconfigured to be next to the name: help remove an extra flex\r\nitem for non-preconfigured items\r\n\r\n\r\nPrevious:\r\n\r\n\r\n\r\n\r\n\r\n- - - \r\n \r\nUpdate:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] ~Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\r\n- [ ]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials~\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] ~If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\r\n- [ ] ~This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.~\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nLow risk—just small UI flexbox changes.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"75694a122814000df42063a8356a908ba1b186eb"}},"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/210423","number":210423,"mergeCommit":{"message":"Fix alignment issues with badges on inference endpoints table (#210423)\n\n## Summary\r\n\r\n- Aligns preconfigured and tech preview badges. \r\n- Adds wrapping to the column\r\n- Moves preconfigured to be next to the name: help remove an extra flex\r\nitem for non-preconfigured items\r\n\r\n\r\nPrevious:\r\n\r\n\r\n\r\n\r\n\r\n- - - \r\n \r\nUpdate:\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] ~Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\r\n- [ ]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials~\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] ~If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\r\n- [ ] ~This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.~\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nLow risk—just small UI flexbox changes.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"75694a122814000df42063a8356a908ba1b186eb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Michael DeFazio <michael.defazio@elastic.co> |
||
|
Kibana Machine
|
f3e3d7ac71
|
[8.18] [Automatic Import] Handle empty categorization results (#210420) (#210448)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Handle empty categorization results (#210420)](https://github.com/elastic/kibana/pull/210420) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T19:07:05Z","message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b","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:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Handle empty categorization results","number":210420,"url":"https://github.com/elastic/kibana/pull/210420","mergeCommit":{"message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b"}},"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/210420","number":210420,"mergeCommit":{"message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
Kibana Machine
|
f2bc9a7c3d
|
[8.18] [Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI (#209936) (#210416)
# Backport This will backport the following commits from `main` to `8.18`: - [[Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI (#209936)](https://github.com/elastic/kibana/pull/209936) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-02-10T16:03:59Z","message":"[Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI (#209936)\n\n### Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/208204. \r\n\r\nThe general idea here is to add aliases to the legacy indices in order\r\nto \"backfill\" some newer fields that are now required in various alerts\r\nUIs. We already have the mechanism to apply mappings changes for just\r\nthis scenario, so this was just a matter of adding the new mappings and\r\nbumping versions appropriately.\r\n\r\nWhile the consumer field is static ('siem'), we're opting to use a\r\n`keyword` runtime field instead of a `constant_keyword` in order to\r\nallow the possibility of other values for this field in the future.\r\n\r\nWhile we do not expect the legacy indices to be written to at all in\r\n8.x+, new legacy indices are still created every 30d due to the rollover\r\npolicy, and so neglecting to add the mappings to those new indices could\r\nlead to mapping conflicts. So: while the mappings on the index template\r\nare not expected to be used, we still update them for\r\nconsistency/future-proofing.\r\n\r\n### Screenshots\r\n<details>\r\n<summary>\r\n</summary>\r\n<kbd>\r\nAlerts Table before fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 15 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1f83d6f3-a1b0-4025-b1e3-78e34340ef91\"\r\n/>\r\n</kbd>\r\n\r\n\r\n<kbd>\r\nAlerts Table after fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 40 02 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/c68ad198-226c-413e-a4ac-7f590e6d500b\"\r\n/>\r\n</kbd>\r\n</details>\r\n\r\n### Steps to review\r\n1. Create a 7.17 cloud GCP instance (on us-west-2 so that you can\r\nupgrade to 8.18)\r\n2. Create several rules of different types (since part of this bug\r\ninvolves mapping existing rule types to the new `rule_type_id` field)\r\n3. Generate alerts with those rules (I prefer to use auditbeat to\r\nquickly ingest some ECS data)\r\n4. (optional) Take a snapshot of your instance (so as to skip steps 2-3\r\nin subsequent tests)\r\n5. Upgrade the instance to 8.18\r\n6. Observe the absence of any 7.17 alerts in the 8.18 Alerts table\r\n(note: if you have no 8.18 alerts, the table will be empty)\r\n7. Connect your local kibana (running this branch) to your cloud\r\ninstance:\r\n\r\n ```yaml\r\n elasticsearch:\r\nusername: USERNAME_HERE # Note: user will need index management\r\nprivileges\r\n password: PASSWORD_HERE\r\n hosts: https://ES_ENDPOINT_HERE.es.us-west2.gcp.elastic-cloud.com\r\n ssl:\r\n verificationMode: none\r\n ignoreVersionMismatch: true\r\n \r\n node.roles: ['ui'] # Only run UI (not task manager) locally\r\n ```\r\n8. Navigate to a security page in your browser. This will trigger the\r\ncall to update 7.x signals\r\n9. Observe that the 7.x alerts are now visible on the alerts table, both\r\nlocally and using the cloud instance's kibana\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2125a8fe21b51817befeb01956322a9337b6786e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","Team:Detection Engine","v8.18.0","v9.1.0"],"title":"[Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI","number":209936,"url":"https://github.com/elastic/kibana/pull/209936","mergeCommit":{"message":"[Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI (#209936)\n\n### Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/208204. \r\n\r\nThe general idea here is to add aliases to the legacy indices in order\r\nto \"backfill\" some newer fields that are now required in various alerts\r\nUIs. We already have the mechanism to apply mappings changes for just\r\nthis scenario, so this was just a matter of adding the new mappings and\r\nbumping versions appropriately.\r\n\r\nWhile the consumer field is static ('siem'), we're opting to use a\r\n`keyword` runtime field instead of a `constant_keyword` in order to\r\nallow the possibility of other values for this field in the future.\r\n\r\nWhile we do not expect the legacy indices to be written to at all in\r\n8.x+, new legacy indices are still created every 30d due to the rollover\r\npolicy, and so neglecting to add the mappings to those new indices could\r\nlead to mapping conflicts. So: while the mappings on the index template\r\nare not expected to be used, we still update them for\r\nconsistency/future-proofing.\r\n\r\n### Screenshots\r\n<details>\r\n<summary>\r\n</summary>\r\n<kbd>\r\nAlerts Table before fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 15 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1f83d6f3-a1b0-4025-b1e3-78e34340ef91\"\r\n/>\r\n</kbd>\r\n\r\n\r\n<kbd>\r\nAlerts Table after fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 40 02 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/c68ad198-226c-413e-a4ac-7f590e6d500b\"\r\n/>\r\n</kbd>\r\n</details>\r\n\r\n### Steps to review\r\n1. Create a 7.17 cloud GCP instance (on us-west-2 so that you can\r\nupgrade to 8.18)\r\n2. Create several rules of different types (since part of this bug\r\ninvolves mapping existing rule types to the new `rule_type_id` field)\r\n3. Generate alerts with those rules (I prefer to use auditbeat to\r\nquickly ingest some ECS data)\r\n4. (optional) Take a snapshot of your instance (so as to skip steps 2-3\r\nin subsequent tests)\r\n5. Upgrade the instance to 8.18\r\n6. Observe the absence of any 7.17 alerts in the 8.18 Alerts table\r\n(note: if you have no 8.18 alerts, the table will be empty)\r\n7. Connect your local kibana (running this branch) to your cloud\r\ninstance:\r\n\r\n ```yaml\r\n elasticsearch:\r\nusername: USERNAME_HERE # Note: user will need index management\r\nprivileges\r\n password: PASSWORD_HERE\r\n hosts: https://ES_ENDPOINT_HERE.es.us-west2.gcp.elastic-cloud.com\r\n ssl:\r\n verificationMode: none\r\n ignoreVersionMismatch: true\r\n \r\n node.roles: ['ui'] # Only run UI (not task manager) locally\r\n ```\r\n8. Navigate to a security page in your browser. This will trigger the\r\ncall to update 7.x signals\r\n9. Observe that the 7.x alerts are now visible on the alerts table, both\r\nlocally and using the cloud instance's kibana\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2125a8fe21b51817befeb01956322a9337b6786e"}},"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/209936","number":209936,"mergeCommit":{"message":"[Detection Engine] Make 7.x signals/alerts compatible with 8.18 alerts UI (#209936)\n\n### Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/208204. \r\n\r\nThe general idea here is to add aliases to the legacy indices in order\r\nto \"backfill\" some newer fields that are now required in various alerts\r\nUIs. We already have the mechanism to apply mappings changes for just\r\nthis scenario, so this was just a matter of adding the new mappings and\r\nbumping versions appropriately.\r\n\r\nWhile the consumer field is static ('siem'), we're opting to use a\r\n`keyword` runtime field instead of a `constant_keyword` in order to\r\nallow the possibility of other values for this field in the future.\r\n\r\nWhile we do not expect the legacy indices to be written to at all in\r\n8.x+, new legacy indices are still created every 30d due to the rollover\r\npolicy, and so neglecting to add the mappings to those new indices could\r\nlead to mapping conflicts. So: while the mappings on the index template\r\nare not expected to be used, we still update them for\r\nconsistency/future-proofing.\r\n\r\n### Screenshots\r\n<details>\r\n<summary>\r\n</summary>\r\n<kbd>\r\nAlerts Table before fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 15 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1f83d6f3-a1b0-4025-b1e3-78e34340ef91\"\r\n/>\r\n</kbd>\r\n\r\n\r\n<kbd>\r\nAlerts Table after fix:\r\n<img width=\"1727\" alt=\"Screenshot 2025-02-06 at 5 40 02 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/c68ad198-226c-413e-a4ac-7f590e6d500b\"\r\n/>\r\n</kbd>\r\n</details>\r\n\r\n### Steps to review\r\n1. Create a 7.17 cloud GCP instance (on us-west-2 so that you can\r\nupgrade to 8.18)\r\n2. Create several rules of different types (since part of this bug\r\ninvolves mapping existing rule types to the new `rule_type_id` field)\r\n3. Generate alerts with those rules (I prefer to use auditbeat to\r\nquickly ingest some ECS data)\r\n4. (optional) Take a snapshot of your instance (so as to skip steps 2-3\r\nin subsequent tests)\r\n5. Upgrade the instance to 8.18\r\n6. Observe the absence of any 7.17 alerts in the 8.18 Alerts table\r\n(note: if you have no 8.18 alerts, the table will be empty)\r\n7. Connect your local kibana (running this branch) to your cloud\r\ninstance:\r\n\r\n ```yaml\r\n elasticsearch:\r\nusername: USERNAME_HERE # Note: user will need index management\r\nprivileges\r\n password: PASSWORD_HERE\r\n hosts: https://ES_ENDPOINT_HERE.es.us-west2.gcp.elastic-cloud.com\r\n ssl:\r\n verificationMode: none\r\n ignoreVersionMismatch: true\r\n \r\n node.roles: ['ui'] # Only run UI (not task manager) locally\r\n ```\r\n8. Navigate to a security page in your browser. This will trigger the\r\ncall to update 7.x signals\r\n9. Observe that the 7.x alerts are now visible on the alerts table, both\r\nlocally and using the cloud instance's kibana\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2125a8fe21b51817befeb01956322a9337b6786e"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
76a2aa80c5
|
[8.18] [Security Solution] Siem migrations UI telemetry (#209633) (#210402)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Siem migrations UI telemetry (#209633)](https://github.com/elastic/kibana/pull/209633) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T15:10:38Z","message":"[Security Solution] Siem migrations UI telemetry (#209633)\n\n## Summary\r\n\r\nCreated a telemetry client with all SIEM migration telemetry events. \r\nAnd added the calls to track them \r\n\r\n### New events\r\n\r\n```ts\r\nSetupConnectorSelected {\r\n connectorType: string;\r\n connectorId: string;\r\n}\r\n\r\nSetupMigrationOpenNew {\r\n isFirstMigration: boolean;\r\n}\r\n\r\nSetupMigrationOpenResources {\r\n migrationId: string;\r\n missingResourcesCount: number;\r\n}\r\n\r\nSetupRulesQueryCopied {\r\n migrationId?: string;\r\n}\r\n\r\nSetupMigrationCreated {\r\n migrationId?: string;\r\n rulesCount: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nSetupMacrosQueryCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupLookupNameCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupResourcesUploaded {\r\n migrationId: string;\r\n type: 'macro' | 'lookup';\r\n count: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nStartTranslation {\r\n migrationId: string;\r\n connectorId: string;\r\n isRetry: boolean;\r\n retryFilter?: 'failed' | 'not_fully_translated';\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n```\r\n\r\n### Existing events (Translated rules actions):\r\n\r\nAlso integrated into the telemetry client\r\n\r\n```ts\r\nTranslatedRuleUpdate {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n}\r\n\r\nTranslatedRuleInstall {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n author: 'elastic' | 'custom';\r\n enabled: boolean;\r\n prebuiltRule?: {\r\n id: string;\r\n title: string;\r\n };\r\n}\r\n\r\nTranslatedRuleBulkInstall {\r\n migrationId: string;\r\n enabled: boolean;\r\n count: number;\r\n}\r\n```","sha":"bcc5389598b9ef23b15465715a952e6b2aca3180","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 UI telemetry","number":209633,"url":"https://github.com/elastic/kibana/pull/209633","mergeCommit":{"message":"[Security Solution] Siem migrations UI telemetry (#209633)\n\n## Summary\r\n\r\nCreated a telemetry client with all SIEM migration telemetry events. \r\nAnd added the calls to track them \r\n\r\n### New events\r\n\r\n```ts\r\nSetupConnectorSelected {\r\n connectorType: string;\r\n connectorId: string;\r\n}\r\n\r\nSetupMigrationOpenNew {\r\n isFirstMigration: boolean;\r\n}\r\n\r\nSetupMigrationOpenResources {\r\n migrationId: string;\r\n missingResourcesCount: number;\r\n}\r\n\r\nSetupRulesQueryCopied {\r\n migrationId?: string;\r\n}\r\n\r\nSetupMigrationCreated {\r\n migrationId?: string;\r\n rulesCount: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nSetupMacrosQueryCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupLookupNameCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupResourcesUploaded {\r\n migrationId: string;\r\n type: 'macro' | 'lookup';\r\n count: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nStartTranslation {\r\n migrationId: string;\r\n connectorId: string;\r\n isRetry: boolean;\r\n retryFilter?: 'failed' | 'not_fully_translated';\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n```\r\n\r\n### Existing events (Translated rules actions):\r\n\r\nAlso integrated into the telemetry client\r\n\r\n```ts\r\nTranslatedRuleUpdate {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n}\r\n\r\nTranslatedRuleInstall {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n author: 'elastic' | 'custom';\r\n enabled: boolean;\r\n prebuiltRule?: {\r\n id: string;\r\n title: string;\r\n };\r\n}\r\n\r\nTranslatedRuleBulkInstall {\r\n migrationId: string;\r\n enabled: boolean;\r\n count: number;\r\n}\r\n```","sha":"bcc5389598b9ef23b15465715a952e6b2aca3180"}},"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/209633","number":209633,"mergeCommit":{"message":"[Security Solution] Siem migrations UI telemetry (#209633)\n\n## Summary\r\n\r\nCreated a telemetry client with all SIEM migration telemetry events. \r\nAnd added the calls to track them \r\n\r\n### New events\r\n\r\n```ts\r\nSetupConnectorSelected {\r\n connectorType: string;\r\n connectorId: string;\r\n}\r\n\r\nSetupMigrationOpenNew {\r\n isFirstMigration: boolean;\r\n}\r\n\r\nSetupMigrationOpenResources {\r\n migrationId: string;\r\n missingResourcesCount: number;\r\n}\r\n\r\nSetupRulesQueryCopied {\r\n migrationId?: string;\r\n}\r\n\r\nSetupMigrationCreated {\r\n migrationId?: string;\r\n rulesCount: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nSetupMacrosQueryCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupLookupNameCopied {\r\n migrationId: string;\r\n}\r\n\r\nSetupResourcesUploaded {\r\n migrationId: string;\r\n type: 'macro' | 'lookup';\r\n count: number;\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n\r\nStartTranslation {\r\n migrationId: string;\r\n connectorId: string;\r\n isRetry: boolean;\r\n retryFilter?: 'failed' | 'not_fully_translated';\r\n result: 'success' | 'failed';\r\n errorMessage?: string;\r\n}\r\n```\r\n\r\n### Existing events (Translated rules actions):\r\n\r\nAlso integrated into the telemetry client\r\n\r\n```ts\r\nTranslatedRuleUpdate {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n}\r\n\r\nTranslatedRuleInstall {\r\n migrationId: string;\r\n ruleMigrationId: string;\r\n author: 'elastic' | 'custom';\r\n enabled: boolean;\r\n prebuiltRule?: {\r\n id: string;\r\n title: string;\r\n };\r\n}\r\n\r\nTranslatedRuleBulkInstall {\r\n migrationId: string;\r\n enabled: boolean;\r\n count: number;\r\n}\r\n```","sha":"bcc5389598b9ef23b15465715a952e6b2aca3180"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
69de508a66
|
[8.18] [DiscoverSession] Change the display name on reporting page (#209250) (#210345)
# Backport This will backport the following commits from `main` to `8.18`: - [[DiscoverSession] Change the display name on reporting page (#209250)](https://github.com/elastic/kibana/pull/209250) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T12:00:57Z","message":"[DiscoverSession] Change the display name on reporting page (#209250)\n\n- Closes https://github.com/elastic/kibana/issues/209239\r\n\r\n## Summary\r\n\r\nThis PR fixes the tooltip for Discover sessions on the reporting page.\r\n\r\n<img width=\"693\" alt=\"Screenshot 2025-02-03 at 11 55 53\"\r\nsrc=\"https://github.com/user-attachments/assets/cf1a952b-ff6c-4d7c-a523-d537ce51d484\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b76ada490e28ff7ce31a39ccfb48928d3e55669","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:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[DiscoverSession] Change the display name on reporting page","number":209250,"url":"https://github.com/elastic/kibana/pull/209250","mergeCommit":{"message":"[DiscoverSession] Change the display name on reporting page (#209250)\n\n- Closes https://github.com/elastic/kibana/issues/209239\r\n\r\n## Summary\r\n\r\nThis PR fixes the tooltip for Discover sessions on the reporting page.\r\n\r\n<img width=\"693\" alt=\"Screenshot 2025-02-03 at 11 55 53\"\r\nsrc=\"https://github.com/user-attachments/assets/cf1a952b-ff6c-4d7c-a523-d537ce51d484\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b76ada490e28ff7ce31a39ccfb48928d3e55669"}},"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/209250","number":209250,"mergeCommit":{"message":"[DiscoverSession] Change the display name on reporting page (#209250)\n\n- Closes https://github.com/elastic/kibana/issues/209239\r\n\r\n## Summary\r\n\r\nThis PR fixes the tooltip for Discover sessions on the reporting page.\r\n\r\n<img width=\"693\" alt=\"Screenshot 2025-02-03 at 11 55 53\"\r\nsrc=\"https://github.com/user-attachments/assets/cf1a952b-ff6c-4d7c-a523-d537ce51d484\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b76ada490e28ff7ce31a39ccfb48928d3e55669"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
04145acf01
|
[8.18] [APM] Missing items in the trace waterfall shouldn't break it entirely (#210210) (#210390)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)](https://github.com/elastic/kibana/pull/210210) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T14:04:33Z","message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7","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] Missing items in the trace waterfall shouldn't break it entirely","number":210210,"url":"https://github.com/elastic/kibana/pull/210210","mergeCommit":{"message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7"}},"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/210210","number":210210,"mergeCommit":{"message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7"}}]}] BACKPORT--> Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com> |
||
|
Kibana Machine
|
303c5faded
|
[8.18] Clicking link in host/user flyout does not refresh details panel (#209863) (#210373)
# Backport This will backport the following commits from `main` to `8.18`: - [Clicking link in host/user flyout does not refresh details panel (#209863)](https://github.com/elastic/kibana/pull/209863) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T13:18:14Z","message":"Clicking link in host/user flyout does not refresh details panel (#209863)\n\n## Summary\r\n\r\nThis PR fixes the issue of navigation link behaviour not updating after\r\nfirst click/update.\r\n\r\n\r\n## Testing Steps \r\n1. Kibana - 8.18 \r\n2. Generate some data using data generator and alerts. \r\n3. Enable Risk Score\r\n4. Go to Security -> Alerts \r\n5. Open Host Flyout of a host with risk score \r\n6. Click alert/risk summary link, then click the other one and observe\r\nthe tab on the left and content change in response ✅\r\n\r\n### Screen Recordings\r\n\r\n#### Host Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ac071adc-8255-496e-956b-cf727191cbe3\r\n\r\n\r\n\r\n#### User Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ab10a640-964d-457f-9ff3-198c19641889\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8c7714a61188a9481b7977ed95a35de378cae2a5","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","Theme: entity_analytics","ci:project-deploy-security","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Clicking link in host/user flyout does not refresh details panel","number":209863,"url":"https://github.com/elastic/kibana/pull/209863","mergeCommit":{"message":"Clicking link in host/user flyout does not refresh details panel (#209863)\n\n## Summary\r\n\r\nThis PR fixes the issue of navigation link behaviour not updating after\r\nfirst click/update.\r\n\r\n\r\n## Testing Steps \r\n1. Kibana - 8.18 \r\n2. Generate some data using data generator and alerts. \r\n3. Enable Risk Score\r\n4. Go to Security -> Alerts \r\n5. Open Host Flyout of a host with risk score \r\n6. Click alert/risk summary link, then click the other one and observe\r\nthe tab on the left and content change in response ✅\r\n\r\n### Screen Recordings\r\n\r\n#### Host Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ac071adc-8255-496e-956b-cf727191cbe3\r\n\r\n\r\n\r\n#### User Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ab10a640-964d-457f-9ff3-198c19641889\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8c7714a61188a9481b7977ed95a35de378cae2a5"}},"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/209863","number":209863,"mergeCommit":{"message":"Clicking link in host/user flyout does not refresh details panel (#209863)\n\n## Summary\r\n\r\nThis PR fixes the issue of navigation link behaviour not updating after\r\nfirst click/update.\r\n\r\n\r\n## Testing Steps \r\n1. Kibana - 8.18 \r\n2. Generate some data using data generator and alerts. \r\n3. Enable Risk Score\r\n4. Go to Security -> Alerts \r\n5. Open Host Flyout of a host with risk score \r\n6. Click alert/risk summary link, then click the other one and observe\r\nthe tab on the left and content change in response ✅\r\n\r\n### Screen Recordings\r\n\r\n#### Host Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ac071adc-8255-496e-956b-cf727191cbe3\r\n\r\n\r\n\r\n#### User Selected \r\n\r\n\r\nhttps://github.com/user-attachments/assets/ab10a640-964d-457f-9ff3-198c19641889\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8c7714a61188a9481b7977ed95a35de378cae2a5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com> |
||
|
Kibana Machine
|
6b79455363
|
[8.18] [Fleet] Fix source mode synthetics when handling experimental datastream features (#210195) (#210376)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Fix source mode synthetics when handling experimental datastream features (#210195)](https://github.com/elastic/kibana/pull/210195) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T13:00:59Z","message":"[Fleet] Fix source mode synthetics when handling experimental datastream features (#210195)","sha":"d2070ca7242a832c158d9a8dd4edcc8bd806649a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Fleet] Fix source mode synthetics when handling experimental datastream features","number":210195,"url":"https://github.com/elastic/kibana/pull/210195","mergeCommit":{"message":"[Fleet] Fix source mode synthetics when handling experimental datastream features (#210195)","sha":"d2070ca7242a832c158d9a8dd4edcc8bd806649a"}},"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/210195","number":210195,"mergeCommit":{"message":"[Fleet] Fix source mode synthetics when handling experimental datastream features (#210195)","sha":"d2070ca7242a832c158d9a8dd4edcc8bd806649a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/210370","number":210370,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
1f301fcdca
|
[8.18] [Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383) (#210343)
# Backport This will backport the following commits from `main` to `8.18`: - [[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)](https://github.com/elastic/kibana/pull/207383) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T11:57:22Z","message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\n\n\n\n<!-- \n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n\n-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:SharingURLs","Team:SharedUX","backport:prev-major","v9.1.0"],"title":"[Share Modal] Reinstate switch to support generating public urls for embed when supported","number":207383,"url":"https://github.com/elastic/kibana/pull/207383","mergeCommit":{"message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\n\n\n\n<!-- \n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n\n-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e"}},"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/207383","number":207383,"mergeCommit":{"message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\n\n\n\n<!-- \n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n\n-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e"}}]}] BACKPORT--> Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com> |
||
|
Kibana Machine
|
b896ae3ba2
|
[8.18] [Synonyms UI] Fix rendering issues and adds a code example (#210229) (#210335)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synonyms UI] Fix rendering issues and adds a code example (#210229)](https://github.com/elastic/kibana/pull/210229) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T11:27:58Z","message":"[Synonyms UI] Fix rendering issues and adds a code example (#210229)\n\n## Summary\r\n\r\nImproved rendering when long lists are added with explicit rule.\r\nAdded code example flyout.\r\n<img width=\"1075\" alt=\"Screenshot 2025-02-07 at 18 09 18\"\r\nsrc=\"https://github.com/user-attachments/assets/95020f5b-8162-4cb7-bf7a-11439ff5b2d0\"\r\n/>\r\n<img width=\"1049\" alt=\"Screenshot 2025-02-07 at 18 09 26\"\r\nsrc=\"https://github.com/user-attachments/assets/5912e930-1356-4919-b637-92ca4009bc30\"\r\n/>\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e326c7759a9eba6e8ce2797ccc109e58d2904f5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Synonyms UI] Fix rendering issues and adds a code example","number":210229,"url":"https://github.com/elastic/kibana/pull/210229","mergeCommit":{"message":"[Synonyms UI] Fix rendering issues and adds a code example (#210229)\n\n## Summary\r\n\r\nImproved rendering when long lists are added with explicit rule.\r\nAdded code example flyout.\r\n<img width=\"1075\" alt=\"Screenshot 2025-02-07 at 18 09 18\"\r\nsrc=\"https://github.com/user-attachments/assets/95020f5b-8162-4cb7-bf7a-11439ff5b2d0\"\r\n/>\r\n<img width=\"1049\" alt=\"Screenshot 2025-02-07 at 18 09 26\"\r\nsrc=\"https://github.com/user-attachments/assets/5912e930-1356-4919-b637-92ca4009bc30\"\r\n/>\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e326c7759a9eba6e8ce2797ccc109e58d2904f5f"}},"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/210229","number":210229,"mergeCommit":{"message":"[Synonyms UI] Fix rendering issues and adds a code example (#210229)\n\n## Summary\r\n\r\nImproved rendering when long lists are added with explicit rule.\r\nAdded code example flyout.\r\n<img width=\"1075\" alt=\"Screenshot 2025-02-07 at 18 09 18\"\r\nsrc=\"https://github.com/user-attachments/assets/95020f5b-8162-4cb7-bf7a-11439ff5b2d0\"\r\n/>\r\n<img width=\"1049\" alt=\"Screenshot 2025-02-07 at 18 09 26\"\r\nsrc=\"https://github.com/user-attachments/assets/5912e930-1356-4919-b637-92ca4009bc30\"\r\n/>\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e326c7759a9eba6e8ce2797ccc109e58d2904f5f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co> |
||
|
Kibana Machine
|
27e0332458
|
[8.18] [Fleet] update component templates with deprecated setting (#210200) (#210323)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] update component templates with deprecated setting (#210200)](https://github.com/elastic/kibana/pull/210200) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T10:15:35Z","message":"[Fleet] update component templates with deprecated setting (#210200)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/209087\r\n\r\nAdded logic to Fleet setup that queries component templates with the\r\ndeprecated `_source.mode` setting.\r\nQuerying only `metrics-*` prefixed component templates, I think only\r\nthose use `_source.mode` setting.\r\n\r\nSteps to verify:\r\n- Upload\r\n[apm-8.8.0.zip](https://github.com/user-attachments/files/18708082/apm-8.8.0.zip)\r\npackage to http://localhost:5601/app/integrations/create/upload\r\n- Deprecation warnings should appear in Upgrade assistant\r\nhttp://localhost:5601/app/management/stack/upgrade_assistant/es_deprecations\r\n- Visit Fleet UI or run setup API to let setup logic run\r\n- Verify that deprecations disappeared\r\n- Verify that the component templates are updated\r\n\r\n<img width=\"1190\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20c4265f-461e-46d1-b075-6ba1111ef9d2\"\r\n/>\r\n\r\n<img width=\"2533\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6961c885-7a91-4d07-90b9-c01a8c133cc9\"\r\n/>\r\n\r\n<img width=\"901\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6b712f94-fd9c-4038-8dc4-cfcf7650cca7\"\r\n/>\r\n\r\n```\r\n[2025-02-07T15:39:42.396+01:00][DEBUG][plugins.fleet] Update deprecated _source.mode in component templates\r\n[2025-02-07T15:39:42.401+01:00][DEBUG][plugins.fleet] Updating component templates with deprecated _source.mode config: metrics-apm.app@package,metrics-apm.internal@package,metrics-apm.service_transaction.1m@package,metrics-apm.service_destination.60m@package,metrics-apm.transaction.1m@package,metrics-apm.service_summary.10m@package,metrics-apm.transaction.10m@package,metrics-apm.service_transaction.10m@package,metrics-apm.transaction.60m@package,metrics-apm.service_destination.10m@package,metrics-apm.service_summary.1m@package,metrics-apm.service_destination.1m@package,metrics-apm.service_transaction.60m@package,metrics-apm.service_summary.60m@package\r\n\r\n\r\nGET _component_template/metrics-*\r\n\r\n{\r\n \"component_templates\": [\r\n {\r\n \"name\": \"metrics-apm.app@package\",\r\n \"component_template\": {\r\n \"template\": {\r\n \"settings\": {\r\n \"index\": {\r\n \"lifecycle\": {\r\n \"name\": \"metrics-apm.app_metrics-default_policy\"\r\n },\r\n \"default_pipeline\": \"metrics-apm.app-8.8.0\",\r\n \"mapping\": {\r\n \"total_fields\": {\r\n \"limit\": \"1000\"\r\n },\r\n \"source\": {\r\n \"mode\": \"synthetic\"\r\n }\r\n }\r\n }\r\n },\r\n \"mappings\": {\r\n \"dynamic\": true,\r\n \"_source\": {},\r\n \"dynamic_templates\": [\r\n {\r\n \"histogram\": {\r\n \"mapping\": {\r\n \"type\": \"histogram\"\r\n }\r\n }\r\n },\r\n```\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a61c7293c004630a9440c5943f453e60d23c595c","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] update component templates with deprecated setting","number":210200,"url":"https://github.com/elastic/kibana/pull/210200","mergeCommit":{"message":"[Fleet] update component templates with deprecated setting (#210200)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/209087\r\n\r\nAdded logic to Fleet setup that queries component templates with the\r\ndeprecated `_source.mode` setting.\r\nQuerying only `metrics-*` prefixed component templates, I think only\r\nthose use `_source.mode` setting.\r\n\r\nSteps to verify:\r\n- Upload\r\n[apm-8.8.0.zip](https://github.com/user-attachments/files/18708082/apm-8.8.0.zip)\r\npackage to http://localhost:5601/app/integrations/create/upload\r\n- Deprecation warnings should appear in Upgrade assistant\r\nhttp://localhost:5601/app/management/stack/upgrade_assistant/es_deprecations\r\n- Visit Fleet UI or run setup API to let setup logic run\r\n- Verify that deprecations disappeared\r\n- Verify that the component templates are updated\r\n\r\n<img width=\"1190\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20c4265f-461e-46d1-b075-6ba1111ef9d2\"\r\n/>\r\n\r\n<img width=\"2533\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6961c885-7a91-4d07-90b9-c01a8c133cc9\"\r\n/>\r\n\r\n<img width=\"901\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6b712f94-fd9c-4038-8dc4-cfcf7650cca7\"\r\n/>\r\n\r\n```\r\n[2025-02-07T15:39:42.396+01:00][DEBUG][plugins.fleet] Update deprecated _source.mode in component templates\r\n[2025-02-07T15:39:42.401+01:00][DEBUG][plugins.fleet] Updating component templates with deprecated _source.mode config: metrics-apm.app@package,metrics-apm.internal@package,metrics-apm.service_transaction.1m@package,metrics-apm.service_destination.60m@package,metrics-apm.transaction.1m@package,metrics-apm.service_summary.10m@package,metrics-apm.transaction.10m@package,metrics-apm.service_transaction.10m@package,metrics-apm.transaction.60m@package,metrics-apm.service_destination.10m@package,metrics-apm.service_summary.1m@package,metrics-apm.service_destination.1m@package,metrics-apm.service_transaction.60m@package,metrics-apm.service_summary.60m@package\r\n\r\n\r\nGET _component_template/metrics-*\r\n\r\n{\r\n \"component_templates\": [\r\n {\r\n \"name\": \"metrics-apm.app@package\",\r\n \"component_template\": {\r\n \"template\": {\r\n \"settings\": {\r\n \"index\": {\r\n \"lifecycle\": {\r\n \"name\": \"metrics-apm.app_metrics-default_policy\"\r\n },\r\n \"default_pipeline\": \"metrics-apm.app-8.8.0\",\r\n \"mapping\": {\r\n \"total_fields\": {\r\n \"limit\": \"1000\"\r\n },\r\n \"source\": {\r\n \"mode\": \"synthetic\"\r\n }\r\n }\r\n }\r\n },\r\n \"mappings\": {\r\n \"dynamic\": true,\r\n \"_source\": {},\r\n \"dynamic_templates\": [\r\n {\r\n \"histogram\": {\r\n \"mapping\": {\r\n \"type\": \"histogram\"\r\n }\r\n }\r\n },\r\n```\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a61c7293c004630a9440c5943f453e60d23c595c"}},"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/210200","number":210200,"mergeCommit":{"message":"[Fleet] update component templates with deprecated setting (#210200)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/209087\r\n\r\nAdded logic to Fleet setup that queries component templates with the\r\ndeprecated `_source.mode` setting.\r\nQuerying only `metrics-*` prefixed component templates, I think only\r\nthose use `_source.mode` setting.\r\n\r\nSteps to verify:\r\n- Upload\r\n[apm-8.8.0.zip](https://github.com/user-attachments/files/18708082/apm-8.8.0.zip)\r\npackage to http://localhost:5601/app/integrations/create/upload\r\n- Deprecation warnings should appear in Upgrade assistant\r\nhttp://localhost:5601/app/management/stack/upgrade_assistant/es_deprecations\r\n- Visit Fleet UI or run setup API to let setup logic run\r\n- Verify that deprecations disappeared\r\n- Verify that the component templates are updated\r\n\r\n<img width=\"1190\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20c4265f-461e-46d1-b075-6ba1111ef9d2\"\r\n/>\r\n\r\n<img width=\"2533\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6961c885-7a91-4d07-90b9-c01a8c133cc9\"\r\n/>\r\n\r\n<img width=\"901\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6b712f94-fd9c-4038-8dc4-cfcf7650cca7\"\r\n/>\r\n\r\n```\r\n[2025-02-07T15:39:42.396+01:00][DEBUG][plugins.fleet] Update deprecated _source.mode in component templates\r\n[2025-02-07T15:39:42.401+01:00][DEBUG][plugins.fleet] Updating component templates with deprecated _source.mode config: metrics-apm.app@package,metrics-apm.internal@package,metrics-apm.service_transaction.1m@package,metrics-apm.service_destination.60m@package,metrics-apm.transaction.1m@package,metrics-apm.service_summary.10m@package,metrics-apm.transaction.10m@package,metrics-apm.service_transaction.10m@package,metrics-apm.transaction.60m@package,metrics-apm.service_destination.10m@package,metrics-apm.service_summary.1m@package,metrics-apm.service_destination.1m@package,metrics-apm.service_transaction.60m@package,metrics-apm.service_summary.60m@package\r\n\r\n\r\nGET _component_template/metrics-*\r\n\r\n{\r\n \"component_templates\": [\r\n {\r\n \"name\": \"metrics-apm.app@package\",\r\n \"component_template\": {\r\n \"template\": {\r\n \"settings\": {\r\n \"index\": {\r\n \"lifecycle\": {\r\n \"name\": \"metrics-apm.app_metrics-default_policy\"\r\n },\r\n \"default_pipeline\": \"metrics-apm.app-8.8.0\",\r\n \"mapping\": {\r\n \"total_fields\": {\r\n \"limit\": \"1000\"\r\n },\r\n \"source\": {\r\n \"mode\": \"synthetic\"\r\n }\r\n }\r\n }\r\n },\r\n \"mappings\": {\r\n \"dynamic\": true,\r\n \"_source\": {},\r\n \"dynamic_templates\": [\r\n {\r\n \"histogram\": {\r\n \"mapping\": {\r\n \"type\": \"histogram\"\r\n }\r\n }\r\n },\r\n```\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a61c7293c004630a9440c5943f453e60d23c595c"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
da50c0aceb
|
[8.18] [APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999) (#210318)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)](https://github.com/elastic/kibana/pull/209999) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T09:52:00Z","message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","apm","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage","number":209999,"url":"https://github.com/elastic/kibana/pull/209999","mergeCommit":{"message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb"}},"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/209999","number":209999,"mergeCommit":{"message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com> |
||
elastic-vault-github-plugin-prod[bot]
|
d723bc5f2c
|
[8.18] Sync bundled packages with Package Storage (#210236)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2233 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Achyut Jhunjhunwala
|
f4a95ef512
|
[8.18] [Logs Explorer] Fix show all logs issue with data source selector (#210158) (#210305)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[Logs Explorer] Fix show all logs issue with data source selector (#210158)](https://github.com/elastic/kibana/pull/210158) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Achyut Jhunjhunwala","email":"achyut.jhunjhunwala@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T12:34:22Z","message":"[Logs Explorer] Fix show all logs issue with data source selector (#210158)\n\n## Summary\n\nCloses - https://github.com/elastic/kibana/issues/208557\n\n1 word change\n\n## What was the issue\n\nUser selected `logSources` setting was not respected by Logs Explorer\nData Source Selector\n\n\n\n\n## What was done to fix it ?\n\n- We fetch the `logSources` from Kibana Advance Settings. This part\nstill happens.\n- When the page load, we initialize 3 state machines in order\n- Observability Logs Explorer - This state machine does the call to\n`uiSettings` to get the default list of `logSources` which the user has\nset. For example -\n`remote_cluster:filebeat-*,remote_cluster:logs-*,remote_cluster:kibana_sample_data_logs*,filebeat-*,kibana_sample_data_logs*,logs-*`\n- Now the `Observability Logs Explorer` state machine initializes the\n`Logs Explorer` state machine and passes this value of `allSelection`\ninside the `initialState` property to this state machine.\n- Now the `Logs Explorer` state machine initialises the `Data Source\nSelector` state machine where it passes a default `initialState` to this\nmachine but misses to pass the definition of `allSelection`.\n \nDue to which this state machine uses a default value for `allSelection`\nwhich is set to `logs-*-*` hardcoded in the code.\n \nHence the value which the user has set in Kibana Advance Settings is not\nrespected any more.\n \nThe way the state machines are designed, 1st time when page loads, the\nuser selected value is passed as selected value. Where as when user\nmanually changes to different data source and then again clicks on `All\nLogs`, since this `DataSourceSelector` state machine, does not know the\nset value for `allSelection` it uses a hard coded value from the code\nwhich is `logs-*-*` instead of the one retrieved from `logSources`\nsettings","sha":"c43e21254b18acd3b3d0eb9790a00b3d82b93c0c","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","v8.18.0","v8.17.3"],"title":"[Logs Explorer] Fix show all logs issue with data source selector","number":210158,"url":"https://github.com/elastic/kibana/pull/210158","mergeCommit":{"message":"[Logs Explorer] Fix show all logs issue with data source selector (#210158)\n\n## Summary\n\nCloses - https://github.com/elastic/kibana/issues/208557\n\n1 word change\n\n## What was the issue\n\nUser selected `logSources` setting was not respected by Logs Explorer\nData Source Selector\n\n\n\n\n## What was done to fix it ?\n\n- We fetch the `logSources` from Kibana Advance Settings. This part\nstill happens.\n- When the page load, we initialize 3 state machines in order\n- Observability Logs Explorer - This state machine does the call to\n`uiSettings` to get the default list of `logSources` which the user has\nset. For example -\n`remote_cluster:filebeat-*,remote_cluster:logs-*,remote_cluster:kibana_sample_data_logs*,filebeat-*,kibana_sample_data_logs*,logs-*`\n- Now the `Observability Logs Explorer` state machine initializes the\n`Logs Explorer` state machine and passes this value of `allSelection`\ninside the `initialState` property to this state machine.\n- Now the `Logs Explorer` state machine initialises the `Data Source\nSelector` state machine where it passes a default `initialState` to this\nmachine but misses to pass the definition of `allSelection`.\n \nDue to which this state machine uses a default value for `allSelection`\nwhich is set to `logs-*-*` hardcoded in the code.\n \nHence the value which the user has set in Kibana Advance Settings is not\nrespected any more.\n \nThe way the state machines are designed, 1st time when page loads, the\nuser selected value is passed as selected value. Where as when user\nmanually changes to different data source and then again clicks on `All\nLogs`, since this `DataSourceSelector` state machine, does not know the\nset value for `allSelection` it uses a hard coded value from the code\nwhich is `logs-*-*` instead of the one retrieved from `logSources`\nsettings","sha":"c43e21254b18acd3b3d0eb9790a00b3d82b93c0c"}},"sourceBranch":"8.x","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.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Ahmad Bamieh
|
4b395d25dd
|
[8.18] [Upgrade Assistant] [Core] Data streams readonly flow (#209562) (#210302)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[Upgrade Assistant] [Core] Data streams readonly flow (#209562)](https://github.com/elastic/kibana/pull/209562) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2025-02-09T16:45:18Z","message":"[Upgrade Assistant] [Core] Data streams readonly flow (#209562)\n\n## Data streams readonly flow\r\n\r\nImplement marking data streams as read only in addition to the already\r\nexisting reindex flow.\r\n\r\n---------\r\n\r\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"9afc910ac4c31d90e993cfd7d06657a67a738fdc","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","v8.18.0","v8.19.0"],"title":"[Upgrade Assistant] [Core] Data streams readonly flow","number":209562,"url":"https://github.com/elastic/kibana/pull/209562","mergeCommit":{"message":"[Upgrade Assistant] [Core] Data streams readonly flow (#209562)\n\n## Data streams readonly flow\r\n\r\nImplement marking data streams as read only in addition to the already\r\nexisting reindex flow.\r\n\r\n---------\r\n\r\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"9afc910ac4c31d90e993cfd7d06657a67a738fdc"}},"sourceBranch":"8.x","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Jatin Kathuria
|
45f6001978
|
[8.18] [Security Solution] Fix timeline dynamic batching (#204034) | [ Security Solution ] Fix Refetch logic with new timeline batching (#205893) (#210066)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix timeline dynamic batching (#204034)](https://github.com/elastic/kibana/pull/204034) - [[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)](https://github.com/elastic/kibana/pull/205893) <!--- Backport version: 9.6.4 --> ### 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-01-07T06:20:30Z","message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport missing","v9.0.0","Team:Threat Hunting:Investigations","backport:prev-minor","v8.16.3","v8.19.0"],"title":"[Security Solution] Fix timeline dynamic batching","number":204034,"url":"https://github.com/elastic/kibana/pull/204034","mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204034","number":204034,"mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/205674","number":205674,"state":"OPEN"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/205676","number":205676,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/205702","number":205702,"branch":"8.x","state":"MERGED","mergeCommit":{"sha":"e480de112ae6bc121c4415e2e1726dd551805672","message":"[8.x] [Security Solution] Fix timeline dynamic batching (#204034) (#205702)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Fix timeline dynamic batching\n(#204034)](https://github.com/elastic/kibana/pull/204034)\n - https://github.com/elastic/kibana/pull/205893\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-07T06:20:30Z\",\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"v8.16.3\"],\"number\":204034,\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"number\":204034,\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},{\"branch\":\"8.16\",\"label\":\"v8.16.3\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/205674\",\"number\":205674,\"state\":\"OPEN\"},{\"url\":\"https://github.com/elastic/kibana/pull/205676\",\"number\":205676,\"branch\":\"8.17\",\"state\":\"OPEN\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]},{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T21:12:38Z","message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\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\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":"54b4fac705c231b52396d70906f3259f9b129a3b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v9.1.0"],"title":"[ Security Solution ] Fix Refetch logic with new timeline batching","number":205893,"url":"https://github.com/elastic/kibana/pull/205893","mergeCommit":{"message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\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\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":"54b4fac705c231b52396d70906f3259f9b129a3b"}},"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/209916","number":209916,"state":"MERGED","mergeCommit":{"sha":"aeaff4957aded708fecfa0e57f16b3cba5f77485","message":"[9.0] [ Security Solution ] Fix Refetch logic with new timeline batching (#205893) (#209916)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[ Security Solution ] Fix Refetch logic with new timeline batching\n(#205893)](https://github.com/elastic/kibana/pull/205893)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T21:12:38Z\",\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"backport\",\"release_note:skip\",\"Team:Threat\nHunting:Investigations\",\"v8.9.1\",\"v9.1.0\"],\"title\":\"[ Security Solution\n] Fix Refetch logic with new timeline\nbatching\",\"number\":205893,\"url\":\"https://github.com/elastic/kibana/pull/205893\",\"mergeCommit\":{\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.9\"],\"targetPullRequestStates\":[{\"branch\":\"8.9\",\"label\":\"v8.9.1\",\"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/205893\",\"number\":205893,\"mergeCommit\":{\"message\":\"[\nSecurity Solution ] Fix Refetch logic with new timeline batching\n(#205893)\\n\\n## Summary\\n\\nPR :\nhttps://github.com/elastic/kibana/pull/204034 fixed some issues\\nwith\ntimeline batching. It was not able to fix one of the issue\nwith\\n`Refetch` logic which exists in `main` ( resulting in a flaky test\n) and\\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\\n\\n##\nIssue Description\\n\\nThere are 2 issues with below video:\\n\\n1. When\nuser updates a status of an alert, the `Refetch` only happens on\\nthe\nfirst `batch`. This behaviour is flaky currently. Even if the user\\nis\non nth batch, table will fetch 0th batch and reset the user's page\\nback\nto\n1.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\\n\n\\n\\n\\n3. When user clicks `Refresh` manually, then also only first\n(0th)\\n`batch` is fetched, which should have rather fetched all the\npresent\\nbatches.\\n\\n\\n\\n\\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\\n\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\",\"sha\":\"54b4fac705c231b52396d70906f3259f9b129a3b\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205893","number":205893,"mergeCommit":{"message":"[ Security Solution ] Fix Refetch logic with new timeline batching (#205893)\n\n## Summary\n\nPR : https://github.com/elastic/kibana/pull/204034 fixed some issues\nwith timeline batching. It was not able to fix one of the issue with\n`Refetch` logic which exists in `main` ( resulting in a flaky test ) and\ncausing some tests to fail in `8.16`, `8.17` and `8.x`.\n\n## Issue Description\n\nThere are 2 issues with below video:\n\n1. When user updates a status of an alert, the `Refetch` only happens on\nthe first `batch`. This behaviour is flaky currently. Even if the user\nis on nth batch, table will fetch 0th batch and reset the user's page\nback to 1.\n\n\n\nhttps://github.com/user-attachments/assets/eaf88a82-0e9b-4743-8b2d-60fd327a2443\n \n\n\n3. When user clicks `Refresh` manually, then also only first (0th)\n`batch` is fetched, which should have rather fetched all the present\nbatches.\n\n\n\n\nhttps://github.com/user-attachments/assets/8d578ce3-4f24-4e70-bc3a-ed6ba99167a0\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\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":"54b4fac705c231b52396d70906f3259f9b129a3b"}},{"url":"https://github.com/elastic/kibana/pull/205676","number":205676,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/205702","number":205702,"branch":"8.x","state":"MERGED","mergeCommit":{"sha":"e480de112ae6bc121c4415e2e1726dd551805672","message":"[8.x] [Security Solution] Fix timeline dynamic batching (#204034) (#205702)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Fix timeline dynamic batching\n(#204034)](https://github.com/elastic/kibana/pull/204034)\n - https://github.com/elastic/kibana/pull/205893\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jatin\nKathuria\",\"email\":\"jatin.kathuria@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-07T06:20:30Z\",\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"v8.16.3\"],\"number\":204034,\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/204034\",\"number\":204034,\"mergeCommit\":{\"message\":\"[Security\nSolution] Fix timeline dynamic batching (#204034)\\n\\n##\nSummary\\r\\n\\r\\nHandles :\\r\\n\\r\\n\\r\\n### Issue with Batches\\r\\n-\nhttps://github.com/elastic/kibana/issues/201405\\r\\n- Timeline had a bug\nwhere if users fetched multiple batches and then if\\r\\nuser adds a new\ncolumn, the value of this new columns will only be\\r\\nfetched for the\nlatest batch and not old batches.\\r\\n- This PR fixes that ✅ by\ncumulatively fetching the data for old batches\\r\\ntill current batch\n`iff a new column has been added`.\\r\\n- For example, if user has already\nfetched the 3rd batch, data for\\r\\n1st,2nd and 3rd will be fetched\ntogether when a column has been added,\\r\\notherwise, data will be\nfetched incrementally.\\r\\n\\r\\n### Issue with Elastic search\nlimit\\r\\n\\r\\n- Elastic search has a limit of 10K hits at max but we\nthrow error at\\r\\n10K which should be allowed.\\r\\n - Error should be\nthrown at anything `>10K`. 10001 for example.\\r\\n - ✅ This PR fixes that\njust for timeline by allowing 10K hits.\\r\\n\\r\\n### Removal of obsolete\ncode\\r\\n\\r\\nBelow files related to old Timeline code are removed as\nwell:\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\\r\\n-\\r\\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nPhilippe Oberti\n<philippe.oberti@elastic.co>\",\"sha\":\"088169f446788f9fa8800d77817881524514943e\"}},{\"branch\":\"8.16\",\"label\":\"v8.16.3\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/205674\",\"number\":205674,\"state\":\"OPEN\"},{\"url\":\"https://github.com/elastic/kibana/pull/205676\",\"number\":205676,\"branch\":\"8.17\",\"state\":\"OPEN\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"url":"https://github.com/elastic/kibana/pull/205674","number":205674,"branch":"8.16","state":"OPEN"}]}] BACKPORT--> |
||
Philippe Oberti
|
e45df29559
|
[8.18] [Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225) (#210288)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)](https://github.com/elastic/kibana/pull/210225) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T22:34:27Z","message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967","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:Investigations","backport:version","v8.18.0","v9.1.0","v8.17.3","v8.16.5"],"title":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel","number":210225,"url":"https://github.com/elastic/kibana/pull/210225","mergeCommit":{"message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17","8.16"],"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/210225","number":210225,"mergeCommit":{"message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
8b58df5ade
|
[8.18] [Rule Migration] Add tests for telemetry (#210081) (#210283)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rule Migration] Add tests for telemetry (#210081)](https://github.com/elastic/kibana/pull/210081) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marius Iversen","email":"marius.iversen@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T19:12:19Z","message":"[Rule Migration] Add tests for telemetry (#210081)\n\n## Summary\n\nResolves a minor issue in reporting telemetry events in SIEM migrations\nwith errors, also adds tests for these scenarios.","sha":"8374def50810128339784822c8ea08cfce591a62","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rule Migration] Add tests for telemetry","number":210081,"url":"https://github.com/elastic/kibana/pull/210081","mergeCommit":{"message":"[Rule Migration] Add tests for telemetry (#210081)\n\n## Summary\n\nResolves a minor issue in reporting telemetry events in SIEM migrations\nwith errors, also adds tests for these scenarios.","sha":"8374def50810128339784822c8ea08cfce591a62"}},"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/210103","number":210103,"state":"MERGED","mergeCommit":{"sha":"5aaa607c193fcdbaf33e6a3d8fe1880970e12956","message":"[9.0] [Rule Migration] Add tests for telemetry (#210081) (#210103)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Rule Migration] Add tests for telemetry\n(#210081)](https://github.com/elastic/kibana/pull/210081)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Marius\nIversen\",\"email\":\"marius.iversen@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-06T19:12:19Z\",\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\",\"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:\nSecuritySolution\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[Rule\nMigration] Add tests for\ntelemetry\",\"number\":210081,\"url\":\"https://github.com/elastic/kibana/pull/210081\",\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\"}},\"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/210081\",\"number\":210081,\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Marius Iversen <marius.iversen@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/210081","number":210081,"mergeCommit":{"message":"[Rule Migration] Add tests for telemetry (#210081)\n\n## Summary\n\nResolves a minor issue in reporting telemetry events in SIEM migrations\nwith errors, also adds tests for these scenarios.","sha":"8374def50810128339784822c8ea08cfce591a62"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210102","number":210102,"state":"MERGED","mergeCommit":{"sha":"ae05c428d7a66075dd4743c465c0b85ce849be57","message":"[8.x] [Rule Migration] Add tests for telemetry (#210081) (#210102)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Rule Migration] Add tests for telemetry\n(#210081)](https://github.com/elastic/kibana/pull/210081)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Marius\nIversen\",\"email\":\"marius.iversen@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-06T19:12:19Z\",\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\",\"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:\nSecuritySolution\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[Rule\nMigration] Add tests for\ntelemetry\",\"number\":210081,\"url\":\"https://github.com/elastic/kibana/pull/210081\",\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\"}},\"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/210081\",\"number\":210081,\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add tests for telemetry (#210081)\\n\\n## Summary\\n\\nResolves a\nminor issue in reporting telemetry events in SIEM migrations\\nwith\nerrors, also adds tests for these\nscenarios.\",\"sha\":\"8374def50810128339784822c8ea08cfce591a62\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Marius Iversen <marius.iversen@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Marius Iversen <marius.iversen@elastic.co> |
||
|
Kibana Machine
|
7f8c1560ae
|
[8.18] Update dependency @types/diff to ^7.0.1 (main) (#210138) (#210279)
# Backport This will backport the following commits from `main` to `8.18`: - [Update dependency @types/diff to ^7.0.1 (main) (#210138)](https://github.com/elastic/kibana/pull/210138) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-07T21:11:42Z","message":"Update dependency @types/diff to ^7.0.1 (main) (#210138)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n|\r\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\r\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\r\n| devDependencies | patch | [`^7.0.0` ->\r\n`^7.0.1`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.0/7.0.1) |\r\n\r\n---\r\n\r\n### Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\r\nAutomerge - At any time (no schedule defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis PR has been generated by [Renovate\r\nBot](https://redirect.github.com/renovatebot/renovate).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOkRhdGFEaXNjb3ZlcnkiLCJiYWNrcG9ydDphbGwtb3BlbiIsInJlbGVhc2Vfbm90ZTpza2lwIl19-->\r\n\r\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ed4c5d53084277d7b092d6a9f647d26703e0ab7f","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:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Update dependency @types/diff to ^7.0.1 (main)","number":210138,"url":"https://github.com/elastic/kibana/pull/210138","mergeCommit":{"message":"Update dependency @types/diff to ^7.0.1 (main) (#210138)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n|\r\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\r\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\r\n| devDependencies | patch | [`^7.0.0` ->\r\n`^7.0.1`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.0/7.0.1) |\r\n\r\n---\r\n\r\n### Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\r\nAutomerge - At any time (no schedule defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis PR has been generated by [Renovate\r\nBot](https://redirect.github.com/renovatebot/renovate).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOkRhdGFEaXNjb3ZlcnkiLCJiYWNrcG9ydDphbGwtb3BlbiIsInJlbGVhc2Vfbm90ZTpza2lwIl19-->\r\n\r\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ed4c5d53084277d7b092d6a9f647d26703e0ab7f"}},"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/210138","number":210138,"mergeCommit":{"message":"Update dependency @types/diff to ^7.0.1 (main) (#210138)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n|\r\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\r\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\r\n| devDependencies | patch | [`^7.0.0` ->\r\n`^7.0.1`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.0/7.0.1) |\r\n\r\n---\r\n\r\n### Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\r\nAutomerge - At any time (no schedule defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis PR has been generated by [Renovate\r\nBot](https://redirect.github.com/renovatebot/renovate).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOkRhdGFEaXNjb3ZlcnkiLCJiYWNrcG9ydDphbGwtb3BlbiIsInJlbGVhc2Vfbm90ZTpza2lwIl19-->\r\n\r\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ed4c5d53084277d7b092d6a9f647d26703e0ab7f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
083e103425
|
[8.18] [Obs AI Assistant] Update the simulate function calling setting to support "auto" (#209628) (#210276)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Update the simulate function calling setting to support "auto" (#209628)](https://github.com/elastic/kibana/pull/209628) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T21:07:20Z","message":"[Obs AI Assistant] Update the simulate function calling setting to support \"auto\" (#209628)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/198\n\n## Summary\n\nThe simulated function calling setting is currently a boolean. It needs\nto be updated to support the option `auto`.\n`export type FunctionCallingMode = 'native' | 'simulated' | 'auto';`\n\nIf the setting is set to `false`, `auto` will be passed to the inference\nclient. If the setting is `true`, `simulated` will be passed to it.\n\nRelates to https://github.com/elastic/kibana/pull/208144\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"343b80a8a0bd231791b1b8fc3fb213938b0b1c23","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Update the simulate function calling setting to support \"auto\"","number":209628,"url":"https://github.com/elastic/kibana/pull/209628","mergeCommit":{"message":"[Obs AI Assistant] Update the simulate function calling setting to support \"auto\" (#209628)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/198\n\n## Summary\n\nThe simulated function calling setting is currently a boolean. It needs\nto be updated to support the option `auto`.\n`export type FunctionCallingMode = 'native' | 'simulated' | 'auto';`\n\nIf the setting is set to `false`, `auto` will be passed to the inference\nclient. If the setting is `true`, `simulated` will be passed to it.\n\nRelates to https://github.com/elastic/kibana/pull/208144\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"343b80a8a0bd231791b1b8fc3fb213938b0b1c23"}},"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/209628","number":209628,"mergeCommit":{"message":"[Obs AI Assistant] Update the simulate function calling setting to support \"auto\" (#209628)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/198\n\n## Summary\n\nThe simulated function calling setting is currently a boolean. It needs\nto be updated to support the option `auto`.\n`export type FunctionCallingMode = 'native' | 'simulated' | 'auto';`\n\nIf the setting is set to `false`, `auto` will be passed to the inference\nclient. If the setting is `true`, `simulated` will be passed to it.\n\nRelates to https://github.com/elastic/kibana/pull/208144\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"343b80a8a0bd231791b1b8fc3fb213938b0b1c23"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
238e2aaf7e
|
[8.18] [Obs AI Assistant] Update colors in the AI Assistant icon (#210233) (#210272)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Update colors in the AI Assistant icon (#210233)](https://github.com/elastic/kibana/pull/210233) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T21:00:50Z","message":"[Obs AI Assistant] Update colors in the AI Assistant icon (#210233)\n\nCloses https://github.com/elastic/kibana/issues/208816\n\n## Summary\n\nUpdate the AI Assistant icon colors\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"77ea8fe8f1974b8f604a3195367df793c3682c20","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Update colors in the AI Assistant icon","number":210233,"url":"https://github.com/elastic/kibana/pull/210233","mergeCommit":{"message":"[Obs AI Assistant] Update colors in the AI Assistant icon (#210233)\n\nCloses https://github.com/elastic/kibana/issues/208816\n\n## Summary\n\nUpdate the AI Assistant icon colors\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"77ea8fe8f1974b8f604a3195367df793c3682c20"}},"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/210233","number":210233,"mergeCommit":{"message":"[Obs AI Assistant] Update colors in the AI Assistant icon (#210233)\n\nCloses https://github.com/elastic/kibana/issues/208816\n\n## Summary\n\nUpdate the AI Assistant icon colors\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"77ea8fe8f1974b8f604a3195367df793c3682c20"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
32e744184c
|
[8.18] ESQL: Add reference entry for LOOKUP JOIN (#210201) (#210265)
# Backport This will backport the following commits from `main` to `8.18`: - [ESQL: Add reference entry for LOOKUP JOIN (#210201)](https://github.com/elastic/kibana/pull/210201) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexander Spies","email":"alexander.spies@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T20:39:10Z","message":"ESQL: Add reference entry for LOOKUP JOIN (#210201)\n\nI couldn't verify if this builds correctly, as I couldn't quickly whip\r\nup a dev environment locally that could build this. Is there a preview\r\nbuilt by the CI?\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"3915d3310cb9b05f598241858aa1bed2cde4c8d6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"ESQL: Add reference entry for LOOKUP JOIN","number":210201,"url":"https://github.com/elastic/kibana/pull/210201","mergeCommit":{"message":"ESQL: Add reference entry for LOOKUP JOIN (#210201)\n\nI couldn't verify if this builds correctly, as I couldn't quickly whip\r\nup a dev environment locally that could build this. Is there a preview\r\nbuilt by the CI?\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"3915d3310cb9b05f598241858aa1bed2cde4c8d6"}},"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/210201","number":210201,"mergeCommit":{"message":"ESQL: Add reference entry for LOOKUP JOIN (#210201)\n\nI couldn't verify if this builds correctly, as I couldn't quickly whip\r\nup a dev environment locally that could build this. Is there a preview\r\nbuilt by the CI?\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"3915d3310cb9b05f598241858aa1bed2cde4c8d6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alexander Spies <alexander.spies@elastic.co> |
||
wajihaparvez
|
a7710a933c
|
[Docs] Backport 8.17.2 release notes to 8.18 (#210269)
## Summary Backporting 8.17.2 release notes. Rel: [210109](https://github.com/elastic/kibana/pull/210109) |
||
|
Kibana Machine
|
b2aa2afb98
|
[8.18] [ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls (#210039) (#210255)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls (#210039)](https://github.com/elastic/kibana/pull/210039) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-07T20:04:35Z","message":"[ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls (#210039)\n\n## Summary\n\nThis PR addresses https://github.com/elastic/kibana/issues/204246 and\nfixes Log rate analysis and change point detection embeddable not\nupdating based on Dashboard's controls\n\n\nhttps://github.com/user-attachments/assets/e6750cca-b579-49e8-af89-4effb3a7536e\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8ce4eefad56a300c95201ff45bb2a6b6c200d147","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls","number":210039,"url":"https://github.com/elastic/kibana/pull/210039","mergeCommit":{"message":"[ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls (#210039)\n\n## Summary\n\nThis PR addresses https://github.com/elastic/kibana/issues/204246 and\nfixes Log rate analysis and change point detection embeddable not\nupdating based on Dashboard's controls\n\n\nhttps://github.com/user-attachments/assets/e6750cca-b579-49e8-af89-4effb3a7536e\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8ce4eefad56a300c95201ff45bb2a6b6c200d147"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210039","number":210039,"mergeCommit":{"message":"[ML] Fix Log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls (#210039)\n\n## Summary\n\nThis PR addresses https://github.com/elastic/kibana/issues/204246 and\nfixes Log rate analysis and change point detection embeddable not\nupdating based on Dashboard's controls\n\n\nhttps://github.com/user-attachments/assets/e6750cca-b579-49e8-af89-4effb3a7536e\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8ce4eefad56a300c95201ff45bb2a6b6c200d147"}}]}] BACKPORT--> Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com> |
||
|
wajihaparvez
|
15fff000b1
|
[Docs] Backport 8.16.4 release notes to 8.18 (#210261)
## Summary Backporting 8.16.4 release notes. Rel: [210108](https://github.com/elastic/kibana/pull/210108) Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
49991eb7df
|
[8.18] [ML] Show analysis not available for vector fields in Index Data Visualizer (#209945) (#210250)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Show analysis not available for vector fields in Index Data Visualizer (#209945)](https://github.com/elastic/kibana/pull/209945) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-07T19:39:59Z","message":"[ML] Show analysis not available for vector fields in Index Data Visualizer (#209945)\n\n## Summary\n\nIn 9.0, vector fields like vector embeddings or offsets are no longer\nexposed in Elasticsearch API, which makes it not possible to sample the\ncount and show examples This PR makes it so that the expanded rows for\nthese fields indicate analysis is not available for these fields.\n\n<img width=\"1295\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/60a95883-2918-4af5-821a-8f8a006d8441\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"14eefced0fb7f36b609d7a643215b158211e1b91","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[ML] Show analysis not available for vector fields in Index Data Visualizer","number":209945,"url":"https://github.com/elastic/kibana/pull/209945","mergeCommit":{"message":"[ML] Show analysis not available for vector fields in Index Data Visualizer (#209945)\n\n## Summary\n\nIn 9.0, vector fields like vector embeddings or offsets are no longer\nexposed in Elasticsearch API, which makes it not possible to sample the\ncount and show examples This PR makes it so that the expanded rows for\nthese fields indicate analysis is not available for these fields.\n\n<img width=\"1295\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/60a95883-2918-4af5-821a-8f8a006d8441\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"14eefced0fb7f36b609d7a643215b158211e1b91"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209945","number":209945,"mergeCommit":{"message":"[ML] Show analysis not available for vector fields in Index Data Visualizer (#209945)\n\n## Summary\n\nIn 9.0, vector fields like vector embeddings or offsets are no longer\nexposed in Elasticsearch API, which makes it not possible to sample the\ncount and show examples This PR makes it so that the expanded rows for\nthese fields indicate analysis is not available for these fields.\n\n<img width=\"1295\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/60a95883-2918-4af5-821a-8f8a006d8441\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"14eefced0fb7f36b609d7a643215b158211e1b91"}}]}] BACKPORT--> Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com> |
||
Marius Iversen
|
d600232af9
|
[8.18] [Rule Migration] Add telemetry events to translation graphs (#209352) (#209962)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rule Migration] Add telemetry events to translation graphs (#209352)](https://github.com/elastic/kibana/pull/209352) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marius Iversen","email":"marius.iversen@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T21:12:50Z","message":"[Rule Migration] Add telemetry events to translation graphs (#209352)\n\n## Summary\n\nThis PR adds telemetry events to SIEM migration backend using the event\nbased telemetry already existing in security solutions.\n\nHere is a list of events:\n\n```typescript\nexport const SIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n translationResult: string;\n prebuiltMatch: boolean;\n}\n\nexport const SIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterRuleNames: string[];\n preFilterRuleCount: number;\n postFilterRuleName: string;\n postFilterRuleCount: number;\n}\n\nexport const SIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterIntegrationNames: string[];\n preFilterIntegrationCount: number;\n postFilterIntegrationName: string;\n postFilterIntegrationCount: number;\n}\n\nexport const SIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n}\n```","sha":"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rule Migration] Add telemetry events to translation graphs","number":209352,"url":"https://github.com/elastic/kibana/pull/209352","mergeCommit":{"message":"[Rule Migration] Add telemetry events to translation graphs (#209352)\n\n## Summary\n\nThis PR adds telemetry events to SIEM migration backend using the event\nbased telemetry already existing in security solutions.\n\nHere is a list of events:\n\n```typescript\nexport const SIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n translationResult: string;\n prebuiltMatch: boolean;\n}\n\nexport const SIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterRuleNames: string[];\n preFilterRuleCount: number;\n postFilterRuleName: string;\n postFilterRuleCount: number;\n}\n\nexport const SIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterIntegrationNames: string[];\n preFilterIntegrationCount: number;\n postFilterIntegrationName: string;\n postFilterIntegrationCount: number;\n}\n\nexport const SIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n}\n```","sha":"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8"}},"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/209915","number":209915,"state":"MERGED","mergeCommit":{"sha":"80d0eb6e5bca24fb8d0b908703d0e23fbd42d95c","message":"[9.0] [Rule Migration] Add telemetry events to translation graphs (#209352) (#209915)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Rule Migration] Add telemetry events to translation graphs\n(#209352)](https://github.com/elastic/kibana/pull/209352)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Marius\nIversen\",\"email\":\"marius.iversen@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T21:12:50Z\",\"message\":\"[Rule\nMigration] Add telemetry events to translation graphs (#209352)\\n\\n##\nSummary\\n\\nThis PR adds telemetry events to SIEM migration backend using\nthe event\\nbased telemetry already existing in security\nsolutions.\\n\\nHere is a list of events:\\n\\n```typescript\\nexport const\nSIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n duration: number;\\n completed: number;\\n failed:\nnumber;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\\n model:\nstring;\\n migrationId: string;\\n duration: number;\\n translationResult:\nstring;\\n prebuiltMatch: boolean;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterRuleNames: string[];\\n\npreFilterRuleCount: number;\\n postFilterRuleName: string;\\n\npostFilterRuleCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterIntegrationNames: string[];\\n\npreFilterIntegrationCount: number;\\n postFilterIntegrationName:\nstring;\\n postFilterIntegrationCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\\n model: string;\\n\nerror: string;\\n migrationId: string;\\n duration: number;\\n completed:\nnumber;\\n failed: number;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\\n model:\nstring;\\n error: string;\\n migrationId:\nstring;\\n}\\n```\",\"sha\":\"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8\",\"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:\nSecuritySolution\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[Rule\nMigration] Add telemetry events to translation\ngraphs\",\"number\":209352,\"url\":\"https://github.com/elastic/kibana/pull/209352\",\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add telemetry events to translation graphs (#209352)\\n\\n##\nSummary\\n\\nThis PR adds telemetry events to SIEM migration backend using\nthe event\\nbased telemetry already existing in security\nsolutions.\\n\\nHere is a list of events:\\n\\n```typescript\\nexport const\nSIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n duration: number;\\n completed: number;\\n failed:\nnumber;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\\n model:\nstring;\\n migrationId: string;\\n duration: number;\\n translationResult:\nstring;\\n prebuiltMatch: boolean;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterRuleNames: string[];\\n\npreFilterRuleCount: number;\\n postFilterRuleName: string;\\n\npostFilterRuleCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterIntegrationNames: string[];\\n\npreFilterIntegrationCount: number;\\n postFilterIntegrationName:\nstring;\\n postFilterIntegrationCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\\n model: string;\\n\nerror: string;\\n migrationId: string;\\n duration: number;\\n completed:\nnumber;\\n failed: number;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\\n model:\nstring;\\n error: string;\\n migrationId:\nstring;\\n}\\n```\",\"sha\":\"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8\"}},\"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/209352\",\"number\":209352,\"mergeCommit\":{\"message\":\"[Rule\nMigration] Add telemetry events to translation graphs (#209352)\\n\\n##\nSummary\\n\\nThis PR adds telemetry events to SIEM migration backend using\nthe event\\nbased telemetry already existing in security\nsolutions.\\n\\nHere is a list of events:\\n\\n```typescript\\nexport const\nSIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n duration: number;\\n completed: number;\\n failed:\nnumber;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\\n model:\nstring;\\n migrationId: string;\\n duration: number;\\n translationResult:\nstring;\\n prebuiltMatch: boolean;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterRuleNames: string[];\\n\npreFilterRuleCount: number;\\n postFilterRuleName: string;\\n\npostFilterRuleCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\\n model: string;\\n\nmigrationId: string;\\n preFilterIntegrationNames: string[];\\n\npreFilterIntegrationCount: number;\\n postFilterIntegrationName:\nstring;\\n postFilterIntegrationCount: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\\n model: string;\\n\nerror: string;\\n migrationId: string;\\n duration: number;\\n completed:\nnumber;\\n failed: number;\\n total: number;\\n}\\n\\nexport const\nSIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\\n model:\nstring;\\n error: string;\\n migrationId:\nstring;\\n}\\n```\",\"sha\":\"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Marius Iversen <marius.iversen@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/209352","number":209352,"mergeCommit":{"message":"[Rule Migration] Add telemetry events to translation graphs (#209352)\n\n## Summary\n\nThis PR adds telemetry events to SIEM migration backend using the event\nbased telemetry already existing in security solutions.\n\nHere is a list of events:\n\n```typescript\nexport const SIEM_MIGRATIONS_MIGRATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_SUCCESS: EventTypeOpts<{\n model: string;\n migrationId: string;\n duration: number;\n translationResult: string;\n prebuiltMatch: boolean;\n}\n\nexport const SIEM_MIGRATIONS_PREBUILT_RULES_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterRuleNames: string[];\n preFilterRuleCount: number;\n postFilterRuleName: string;\n postFilterRuleCount: number;\n}\n\nexport const SIEM_MIGRATIONS_INTEGRATIONS_MATCH: EventTypeOpts<{\n model: string;\n migrationId: string;\n preFilterIntegrationNames: string[];\n preFilterIntegrationCount: number;\n postFilterIntegrationName: string;\n postFilterIntegrationCount: number;\n}\n\nexport const SIEM_MIGRATIONS_MIGRATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n duration: number;\n completed: number;\n failed: number;\n total: number;\n}\n\nexport const SIEM_MIGRATIONS_RULE_TRANSLATION_FAILURE: EventTypeOpts<{\n model: string;\n error: string;\n migrationId: string;\n}\n```","sha":"6cab1dc6f8cd1f48b17a1ad7546c65cbbd79f4a8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209961","number":209961,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
8777121f36
|
[8.18] [Index Management] Only show standard and lookup index mode in create index modal (#209998) (#210226)
# Backport This will backport the following commits from `main` to `8.18`: - [[Index Management] Only show standard and lookup index mode in create index modal (#209998)](https://github.com/elastic/kibana/pull/209998) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-07T16:56:39Z","message":"[Index Management] Only show standard and lookup index mode in create index modal (#209998)\n\nFixes https://github.com/elastic/kibana/issues/209889\r\n\r\n## Summary\r\n\r\nThis PR removes the \"LogsDB\" and \"Time Series\" index mode options in the\r\ncreate index modal as per the suggestion in\r\nhttps://github.com/elastic/kibana/issues/209889#issuecomment-2638045561.\r\n\r\nThe index mode field was added in\r\nhttps://github.com/elastic/kibana/pull/207413.","sha":"9409a4364b6e0b066ff2b2ed15aabae471a5808f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.18.0","v9.1.0","v8.19.0"],"title":"[Index Management] Only show standard and lookup index mode in create index modal","number":209998,"url":"https://github.com/elastic/kibana/pull/209998","mergeCommit":{"message":"[Index Management] Only show standard and lookup index mode in create index modal (#209998)\n\nFixes https://github.com/elastic/kibana/issues/209889\r\n\r\n## Summary\r\n\r\nThis PR removes the \"LogsDB\" and \"Time Series\" index mode options in the\r\ncreate index modal as per the suggestion in\r\nhttps://github.com/elastic/kibana/issues/209889#issuecomment-2638045561.\r\n\r\nThe index mode field was added in\r\nhttps://github.com/elastic/kibana/pull/207413.","sha":"9409a4364b6e0b066ff2b2ed15aabae471a5808f"}},"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/209998","number":209998,"mergeCommit":{"message":"[Index Management] Only show standard and lookup index mode in create index modal (#209998)\n\nFixes https://github.com/elastic/kibana/issues/209889\r\n\r\n## Summary\r\n\r\nThis PR removes the \"LogsDB\" and \"Time Series\" index mode options in the\r\ncreate index modal as per the suggestion in\r\nhttps://github.com/elastic/kibana/issues/209889#issuecomment-2638045561.\r\n\r\nThe index mode field was added in\r\nhttps://github.com/elastic/kibana/pull/207413.","sha":"9409a4364b6e0b066ff2b2ed15aabae471a5808f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
05caf4f3d9
|
[8.18] [ML] Unskipping transform test (#209109) (#210211)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Unskipping transform test (#209109)](https://github.com/elastic/kibana/pull/209109) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T16:04:14Z","message":"[ML] Unskipping transform test (#209109)\n\nFlaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7844\r\nFlakey tests all passed\r\n\r\nThe underlying cause of this issue has been fixed by\r\nhttps://github.com/elastic/elasticsearch/pull/121912","sha":"fa76d89e48276fa14196fe8330fb28409e37156e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","release_note:skip","Feature:Transforms","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ML] Unskipping transform test","number":209109,"url":"https://github.com/elastic/kibana/pull/209109","mergeCommit":{"message":"[ML] Unskipping transform test (#209109)\n\nFlaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7844\r\nFlakey tests all passed\r\n\r\nThe underlying cause of this issue has been fixed by\r\nhttps://github.com/elastic/elasticsearch/pull/121912","sha":"fa76d89e48276fa14196fe8330fb28409e37156e"}},"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/209109","number":209109,"mergeCommit":{"message":"[ML] Unskipping transform test (#209109)\n\nFlaky test runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7844\r\nFlakey tests all passed\r\n\r\nThe underlying cause of this issue has been fixed by\r\nhttps://github.com/elastic/elasticsearch/pull/121912","sha":"fa76d89e48276fa14196fe8330fb28409e37156e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
Alex Szabo
|
1c8b317cfd | skip failing suite (#207077) | ||
|
Kibana Machine
|
5b7bc0664c
|
[8.18] [Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation (#209314) (#210145)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation (#209314)](https://github.com/elastic/kibana/pull/209314) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-07T09:22:37Z","message":"[Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation (#209314)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana-team/issues/1442\r\n\r\nThis PR replaces a poorly performing regular expression with a constant\r\ntime string manipulation approach.\r\n\r\nContext:\r\nThe regex is used to remove all references from a string when a user\r\ncopies a message from the assistant and when conversation history is\r\npassed to the LLM e.g.\r\n```\r\n\"The sky is blue{reference(1234)} and the grass is green{reference(4321)}\" -> \"The sky is blue and the grass is green\"\r\n```\r\n\r\nChanges:\r\n- Replace the regular expression inside of `removeContentReferences()`\r\n- Add tests to verify new logic is correct.\r\n- Fix a bug in the contentReference markdown parser that was found by\r\n@andrew-goldstein\r\n[here](https://github.com/elastic/kibana/pull/209314/files#r1943198510)\r\n- For alerts page citations, add a filter for open and acknowledge\r\nalerts within the last 24 hours\r\n[here](https://github.com/elastic/kibana/pull/209314/files#diff-f17fbe7edfe72943fecbe5ddd8dca6c024a48fe4f90bf4f66650cef16091b769R36)\r\n\r\n\r\n### How to test new regex:\r\nOne of the changes in this PR improves the performance of a regex. In\r\nreal life, no one has ever reached any performance issues with this\r\nregex's and I don't think it is realistically possible to reach that\r\nlimit without other things breaking (i.e. the message sent to/returned\r\nby the assistant would need to be so large that it would exceed the\r\ncontext window). Therefore, all we can test is that the functionality\r\nstill works as expected after this change.\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask the assistant a question about your alerts or a document in your\r\nKB. The assistant response should contain citations.\r\n- Copy the response to the clipboard using the copy button.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/edded3a3-8cb9-40a8-918e-a9718e7afc22\"\r\n/>\r\n- Your clipboard should contain the response without any citations\r\n\r\n### How to test the alerts page filter\r\n- Ask a question about your open alerts and make sure a citation is\r\nreturned.\r\n- Click on the citation\r\n- Verify a new tab is opened and the alerts page is visible with a\r\nfilter for open and acknowledge alerts and there is a now-24h time\r\nwindow filter.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2bf8a24c5cb56b2ccb16e6c38f18cc9c39d65fcd","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:Security Generative AI","backport:version","v8.18.0","v9.1.0"],"title":"[Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation","number":209314,"url":"https://github.com/elastic/kibana/pull/209314","mergeCommit":{"message":"[Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation (#209314)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana-team/issues/1442\r\n\r\nThis PR replaces a poorly performing regular expression with a constant\r\ntime string manipulation approach.\r\n\r\nContext:\r\nThe regex is used to remove all references from a string when a user\r\ncopies a message from the assistant and when conversation history is\r\npassed to the LLM e.g.\r\n```\r\n\"The sky is blue{reference(1234)} and the grass is green{reference(4321)}\" -> \"The sky is blue and the grass is green\"\r\n```\r\n\r\nChanges:\r\n- Replace the regular expression inside of `removeContentReferences()`\r\n- Add tests to verify new logic is correct.\r\n- Fix a bug in the contentReference markdown parser that was found by\r\n@andrew-goldstein\r\n[here](https://github.com/elastic/kibana/pull/209314/files#r1943198510)\r\n- For alerts page citations, add a filter for open and acknowledge\r\nalerts within the last 24 hours\r\n[here](https://github.com/elastic/kibana/pull/209314/files#diff-f17fbe7edfe72943fecbe5ddd8dca6c024a48fe4f90bf4f66650cef16091b769R36)\r\n\r\n\r\n### How to test new regex:\r\nOne of the changes in this PR improves the performance of a regex. In\r\nreal life, no one has ever reached any performance issues with this\r\nregex's and I don't think it is realistically possible to reach that\r\nlimit without other things breaking (i.e. the message sent to/returned\r\nby the assistant would need to be so large that it would exceed the\r\ncontext window). Therefore, all we can test is that the functionality\r\nstill works as expected after this change.\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask the assistant a question about your alerts or a document in your\r\nKB. The assistant response should contain citations.\r\n- Copy the response to the clipboard using the copy button.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/edded3a3-8cb9-40a8-918e-a9718e7afc22\"\r\n/>\r\n- Your clipboard should contain the response without any citations\r\n\r\n### How to test the alerts page filter\r\n- Ask a question about your open alerts and make sure a citation is\r\nreturned.\r\n- Click on the citation\r\n- Verify a new tab is opened and the alerts page is visible with a\r\nfilter for open and acknowledge alerts and there is a now-24h time\r\nwindow filter.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2bf8a24c5cb56b2ccb16e6c38f18cc9c39d65fcd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209314","number":209314,"mergeCommit":{"message":"[Security Solution] [AI Assistant] Replace polynomial regular expression with constant time string manipulation (#209314)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana-team/issues/1442\r\n\r\nThis PR replaces a poorly performing regular expression with a constant\r\ntime string manipulation approach.\r\n\r\nContext:\r\nThe regex is used to remove all references from a string when a user\r\ncopies a message from the assistant and when conversation history is\r\npassed to the LLM e.g.\r\n```\r\n\"The sky is blue{reference(1234)} and the grass is green{reference(4321)}\" -> \"The sky is blue and the grass is green\"\r\n```\r\n\r\nChanges:\r\n- Replace the regular expression inside of `removeContentReferences()`\r\n- Add tests to verify new logic is correct.\r\n- Fix a bug in the contentReference markdown parser that was found by\r\n@andrew-goldstein\r\n[here](https://github.com/elastic/kibana/pull/209314/files#r1943198510)\r\n- For alerts page citations, add a filter for open and acknowledge\r\nalerts within the last 24 hours\r\n[here](https://github.com/elastic/kibana/pull/209314/files#diff-f17fbe7edfe72943fecbe5ddd8dca6c024a48fe4f90bf4f66650cef16091b769R36)\r\n\r\n\r\n### How to test new regex:\r\nOne of the changes in this PR improves the performance of a regex. In\r\nreal life, no one has ever reached any performance issues with this\r\nregex's and I don't think it is realistically possible to reach that\r\nlimit without other things breaking (i.e. the message sent to/returned\r\nby the assistant would need to be so large that it would exceed the\r\ncontext window). Therefore, all we can test is that the functionality\r\nstill works as expected after this change.\r\n- Enable the feature flag\r\n```yaml\r\n# kibana.dev.yml\r\nxpack.securitySolution.enableExperimental: ['contentReferencesEnabled']\r\n```\r\n- Open the security assistant\r\n- Ask the assistant a question about your alerts or a document in your\r\nKB. The assistant response should contain citations.\r\n- Copy the response to the clipboard using the copy button.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/edded3a3-8cb9-40a8-918e-a9718e7afc22\"\r\n/>\r\n- Your clipboard should contain the response without any citations\r\n\r\n### How to test the alerts page filter\r\n- Ask a question about your open alerts and make sure a citation is\r\nreturned.\r\n- Click on the citation\r\n- Verify a new tab is opened and the alerts page is visible with a\r\nfilter for open and acknowledge alerts and there is a now-24h time\r\nwindow filter.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2bf8a24c5cb56b2ccb16e6c38f18cc9c39d65fcd"}}]}] BACKPORT--> Co-authored-by: Kenneth Kreindler <42113355+KDKHD@users.noreply.github.com> |
||
|
Kibana Machine
|
e08daa97e3
|
[8.18] [EDR Workflows] Fix agent count on policy deploy modal (#209593) (#210043)
# Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Fix agent count on policy deploy modal (#209593)](https://github.com/elastic/kibana/pull/209593) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T15:17:47Z","message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5","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] Fix agent count on policy deploy modal","number":209593,"url":"https://github.com/elastic/kibana/pull/209593","mergeCommit":{"message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5"}},"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/209593","number":209593,"mergeCommit":{"message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5"}}]}] BACKPORT--> --------- Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |
||
Sergi Massaneda
|
a8f9e6e492
|
[8.18] [Security Solution] SIEM Migrations RBAC (#207087) (#210152)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] SIEM Migrations RBAC (#207087)](https://github.com/elastic/kibana/pull/207087) <!--- Backport version: 9.6.4 --> ### 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-02-06T17:41:21Z","message":"[Security Solution] SIEM Migrations RBAC (#207087)\n\n## Summary\r\n\r\nImplements the access controls for SIEM rule migrations.\r\n\r\n## API changes\r\n\r\n- All API routes have been secured with \"SIEM Migration\" feature checks\r\n- Start migration API route now checks if the user has privileges to use\r\nthe connector ID received\r\n \r\n## UI changes\r\n\r\n### Onboarding SIEM migrations\r\n\r\n- AI Connector selection\r\n- Actions & Connectors: Read -> This privilege allows reading and\r\nselecting a connector\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n- Create a migration\r\n - Security All -> Main Security read & write access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n### Rule Translations page\r\n\r\n- Minimum privileges to make the page accessible (read access):\r\n - Security Read -> Main Security read access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n \r\nOtherwise, we hide the link in the navigation and display the generic\r\nempty state if accessed:\r\n\r\n\r\n- To successfully install rules the following privileges are also\r\nrequired (write access):\r\n - Security All -> Main Security read & write access\r\n- Index privileges for `.alerts*` pattern: _read, write,\r\nview_index_metadata, manage_\r\n - Index privileges for `lookup_*` pattern: _read_\r\n\r\nOtherwise, we show a callout at the top of the page, this callout is\r\nconsistent with the one displayed on the Detection Rules page\r\n(`/app/security/rules`)\r\n\r\n\r\n- To retry rule translations (upload missing macros/lookups or retry\r\nerrors)\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, when attempted, we show a toast with the missing privilege. \r\n\r\n\r\n\r\n## Other changes\r\n\r\n- Technical preview label\r\n\r\n\r\n\r\n- No connector selected toast\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\r\n\r\n## Fixes\r\n\r\n- [Fixed] Not possible to select a connector when no connector is\r\nselected:\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a990be66dffbe89b271722630fd78b544b6ae903","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 RBAC","number":207087,"url":"https://github.com/elastic/kibana/pull/207087","mergeCommit":{"message":"[Security Solution] SIEM Migrations RBAC (#207087)\n\n## Summary\r\n\r\nImplements the access controls for SIEM rule migrations.\r\n\r\n## API changes\r\n\r\n- All API routes have been secured with \"SIEM Migration\" feature checks\r\n- Start migration API route now checks if the user has privileges to use\r\nthe connector ID received\r\n \r\n## UI changes\r\n\r\n### Onboarding SIEM migrations\r\n\r\n- AI Connector selection\r\n- Actions & Connectors: Read -> This privilege allows reading and\r\nselecting a connector\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n- Create a migration\r\n - Security All -> Main Security read & write access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n### Rule Translations page\r\n\r\n- Minimum privileges to make the page accessible (read access):\r\n - Security Read -> Main Security read access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n \r\nOtherwise, we hide the link in the navigation and display the generic\r\nempty state if accessed:\r\n\r\n\r\n- To successfully install rules the following privileges are also\r\nrequired (write access):\r\n - Security All -> Main Security read & write access\r\n- Index privileges for `.alerts*` pattern: _read, write,\r\nview_index_metadata, manage_\r\n - Index privileges for `lookup_*` pattern: _read_\r\n\r\nOtherwise, we show a callout at the top of the page, this callout is\r\nconsistent with the one displayed on the Detection Rules page\r\n(`/app/security/rules`)\r\n\r\n\r\n- To retry rule translations (upload missing macros/lookups or retry\r\nerrors)\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, when attempted, we show a toast with the missing privilege. \r\n\r\n\r\n\r\n## Other changes\r\n\r\n- Technical preview label\r\n\r\n\r\n\r\n- No connector selected toast\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\r\n\r\n## Fixes\r\n\r\n- [Fixed] Not possible to select a connector when no connector is\r\nselected:\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a990be66dffbe89b271722630fd78b544b6ae903"}},"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/210086","number":210086,"state":"MERGED","mergeCommit":{"sha":"8acee959bc8252dade3aa5f2a335dbe129d962c3","message":"[9.0] [Security Solution] SIEM Migrations RBAC (#207087) (#210086)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Security Solution] SIEM Migrations RBAC\n(#207087)](https://github.com/elastic/kibana/pull/207087)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Sergi\nMassaneda\",\"email\":\"sergi.massaneda@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-06T17:41:21Z\",\"message\":\"[Security\nSolution] SIEM Migrations RBAC (#207087)\\n\\n## Summary\\r\\n\\r\\nImplements\nthe access controls for SIEM rule migrations.\\r\\n\\r\\n## API\nchanges\\r\\n\\r\\n- All API routes have been secured with \\\"SIEM\nMigration\\\" feature checks\\r\\n- Start migration API route now checks if\nthe user has privileges to use\\r\\nthe connector ID received\\r\\n \\r\\n##\nUI changes\\r\\n\\r\\n### Onboarding SIEM migrations\\r\\n\\r\\n- AI Connector\nselection\\r\\n- Actions & Connectors: Read -> This privilege allows\nreading and\\r\\nselecting a connector\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n-\nCreate a migration\\r\\n - Security All -> Main Security read & write\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n- Actions & Connectors: Read -> This privilege allows\nconnector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n###\nRule Translations page\\r\\n\\r\\n- Minimum privileges to make the page\naccessible (read access):\\r\\n - Security Read -> Main Security read\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n \\r\\nOtherwise, we hide the link in the navigation and\ndisplay the generic\\r\\nempty state if accessed:\\r\\n\\r\\n\\r\\n-\nTo successfully install rules the following privileges are\nalso\\r\\nrequired (write access):\\r\\n - Security All -> Main Security\nread & write access\\r\\n- Index privileges for `.alerts*` pattern: _read,\nwrite,\\r\\nview_index_metadata, manage_\\r\\n - Index privileges for\n`lookup_*` pattern: _read_\\r\\n\\r\\nOtherwise, we show a callout at the\ntop of the page, this callout is\\r\\nconsistent with the one displayed on\nthe Detection Rules page\\r\\n(`/app/security/rules`)\\r\\n\\r\\n\\r\\n-\nTo retry rule translations (upload missing macros/lookups or\nretry\\r\\nerrors)\\r\\n- Actions & Connectors: Read -> This privilege\nallows connector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, when\nattempted, we show a toast with the missing privilege.\n\\r\\n\\r\\n\\r\\n\\r\\n##\nOther changes\\r\\n\\r\\n- Technical preview\nlabel\\r\\n\\r\\n\\r\\n\\r\\n-\nNo connector selected\ntoast\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\\r\\n\\r\\n##\nFixes\\r\\n\\r\\n- [Fixed] Not possible to select a connector when no\nconnector\nis\\r\\nselected:\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"a990be66dffbe89b271722630fd78b544b6ae903\",\"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\nHunting\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[Security\nSolution] SIEM Migrations\nRBAC\",\"number\":207087,\"url\":\"https://github.com/elastic/kibana/pull/207087\",\"mergeCommit\":{\"message\":\"[Security\nSolution] SIEM Migrations RBAC (#207087)\\n\\n## Summary\\r\\n\\r\\nImplements\nthe access controls for SIEM rule migrations.\\r\\n\\r\\n## API\nchanges\\r\\n\\r\\n- All API routes have been secured with \\\"SIEM\nMigration\\\" feature checks\\r\\n- Start migration API route now checks if\nthe user has privileges to use\\r\\nthe connector ID received\\r\\n \\r\\n##\nUI changes\\r\\n\\r\\n### Onboarding SIEM migrations\\r\\n\\r\\n- AI Connector\nselection\\r\\n- Actions & Connectors: Read -> This privilege allows\nreading and\\r\\nselecting a connector\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n-\nCreate a migration\\r\\n - Security All -> Main Security read & write\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n- Actions & Connectors: Read -> This privilege allows\nconnector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n###\nRule Translations page\\r\\n\\r\\n- Minimum privileges to make the page\naccessible (read access):\\r\\n - Security Read -> Main Security read\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n \\r\\nOtherwise, we hide the link in the navigation and\ndisplay the generic\\r\\nempty state if accessed:\\r\\n\\r\\n\\r\\n-\nTo successfully install rules the following privileges are\nalso\\r\\nrequired (write access):\\r\\n - Security All -> Main Security\nread & write access\\r\\n- Index privileges for `.alerts*` pattern: _read,\nwrite,\\r\\nview_index_metadata, manage_\\r\\n - Index privileges for\n`lookup_*` pattern: _read_\\r\\n\\r\\nOtherwise, we show a callout at the\ntop of the page, this callout is\\r\\nconsistent with the one displayed on\nthe Detection Rules page\\r\\n(`/app/security/rules`)\\r\\n\\r\\n\\r\\n-\nTo retry rule translations (upload missing macros/lookups or\nretry\\r\\nerrors)\\r\\n- Actions & Connectors: Read -> This privilege\nallows connector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, when\nattempted, we show a toast with the missing privilege.\n\\r\\n\\r\\n\\r\\n\\r\\n##\nOther changes\\r\\n\\r\\n- Technical preview\nlabel\\r\\n\\r\\n\\r\\n\\r\\n-\nNo connector selected\ntoast\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\\r\\n\\r\\n##\nFixes\\r\\n\\r\\n- [Fixed] Not possible to select a connector when no\nconnector\nis\\r\\nselected:\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"a990be66dffbe89b271722630fd78b544b6ae903\"}},\"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/207087\",\"number\":207087,\"mergeCommit\":{\"message\":\"[Security\nSolution] SIEM Migrations RBAC (#207087)\\n\\n## Summary\\r\\n\\r\\nImplements\nthe access controls for SIEM rule migrations.\\r\\n\\r\\n## API\nchanges\\r\\n\\r\\n- All API routes have been secured with \\\"SIEM\nMigration\\\" feature checks\\r\\n- Start migration API route now checks if\nthe user has privileges to use\\r\\nthe connector ID received\\r\\n \\r\\n##\nUI changes\\r\\n\\r\\n### Onboarding SIEM migrations\\r\\n\\r\\n- AI Connector\nselection\\r\\n- Actions & Connectors: Read -> This privilege allows\nreading and\\r\\nselecting a connector\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n-\nCreate a migration\\r\\n - Security All -> Main Security read & write\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n- Actions & Connectors: Read -> This privilege allows\nconnector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, we show a callout\nwith the missing privileges:\\r\\n\\r\\n\\r\\n###\nRule Translations page\\r\\n\\r\\n- Minimum privileges to make the page\naccessible (read access):\\r\\n - Security Read -> Main Security read\naccess\\r\\n - Siem Migrations All -> new feature under the Security\ncatalog\\r\\n \\r\\nOtherwise, we hide the link in the navigation and\ndisplay the generic\\r\\nempty state if accessed:\\r\\n\\r\\n\\r\\n-\nTo successfully install rules the following privileges are\nalso\\r\\nrequired (write access):\\r\\n - Security All -> Main Security\nread & write access\\r\\n- Index privileges for `.alerts*` pattern: _read,\nwrite,\\r\\nview_index_metadata, manage_\\r\\n - Index privileges for\n`lookup_*` pattern: _read_\\r\\n\\r\\nOtherwise, we show a callout at the\ntop of the page, this callout is\\r\\nconsistent with the one displayed on\nthe Detection Rules page\\r\\n(`/app/security/rules`)\\r\\n\\r\\n\\r\\n-\nTo retry rule translations (upload missing macros/lookups or\nretry\\r\\nerrors)\\r\\n- Actions & Connectors: Read -> This privilege\nallows connector\\r\\nexecution for LLM calls\\r\\n\\r\\nOtherwise, when\nattempted, we show a toast with the missing privilege.\n\\r\\n\\r\\n\\r\\n\\r\\n##\nOther changes\\r\\n\\r\\n- Technical preview\nlabel\\r\\n\\r\\n\\r\\n\\r\\n-\nNo connector selected\ntoast\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\\r\\n\\r\\n##\nFixes\\r\\n\\r\\n- [Fixed] Not possible to select a connector when no\nconnector\nis\\r\\nselected:\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"a990be66dffbe89b271722630fd78b544b6ae903\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\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/207087","number":207087,"mergeCommit":{"message":"[Security Solution] SIEM Migrations RBAC (#207087)\n\n## Summary\r\n\r\nImplements the access controls for SIEM rule migrations.\r\n\r\n## API changes\r\n\r\n- All API routes have been secured with \"SIEM Migration\" feature checks\r\n- Start migration API route now checks if the user has privileges to use\r\nthe connector ID received\r\n \r\n## UI changes\r\n\r\n### Onboarding SIEM migrations\r\n\r\n- AI Connector selection\r\n- Actions & Connectors: Read -> This privilege allows reading and\r\nselecting a connector\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n- Create a migration\r\n - Security All -> Main Security read & write access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, we show a callout with the missing privileges:\r\n\r\n\r\n### Rule Translations page\r\n\r\n- Minimum privileges to make the page accessible (read access):\r\n - Security Read -> Main Security read access\r\n - Siem Migrations All -> new feature under the Security catalog\r\n \r\nOtherwise, we hide the link in the navigation and display the generic\r\nempty state if accessed:\r\n\r\n\r\n- To successfully install rules the following privileges are also\r\nrequired (write access):\r\n - Security All -> Main Security read & write access\r\n- Index privileges for `.alerts*` pattern: _read, write,\r\nview_index_metadata, manage_\r\n - Index privileges for `lookup_*` pattern: _read_\r\n\r\nOtherwise, we show a callout at the top of the page, this callout is\r\nconsistent with the one displayed on the Detection Rules page\r\n(`/app/security/rules`)\r\n\r\n\r\n- To retry rule translations (upload missing macros/lookups or retry\r\nerrors)\r\n- Actions & Connectors: Read -> This privilege allows connector\r\nexecution for LLM calls\r\n\r\nOtherwise, when attempted, we show a toast with the missing privilege. \r\n\r\n\r\n\r\n## Other changes\r\n\r\n- Technical preview label\r\n\r\n\r\n\r\n- No connector selected toast\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e4900129-ae9c-413f-9a41-f7dca452e71d\r\n\r\n## Fixes\r\n\r\n- [Fixed] Not possible to select a connector when no connector is\r\nselected:\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a990be66dffbe89b271722630fd78b544b6ae903"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Arturo Lidueña
|
2d36c65bc3
|
[8.18] [Observability AI Assistant] rule connector - handle multiple prompt (#209221) (#210050)
# Backport This will backport the following commits from `main` to `8.18`: - [[Observability AI Assistant] rule connector - handle multiple prompt (#209221)](https://github.com/elastic/kibana/pull/209221) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T09:16:42Z","message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport missing","release_note:feature","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0"],"title":"[Observability AI Assistant] rule connector - handle multiple prompt ","number":209221,"url":"https://github.com/elastic/kibana/pull/209221","mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},"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/209221","number":209221,"mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}}]}] BACKPORT--> |
||
Yara Tercero
|
4ffa5a54c0
|
[8.18] [Detection Engine][Docs] Updating examples to meet old ascii docs (#207558) (#209942)
# Backport This will backport the following commits from `main` to `8.18`: - [[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)](https://github.com/elastic/kibana/pull/207558) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-05T07:02:48Z","message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74","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:Detection Engine","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[Detection Engine][Docs] Updating examples to meet old ascii docs","number":207558,"url":"https://github.com/elastic/kibana/pull/207558","mergeCommit":{"message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"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/207558","number":207558,"mergeCommit":{"message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
5f58a5b423
|
[8.18] [ML] Switching from _unified to _stream for the chat_completion task type (#210104) (#210110)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Switching from _unified to _stream for the chat_completion task type (#210104)](https://github.com/elastic/kibana/pull/210104) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jonathan Buttner","email":"56361221+jonathan-buttner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-06T21:40:47Z","message":"[ML] Switching from _unified to _stream for the chat_completion task type (#210104)\n\nThis PR switch the endpoint used for the `chat_completion` task type to\r\n`_stream`. Only the URL changes, the request and response format stay\r\nthe same. The `_stream` URL was introduced a couple verisons ago and is\r\nthe preferred route for interacting with `chat_completion`.\r\n\r\n### Testing\r\n\r\nSetup a pre-configured connector for security. Add this to your\r\n`config/kibana.dev.yml`\r\n\r\n```\r\nxpack.actions.preconfigured:\r\n my-inference-open-ai:\r\n name: Inference Preconfig Jon\r\n actionTypeId: .inference\r\n exposeConfig: true\r\n config:\r\n provider: 'openai'\r\n taskType: 'chat_completion'\r\n inferenceId: 'openai-chat_completion-123'\r\n providerConfig:\r\n rate_limit:\r\n requests_per_minute: 80000\r\n model_id: 'gpt-4o'\r\n url: https://api.openai.com/v1/chat/completions\r\n secrets:\r\n providerSecrets:\r\n api_key: '<api key>'\r\n```\r\n\r\nThen via the Connectors page, create an AI connector with the inference\r\nendpoint id set to `openai-chat_completion-123`\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29d56d58-cd96-432f-9d13-460446d204a1","sha":"3a14752dad189a9702be1f108b14680e7d1fe9bc","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:ML","Feature:GenAI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ML] Switching from _unified to _stream for the chat_completion task type","number":210104,"url":"https://github.com/elastic/kibana/pull/210104","mergeCommit":{"message":"[ML] Switching from _unified to _stream for the chat_completion task type (#210104)\n\nThis PR switch the endpoint used for the `chat_completion` task type to\r\n`_stream`. Only the URL changes, the request and response format stay\r\nthe same. The `_stream` URL was introduced a couple verisons ago and is\r\nthe preferred route for interacting with `chat_completion`.\r\n\r\n### Testing\r\n\r\nSetup a pre-configured connector for security. Add this to your\r\n`config/kibana.dev.yml`\r\n\r\n```\r\nxpack.actions.preconfigured:\r\n my-inference-open-ai:\r\n name: Inference Preconfig Jon\r\n actionTypeId: .inference\r\n exposeConfig: true\r\n config:\r\n provider: 'openai'\r\n taskType: 'chat_completion'\r\n inferenceId: 'openai-chat_completion-123'\r\n providerConfig:\r\n rate_limit:\r\n requests_per_minute: 80000\r\n model_id: 'gpt-4o'\r\n url: https://api.openai.com/v1/chat/completions\r\n secrets:\r\n providerSecrets:\r\n api_key: '<api key>'\r\n```\r\n\r\nThen via the Connectors page, create an AI connector with the inference\r\nendpoint id set to `openai-chat_completion-123`\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29d56d58-cd96-432f-9d13-460446d204a1","sha":"3a14752dad189a9702be1f108b14680e7d1fe9bc"}},"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/210104","number":210104,"mergeCommit":{"message":"[ML] Switching from _unified to _stream for the chat_completion task type (#210104)\n\nThis PR switch the endpoint used for the `chat_completion` task type to\r\n`_stream`. Only the URL changes, the request and response format stay\r\nthe same. The `_stream` URL was introduced a couple verisons ago and is\r\nthe preferred route for interacting with `chat_completion`.\r\n\r\n### Testing\r\n\r\nSetup a pre-configured connector for security. Add this to your\r\n`config/kibana.dev.yml`\r\n\r\n```\r\nxpack.actions.preconfigured:\r\n my-inference-open-ai:\r\n name: Inference Preconfig Jon\r\n actionTypeId: .inference\r\n exposeConfig: true\r\n config:\r\n provider: 'openai'\r\n taskType: 'chat_completion'\r\n inferenceId: 'openai-chat_completion-123'\r\n providerConfig:\r\n rate_limit:\r\n requests_per_minute: 80000\r\n model_id: 'gpt-4o'\r\n url: https://api.openai.com/v1/chat/completions\r\n secrets:\r\n providerSecrets:\r\n api_key: '<api key>'\r\n```\r\n\r\nThen via the Connectors page, create an AI connector with the inference\r\nendpoint id set to `openai-chat_completion-123`\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29d56d58-cd96-432f-9d13-460446d204a1","sha":"3a14752dad189a9702be1f108b14680e7d1fe9bc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jonathan Buttner <56361221+jonathan-buttner@users.noreply.github.com> |
||
Hannah Mudge
|
b97ae80369
|
[8.18] [9.0] [Dashboard] Ensure resize handle does not overlap sticky header (#209937) (#210031)
# Backport This will backport the following commits from `9.0` to `8.18`: - [[9.0] [Dashboard] Ensure resize handle does not overlap sticky header (#209937)](https://github.com/elastic/kibana/pull/209937) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-06T15:03:28Z","message":"[9.0] [Dashboard] Ensure resize handle does not overlap sticky header (#209937)\n\n## Summary\r\n\r\nSince https://github.com/elastic/kibana/pull/207275 is too large to\r\nbackport to `9.0`/`8.18` and will only be in `9.1`/`8.19`, I wanted to\r\nat least backport **just** the z-index fix for the resize handler as\r\ndescribed\r\n[here](https://github.com/elastic/kibana/pull/207275/files#r1931305375)\r\n. Unfortunately, the z-index used in that PR\r\n(`euiTheme.levels.maskBelowHeader`) only works thanks to other\r\nhover-action style changes, so I've had to set a hardcoded z-index\r\n(`2000`) in this PR instead. This acts as a \"quick fix\" for a pretty\r\nannoying bug while avoiding the risk of backporting the entire\r\npresentation panel refactor PR to `9.0`/`8.18`\r\n\r\n\r\n| Before | After |\r\n|--------|--------|\r\n| ` when chrome is remounted (#210075) (#210099)
# Backport This will backport the following commits from `main` to `8.18`: - [fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)](https://github.com/elastic/kibana/pull/210075) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T19:02:59Z","message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted ","number":210075,"url":"https://github.com/elastic/kibana/pull/210075","mergeCommit":{"message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8"}},"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/210075","number":210075,"mergeCommit":{"message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
|
Kibana Machine
|
443bfc7537
|
[8.18] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#210087)
# Backport This will backport the following commits from `main` to `8.18`: - [[scout] unique runId for reporting, disabled failed test reporter locally (#209507)](https://github.com/elastic/kibana/pull/209507) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T15:35:26Z","message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","test:scout","v9.1.0"],"title":"[scout] unique runId for reporting, disabled failed test reporter locally","number":209507,"url":"https://github.com/elastic/kibana/pull/209507","mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}},"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/209808","number":209808,"state":"MERGED","mergeCommit":{"sha":"2c04505bd6ad9db59e0ea3aa617d649b41134294","message":"[9.0] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#209808)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[scout] unique runId for reporting, disabled failed test reporter\nlocally (#209507)](https://github.com/elastic/kibana/pull/209507)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T15:35:26Z\",\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"test:scout\",\"v9.1.0\"],\"title\":\"[scout]\nunique runId for reporting, disabled failed test reporter\nlocally\",\"number\":209507,\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"number\":209507,\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be enough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209507","number":209507,"mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Kibana Machine
|
d07a9d6d2f
|
[8.18] [Lens] Replace scss for heatmap expression (#209246) (#210070)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens] Replace scss for heatmap expression (#209246)](https://github.com/elastic/kibana/pull/209246) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maria Iriarte","email":"106958839+mariairiartef@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-06T16:38:08Z","message":"[Lens] Replace scss for heatmap expression (#209246)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. \r\n\r\n### Checklist\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"228f83fde3b872121b8149196b65d9aa4d842156","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Lens] Replace scss for heatmap expression","number":209246,"url":"https://github.com/elastic/kibana/pull/209246","mergeCommit":{"message":"[Lens] Replace scss for heatmap expression (#209246)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. \r\n\r\n### Checklist\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"228f83fde3b872121b8149196b65d9aa4d842156"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209246","number":209246,"mergeCommit":{"message":"[Lens] Replace scss for heatmap expression (#209246)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/208908\r\n\r\nReplaces scss to css-in-js. \r\n\r\n### Checklist\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"228f83fde3b872121b8149196b65d9aa4d842156"}}]}] BACKPORT--> Co-authored-by: Maria Iriarte <106958839+mariairiartef@users.noreply.github.com> |
||
|
Kibana Machine
|
cdeb5043a4
|
[8.18] Remove beta badge for manual rule run (#209535) (#210072)
# Backport This will backport the following commits from `main` to `8.18`: - [Remove beta badge for manual rule run (#209535)](https://github.com/elastic/kibana/pull/209535) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T16:31:03Z","message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Remove beta badge for manual rule run","number":209535,"url":"https://github.com/elastic/kibana/pull/209535","mergeCommit":{"message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170"}},"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/209535","number":209535,"mergeCommit":{"message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
Kibana Machine
|
afbcfc3c46
|
[8.18] [Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature (#209623) (#210036)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature (#209623)](https://github.com/elastic/kibana/pull/209623) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T15:11:33Z","message":"[Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature (#209623)","sha":"f299c9fdab11b37c882c6afbcaaa87916f71dbb6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:Security Generative AI","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature ","number":209623,"url":"https://github.com/elastic/kibana/pull/209623","mergeCommit":{"message":"[Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature (#209623)","sha":"f299c9fdab11b37c882c6afbcaaa87916f71dbb6"}},"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/209623","number":209623,"mergeCommit":{"message":"[Security GenAI] Add Telemetry related to the Attack Discovery Alert Filtering feature (#209623)","sha":"f299c9fdab11b37c882c6afbcaaa87916f71dbb6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
d454b980c7
|
[8.18] [ES|QL] WHERE replacement ranges correctly generated for every case (#209684) (#210051)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] WHERE replacement ranges correctly generated for every case (#209684)](https://github.com/elastic/kibana/pull/209684) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Drew Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T15:36:07Z","message":"[ES|QL] WHERE replacement ranges correctly generated for every case (#209684)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/204441\r\n\r\nIt ain't beautiful but it works. I am going to come in with another pr\r\nto deal with prefix detection holistically\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4ee3b50584eec0d596a3aa3694a3d7047ba66002","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] WHERE replacement ranges correctly generated for every case","number":209684,"url":"https://github.com/elastic/kibana/pull/209684","mergeCommit":{"message":"[ES|QL] WHERE replacement ranges correctly generated for every case (#209684)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/204441\r\n\r\nIt ain't beautiful but it works. I am going to come in with another pr\r\nto deal with prefix detection holistically\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4ee3b50584eec0d596a3aa3694a3d7047ba66002"}},"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/209684","number":209684,"mergeCommit":{"message":"[ES|QL] WHERE replacement ranges correctly generated for every case (#209684)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/204441\r\n\r\nIt ain't beautiful but it works. I am going to come in with another pr\r\nto deal with prefix detection holistically\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4ee3b50584eec0d596a3aa3694a3d7047ba66002"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Drew Tate <drew.tate@elastic.co> |
||
|
Kibana Machine
|
584a878ff0
|
[8.18] Update lexer / parser and fix the categorize function (#209964) (#210032)
# Backport This will backport the following commits from `main` to `8.18`: - [Update lexer / parser and fix the categorize function (#209964)](https://github.com/elastic/kibana/pull/209964) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T14:57:02Z","message":"Update lexer / parser and fix the categorize function (#209964)\n\n## Summary\n\n- Fixes the categorize wrong autocomplete suggestions\n- Updates the lexer / parser as I want this to get merged in 8.18 / 9.0","sha":"ee866a745a23efd7442262232f149080fa4de609","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Update lexer / parser and fix the categorize function","number":209964,"url":"https://github.com/elastic/kibana/pull/209964","mergeCommit":{"message":"Update lexer / parser and fix the categorize function (#209964)\n\n## Summary\n\n- Fixes the categorize wrong autocomplete suggestions\n- Updates the lexer / parser as I want this to get merged in 8.18 / 9.0","sha":"ee866a745a23efd7442262232f149080fa4de609"}},"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/209964","number":209964,"mergeCommit":{"message":"Update lexer / parser and fix the categorize function (#209964)\n\n## Summary\n\n- Fixes the categorize wrong autocomplete suggestions\n- Updates the lexer / parser as I want this to get merged in 8.18 / 9.0","sha":"ee866a745a23efd7442262232f149080fa4de609"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
a9233d8b04
|
[8.18] [ML] Adding tests for file upload merge tools (#209704) (#210026)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Adding tests for file upload merge tools (#209704)](https://github.com/elastic/kibana/pull/209704) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T14:53:14Z","message":"[ML] Adding tests for file upload merge tools (#209704)\n\nAdding tests for the merge tools utility functions.","sha":"42def2d71bcbf5391280cf87ad72bba7b0a9c271","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","test-coverage","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ML] Adding tests for file upload merge tools","number":209704,"url":"https://github.com/elastic/kibana/pull/209704","mergeCommit":{"message":"[ML] Adding tests for file upload merge tools (#209704)\n\nAdding tests for the merge tools utility functions.","sha":"42def2d71bcbf5391280cf87ad72bba7b0a9c271"}},"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/209704","number":209704,"mergeCommit":{"message":"[ML] Adding tests for file upload merge tools (#209704)\n\nAdding tests for the merge tools utility functions.","sha":"42def2d71bcbf5391280cf87ad72bba7b0a9c271"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
Kibana Machine
|
bf9401474b
|
[8.18] [GenAI Connectors] Add support for telemetry metadata (#208180) (#210016)
# Backport This will backport the following commits from `main` to `8.18`: - [[GenAI Connectors] Add support for telemetry metadata (#208180)](https://github.com/elastic/kibana/pull/208180) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marius Iversen","email":"marius.iversen@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T14:24:35Z","message":"[GenAI Connectors] Add support for telemetry metadata (#208180)\n\n## Summary\n\nThis extends initial connector telemetry from PR ref\nhttps://github.com/elastic/kibana/pull/186936.\n\nThe PR adds the following optional fields when instantiating a new\nactionClient as part of its `subActionParams`:\n\n```ts\n{\n telemetryMetadata : {\n pluginId: \"your plugin name or unique identifier\",\n aggregateBy: \"ID to aggregate on\" \n }\n}\n```\n\nThe support is added to all AI connector models for both\nstream/non-stream/raw.\n\nThe PR also adds token count usage for bedrock `InvokeAIRaw`, as that\nwas currently not added correctly.\n\nPierre also helped with adding a new metadata optional field for the `NL\nto ESQL functions`, so that users can pass in similar metadata for LLM\nconversations using the InfereceClient.\n\nPluginId is a field used to filter telemetry in the way the team wants\nto implement it. It could be a team name, a plugin name etc, all\ndepending on how the team wants to group and filter on the telemetry\nevent.\n\nAggregateBy is intended to be used to group multiple LLM calls for\naggregations and stats, for example a conversationId that has multiple\nLLM calls.\n\nBoth fields are optional, so when you do not want to aggregate the\noption can simply be ignored.\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\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: pgayvallet <pierre.gayvallet@elastic.co>","sha":"3394b691b1582d504195182013f833ba727c5e7e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[GenAI Connectors] Add support for telemetry metadata","number":208180,"url":"https://github.com/elastic/kibana/pull/208180","mergeCommit":{"message":"[GenAI Connectors] Add support for telemetry metadata (#208180)\n\n## Summary\n\nThis extends initial connector telemetry from PR ref\nhttps://github.com/elastic/kibana/pull/186936.\n\nThe PR adds the following optional fields when instantiating a new\nactionClient as part of its `subActionParams`:\n\n```ts\n{\n telemetryMetadata : {\n pluginId: \"your plugin name or unique identifier\",\n aggregateBy: \"ID to aggregate on\" \n }\n}\n```\n\nThe support is added to all AI connector models for both\nstream/non-stream/raw.\n\nThe PR also adds token count usage for bedrock `InvokeAIRaw`, as that\nwas currently not added correctly.\n\nPierre also helped with adding a new metadata optional field for the `NL\nto ESQL functions`, so that users can pass in similar metadata for LLM\nconversations using the InfereceClient.\n\nPluginId is a field used to filter telemetry in the way the team wants\nto implement it. It could be a team name, a plugin name etc, all\ndepending on how the team wants to group and filter on the telemetry\nevent.\n\nAggregateBy is intended to be used to group multiple LLM calls for\naggregations and stats, for example a conversationId that has multiple\nLLM calls.\n\nBoth fields are optional, so when you do not want to aggregate the\noption can simply be ignored.\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\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: pgayvallet <pierre.gayvallet@elastic.co>","sha":"3394b691b1582d504195182013f833ba727c5e7e"}},"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/208180","number":208180,"mergeCommit":{"message":"[GenAI Connectors] Add support for telemetry metadata (#208180)\n\n## Summary\n\nThis extends initial connector telemetry from PR ref\nhttps://github.com/elastic/kibana/pull/186936.\n\nThe PR adds the following optional fields when instantiating a new\nactionClient as part of its `subActionParams`:\n\n```ts\n{\n telemetryMetadata : {\n pluginId: \"your plugin name or unique identifier\",\n aggregateBy: \"ID to aggregate on\" \n }\n}\n```\n\nThe support is added to all AI connector models for both\nstream/non-stream/raw.\n\nThe PR also adds token count usage for bedrock `InvokeAIRaw`, as that\nwas currently not added correctly.\n\nPierre also helped with adding a new metadata optional field for the `NL\nto ESQL functions`, so that users can pass in similar metadata for LLM\nconversations using the InfereceClient.\n\nPluginId is a field used to filter telemetry in the way the team wants\nto implement it. It could be a team name, a plugin name etc, all\ndepending on how the team wants to group and filter on the telemetry\nevent.\n\nAggregateBy is intended to be used to group multiple LLM calls for\naggregations and stats, for example a conversationId that has multiple\nLLM calls.\n\nBoth fields are optional, so when you do not want to aggregate the\noption can simply be ignored.\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\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: pgayvallet <pierre.gayvallet@elastic.co>","sha":"3394b691b1582d504195182013f833ba727c5e7e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marius Iversen <marius.iversen@elastic.co> |
||
elastic-renovate-prod[bot]
|
f8f9d2a79b
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 8df3ca6 (8.18) (#209902)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `d04ee51` -> `8df3ca6` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
ccc9e5028e
|
[8.18] [EDR Workflows] Fix `allow_cloud_features` advanced option description text (#209766) (#209965)
# Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Fix `allow_cloud_features` advanced option description text (#209766)](https://github.com/elastic/kibana/pull/209766) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T09:10:00Z","message":"[EDR Workflows] Fix `allow_cloud_features` advanced option description text (#209766)\n\n## Summary\r\n\r\nbefore\r\n> It's meant only for telemetry extra-avoidant users users.\r\n\r\nafter\r\n> It's meant only for telemetry extra-avoidant users.\r\n\r\n<img width=\"565\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c55e551-7a9a-485a-b8e3-bccc57bc0910\"\r\n/>","sha":"ca390dadc029758f902917b530a26857b0f9a891","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:Defend Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[EDR Workflows] Fix `allow_cloud_features` advanced option description text","number":209766,"url":"https://github.com/elastic/kibana/pull/209766","mergeCommit":{"message":"[EDR Workflows] Fix `allow_cloud_features` advanced option description text (#209766)\n\n## Summary\r\n\r\nbefore\r\n> It's meant only for telemetry extra-avoidant users users.\r\n\r\nafter\r\n> It's meant only for telemetry extra-avoidant users.\r\n\r\n<img width=\"565\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c55e551-7a9a-485a-b8e3-bccc57bc0910\"\r\n/>","sha":"ca390dadc029758f902917b530a26857b0f9a891"}},"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/209766","number":209766,"mergeCommit":{"message":"[EDR Workflows] Fix `allow_cloud_features` advanced option description text (#209766)\n\n## Summary\r\n\r\nbefore\r\n> It's meant only for telemetry extra-avoidant users users.\r\n\r\nafter\r\n> It's meant only for telemetry extra-avoidant users.\r\n\r\n<img width=\"565\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c55e551-7a9a-485a-b8e3-bccc57bc0910\"\r\n/>","sha":"ca390dadc029758f902917b530a26857b0f9a891"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |