mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 01:13:23 -04:00
45561 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Lisa Cawley
|
f90e078e09
|
[8.18] Update API URLs in doc link service (#215084) (#218493)
# Backport This will backport the following commits from `main` to `8.18`: - [Update API URLs in doc link service (#215084)](https://github.com/elastic/kibana/pull/215084) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T14:18:47Z","message":"Update API URLs in doc link service (#215084)\n\n\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b969cc9e3dac819c0498ab2e68e27a74c4b91a88","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"Update API URLs in doc link service","number":215084,"url":"https://github.com/elastic/kibana/pull/215084","mergeCommit":{"message":"Update API URLs in doc link service (#215084)\n\n\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b969cc9e3dac819c0498ab2e68e27a74c4b91a88"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215084","number":215084,"mergeCommit":{"message":"Update API URLs in doc link service (#215084)\n\n\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"b969cc9e3dac819c0498ab2e68e27a74c4b91a88"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218457","number":218457,"state":"OPEN"}]}] BACKPORT--> |
||
Kibana Machine
|
c602c8f6e2
|
[8.18] [ML] Improving anomaly charts object safety (#217552) (#218835)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Improving anomaly charts object safety (#217552)](https://github.com/elastic/kibana/pull/217552) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-04-22T14:52:12Z","message":"[ML] Improving anomaly charts object safety (#217552)\n\nAdds checks for the values `__proto__` and `prototype` when reading\ndetector fields to reduce the risk of prototype pollution.","sha":"60af3ff3d525e830812b0986825d23d7041bef63","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[ML] Improving anomaly charts object safety","number":217552,"url":"https://github.com/elastic/kibana/pull/217552","mergeCommit":{"message":"[ML] Improving anomaly charts object safety (#217552)\n\nAdds checks for the values `__proto__` and `prototype` when reading\ndetector fields to reduce the risk of prototype pollution.","sha":"60af3ff3d525e830812b0986825d23d7041bef63"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217552","number":217552,"mergeCommit":{"message":"[ML] Improving anomaly charts object safety (#217552)\n\nAdds checks for the values `__proto__` and `prototype` when reading\ndetector fields to reduce the risk of prototype pollution.","sha":"60af3ff3d525e830812b0986825d23d7041bef63"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
Kibana Machine
|
5642748856
|
[8.18] [ObsUX][Infra] Filter out null values from sourceDataStreams (#218772) (#218798)
# Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX][Infra] Filter out null values from `sourceDataStreams` (#218772)](https://github.com/elastic/kibana/pull/218772) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-22T10:37:09Z","message":"[ObsUX][Infra] Filter out null values from `sourceDataStreams` (#218772)\n\n## Summary\n\nPart of #213045\n\nThis PR fixes an issue when the `observability:entityCentricExperience`\nflag is enabled.\nBy some reason, we may get null values in `sourceDataStreams` and when\nwe try to validate it with the zod schema, it breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[ObsUX][Infra] Filter out null values from `sourceDataStreams`","number":218772,"url":"https://github.com/elastic/kibana/pull/218772","mergeCommit":{"message":"[ObsUX][Infra] Filter out null values from `sourceDataStreams` (#218772)\n\n## Summary\n\nPart of #213045\n\nThis PR fixes an issue when the `observability:entityCentricExperience`\nflag is enabled.\nBy some reason, we may get null values in `sourceDataStreams` and when\nwe try to validate it with the zod schema, it breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218772","number":218772,"mergeCommit":{"message":"[ObsUX][Infra] Filter out null values from `sourceDataStreams` (#218772)\n\n## Summary\n\nPart of #213045\n\nThis PR fixes an issue when the `observability:entityCentricExperience`\nflag is enabled.\nBy some reason, we may get null values in `sourceDataStreams` and when\nwe try to validate it with the zod schema, it breaks.","sha":"2dea36a0a63d4cd594e556eb4cfd346cb11f30a3"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
e020de9842
|
[8.18] fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement (#218214) (#218794)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement (#218214)](https://github.com/elastic/kibana/pull/218214) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-22T10:26:56Z","message":"fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement (#218214)\n\nCloses: #217971\nRework of: https://github.com/elastic/kibana/pull/205604\n\n**Description**\nThis update improves accessibility by ensuring that dialog modals,\nflyouts, and field titles are properly announced for users—particularly\nthose using assistive technologies. It ensures users are clearly\ninformed about which dialog or flyout has opened, which field is active,\nand what input is expected.\n\n**Changes Made**\n- Reverted a regression introduced in\n[#205604](https://github.com/elastic/kibana/pull/205604), which involved\nincorrect usage of `EuiSwitch`. The component now uses the default\n`EuiSwitch` behavior as intended.\n\n- Updated the Cases page UI to better align with the EUI style guide.\n\n**Screenshots**\n\n- Cases Page\n\n<img width=\"947\" alt=\"Cases Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/0b8d7fd4-543f-4751-a17b-3b774c0e1c8c\"\n/>\n\n- Ingest Pipelines Page\n\n<img width=\"947\" alt=\"Ingest Pipelines Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/78185612-9a01-4227-a1a1-b928e848ca78\"\n/>","sha":"3ad8bad478008c5587c6b41d84430695d148d561","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement","number":218214,"url":"https://github.com/elastic/kibana/pull/218214","mergeCommit":{"message":"fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement (#218214)\n\nCloses: #217971\nRework of: https://github.com/elastic/kibana/pull/205604\n\n**Description**\nThis update improves accessibility by ensuring that dialog modals,\nflyouts, and field titles are properly announced for users—particularly\nthose using assistive technologies. It ensures users are clearly\ninformed about which dialog or flyout has opened, which field is active,\nand what input is expected.\n\n**Changes Made**\n- Reverted a regression introduced in\n[#205604](https://github.com/elastic/kibana/pull/205604), which involved\nincorrect usage of `EuiSwitch`. The component now uses the default\n`EuiSwitch` behavior as intended.\n\n- Updated the Cases page UI to better align with the EUI style guide.\n\n**Screenshots**\n\n- Cases Page\n\n<img width=\"947\" alt=\"Cases Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/0b8d7fd4-543f-4751-a17b-3b774c0e1c8c\"\n/>\n\n- Ingest Pipelines Page\n\n<img width=\"947\" alt=\"Ingest Pipelines Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/78185612-9a01-4227-a1a1-b928e848ca78\"\n/>","sha":"3ad8bad478008c5587c6b41d84430695d148d561"}},"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/218214","number":218214,"mergeCommit":{"message":"fix: [Platform:StackManagement:IngestPipelines:Create pipeline page]Switch button missing title from announcement (#218214)\n\nCloses: #217971\nRework of: https://github.com/elastic/kibana/pull/205604\n\n**Description**\nThis update improves accessibility by ensuring that dialog modals,\nflyouts, and field titles are properly announced for users—particularly\nthose using assistive technologies. It ensures users are clearly\ninformed about which dialog or flyout has opened, which field is active,\nand what input is expected.\n\n**Changes Made**\n- Reverted a regression introduced in\n[#205604](https://github.com/elastic/kibana/pull/205604), which involved\nincorrect usage of `EuiSwitch`. The component now uses the default\n`EuiSwitch` behavior as intended.\n\n- Updated the Cases page UI to better align with the EUI style guide.\n\n**Screenshots**\n\n- Cases Page\n\n<img width=\"947\" alt=\"Cases Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/0b8d7fd4-543f-4751-a17b-3b774c0e1c8c\"\n/>\n\n- Ingest Pipelines Page\n\n<img width=\"947\" alt=\"Ingest Pipelines Page Screenshot\"\nsrc=\"https://github.com/user-attachments/assets/78185612-9a01-4227-a1a1-b928e848ca78\"\n/>","sha":"3ad8bad478008c5587c6b41d84430695d148d561"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
317dbd86c8
|
[8.18] [Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426) (#218775)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426)](https://github.com/elastic/kibana/pull/216426) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-22T08:21:48Z","message":"[Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426)\n\nThis PR closes #197786 .\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics] When changing condition type of a monitor status rule other conditions are not changed","number":216426,"url":"https://github.com/elastic/kibana/pull/216426","mergeCommit":{"message":"[Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426)\n\nThis PR closes #197786 .\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216426","number":216426,"mergeCommit":{"message":"[Synthetics] When changing condition type of a monitor status rule other conditions are not changed (#216426)\n\nThis PR closes #197786 .\n\n\n\nhttps://github.com/user-attachments/assets/85c92b09-f477-4e42-9fb7-a8143876e079","sha":"b936b4719ed06ac89203a46cd964e820be391fb3"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
1e15aed03c
|
[8.18] [Synthetics] Fixed monitor history histogram and group by location issue (#218550) (#218761)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Fixed monitor history histogram and group by location issue (#218550)](https://github.com/elastic/kibana/pull/218550) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-22T07:28:35Z","message":"[Synthetics] Fixed monitor history histogram and group by location issue (#218550)\n\nThis PR closes #217105 and closes #217118 \n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics] Fixed monitor history histogram and group by location issue","number":218550,"url":"https://github.com/elastic/kibana/pull/218550","mergeCommit":{"message":"[Synthetics] Fixed monitor history histogram and group by location issue (#218550)\n\nThis PR closes #217105 and closes #217118 \n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218550","number":218550,"mergeCommit":{"message":"[Synthetics] Fixed monitor history histogram and group by location issue (#218550)\n\nThis PR closes #217105 and closes #217118 \n\n\n\nhttps://github.com/user-attachments/assets/4426c5bc-dfda-483c-a974-3a3d6832d6c7\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"af381920ee321835dfdfa01fd2d57f4f77ae3d4a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
f83f7de27e
|
[8.18] [Security Solution][Telemetry] Add index metadata EBT event (#218546) (#218600)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Telemetry] Add index metadata EBT event (#218546)](https://github.com/elastic/kibana/pull/218546) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sebastián Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T18:00:26Z","message":"[Security Solution][Telemetry] Add index metadata EBT event (#218546)\n\n## Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n- Add a new EBT event collecting index template info\n ```typescript\n export interface IndexTemplateInfo {\n template_name: string;\n index_mode: Nullable<string>;\n datastream: boolean;\n package_name: Nullable<string>;\n managed_by: Nullable<string>;\n beat: Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of: string[];\n source_enabled: Nullable<boolean>;\n source_includes: string[];\n source_excludes: string[];\n }\n ```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","ci:build-cloud-image","v9.1.0"],"title":"[Security Solution][Telemetry] Add index metadata EBT event","number":218546,"url":"https://github.com/elastic/kibana/pull/218546","mergeCommit":{"message":"[Security Solution][Telemetry] Add index metadata EBT event (#218546)\n\n## Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n- Add a new EBT event collecting index template info\n ```typescript\n export interface IndexTemplateInfo {\n template_name: string;\n index_mode: Nullable<string>;\n datastream: boolean;\n package_name: Nullable<string>;\n managed_by: Nullable<string>;\n beat: Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of: string[];\n source_enabled: Nullable<boolean>;\n source_includes: string[];\n source_excludes: string[];\n }\n ```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218546","number":218546,"mergeCommit":{"message":"[Security Solution][Telemetry] Add index metadata EBT event (#218546)\n\n## Summary\n\n\n\n- Fix https://github.com/elastic/kibana/issues/216044\n- Add a new EBT event collecting index template info\n ```typescript\n export interface IndexTemplateInfo {\n template_name: string;\n index_mode: Nullable<string>;\n datastream: boolean;\n package_name: Nullable<string>;\n managed_by: Nullable<string>;\n beat: Nullable<string>;\n is_managed: Nullable<boolean>;\n composed_of: string[];\n source_enabled: Nullable<boolean>;\n source_includes: string[];\n source_excludes: string[];\n }\n ```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"c9b3a3e27b27f977f0ce494fc1b52d6166b21511"}}]}] BACKPORT--> Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Tomasz Ciecierski
|
efd16d98fe
|
[8.18] [EDR Workflows] Fix Osquery tests (#215507) (#218643)
# Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Fix Osquery tests (#215507)](https://github.com/elastic/kibana/pull/215507) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T07:37:58Z","message":"[EDR Workflows] Fix Osquery tests (#215507)\n\nCloses #197335\nCloses #192128\nCloses #181889\nCloses #178404 \nCloses #169785","sha":"9595c1ebd519091ad3dba82f67613e6133c9a850","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Defend Workflows","backport:version","v9.1.0","v8.18.1"],"title":"[EDR Workflows] Fix Osquery tests","number":215507,"url":"https://github.com/elastic/kibana/pull/215507","mergeCommit":{"message":"[EDR Workflows] Fix Osquery tests (#215507)\n\nCloses #197335\nCloses #192128\nCloses #181889\nCloses #178404 \nCloses #169785","sha":"9595c1ebd519091ad3dba82f67613e6133c9a850"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215507","number":215507,"mergeCommit":{"message":"[EDR Workflows] Fix Osquery tests (#215507)\n\nCloses #197335\nCloses #192128\nCloses #181889\nCloses #178404 \nCloses #169785","sha":"9595c1ebd519091ad3dba82f67613e6133c9a850"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Nicolas Chaulet
|
7734d99700
|
[8.18] [Fleet] Fix fleet server policy creation with non es default output (#214590) (#218656)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Fix fleet server policy creation with non es default output (#214590)](https://github.com/elastic/kibana/pull/214590) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T19:14:25Z","message":"[Fleet] Fix fleet server policy creation with non es default output (#214590)","sha":"6ed6d02f37c67935cfb25aa9bb075096d4b6351a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Fleet","backport:prev-minor","backport:version","v9.1.0","v8.18.1"],"title":"[Fleet] Fix fleet server policy creation with non es default output","number":214590,"url":"https://github.com/elastic/kibana/pull/214590","mergeCommit":{"message":"[Fleet] Fix fleet server policy creation with non es default output (#214590)","sha":"6ed6d02f37c67935cfb25aa9bb075096d4b6351a"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214590","number":214590,"mergeCommit":{"message":"[Fleet] Fix fleet server policy creation with non es default output (#214590)","sha":"6ed6d02f37c67935cfb25aa9bb075096d4b6351a"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
025cff5840
|
[8.18] Advanced policy opt-out for scan-on-event (#218354) (#218612)
# Backport This will backport the following commits from `main` to `8.18`: - [Advanced policy opt-out for scan-on-event (#218354)](https://github.com/elastic/kibana/pull/218354) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gabriel Landau","email":"42078554+gabriellandau@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T19:00:15Z","message":"Advanced policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users to opt out of scan-on-event to help troubleshoot and resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend} users can now opt out of event-driven Memory Protection\nscanning via advanced policy.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Defend Workflows","backport:version","v9.1.0","v8.18.1","v9.0.1","v8.17.6"],"title":"Advanced policy opt-out for scan-on-event","number":218354,"url":"https://github.com/elastic/kibana/pull/218354","mergeCommit":{"message":"Advanced policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users to opt out of scan-on-event to help troubleshoot and resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend} users can now opt out of event-driven Memory Protection\nscanning via advanced policy.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218354","number":218354,"mergeCommit":{"message":"Advanced policy opt-out for scan-on-event (#218354)\n\n## Summary\n\nAllow users to opt out of scan-on-event to help troubleshoot and resolve\nperformance issues.\n\n## Release note\n\n{elastic-defend} users can now opt out of event-driven Memory Protection\nscanning via advanced policy.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>","sha":"906c8978e7b0a2e9e503bc10a758d3b6a03f237d"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gabriel Landau <42078554+gabriellandau@users.noreply.github.com> |
||
|
Kibana Machine
|
946a98671f
|
[8.18] Improve accessibility in create connector flyout (#218426) (#218681)
# Backport This will backport the following commits from `main` to `8.18`: - [Improve accessibility in create connector flyout (#218426)](https://github.com/elastic/kibana/pull/218426) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-04-18T20:32:17Z","message":"Improve accessibility in create connector flyout (#218426)\n\npart of #212776 \n\n## Summary\nImproves screen reader accessibility for the GenAI connector panels in\nthe Observability AI Assistant by providing more descriptive\nannouncements when these panels are opened. Previously, Kibana would\nannounce a generic modal dialog message (from EUI) without context,\nwhich could confuse screen reader users.\n\n### Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on the “Set up\nGenAI connector” button, Kibana announces a generic message like “modal\ndialog” without explaining what the modal is about.\n\n### Fix\n•\tInclude aria-label to the `CreateConnectorFlyout` component\n\n### How to Test\n1.\tNavigate to Observability → AI Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick “Set up GenAI connector”\n4.\tVerify that the screen reader announces \"create connector flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:feature","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","v9.1.0"],"title":"Improve accessibility in create connector flyout ","number":218426,"url":"https://github.com/elastic/kibana/pull/218426","mergeCommit":{"message":"Improve accessibility in create connector flyout (#218426)\n\npart of #212776 \n\n## Summary\nImproves screen reader accessibility for the GenAI connector panels in\nthe Observability AI Assistant by providing more descriptive\nannouncements when these panels are opened. Previously, Kibana would\nannounce a generic modal dialog message (from EUI) without context,\nwhich could confuse screen reader users.\n\n### Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on the “Set up\nGenAI connector” button, Kibana announces a generic message like “modal\ndialog” without explaining what the modal is about.\n\n### Fix\n•\tInclude aria-label to the `CreateConnectorFlyout` component\n\n### How to Test\n1.\tNavigate to Observability → AI Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick “Set up GenAI connector”\n4.\tVerify that the screen reader announces \"create connector flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218426","number":218426,"mergeCommit":{"message":"Improve accessibility in create connector flyout (#218426)\n\npart of #212776 \n\n## Summary\nImproves screen reader accessibility for the GenAI connector panels in\nthe Observability AI Assistant by providing more descriptive\nannouncements when these panels are opened. Previously, Kibana would\nannounce a generic modal dialog message (from EUI) without context,\nwhich could confuse screen reader users.\n\n### Problem\n\nWhen a user with a screen reader (e.g., VoiceOver) clicks on the “Set up\nGenAI connector” button, Kibana announces a generic message like “modal\ndialog” without explaining what the modal is about.\n\n### Fix\n•\tInclude aria-label to the `CreateConnectorFlyout` component\n\n### How to Test\n1.\tNavigate to Observability → AI Assistant\n2.\tUse VoiceOver (macOS) or another screen reader\n3.\tClick “Set up GenAI connector”\n4.\tVerify that the screen reader announces \"create connector flyout\".","sha":"962cfb4c67a3e0dce1f45a83364b871508ca7061"}}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
|
Kibana Machine
|
1af5b2556a
|
[8.18] [Security Solution] Fixes related integrations render performance on rule editing pages (#217254) (#218669)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fixes related integrations render performance on rule editing pages (#217254)](https://github.com/elastic/kibana/pull/217254) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-18T18:47:20Z","message":"[Security Solution] Fixes related integrations render performance on rule editing pages (#217254)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the re-render performance issues caused by the related\nintegrations component on the rule edit and creation pages. This copies\na strategy used in https://github.com/elastic/kibana/pull/180682 to fix\na similar issue with required fields. Related integrations component now\ndoesn't re-render when there are updates to components that don't affect\nit.\n\n#### React Profile while typing in query field component\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","Team:Detection Rule Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Fixes related integrations render performance on rule editing pages","number":217254,"url":"https://github.com/elastic/kibana/pull/217254","mergeCommit":{"message":"[Security Solution] Fixes related integrations render performance on rule editing pages (#217254)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the re-render performance issues caused by the related\nintegrations component on the rule edit and creation pages. This copies\na strategy used in https://github.com/elastic/kibana/pull/180682 to fix\na similar issue with required fields. Related integrations component now\ndoesn't re-render when there are updates to components that don't affect\nit.\n\n#### React Profile while typing in query field component\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217254","number":217254,"mergeCommit":{"message":"[Security Solution] Fixes related integrations render performance on rule editing pages (#217254)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/183607\n\nAdds logic to fix the re-render performance issues caused by the related\nintegrations component on the rule edit and creation pages. This copies\na strategy used in https://github.com/elastic/kibana/pull/180682 to fix\na similar issue with required fields. Related integrations component now\ndoesn't re-render when there are updates to components that don't affect\nit.\n\n#### React Profile while typing in query field component\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1b6376e9c9e09edb5b0e790bdccc7d14bd5801ca"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> |
||
|
Kibana Machine
|
1685caeffb
|
[8.18] fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576) (#218608)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576)](https://github.com/elastic/kibana/pull/218576) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-17T18:52:56Z","message":"fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576)\n\nCloses: #218351\n\n**Description**\nWhen user clicks on assign new roles to a space button, the resulting\nflyout gets announced incorrectly as \"you are in a modal dialog...\"\nwhich doesn't give any context to non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby' attribute\n\n**Screen:**\n<img width=\"1323\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly","number":218576,"url":"https://github.com/elastic/kibana/pull/218576","mergeCommit":{"message":"fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576)\n\nCloses: #218351\n\n**Description**\nWhen user clicks on assign new roles to a space button, the resulting\nflyout gets announced incorrectly as \"you are in a modal dialog...\"\nwhich doesn't give any context to non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby' attribute\n\n**Screen:**\n<img width=\"1323\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad"}},"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/218576","number":218576,"mergeCommit":{"message":"fix: [Platform:StackManagement:Kibana:Spaces] Assign roles to a space flyout announced incorrectly (#218576)\n\nCloses: #218351\n\n**Description**\nWhen user clicks on assign new roles to a space button, the resulting\nflyout gets announced incorrectly as \"you are in a modal dialog...\"\nwhich doesn't give any context to non-sighted user.\n\n**Changes made:**\n1. added 'aria-labelledby' attribute\n\n**Screen:**\n<img width=\"1323\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/63ffdcca-2139-4302-9dce-ded3a4d3b9a2\"\n/>","sha":"78bf949dbf12a8da845f1fa0e45336eac003eaad"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
8c1a846ef9
|
[8.18] [Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540) (#218594)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540)](https://github.com/elastic/kibana/pull/218540) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T17:11:47Z","message":"[Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540)\n\n**Resolves: https://github.com/elastic/kibana/issues/209000**\n**Related PR: https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR updates the code to show a promo banner in the rules table. With\nthis change, this banner will be shown in both ESS (8.18+) and\nServerless. Previously it was shown only in ESS. In both ESS and\nServerless the blog link is the same – this is expected and correct.\n\nWe couldn't add a banner for Serverless earlier, because the blog post\nwas published on the 8.18/9.0 release day. If we would have added it\nearlier, Serverless users would click on a link at get a 404 page.\n\nExpected behaviour for both ESS and Serverless:\n - Banner is visible above the rules table\n- The link leads to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img width=\"1006\" alt=\"Schermafbeelding 2025-03-11 om 12 25 45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n- Adds a rule management table banner to promote prebuilt rule\ncustomization in Serverless. Previously this banner was only shown in\nESS. Banner is dismissible. Its state is stored in localStorage.\n- Tweaks banner wording a bit as per docs suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS","number":218540,"url":"https://github.com/elastic/kibana/pull/218540","mergeCommit":{"message":"[Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540)\n\n**Resolves: https://github.com/elastic/kibana/issues/209000**\n**Related PR: https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR updates the code to show a promo banner in the rules table. With\nthis change, this banner will be shown in both ESS (8.18+) and\nServerless. Previously it was shown only in ESS. In both ESS and\nServerless the blog link is the same – this is expected and correct.\n\nWe couldn't add a banner for Serverless earlier, because the blog post\nwas published on the 8.18/9.0 release day. If we would have added it\nearlier, Serverless users would click on a link at get a 404 page.\n\nExpected behaviour for both ESS and Serverless:\n - Banner is visible above the rules table\n- The link leads to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img width=\"1006\" alt=\"Schermafbeelding 2025-03-11 om 12 25 45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n- Adds a rule management table banner to promote prebuilt rule\ncustomization in Serverless. Previously this banner was only shown in\nESS. Banner is dismissible. Its state is stored in localStorage.\n- Tweaks banner wording a bit as per docs suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218540","number":218540,"mergeCommit":{"message":"[Security Solution] Show banner to promote prebuilt rule customization in both Serverless and ESS (#218540)\n\n**Resolves: https://github.com/elastic/kibana/issues/209000**\n**Related PR: https://github.com/elastic/kibana/pull/213750**\n\n## Summary\n\nThis PR updates the code to show a promo banner in the rules table. With\nthis change, this banner will be shown in both ESS (8.18+) and\nServerless. Previously it was shown only in ESS. In both ESS and\nServerless the blog link is the same – this is expected and correct.\n\nWe couldn't add a banner for Serverless earlier, because the blog post\nwas published on the 8.18/9.0 release day. If we would have added it\nearlier, Serverless users would click on a link at get a 404 page.\n\nExpected behaviour for both ESS and Serverless:\n - Banner is visible above the rules table\n- The link leads to\nhttps://www.elastic.co/blog/security-prebuilt-rules-editing\n\n<img width=\"1006\" alt=\"Schermafbeelding 2025-03-11 om 12 25 45\"\nsrc=\"https://github.com/user-attachments/assets/41d83db9-4bc4-433e-a7e2-c5ef1049a20c\"\n/>\n\n**Changes:**\n- Adds a rule management table banner to promote prebuilt rule\ncustomization in Serverless. Previously this banner was only shown in\nESS. Banner is dismissible. Its state is stored in localStorage.\n- Tweaks banner wording a bit as per docs suggestion\n([comment](https://github.com/elastic/kibana/pull/213750/files#r1989313701))","sha":"40a91594350a02d6756caf78c7e337df65a48ecf"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
Vitalii Dmyterko
|
d8e5155c84
|
[8.18] [Security Solution][Detection Engine] adds async ES|QL query (#216667) (#218585)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Detection Engine] adds async ES|QL query (#216667)](https://github.com/elastic/kibana/pull/216667) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-17T14:23:07Z","message":"[Security Solution][Detection Engine] adds async ES|QL query (#216667)\n\n## Summary\n\n- addresses https://github.com/elastic/security-team/issues/11116 (list\nitem 2)\n\nIntroducing async query would allow to overcome ES request timeout for\nlong running rules and queries.\n\nTimeout for ES request is [defined in alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand is smaller value out of rule execution timeout or default ES request\ntimeout(which is 5m and hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf ES|QL rule performs a single long-running ES query, it can time out\nafter 5m due to this ES request timeout. This value can't be changed,\nunlike rule execution timeout. It can be overwritten in Kibana config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we can encounter situations when rule fails execution after 5m due\nto ES request timeout, despite a fact it configured with longer timeout\nof 15m\n\nBy using async query, we can overcome this limitation and can poll async\nquery results until it completes or rule timeouts\n\nMore details in internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by: Ryland Herrick <ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Detection Engine","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution][Detection Engine] adds async ES|QL query","number":216667,"url":"https://github.com/elastic/kibana/pull/216667","mergeCommit":{"message":"[Security Solution][Detection Engine] adds async ES|QL query (#216667)\n\n## Summary\n\n- addresses https://github.com/elastic/security-team/issues/11116 (list\nitem 2)\n\nIntroducing async query would allow to overcome ES request timeout for\nlong running rules and queries.\n\nTimeout for ES request is [defined in alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand is smaller value out of rule execution timeout or default ES request\ntimeout(which is 5m and hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf ES|QL rule performs a single long-running ES query, it can time out\nafter 5m due to this ES request timeout. This value can't be changed,\nunlike rule execution timeout. It can be overwritten in Kibana config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we can encounter situations when rule fails execution after 5m due\nto ES request timeout, despite a fact it configured with longer timeout\nof 15m\n\nBy using async query, we can overcome this limitation and can poll async\nquery results until it completes or rule timeouts\n\nMore details in internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by: Ryland Herrick <ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216667","number":216667,"mergeCommit":{"message":"[Security Solution][Detection Engine] adds async ES|QL query (#216667)\n\n## Summary\n\n- addresses https://github.com/elastic/security-team/issues/11116 (list\nitem 2)\n\nIntroducing async query would allow to overcome ES request timeout for\nlong running rules and queries.\n\nTimeout for ES request is [defined in alerting\nframework](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_es_request_timeout.ts#L21)\nand is smaller value out of rule execution timeout or default ES request\ntimeout(which is 5m and hardcoded\n[here](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/alerting/server/lib/get_rule_task_timeout.ts)).\n\nIf ES|QL rule performs a single long-running ES query, it can time out\nafter 5m due to this ES request timeout. This value can't be changed,\nunlike rule execution timeout. It can be overwritten in Kibana config\n\n```\nxpack.alerting.rules.run:\n timeout: '10m'\n ruleTypeOverrides:\n - id: 'siem.esqlRule'\n timeout: '15m'\n```\nSo, we can encounter situations when rule fails execution after 5m due\nto ES request timeout, despite a fact it configured with longer timeout\nof 15m\n\nBy using async query, we can overcome this limitation and can poll async\nquery results until it completes or rule timeouts\n\nMore details in internal\n[issue](https://github.com/elastic/sdh-security-team/issues/1224)\n\n---------\n\nCo-authored-by: Ryland Herrick <ryalnd@gmail.com>","sha":"3d7aac1a443092ebdbc20fbd9345d373bcb16c48"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218567","number":218567,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3a0e234b20
|
[8.18] [ML] Fix vCPU usage message in the Start deployment dialog (#218557) (#218578)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] Fix vCPU usage message in the Start deployment dialog (#218557)](https://github.com/elastic/kibana/pull/218557) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-17T15:23:20Z","message":"[ML] Fix vCPU usage message in the Start deployment dialog (#218557)\n\n## Summary\n\nFixes the info callout message in the “Start model deployment” dialog by\nreplacing the ELSER name with a generic model reference.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[ML] Fix vCPU usage message in the Start deployment dialog ","number":218557,"url":"https://github.com/elastic/kibana/pull/218557","mergeCommit":{"message":"[ML] Fix vCPU usage message in the Start deployment dialog (#218557)\n\n## Summary\n\nFixes the info callout message in the “Start model deployment” dialog by\nreplacing the ELSER name with a generic model reference.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218557","number":218557,"mergeCommit":{"message":"[ML] Fix vCPU usage message in the Start deployment dialog (#218557)\n\n## Summary\n\nFixes the info callout message in the “Start model deployment” dialog by\nreplacing the ELSER name with a generic model reference.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1958da5d180dfbb797962cd9d1d8475a8d5ff5d"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
Marshall Main
|
a2630eb4ab
|
[8.18] [Security Solution][Rules Management] Separate actions import logic from rules import (#216380) (#218484)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Rules Management] Separate actions import logic from rules import (#216380)](https://github.com/elastic/kibana/pull/216380) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T15:47:26Z","message":"[Security Solution][Rules Management] Separate actions import logic from rules import (#216380)\n\n## Summary\n\nRedo of https://github.com/elastic/kibana/pull/193471\nCloses https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug where importing a rule fails with a connector into a space\nwhere (1) the connector already exists, and (2) the existing connector\nwas exported and re-imported from another space. The import logic in\nthis scenario effectively tries to convert the action ID on the rule\nimport twice. The second conversion attempt tries to use the old action\nID to look up the correct new action ID in a map, however, in this test\nscenario the action ID has already been updated by legacy SO ID\nmigration logic and there is no map entry with the new ID as a key. The\nresult is that the second attempt sets the action ID to undefined,\nresulting in an import failure.\n\nThe root cause of the bug is that we have two different places in the\nrule import logic where action IDs are migrated. The first ID migration\nwas done by `migrateLegacyActionsIds` prior to importing rule actions,\nand the second migration was done by `importRuleActionConnectors` after\nimporting the actions. `importRuleActionConnectors` used a lookup table\nto convert old IDs to new IDs, but if the connector already existed and\nhad an `originId` then the rule action would already be migrated by\n`migrateLegacyActionsIds`. The lookup table used by\n`importRuleActionConnectors` does not have entries for migrated IDs,\nonly the original IDs, so in that case the result of the lookup is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the logic to create a clean separation between action\nand rule import. We now import the connectors first, ignoring the rules,\nthen migrate action IDs on the rules afterwards. This handles connectors\nchanging IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs changing on import if there are ID conflicts. Only after the\nconnectors are imported and rule actions are migrated do we then verify\nif each rule action references a connector ID that actually exists with\nthe new `checkRuleActions` function, replacing\n`checkIfActionsHaveMissingConnectors` and related functions that were\nalso buggy.\n\nFinally, as a nice side effect this rework removes \"rule action\nconnector missing\" errors out of the `action_connector_errors` part of\nthe response. `action_connector_errors` is reserved for errors importing\nconnectors specifically. If a rule action is missing a connector and\ntherefore we don't import the rule, that's a rule error and it's\nrepresented in the `errors` part of the response. Since the shape of the\nresponse is not changing, I don't consider this a breaking change but\nrather a bug fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below and change the extension back to\n.ndjson from .json (github does not allow .ndjson files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2. Import the rule and connector into a space (default is fine)\n3. Create a new space\n4. Import the rule and connector into the new space\n5. Import the rule and connector into the new space again, but check the\n`Overwrite existing connectors with conflicting action \"id\"` box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection Rule Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution][Rules Management] Separate actions import logic from rules import","number":216380,"url":"https://github.com/elastic/kibana/pull/216380","mergeCommit":{"message":"[Security Solution][Rules Management] Separate actions import logic from rules import (#216380)\n\n## Summary\n\nRedo of https://github.com/elastic/kibana/pull/193471\nCloses https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug where importing a rule fails with a connector into a space\nwhere (1) the connector already exists, and (2) the existing connector\nwas exported and re-imported from another space. The import logic in\nthis scenario effectively tries to convert the action ID on the rule\nimport twice. The second conversion attempt tries to use the old action\nID to look up the correct new action ID in a map, however, in this test\nscenario the action ID has already been updated by legacy SO ID\nmigration logic and there is no map entry with the new ID as a key. The\nresult is that the second attempt sets the action ID to undefined,\nresulting in an import failure.\n\nThe root cause of the bug is that we have two different places in the\nrule import logic where action IDs are migrated. The first ID migration\nwas done by `migrateLegacyActionsIds` prior to importing rule actions,\nand the second migration was done by `importRuleActionConnectors` after\nimporting the actions. `importRuleActionConnectors` used a lookup table\nto convert old IDs to new IDs, but if the connector already existed and\nhad an `originId` then the rule action would already be migrated by\n`migrateLegacyActionsIds`. The lookup table used by\n`importRuleActionConnectors` does not have entries for migrated IDs,\nonly the original IDs, so in that case the result of the lookup is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the logic to create a clean separation between action\nand rule import. We now import the connectors first, ignoring the rules,\nthen migrate action IDs on the rules afterwards. This handles connectors\nchanging IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs changing on import if there are ID conflicts. Only after the\nconnectors are imported and rule actions are migrated do we then verify\nif each rule action references a connector ID that actually exists with\nthe new `checkRuleActions` function, replacing\n`checkIfActionsHaveMissingConnectors` and related functions that were\nalso buggy.\n\nFinally, as a nice side effect this rework removes \"rule action\nconnector missing\" errors out of the `action_connector_errors` part of\nthe response. `action_connector_errors` is reserved for errors importing\nconnectors specifically. If a rule action is missing a connector and\ntherefore we don't import the rule, that's a rule error and it's\nrepresented in the `errors` part of the response. Since the shape of the\nresponse is not changing, I don't consider this a breaking change but\nrather a bug fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below and change the extension back to\n.ndjson from .json (github does not allow .ndjson files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2. Import the rule and connector into a space (default is fine)\n3. Create a new space\n4. Import the rule and connector into the new space\n5. Import the rule and connector into the new space again, but check the\n`Overwrite existing connectors with conflicting action \"id\"` box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216380","number":216380,"mergeCommit":{"message":"[Security Solution][Rules Management] Separate actions import logic from rules import (#216380)\n\n## Summary\n\nRedo of https://github.com/elastic/kibana/pull/193471\nCloses https://github.com/elastic/security-team/issues/8644\n\n> Fixes a bug where importing a rule fails with a connector into a space\nwhere (1) the connector already exists, and (2) the existing connector\nwas exported and re-imported from another space. The import logic in\nthis scenario effectively tries to convert the action ID on the rule\nimport twice. The second conversion attempt tries to use the old action\nID to look up the correct new action ID in a map, however, in this test\nscenario the action ID has already been updated by legacy SO ID\nmigration logic and there is no map entry with the new ID as a key. The\nresult is that the second attempt sets the action ID to undefined,\nresulting in an import failure.\n\nThe root cause of the bug is that we have two different places in the\nrule import logic where action IDs are migrated. The first ID migration\nwas done by `migrateLegacyActionsIds` prior to importing rule actions,\nand the second migration was done by `importRuleActionConnectors` after\nimporting the actions. `importRuleActionConnectors` used a lookup table\nto convert old IDs to new IDs, but if the connector already existed and\nhad an `originId` then the rule action would already be migrated by\n`migrateLegacyActionsIds`. The lookup table used by\n`importRuleActionConnectors` does not have entries for migrated IDs,\nonly the original IDs, so in that case the result of the lookup is\n`undefined` which we assign to the action ID.\n\nThis PR reworks the logic to create a clean separation between action\nand rule import. We now import the connectors first, ignoring the rules,\nthen migrate action IDs on the rules afterwards. This handles connectors\nchanging IDs in any way, either through the 7.x->8.0 migration long ago\nor IDs changing on import if there are ID conflicts. Only after the\nconnectors are imported and rule actions are migrated do we then verify\nif each rule action references a connector ID that actually exists with\nthe new `checkRuleActions` function, replacing\n`checkIfActionsHaveMissingConnectors` and related functions that were\nalso buggy.\n\nFinally, as a nice side effect this rework removes \"rule action\nconnector missing\" errors out of the `action_connector_errors` part of\nthe response. `action_connector_errors` is reserved for errors importing\nconnectors specifically. If a rule action is missing a connector and\ntherefore we don't import the rule, that's a rule error and it's\nrepresented in the `errors` part of the response. Since the shape of the\nresponse is not changing, I don't consider this a breaking change but\nrather a bug fix.\n\n## Repro Steps\n\nRepro Steps\n1. Download the export file below and change the extension back to\n.ndjson from .json (github does not allow .ndjson files\n\n[rules_export.json](https://github.com/user-attachments/files/17065272/rules_export.json)\n2. Import the rule and connector into a space (default is fine)\n3. Create a new space\n4. Import the rule and connector into the new space\n5. Import the rule and connector into the new space again, but check the\n`Overwrite existing connectors with conflicting action \"id\"` box.\nObserve the failure.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"52ecdd0ac76e6f56ff799399f453596c0cb3538c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218466","number":218466,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218465","number":218465,"state":"OPEN"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218467","number":218467,"state":"OPEN"}]}] BACKPORT--> |
||
elastic-vault-github-plugin-prod[bot]
|
1aeb2fc384
|
[8.18] Sync bundled packages with Package Storage (#217540)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2596 --------- Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
ed4a8c3873
|
[8.18] [Synthetics] Fixed test run logs per page (#218458) (#218524)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Fixed test run logs per page (#218458)](https://github.com/elastic/kibana/pull/218458) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-17T05:34:38Z","message":"[Synthetics] Fixed test run logs per page (#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.6"],"title":"[Synthetics] Fixed test run logs per page","number":218458,"url":"https://github.com/elastic/kibana/pull/218458","mergeCommit":{"message":"[Synthetics] Fixed test run logs per page (#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218458","number":218458,"mergeCommit":{"message":"[Synthetics] Fixed test run logs per page (#218458)","sha":"e96f0566ce37c478e35c31e5a01419938062758d"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
0b4badc7d1
|
[8.18] [Custom threshold rule] Allow group for ip type fields !! (#216062) (#218336)
# Backport This will backport the following commits from `main` to `8.18`: - [[Custom threshold rule] Allow group for ip type fields !! (#216062)](https://github.com/elastic/kibana/pull/216062) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T18:15:02Z","message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:all-open","Team:obs-ux-management","v9.1.0"],"title":"[Custom threshold rule] Allow group for ip type fields !!","number":216062,"url":"https://github.com/elastic/kibana/pull/216062","mergeCommit":{"message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216062","number":216062,"mergeCommit":{"message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
Tiago Costa
|
ca00255b3f
|
chore(NA): bump version to 8.18.1 (#218303)
Usually bump from 8.18.0 to 8.18.1 |
||
jennypavlova
|
906ff07331
|
[8.18] [APM][OTel] Encode service name in the APM URLs (#217092) (#218477)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM][OTel] Encode service name in the APM URLs (#217092)](https://github.com/elastic/kibana/pull/217092) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T15:52:33Z","message":"[APM][OTel] Encode service name in the APM URLs (#217092)\n\nCloses #213943\n\n## Summary\n\nThis PR ensures the service name is always encoded in the APM UIs. It's\na follow-up of https://github.com/elastic/kibana/pull/215031 and aims to\nfind a better solution to the problem:\n- Add the encoding directly to `formatRequest` as suggested there\n- I saw that there are many places where we use legacy Url builders, so\nI will try to replace them where possible and use\napm router link method where the path is encoded\n([ref]( |
||
|
Kibana Machine
|
fde4a3d9ea
|
[8.18] [Security Solution] Fix redux action being fired because of unused react-router value (#217055) (#218454)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix redux action being fired because of unused react-router value (#217055)](https://github.com/elastic/kibana/pull/217055) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kevin Qualters","email":"56408403+kqualters-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-16T14:13:44Z","message":"[Security Solution] Fix redux action being fired because of unused react-router value (#217055)\n\n## Summary\n\nThis pr fixes a bug with the RouteCapture component, used at a high\nlevel in the security solution component tree, to reflect url changes\ninto redux. The code previously used the full result of\n'react-router-dom' 's useLocation hook as the payload, which contains 4\nparameters, pathname, search, hash that we make use of, and a 4th that\nwas added sometime later by the library that is essentially a random id\ngenerated every time the hook is called, called key. We have never used\nthis, and it was being inadvertently copied into the redux state, and\nalso causing some other actions or hooks based listeners to run I think\nas well.\n\nBelow is the contrived example of going from the home page to an empty\nalerts page, and you can see 4 actions in the after, and 5 in the\nbefore, with 1 updating only the key. May reduce more unneeded actions\nwith more going on in the page, but exactly how many is not known.\nBefore:\n\n (#218444)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement (#217829)](https://github.com/elastic/kibana/pull/217829) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-16T13:19:03Z","message":"fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}` for mentioned places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement","number":217829,"url":"https://github.com/elastic/kibana/pull/217829","mergeCommit":{"message":"fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}` for mentioned places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7"}},"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/217829","number":217829,"mergeCommit":{"message":"fix: [Analytics:Visualize Library page]Dialog modal missing title from announcement (#217829)\n\nCloses: #215112\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added `aria-labelledby={flyoutTitleId}` for mentioned places","sha":"bf7389f515480a4d518e3a238c5fd54caac033f7"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
9556de5d7e
|
[8.18] [Security Solution] Allow disabling experimental features via config (#217363) (#218427)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Allow disabling experimental features via config (#217363)](https://github.com/elastic/kibana/pull/217363) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-04-16T12:09:28Z","message":"[Security Solution] Allow disabling experimental features via config (#217363)\n\n## Summary\n\nThis PR adds support for disabling experimental features using the\nexisting `xpack.securitySolution.enableExperimental` configuration.\n\nThis solves the problem of not being able to disable a feature by config\nonce the feature has been enabled by default.\n\n### The Challenge \n\nWhen we start developing a feature under an experimental flag we always\nfollow the same steps:\n\n1 - Create the experimental flag disabled by default + enable it via\nconfig for testing\n2 - Implement the feature\n3 - Enable the experimental flag by default when we want to release the\nfeature.\n4 - Deployments can disable the feature via config (as a safety\nmeasure).\n5 - Remove the experimental flag after some time.\n\nWe start by creating the flag disabled by default while we implement it.\nIn `experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n [...]\n```\nAnd enable it via config with:\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureEnabled\n```\n\nOnce the implementation is done and the experimental flag can be enabled\nby default, we have to do a trick:\nSince the `xpack.securitySolution.enableExperimental` config can only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`, what\nwe have to do is rename the flag to `myFeatureDisabled` and keep the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also need to do a code refactor to update all the places in the\ncode where the flag was checked: `if (myFeatureEnabled)` -> `if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling the feature via config (in\ncase something goes wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the possibility to turn a flag to _false_ using the\nsame `xpack.securitySolution.enableExperimental` config. This was\npreferable to introducing a new config since this one is already\nwhitelisted in Cloud UI, can be easily overritten in deployments, and\nalso because people are used to it.\n\nWith these changes, the first two steps would be the same, with the\ndifference that we won't need to have the _Enabled_ or _Disabled_ word\nat the end of the flag name. It could be just the feature name, in\n`experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n [...]\n```\n\nAnd when we need to enable the feature by default, we can just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor or confusing naming would be required. \n\nThen, in case we need to disable the feature in a production deployment\nfor some reason, we could just do this via config :\n```yml\nxpack.securitySolution.enableExperimental:\n - disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[Security Solution] Allow disabling experimental features via config","number":217363,"url":"https://github.com/elastic/kibana/pull/217363","mergeCommit":{"message":"[Security Solution] Allow disabling experimental features via config (#217363)\n\n## Summary\n\nThis PR adds support for disabling experimental features using the\nexisting `xpack.securitySolution.enableExperimental` configuration.\n\nThis solves the problem of not being able to disable a feature by config\nonce the feature has been enabled by default.\n\n### The Challenge \n\nWhen we start developing a feature under an experimental flag we always\nfollow the same steps:\n\n1 - Create the experimental flag disabled by default + enable it via\nconfig for testing\n2 - Implement the feature\n3 - Enable the experimental flag by default when we want to release the\nfeature.\n4 - Deployments can disable the feature via config (as a safety\nmeasure).\n5 - Remove the experimental flag after some time.\n\nWe start by creating the flag disabled by default while we implement it.\nIn `experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n [...]\n```\nAnd enable it via config with:\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureEnabled\n```\n\nOnce the implementation is done and the experimental flag can be enabled\nby default, we have to do a trick:\nSince the `xpack.securitySolution.enableExperimental` config can only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`, what\nwe have to do is rename the flag to `myFeatureDisabled` and keep the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also need to do a code refactor to update all the places in the\ncode where the flag was checked: `if (myFeatureEnabled)` -> `if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling the feature via config (in\ncase something goes wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the possibility to turn a flag to _false_ using the\nsame `xpack.securitySolution.enableExperimental` config. This was\npreferable to introducing a new config since this one is already\nwhitelisted in Cloud UI, can be easily overritten in deployments, and\nalso because people are used to it.\n\nWith these changes, the first two steps would be the same, with the\ndifference that we won't need to have the _Enabled_ or _Disabled_ word\nat the end of the flag name. It could be just the feature name, in\n`experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n [...]\n```\n\nAnd when we need to enable the feature by default, we can just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor or confusing naming would be required. \n\nThen, in case we need to disable the feature in a production deployment\nfor some reason, we could just do this via config :\n```yml\nxpack.securitySolution.enableExperimental:\n - disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217363","number":217363,"mergeCommit":{"message":"[Security Solution] Allow disabling experimental features via config (#217363)\n\n## Summary\n\nThis PR adds support for disabling experimental features using the\nexisting `xpack.securitySolution.enableExperimental` configuration.\n\nThis solves the problem of not being able to disable a feature by config\nonce the feature has been enabled by default.\n\n### The Challenge \n\nWhen we start developing a feature under an experimental flag we always\nfollow the same steps:\n\n1 - Create the experimental flag disabled by default + enable it via\nconfig for testing\n2 - Implement the feature\n3 - Enable the experimental flag by default when we want to release the\nfeature.\n4 - Deployments can disable the feature via config (as a safety\nmeasure).\n5 - Remove the experimental flag after some time.\n\nWe start by creating the flag disabled by default while we implement it.\nIn `experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureEnabled: false,\n [...]\n```\nAnd enable it via config with:\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureEnabled\n```\n\nOnce the implementation is done and the experimental flag can be enabled\nby default, we have to do a trick:\nSince the `xpack.securitySolution.enableExperimental` config can only\nturn flags to _true_, instead of setting `myFeatureEnabled: true`, what\nwe have to do is rename the flag to `myFeatureDisabled` and keep the\nvalue as _false_:\n\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeatureDisabled: false,\n [...]\n```\nThen we also need to do a code refactor to update all the places in the\ncode where the flag was checked: `if (myFeatureEnabled)` -> `if\n(!myFeatureDisabled)`\n\nThis way, we have the option of disabling the feature via config (in\ncase something goes wrong):\n```yml\nxpack.securitySolution.enableExperimental:\n - myFeatureDisabled\n```\n\n### A solution\n\nThis PR introduces the possibility to turn a flag to _false_ using the\nsame `xpack.securitySolution.enableExperimental` config. This was\npreferable to introducing a new config since this one is already\nwhitelisted in Cloud UI, can be easily overritten in deployments, and\nalso because people are used to it.\n\nWith these changes, the first two steps would be the same, with the\ndifference that we won't need to have the _Enabled_ or _Disabled_ word\nat the end of the flag name. It could be just the feature name, in\n`experimental_features.ts`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: false,\n [...]\n```\n\nAnd when we need to enable the feature by default, we can just turn it\nto `true`:\n```ts\nexport const allowedExperimentalValues = Object.freeze({\n myFeature: true,\n [...]\n```\nNo tedious refactor or confusing naming would be required. \n\nThen, in case we need to disable the feature in a production deployment\nfor some reason, we could just do this via config :\n```yml\nxpack.securitySolution.enableExperimental:\n - disable:myFeature\n```\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"937dbba41ef6d52b1d060f03f0e2d9a99247016e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
cea79ffef7
|
[8.18] fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827) (#218423)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827)](https://github.com/elastic/kibana/pull/217827) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-16T12:03:38Z","message":"fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Set correct value for` aria-labelledby` attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:Graph page]Dialog modal missing title from announcement","number":217827,"url":"https://github.com/elastic/kibana/pull/217827","mergeCommit":{"message":"fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Set correct value for` aria-labelledby` attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0"}},"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/217827","number":217827,"mergeCommit":{"message":"fix: [Analytics:Graph page]Dialog modal missing title from announcement (#217827)\n\nCloses: #214760\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Set correct value for` aria-labelledby` attr.","sha":"b91da375a3c965181e2b2ee6f899d42ee6dcc0f0"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
39e48f126d
|
[8.18] [Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123) (#218247)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)](https://github.com/elastic/kibana/pull/218123) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T11:45:08Z","message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint","number":218123,"url":"https://github.com/elastic/kibana/pull/218123","mergeCommit":{"message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218123","number":218123,"mergeCommit":{"message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
145f88fabd
|
[8.18] fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666) (#218258)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)](https://github.com/elastic/kibana/pull/217666) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T12:17:20Z","message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","release_note:skip","Feature:Data Frame Analytics","backport:prev-major","v9.1.0"],"title":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement","number":217666,"url":"https://github.com/elastic/kibana/pull/217666","mergeCommit":{"message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}},"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/217666","number":217666,"mergeCommit":{"message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
85ce57c0f7
|
[8.18] fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831) (#218273)
# Backport This will backport the following commits from `main` to `8.18`: - [fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)](https://github.com/elastic/kibana/pull/217831) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T13:38:48Z","message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","Feature:Anomaly Detection","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement","number":217831,"url":"https://github.com/elastic/kibana/pull/217831","mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}},"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/217831","number":217831,"mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Tomasz Ciecierski
|
330e31c5f7
|
[EDR Workflows][8.18] Upgrade Osquery and ECS schemas (#217807) | ||
|
Kibana Machine
|
a50eb4c01f
|
[8.18] [ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107) (#218216)
# Backport This will backport the following commits from `main` to `8.18`: - [[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)](https://github.com/elastic/kibana/pull/218107) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T09:06:29Z","message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar","number":218107,"url":"https://github.com/elastic/kibana/pull/218107","mergeCommit":{"message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218107","number":218107,"mergeCommit":{"message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co> |
||
Francesco Fagnani
|
a5f832e6cd
|
[8.18] [Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197) (#218292)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197)](https://github.com/elastic/kibana/pull/216197) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T14:53:14Z","message":"[Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197)\n\nThis PR closes #215668.\n\nThe global parameters are synched in the endpoints where they are\ncreated, edited or deleted.\n\n---------\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params","number":216197,"url":"https://github.com/elastic/kibana/pull/216197","mergeCommit":{"message":"[Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197)\n\nThis PR closes #215668.\n\nThe global parameters are synched in the endpoints where they are\ncreated, edited or deleted.\n\n---------\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216197","number":216197,"mergeCommit":{"message":"[Synthetics] Sync global parameters is called in the endpoints to add, edit or delete global params (#216197)\n\nThis PR closes #215668.\n\nThe global parameters are synched in the endpoints where they are\ncreated, edited or deleted.\n\n---------\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"f693e7218e0edb145f1d4344b484b5b48e80998d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218290","number":218290,"state":"OPEN"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Jeramy Soucy
|
9ff3c8f207
|
[8.18] Fixes bulk re-encryption for encrypted objects located in all spaces (#217625) (#218179)
# Backport This will backport the following commits from `main` to `8.18`: - [Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)](https://github.com/elastic/kibana/pull/217625) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T19:20:38Z","message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","backport:all-open","v9.1.0"],"title":"Fixes bulk re-encryption for encrypted objects located in all spaces","number":217625,"url":"https://github.com/elastic/kibana/pull/217625","mergeCommit":{"message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217625","number":217625,"mergeCommit":{"message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
fc87edd906
|
[8.18] [Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959) (#218153)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959)](https://github.com/elastic/kibana/pull/217959) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:22:38Z","message":"[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959)\n\n**Resolves: https://github.com/elastic/security-team/issues/7216**\n\n## Summary\n\nThis PR updates the Endpoint policy callback to: \n\n- **Install only the Elastic Defend rule if it's missing**, without\nupgrading it to the latest version. Previously, the rule was both\ninstalled and updated whenever an Endpoint policy was created, which\nconflicted with rule customization. Automatic upgrades could erase\nexisting user customizations.\n\n- **Avoid triggering the installation or upgrade of any other prebuilt\nrules** as part of this flow. The Endpoint package policy creation\ncallback\n([source]( |
||
|
Kibana Machine
|
4dd7c79ecf
|
[8.18] [ObsUX][A11y] Fix focus for popover in details flyout (#218095) (#218125)
# Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX][A11y] Fix focus for popover in details flyout (#218095)](https://github.com/elastic/kibana/pull/218095) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-14T14:15:25Z","message":"[ObsUX][A11y] Fix focus for popover in details flyout (#218095)\n\nCloses https://github.com/elastic/kibana/issues/212633\n\n## Summary\n\nFixed navigation by keeping focus on Popover opener element\n\n### How to test\nObservability -> Infrastructure -> Infrastructure inventory page.\n1. Navigate to any square below All button.\n2. Press Enter.\n3. Navigate to infographic for Host IP.\n4. Press Enter.\n5. Press Esc.\n\nExpected result: Navigation continues to next element when Tab key is\npressed.\n\nBEFORE \n\n\n |
||
Milosz Marcinkowski
|
6d7097d6be
|
[8.18] [APM][UI] Sort environment dropdown alphabetically (#217710) (#217880)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM][UI] Sort environment dropdown alphabetically (#217710)](https://github.com/elastic/kibana/pull/217710) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-10T15:38:20Z","message":"[APM][UI] Sort environment dropdown alphabetically (#217710)\n\nCloses #217814\n\n### Summary\n\nSort environment list alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\" alt=\"Screenshot 2025-04-10 at 12 01 15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58 27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][UI] Sort environment dropdown alphabetically","number":217710,"url":"https://github.com/elastic/kibana/pull/217710","mergeCommit":{"message":"[APM][UI] Sort environment dropdown alphabetically (#217710)\n\nCloses #217814\n\n### Summary\n\nSort environment list alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\" alt=\"Screenshot 2025-04-10 at 12 01 15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58 27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217710","number":217710,"mergeCommit":{"message":"[APM][UI] Sort environment dropdown alphabetically (#217710)\n\nCloses #217814\n\n### Summary\n\nSort environment list alphabetically.\n\n|Before|After|\n|-|-|\n|<img width=\"1724\" alt=\"Screenshot 2025-04-10 at 12 01 15\"\nsrc=\"https://github.com/user-attachments/assets/53f0b66d-146a-45d9-b4e3-25bde350a263\"\n/>|<img width=\"1722\" alt=\"Screenshot 2025-04-10 at 11 58 27\"\nsrc=\"https://github.com/user-attachments/assets/91315d23-801c-4a16-8688-c43d60c389c8\"\n/>|","sha":"23cbaa6d55de4e331ce180f6857db94ca11c209a"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Julia Rechkunova
|
43fde917fb
|
[8.18] [Discover] Fix CSV for ES|QL embeddable (#216325) (#216868)
# Backport This will backport the following commits from `main` to `8.18`: - [[Discover] Fix CSV for ES|QL embeddable (#216325)](https://github.com/elastic/kibana/pull/216325) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:14:55Z","message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","v9.0.0","Team:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Fix CSV for ES|QL embeddable","number":216325,"url":"https://github.com/elastic/kibana/pull/216325","mergeCommit":{"message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5"}},"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/216325","number":216325,"mergeCommit":{"message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216851","number":216851,"state":"OPEN"}]}] BACKPORT--> |
||
|
Lisa Cawley
|
c3769d1c0b
|
[8.18] [DOCS] Add minimal synthetic APIs (#214518) (#217902)
# Backport This will backport the following commits from `main` to `8.18`: - [[DOCS] Add minimal synthetic APIs (#214518)](https://github.com/elastic/kibana/pull/214518) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T17:26:49Z","message":"[DOCS] Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[DOCS] Add minimal synthetic APIs","number":214518,"url":"https://github.com/elastic/kibana/pull/214518","mergeCommit":{"message":"[DOCS] Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214518","number":214518,"mergeCommit":{"message":"[DOCS] Add minimal synthetic APIs (#214518)\n\nCo-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>","sha":"e00f013b62a42a2870be3b7a3e4cadab8ba191c4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
6ccf8447c6 | skip failing test suite (#207913) | ||
|
Kibana Machine
|
f1b0ff7404
|
[8.18] [Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests (#217847) (#217972)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests (#217847)](https://github.com/elastic/kibana/pull/217847) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2025-04-11T10:47:23Z","message":"[Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests (#217847)\n\n## Summary\n\n[Preconfigured\nconnectors](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html)\nare those that are specified via the `kibana.yml` config, and thus they\ncan't be deleted. In tests, we've hardcoded their ids to skip deleting\nthem when we need to clean up the tests' state.\n\nSometimes, the id of a preconfigured connector gets changed by somebody,\nwhich breaks tests of multiple teams in MKI pipelines, such as the\nperiodic pipeline or the release quality gates. The problem is that it\ndoesn't happen on CI where Kibana doesn't have any preconfigured\nconnectors, so this feedback loop is too long. When tests in an MKI\npipeline break, it's not immediately clear what happened and who should\nfix it. Eventually it gets fixed by someone [like\nthis](https://github.com/elastic/kibana/pull/217570/files).\n\nInstead of hardcoding the ids, we should dynamically determine if a\nconnector is preconfigured and if it should be deleted by a test or not.\nThis is possible to do as each connector has the corresponding\n`is_preconfigured` property.\n\n<img width=\"1073\" alt=\"Screenshot 2025-04-10 at 14 16 15\"\nsrc=\"https://github.com/user-attachments/assets/e330cd5f-c9f0-43da-b4b4-f2a0a2fd10a5\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b4d3a2a8f2b135436ea510c52aa82e4a77d6fca8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Team:Threat Hunting:Explore","Team:Detection Engine","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests","number":217847,"url":"https://github.com/elastic/kibana/pull/217847","mergeCommit":{"message":"[Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests (#217847)\n\n## Summary\n\n[Preconfigured\nconnectors](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html)\nare those that are specified via the `kibana.yml` config, and thus they\ncan't be deleted. In tests, we've hardcoded their ids to skip deleting\nthem when we need to clean up the tests' state.\n\nSometimes, the id of a preconfigured connector gets changed by somebody,\nwhich breaks tests of multiple teams in MKI pipelines, such as the\nperiodic pipeline or the release quality gates. The problem is that it\ndoesn't happen on CI where Kibana doesn't have any preconfigured\nconnectors, so this feedback loop is too long. When tests in an MKI\npipeline break, it's not immediately clear what happened and who should\nfix it. Eventually it gets fixed by someone [like\nthis](https://github.com/elastic/kibana/pull/217570/files).\n\nInstead of hardcoding the ids, we should dynamically determine if a\nconnector is preconfigured and if it should be deleted by a test or not.\nThis is possible to do as each connector has the corresponding\n`is_preconfigured` property.\n\n<img width=\"1073\" alt=\"Screenshot 2025-04-10 at 14 16 15\"\nsrc=\"https://github.com/user-attachments/assets/e330cd5f-c9f0-43da-b4b4-f2a0a2fd10a5\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b4d3a2a8f2b135436ea510c52aa82e4a77d6fca8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217847","number":217847,"mergeCommit":{"message":"[Security Solution] Remove hardcoded ids of preconfigured connectors from Security Solution Cypress tests (#217847)\n\n## Summary\n\n[Preconfigured\nconnectors](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html)\nare those that are specified via the `kibana.yml` config, and thus they\ncan't be deleted. In tests, we've hardcoded their ids to skip deleting\nthem when we need to clean up the tests' state.\n\nSometimes, the id of a preconfigured connector gets changed by somebody,\nwhich breaks tests of multiple teams in MKI pipelines, such as the\nperiodic pipeline or the release quality gates. The problem is that it\ndoesn't happen on CI where Kibana doesn't have any preconfigured\nconnectors, so this feedback loop is too long. When tests in an MKI\npipeline break, it's not immediately clear what happened and who should\nfix it. Eventually it gets fixed by someone [like\nthis](https://github.com/elastic/kibana/pull/217570/files).\n\nInstead of hardcoding the ids, we should dynamically determine if a\nconnector is preconfigured and if it should be deleted by a test or not.\nThis is possible to do as each connector has the corresponding\n`is_preconfigured` property.\n\n<img width=\"1073\" alt=\"Screenshot 2025-04-10 at 14 16 15\"\nsrc=\"https://github.com/user-attachments/assets/e330cd5f-c9f0-43da-b4b4-f2a0a2fd10a5\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b4d3a2a8f2b135436ea510c52aa82e4a77d6fca8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> |
||
Sergi Romeu
|
dd276315fb
|
[8.18] [APM][Cypress] Attempt to fix mobile transactions test (#217648) (#217954)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM][Cypress] Attempt to fix mobile transactions test (#217648)](https://github.com/elastic/kibana/pull/217648) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-11T08:28:49Z","message":"[APM][Cypress] Attempt to fix mobile transactions test (#217648)\n\n## Summary\n\nCloses #207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","apm:mobile","backport:all-open","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][Cypress] Attempt to fix mobile transactions test","number":217648,"url":"https://github.com/elastic/kibana/pull/217648","mergeCommit":{"message":"[APM][Cypress] Attempt to fix mobile transactions test (#217648)\n\n## Summary\n\nCloses #207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217648","number":217648,"mergeCommit":{"message":"[APM][Cypress] Attempt to fix mobile transactions test (#217648)\n\n## Summary\n\nCloses #207040","sha":"429a9db67d361b25f191a67c16775354a0c2d631"}}]}] BACKPORT--> |
||
Georgii Gorbachev
|
6bedafe4c0
|
[8.18] [Security Solution] Improving documentations for bulk_actions (#216852) (#217824)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Improving documentations for bulk_actions (#216852)](https://github.com/elastic/kibana/pull/216852) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-09T16:03:19Z","message":"[Security Solution] Improving documentations for bulk_actions (#216852)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn this PR I am improving documentation for the bulk_actions endpoint.\nThe focus is on improving descriptions of parameters and providing\nexamples for all important situations, especially setting / adding\nactions.\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","APIDocs","Team:Detection Rule Management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Improving documentations for bulk_actions","number":216852,"url":"https://github.com/elastic/kibana/pull/216852","mergeCommit":{"message":"[Security Solution] Improving documentations for bulk_actions (#216852)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn this PR I am improving documentation for the bulk_actions endpoint.\nThe focus is on improving descriptions of parameters and providing\nexamples for all important situations, especially setting / adding\nactions.\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217717","number":217717,"state":"MERGED","mergeCommit":{"sha":"91cdba78ba8586974f5cb317fb33e8c0cbf32e60","message":"[9.0] [Security Solution] Improving documentations for bulk_actions (#216852) (#217717)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Security Solution] Improving documentations for bulk_actions\n(#216852)](https://github.com/elastic/kibana/pull/216852)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216852","number":216852,"mergeCommit":{"message":"[Security Solution] Improving documentations for bulk_actions (#216852)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3019**\n\n## Summary\nIn this PR I am improving documentation for the bulk_actions endpoint.\nThe focus is on improving descriptions of parameters and providing\nexamples for all important situations, especially setting / adding\nactions.\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9d659b76dd31364ef5a4d4b5292f5988de1dca77"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217716","number":217716,"state":"MERGED","mergeCommit":{"sha":"3fa939ea4d4b7e3ec59009782c638ccb3dda95ac","message":"[8.x] [Security Solution] Improving documentations for bulk_actions (#216852) (#217716)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Improving documentations for bulk_actions\n(#216852)](https://github.com/elastic/kibana/pull/216852)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
c86177c561 | skip failing test suite (#144057) | ||
|
Kibana Machine
|
fd1ad53887 | skip failing test suite (#191707) | ||
Kevin Delemme
|
bc9f967272
|
[8.18] fix(slo): search bar filters (#217702) (#217869) | ||
|
Kibana Machine
|
9001dd9290
|
[8.18] [Obs AI Assistant] Fix navigating to the search connectors page (#217749) (#217861)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Fix navigating to the search connectors page (#217749)](https://github.com/elastic/kibana/pull/217749) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T14:27:54Z","message":"[Obs AI Assistant] Fix navigating to the search connectors page (#217749)\n\nCloses https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n### Problem\n\nClicking on connectors in the Search connectors tab in the AI Assistant\nsettings navigates the user to a blank page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis happens because `enterprise_search` URLs are deprecated and it's\nrenamed to `elasticsearch`.\nRelated to https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs -\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n### Solution\n\nReplace the URL path from `enterpriseSearch` to `elasticsearch`\n\nAfter the fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1"],"title":"[Obs AI Assistant] Fix navigating to the search connectors page","number":217749,"url":"https://github.com/elastic/kibana/pull/217749","mergeCommit":{"message":"[Obs AI Assistant] Fix navigating to the search connectors page (#217749)\n\nCloses https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n### Problem\n\nClicking on connectors in the Search connectors tab in the AI Assistant\nsettings navigates the user to a blank page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis happens because `enterprise_search` URLs are deprecated and it's\nrenamed to `elasticsearch`.\nRelated to https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs -\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n### Solution\n\nReplace the URL path from `enterpriseSearch` to `elasticsearch`\n\nAfter the fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217749","number":217749,"mergeCommit":{"message":"[Obs AI Assistant] Fix navigating to the search connectors page (#217749)\n\nCloses https://github.com/elastic/kibana/issues/217748\n\n## Summary\n\n### Problem\n\nClicking on connectors in the Search connectors tab in the AI Assistant\nsettings navigates the user to a blank page.\n\n\nhttps://github.com/user-attachments/assets/e369e539-cf75-4ea4-8cd0-343dbfbf9a33\n\nThis happens because `enterprise_search` URLs are deprecated and it's\nrenamed to `elasticsearch`.\nRelated to https://github.com/elastic/kibana/pull/202838\n\nList of changed URLs -\nhttps://github.com/elastic/search-team/issues/7961#issuecomment-2433029797\n\n### Solution\n\nReplace the URL path from `enterpriseSearch` to `elasticsearch`\n\nAfter the fix:\n\n\nhttps://github.com/user-attachments/assets/5ebad872-9a87-46b0-ad2f-83a8ff6e017e\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"368d4bf5c53e7b4c64ac1e768eec72c82a004ed1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
Carlos Crespo
|
cf9e5ce9b7
|
[8.18] [APM] Treat "links" field as array (#215906) (#217662)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM] Treat "links" field as array (#215906)](https://github.com/elastic/kibana/pull/215906) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T07:10:15Z","message":"[APM] Treat \"links\" field as array (#215906)\n\nFixes [#215706](https://github.com/elastic/kibana/issues/215706)\n\n## Summary\n\nThis fixes the problem where Otel span links were not considered a\ncollection of links.\n\n\n<img width=\"1721\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n### How to test\n\nRun: `node scripts/synthtrace span_links.ts --live --uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel` and wait a few\nminutes\n\nNavigate to Services Inventory -> product consumer -> Transactions and\ninspect the span links from `Span B`\n\nRun the query below to confirm that there are `links` with a collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n \"exists\": {\n \"field\": \"links*\"\n }\n }\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Treat \"links\" field as array","number":215906,"url":"https://github.com/elastic/kibana/pull/215906","mergeCommit":{"message":"[APM] Treat \"links\" field as array (#215906)\n\nFixes [#215706](https://github.com/elastic/kibana/issues/215706)\n\n## Summary\n\nThis fixes the problem where Otel span links were not considered a\ncollection of links.\n\n\n<img width=\"1721\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n### How to test\n\nRun: `node scripts/synthtrace span_links.ts --live --uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel` and wait a few\nminutes\n\nNavigate to Services Inventory -> product consumer -> Transactions and\ninspect the span links from `Span B`\n\nRun the query below to confirm that there are `links` with a collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n \"exists\": {\n \"field\": \"links*\"\n }\n }\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215906","number":215906,"mergeCommit":{"message":"[APM] Treat \"links\" field as array (#215906)\n\nFixes [#215706](https://github.com/elastic/kibana/issues/215706)\n\n## Summary\n\nThis fixes the problem where Otel span links were not considered a\ncollection of links.\n\n\n<img width=\"1721\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bce354d5-8473-41db-856e-3bbb66b88c18\"\n/>\n\n\n### How to test\n\nRun: `node scripts/synthtrace span_links.ts --live --uniqueIds --clean\n--logLevel=debug --scenarioOpts pipeline=apmToOtel` and wait a few\nminutes\n\nNavigate to Services Inventory -> product consumer -> Transactions and\ninspect the span links from `Span B`\n\nRun the query below to confirm that there are `links` with a collection\nof items\n```\nGET traces-*otel*/_search\n{\n \"query\": {\n \"exists\": {\n \"field\": \"links*\"\n }\n }\n}\n```","sha":"704a3d4a9e319e96743b9763bd24809763f969e7"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
70ed457075
|
[8.18] [A11y][APM] Improve aria-label for correlations (#217512) (#217808)
# Backport This will backport the following commits from `main` to `8.18`: - [[A11y][APM] Improve `aria-label` for correlations (#217512)](https://github.com/elastic/kibana/pull/217512) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T09:52:11Z","message":"[A11y][APM] Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the `aria-label` attributes in the latency correlations\npage to add more context about the selected field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"[A11y][APM] Improve `aria-label` for correlations","number":217512,"url":"https://github.com/elastic/kibana/pull/217512","mergeCommit":{"message":"[A11y][APM] Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the `aria-label` attributes in the latency correlations\npage to add more context about the selected field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217512","number":217512,"mergeCommit":{"message":"[A11y][APM] Improve `aria-label` for correlations (#217512)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194975\n\nThis PR improves the `aria-label` attributes in the latency correlations\npage to add more context about the selected field.","sha":"6190ca8c140a4faba7a75b70a33e79736dd937fe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
Miriam
|
3bdc2d40c3
|
[8.18] [ObsUx][A11y] Add unique accessible lables to metadata table (#217496) (#217813)
# Backport This will backport the following commits from `main` to `8.18`: - [[ObsUx][A11y] Add unique accessible lables to metadata table (#217496)](https://github.com/elastic/kibana/pull/217496) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T07:41:30Z","message":"[ObsUx][A11y] Add unique accessible lables to metadata table (#217496)\n\nCloses https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd unique accessible labels to metadata table\n\n### How to test\n\nUse a screen reader to navigate the table\n\nOn Host details, Metadata tab\n\n1. Verify the first column in the table header announces Pin Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2. Verify the Pin column row announces which field pins\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3. Verify the \"+ x more\" does announce more of which field\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUx][A11y] Add unique accessible lables to metadata table","number":217496,"url":"https://github.com/elastic/kibana/pull/217496","mergeCommit":{"message":"[ObsUx][A11y] Add unique accessible lables to metadata table (#217496)\n\nCloses https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd unique accessible labels to metadata table\n\n### How to test\n\nUse a screen reader to navigate the table\n\nOn Host details, Metadata tab\n\n1. Verify the first column in the table header announces Pin Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2. Verify the Pin column row announces which field pins\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3. Verify the \"+ x more\" does announce more of which field\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217621","number":217621,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217496","number":217496,"mergeCommit":{"message":"[ObsUx][A11y] Add unique accessible lables to metadata table (#217496)\n\nCloses https://github.com/elastic/kibana/issues/194972\n\n## Summary\n\nAdd unique accessible labels to metadata table\n\n### How to test\n\nUse a screen reader to navigate the table\n\nOn Host details, Metadata tab\n\n1. Verify the first column in the table header announces Pin Fields\ncolumn\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 28\"\nsrc=\"https://github.com/user-attachments/assets/bdac5799-97d4-4001-b5f0-f9230227b749\"\n/>\n\n2. Verify the Pin column row announces which field pins\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 38 45\"\nsrc=\"https://github.com/user-attachments/assets/a9a18fc4-4f46-49d7-880e-9b77eca476dd\"\n/>\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 14\"\nsrc=\"https://github.com/user-attachments/assets/889ca03f-aa00-4360-87b5-6d767fe11cff\"\n/>\n\n3. Verify the \"+ x more\" does announce more of which field\n\n<img width=\"1262\" alt=\"Screenshot 2025-04-08 at 12 39 35\"\nsrc=\"https://github.com/user-attachments/assets/dfba3fd9-7e71-4ef6-956e-3761094f4667\"\n/>","sha":"92a9f8531afa6bb93719db65f4637607c9435beb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217657","number":217657,"state":"MERGED","mergeCommit":{"sha":"3b5e43ab47a19264d60771b161202ac677060a3b","message":"[8.x] [ObsUx][A11y] Add unique accessible lables to metadata table (#217496) (#217657)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ObsUx][A11y] Add unique accessible lables to metadata table\n(#217496)](https://github.com/elastic/kibana/pull/217496)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
9759b0f781
|
[8.18] [ResponseOps][Cases]Fix table layout in the add to existing case modal (#217653) (#217803)
# Backport This will backport the following commits from `main` to `8.18`: - [[ResponseOps][Cases]Fix table layout in the add to existing case modal (#217653)](https://github.com/elastic/kibana/pull/217653) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T09:32:28Z","message":"[ResponseOps][Cases]Fix table layout in the add to existing case modal (#217653)\n\nCloses https://github.com/elastic/kibana/issues/216582\n## Summary\n\n- increased column width to fit the `select` button\n\n\nhttps://github.com/user-attachments/assets/64199991-c765-40e4-8d17-38cb6dfd16f6","sha":"47726988dc24d750082e404db09c76a9368dab04","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ResponseOps][Cases]Fix table layout in the add to existing case modal","number":217653,"url":"https://github.com/elastic/kibana/pull/217653","mergeCommit":{"message":"[ResponseOps][Cases]Fix table layout in the add to existing case modal (#217653)\n\nCloses https://github.com/elastic/kibana/issues/216582\n## Summary\n\n- increased column width to fit the `select` button\n\n\nhttps://github.com/user-attachments/assets/64199991-c765-40e4-8d17-38cb6dfd16f6","sha":"47726988dc24d750082e404db09c76a9368dab04"}},"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/217653","number":217653,"mergeCommit":{"message":"[ResponseOps][Cases]Fix table layout in the add to existing case modal (#217653)\n\nCloses https://github.com/elastic/kibana/issues/216582\n## Summary\n\n- increased column width to fit the `select` button\n\n\nhttps://github.com/user-attachments/assets/64199991-c765-40e4-8d17-38cb6dfd16f6","sha":"47726988dc24d750082e404db09c76a9368dab04"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co> |