mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
12299 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Vitalii Dmyterko
|
7faf92952e | backport | ||
Kibana Machine
|
1cdfcb789c
|
[8.x] [Stack Monitoring] New FTR for "view logs" link (#208351) (#214297)
# Backport This will backport the following commits from `main` to `8.x`: - [[Stack Monitoring] New FTR for "view logs" link (#208351)](https://github.com/elastic/kibana/pull/208351) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T22:35:28Z","message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","FTR","v8.18.0","v8.17.2","v9.1.0"],"title":"[Stack Monitoring] New FTR for \"view logs\" link","number":208351,"url":"https://github.com/elastic/kibana/pull/208351","mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208351","number":208351,"mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co> |
||
|
Kibana Machine
|
98bec018ad
|
[8.x] [Security Solution] Force upgrading to target version for "Reference URLs" when base version is missing (#214161) (#214254)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Force upgrading to target version for "Reference URLs" when base version is missing (#214161)](https://github.com/elastic/kibana/pull/214161) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:41:32Z","message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing","number":214161,"url":"https://github.com/elastic/kibana/pull/214161","mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214161","number":214161,"mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
3a6fc9dc32 | skip failing test suite (#213821) | ||
|
Kibana Machine
|
e2800dd7aa
|
[8.x] [Logs UI] Make logs ui categories page tests more robust (#213834) (#214222)
# Backport This will backport the following commits from `main` to `8.x`: - [[Logs UI] Make logs ui categories page tests more robust (#213834)](https://github.com/elastic/kibana/pull/213834) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T16:08:11Z","message":"[Logs UI] Make logs ui categories page tests more robust (#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Logs UI","release_note:skip","backport:all-open","Team:obs-ux-logs","v9.1.0"],"title":"[Logs UI] Make logs ui categories page tests more robust","number":213834,"url":"https://github.com/elastic/kibana/pull/213834","mergeCommit":{"message":"[Logs UI] Make logs ui categories page tests more robust (#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213834","number":213834,"mergeCommit":{"message":"[Logs UI] Make logs ui categories page tests more robust (#213834)","sha":"3338092efcc707ef7fa80c0ef34d1b23d257193e"}}]}] BACKPORT--> Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com> |
||
|
Kibana Machine
|
961f1e015c
|
[8.x] unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts (#213977) (#214163)
# Backport This will backport the following commits from `main` to `8.x`: - [unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts (#213977)](https://github.com/elastic/kibana/pull/213977) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T13:37:56Z","message":"unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts (#213977)\n\ncloses https://github.com/elastic/kibana/issues/160583\n\nflaky test runner with 25 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8018\nflaky test runner with 100 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8019\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dce80083c20a90030c8c2a3e060c12d7fb90a712","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts","number":213977,"url":"https://github.com/elastic/kibana/pull/213977","mergeCommit":{"message":"unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts (#213977)\n\ncloses https://github.com/elastic/kibana/issues/160583\n\nflaky test runner with 25 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8018\nflaky test runner with 100 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8019\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dce80083c20a90030c8c2a3e060c12d7fb90a712"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213977","number":213977,"mergeCommit":{"message":"unskip Failing test: X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/dashboard_integration·ts (#213977)\n\ncloses https://github.com/elastic/kibana/issues/160583\n\nflaky test runner with 25 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8018\nflaky test runner with 100 runs\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8019\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dce80083c20a90030c8c2a3e060c12d7fb90a712"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
Joe Reuter
|
9526682fe1
|
[8.x] 🌊 Streams: Fix unnecessary rollovers (#213594) (#214093)
# Backport This will backport the following commits from `main` to `8.x`: - 🌊 Streams: Fix unnecessary rollovers (#213594)](https://github.com/elastic/kibana/pull/213594) |
||
David Sánchez
|
aef110ddaf
|
[8.x] [Security Solution] [Defend Workflows] Enables skipped tests in 9.0 (#213399) (#214130)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] [Defend Workflows] Enables skipped tests in 9.0 (#213399)](https://github.com/elastic/kibana/pull/213399) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T10:43:40Z","message":"[Security Solution] [Defend Workflows] Enables skipped tests in 9.0 (#213399)\n\n## Summary\n\nEnables skipped tests in 9.0 and previous stack versions.\n\ncloses: https://github.com/elastic/kibana/issues/180401\ncloses: https://github.com/elastic/kibana/issues/203894\ncloses: https://github.com/elastic/kibana/issues/205141\ncloses: https://github.com/elastic/kibana/issues/206204\ncloses: https://github.com/elastic/kibana/issues/209056\ncloses: https://github.com/elastic/kibana/issues/209064\ncloses: https://github.com/elastic/kibana/issues/209063\ncloses: https://github.com/elastic/kibana/issues/209066\ncloses: https://github.com/elastic/kibana/issues/209065\n\nThis one will be tracked in a follow up pr:\nhttps://github.com/elastic/kibana/issues/203916\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"87e2edd5992399a1d239a01839f23b2e9f8dc63a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] [Defend Workflows] Enables skipped tests in 9.0","number":213399,"url":"https://github.com/elastic/kibana/pull/213399","mergeCommit":{"message":"[Security Solution] [Defend Workflows] Enables skipped tests in 9.0 (#213399)\n\n## Summary\n\nEnables skipped tests in 9.0 and previous stack versions.\n\ncloses: https://github.com/elastic/kibana/issues/180401\ncloses: https://github.com/elastic/kibana/issues/203894\ncloses: https://github.com/elastic/kibana/issues/205141\ncloses: https://github.com/elastic/kibana/issues/206204\ncloses: https://github.com/elastic/kibana/issues/209056\ncloses: https://github.com/elastic/kibana/issues/209064\ncloses: https://github.com/elastic/kibana/issues/209063\ncloses: https://github.com/elastic/kibana/issues/209066\ncloses: https://github.com/elastic/kibana/issues/209065\n\nThis one will be tracked in a follow up pr:\nhttps://github.com/elastic/kibana/issues/203916\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"87e2edd5992399a1d239a01839f23b2e9f8dc63a"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214129","number":214129,"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/213399","number":213399,"mergeCommit":{"message":"[Security Solution] [Defend Workflows] Enables skipped tests in 9.0 (#213399)\n\n## Summary\n\nEnables skipped tests in 9.0 and previous stack versions.\n\ncloses: https://github.com/elastic/kibana/issues/180401\ncloses: https://github.com/elastic/kibana/issues/203894\ncloses: https://github.com/elastic/kibana/issues/205141\ncloses: https://github.com/elastic/kibana/issues/206204\ncloses: https://github.com/elastic/kibana/issues/209056\ncloses: https://github.com/elastic/kibana/issues/209064\ncloses: https://github.com/elastic/kibana/issues/209063\ncloses: https://github.com/elastic/kibana/issues/209066\ncloses: https://github.com/elastic/kibana/issues/209065\n\nThis one will be tracked in a follow up pr:\nhttps://github.com/elastic/kibana/issues/203916\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"87e2edd5992399a1d239a01839f23b2e9f8dc63a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ef39ce84d7
|
[8.x] [Obs AI Assistant] Ensure semantic query contribute to score (#213870) (#214083)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Ensure semantic query contribute to score (#213870)](https://github.com/elastic/kibana/pull/213870) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T09:35:39Z","message":"[Obs AI Assistant] Ensure semantic query contribute to score (#213870)\n\nCloses https://github.com/elastic/kibana/issues/213869\n\nRegression introduced in 8.17\n(https://github.com/elastic/kibana/pull/200184/)\n\n#### **Fix** \nSemantic queries were incorrectly wrapped in a `filter` context,\npreventing them from contributing to scoring. This PR removes the\n`filter` wrapper so that semantic queries run in query context and\ninfluence ranking.\n\nThis also replaces the `semantic` query with a `match` query. This is\nnecessary because `fieldCaps` api no longer returns `semantic_text` when\nfiltering with `GET\nanimals_kb/_field_caps?fields=*&types=semantic_text`. Instead we need to\nretrieve text fields and perform the search against all of them.","sha":"5c5b6ebc8a3356e1e8a665b7b89deb4134103343","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","v9.1.0"],"title":"[Obs AI Assistant] Ensure semantic query contribute to score","number":213870,"url":"https://github.com/elastic/kibana/pull/213870","mergeCommit":{"message":"[Obs AI Assistant] Ensure semantic query contribute to score (#213870)\n\nCloses https://github.com/elastic/kibana/issues/213869\n\nRegression introduced in 8.17\n(https://github.com/elastic/kibana/pull/200184/)\n\n#### **Fix** \nSemantic queries were incorrectly wrapped in a `filter` context,\npreventing them from contributing to scoring. This PR removes the\n`filter` wrapper so that semantic queries run in query context and\ninfluence ranking.\n\nThis also replaces the `semantic` query with a `match` query. This is\nnecessary because `fieldCaps` api no longer returns `semantic_text` when\nfiltering with `GET\nanimals_kb/_field_caps?fields=*&types=semantic_text`. Instead we need to\nretrieve text fields and perform the search against all of them.","sha":"5c5b6ebc8a3356e1e8a665b7b89deb4134103343"}},"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/213870","number":213870,"mergeCommit":{"message":"[Obs AI Assistant] Ensure semantic query contribute to score (#213870)\n\nCloses https://github.com/elastic/kibana/issues/213869\n\nRegression introduced in 8.17\n(https://github.com/elastic/kibana/pull/200184/)\n\n#### **Fix** \nSemantic queries were incorrectly wrapped in a `filter` context,\npreventing them from contributing to scoring. This PR removes the\n`filter` wrapper so that semantic queries run in query context and\ninfluence ranking.\n\nThis also replaces the `semantic` query with a `match` query. This is\nnecessary because `fieldCaps` api no longer returns `semantic_text` when\nfiltering with `GET\nanimals_kb/_field_caps?fields=*&types=semantic_text`. Instead we need to\nretrieve text fields and perform the search against all of them.","sha":"5c5b6ebc8a3356e1e8a665b7b89deb4134103343"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
|
Kibana Machine
|
e51bb2215e
|
[8.x] [Security Solution] Enable prebuilt rules customization feature flag (#212761) (#214024)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Enable prebuilt rules customization feature flag (#212761)](https://github.com/elastic/kibana/pull/212761) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T21:45:49Z","message":"[Security Solution] Enable prebuilt rules customization feature flag (#212761)\n\n**Addresses:** https://github.com/elastic/kibana/issues/180267\n\n## Summary\n\nThis PR enables `prebuiltRulesCustomizationEnabled` feature flag.\n\n## Details\n\nBesides simply enabling `prebuiltRulesCustomizationEnabled` feature flag the following required changes were done\n\n- failed tests due enabling the FF were fixed\n- FF setting was removed from test configurations (integrations and Cypress tests)\n- FF logic was removed from the codebase. Disabling the FF would require roll back test changes as well. So just in case we have to disable the FF it's simpler to roll back the PR's commit.","sha":"f7d4f19096e0711021b8587fb4d0575998d18f3e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Enable prebuilt rules customization feature flag","number":212761,"url":"https://github.com/elastic/kibana/pull/212761","mergeCommit":{"message":"[Security Solution] Enable prebuilt rules customization feature flag (#212761)\n\n**Addresses:** https://github.com/elastic/kibana/issues/180267\n\n## Summary\n\nThis PR enables `prebuiltRulesCustomizationEnabled` feature flag.\n\n## Details\n\nBesides simply enabling `prebuiltRulesCustomizationEnabled` feature flag the following required changes were done\n\n- failed tests due enabling the FF were fixed\n- FF setting was removed from test configurations (integrations and Cypress tests)\n- FF logic was removed from the codebase. Disabling the FF would require roll back test changes as well. So just in case we have to disable the FF it's simpler to roll back the PR's commit.","sha":"f7d4f19096e0711021b8587fb4d0575998d18f3e"}},"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/212761","number":212761,"mergeCommit":{"message":"[Security Solution] Enable prebuilt rules customization feature flag (#212761)\n\n**Addresses:** https://github.com/elastic/kibana/issues/180267\n\n## Summary\n\nThis PR enables `prebuiltRulesCustomizationEnabled` feature flag.\n\n## Details\n\nBesides simply enabling `prebuiltRulesCustomizationEnabled` feature flag the following required changes were done\n\n- failed tests due enabling the FF were fixed\n- FF setting was removed from test configurations (integrations and Cypress tests)\n- FF logic was removed from the codebase. Disabling the FF would require roll back test changes as well. So just in case we have to disable the FF it's simpler to roll back the PR's commit.","sha":"f7d4f19096e0711021b8587fb4d0575998d18f3e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
ce08437e98
|
[8.x] [Obs AI Assistant] Add API test for execute_query tool (#213517) (#214021)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Add API test for `execute_query` tool (#213517)](https://github.com/elastic/kibana/pull/213517) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T21:45:28Z","message":"[Obs AI Assistant] Add API test for `execute_query` tool (#213517)\n\n- Adds test for `execute_query` function\n- Add `drop_null_columns` to esql query in order to avoid column\nexplosion\n\nDepends on: https://github.com/elastic/kibana/pull/213231\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"3ed6e4583e254dec62e79bfda95f369470e66de4","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 AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Add API test for `execute_query` tool","number":213517,"url":"https://github.com/elastic/kibana/pull/213517","mergeCommit":{"message":"[Obs AI Assistant] Add API test for `execute_query` tool (#213517)\n\n- Adds test for `execute_query` function\n- Add `drop_null_columns` to esql query in order to avoid column\nexplosion\n\nDepends on: https://github.com/elastic/kibana/pull/213231\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"3ed6e4583e254dec62e79bfda95f369470e66de4"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213517","number":213517,"mergeCommit":{"message":"[Obs AI Assistant] Add API test for `execute_query` tool (#213517)\n\n- Adds test for `execute_query` function\n- Add `drop_null_columns` to esql query in order to avoid column\nexplosion\n\nDepends on: https://github.com/elastic/kibana/pull/213231\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"3ed6e4583e254dec62e79bfda95f369470e66de4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Maxim Palenov
|
a042f34624
|
[8.x] [Security Solution] Disallow merging critical rule field values upon rule upgrade when base version is missing (#213757) (#214000)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Disallow merging critical rule field values upon rule upgrade when base version is missing #213757](https://github.com/elastic/kibana/pull/213757) |
||
|
Kibana Machine
|
7c36cedfe6
|
[8.x] [Obs AI Assistant] Make KB retrieval namespace specific (#213505) (#213985)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Make KB retrieval namespace specific (#213505)](https://github.com/elastic/kibana/pull/213505) <!--- 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-03-11T17:44:28Z","message":"[Obs AI Assistant] Make KB retrieval namespace specific (#213505)\n\nCloses https://github.com/elastic/kibana/issues/213504\n\n## Summary\n\n### Problem\n\nKB retrievals are not space specific at present. Therefore, users are\nable to view entries across spaces.\n\n### Solution\n\nFilter by `namespace` when retrieving KB entries.\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- [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":"9b1455c7f7beeddd70d2ecefaa58bd6f5ff8cb0e","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","ci:project-deploy-observability","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[Obs AI Assistant] Make KB retrieval namespace specific ","number":213505,"url":"https://github.com/elastic/kibana/pull/213505","mergeCommit":{"message":"[Obs AI Assistant] Make KB retrieval namespace specific (#213505)\n\nCloses https://github.com/elastic/kibana/issues/213504\n\n## Summary\n\n### Problem\n\nKB retrievals are not space specific at present. Therefore, users are\nable to view entries across spaces.\n\n### Solution\n\nFilter by `namespace` when retrieving KB entries.\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- [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":"9b1455c7f7beeddd70d2ecefaa58bd6f5ff8cb0e"}},"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/213505","number":213505,"mergeCommit":{"message":"[Obs AI Assistant] Make KB retrieval namespace specific (#213505)\n\nCloses https://github.com/elastic/kibana/issues/213504\n\n## Summary\n\n### Problem\n\nKB retrievals are not space specific at present. Therefore, users are\nable to view entries across spaces.\n\n### Solution\n\nFilter by `namespace` when retrieving KB entries.\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- [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":"9b1455c7f7beeddd70d2ecefaa58bd6f5ff8cb0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
Viduni Wickramarachchi
|
7b2a3c0977
|
[8.x] [Obs AI Assistant] Share conversations (#211854) (#213954)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Share conversations (#211854)](https://github.com/elastic/kibana/pull/211854) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) |
||
Matthew Kime
|
290e96cd7c
|
[8.x] [data views] data views + rollup index referenced by alias (#212592) (#213856)
# Backport This will backport the following commits from `main` to `8.x`: - [[data views] data views + rollup index referenced by alias (#212592)](https://github.com/elastic/kibana/pull/212592) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-03-11T01:16:04Z","message":"[data views] data views + rollup index referenced by alias (#212592)\n\n## Summary\n\nUpgrading to 9.x involves reindexing indices created in 7.x, which does\ninclude rollup indices. Reindexing means relying on aliases to preserve\nexisting index names. As it turns out, our existing code did not work\nwith rollups that referenced aliases, rather than indices. This is\nbecause the index name is used as an object key even if it was retrieved\nvia alias.\n\n\nNote - I need to verify this on 9.0 from scratch. I used upgraded data\nand need to verify the steps to make this work when testing.\n\nTo test\n1. Add sample data\n2. Create a rollup job that references the sample data. \n3. Create a data view that references the rollup index. It may take a\nfew minutes for the rollup index to be populated.\n4. Create an alias from the dev console, like such - \n\n```\nPOST _aliases\n{\n \"actions\": [\n {\n \"add\": {\n \"index\": \"rollup\",\n \"alias\": \"my-alias\"\n }\n }\n ]\n}\n``` \n5. Create a rollup data view based in the alias you just created.\n\nPart of https://github.com/elastic/kibana/issues/211850\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b6dbf2b2711c94cb32a39e6487f95abd128433c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","Team:Kibana Management","Feature:Rollups","backport:prev-minor","v9.1.0"],"title":"[data views] data views + rollup index referenced by alias","number":212592,"url":"https://github.com/elastic/kibana/pull/212592","mergeCommit":{"message":"[data views] data views + rollup index referenced by alias (#212592)\n\n## Summary\n\nUpgrading to 9.x involves reindexing indices created in 7.x, which does\ninclude rollup indices. Reindexing means relying on aliases to preserve\nexisting index names. As it turns out, our existing code did not work\nwith rollups that referenced aliases, rather than indices. This is\nbecause the index name is used as an object key even if it was retrieved\nvia alias.\n\n\nNote - I need to verify this on 9.0 from scratch. I used upgraded data\nand need to verify the steps to make this work when testing.\n\nTo test\n1. Add sample data\n2. Create a rollup job that references the sample data. \n3. Create a data view that references the rollup index. It may take a\nfew minutes for the rollup index to be populated.\n4. Create an alias from the dev console, like such - \n\n```\nPOST _aliases\n{\n \"actions\": [\n {\n \"add\": {\n \"index\": \"rollup\",\n \"alias\": \"my-alias\"\n }\n }\n ]\n}\n``` \n5. Create a rollup data view based in the alias you just created.\n\nPart of https://github.com/elastic/kibana/issues/211850\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b6dbf2b2711c94cb32a39e6487f95abd128433c"}},"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/212592","number":212592,"mergeCommit":{"message":"[data views] data views + rollup index referenced by alias (#212592)\n\n## Summary\n\nUpgrading to 9.x involves reindexing indices created in 7.x, which does\ninclude rollup indices. Reindexing means relying on aliases to preserve\nexisting index names. As it turns out, our existing code did not work\nwith rollups that referenced aliases, rather than indices. This is\nbecause the index name is used as an object key even if it was retrieved\nvia alias.\n\n\nNote - I need to verify this on 9.0 from scratch. I used upgraded data\nand need to verify the steps to make this work when testing.\n\nTo test\n1. Add sample data\n2. Create a rollup job that references the sample data. \n3. Create a data view that references the rollup index. It may take a\nfew minutes for the rollup index to be populated.\n4. Create an alias from the dev console, like such - \n\n```\nPOST _aliases\n{\n \"actions\": [\n {\n \"add\": {\n \"index\": \"rollup\",\n \"alias\": \"my-alias\"\n }\n }\n ]\n}\n``` \n5. Create a rollup data view based in the alias you just created.\n\nPart of https://github.com/elastic/kibana/issues/211850\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b6dbf2b2711c94cb32a39e6487f95abd128433c"}},{"url":"https://github.com/elastic/kibana/pull/213852","number":213852,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
Alexi Doak
|
1ee1b84d55
|
[8.x] [ResponseOps][OnWeek] Investigate isolating flapping feature in the code (#212454) (#213825)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][OnWeek] Investigate isolating flapping feature in the code (#212454)](https://github.com/elastic/kibana/pull/212454) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T20:01:10Z","message":"[ResponseOps][OnWeek] Investigate isolating flapping feature in the code (#212454)\n\nPart of https://github.com/elastic/kibana/issues/194222\n\n## Summary\n\nThis PR moves the flapping and alert delay features into two new\nfunctions in the alerts client `determineFlappingAlerts` and\n`determineDelayedAlerts`. They will be called in the rule_type_runner\nafter `processAlerts`.\n- I removed `recoveredCurrent` and `activeCurrent` 😌 . This PR\nsimplifies them to be activeAlerts, recoveredAlerts,\ntrackedRecoveredAlerts, and trackedActiveAlerts. trackedRecoveredAlerts\nand trackedActiveAlerts are the alerts that will be stored in the task\nstate.\n- I also updated the logic so that the AAD docs and state match to help\nwith ongoing work to use AAD docs instead of the state.\n- I removed an optimization for the task state to stop tracking a\nrecovered alert if it wasn't flapping and doesn't have state changes. We\nwon't need this optimization with using AAD docs instead of the state.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"eed986162baf239db04fe117e1f045c28ad43c91","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][OnWeek] Investigate isolating flapping feature in the code","number":212454,"url":"https://github.com/elastic/kibana/pull/212454","mergeCommit":{"message":"[ResponseOps][OnWeek] Investigate isolating flapping feature in the code (#212454)\n\nPart of https://github.com/elastic/kibana/issues/194222\n\n## Summary\n\nThis PR moves the flapping and alert delay features into two new\nfunctions in the alerts client `determineFlappingAlerts` and\n`determineDelayedAlerts`. They will be called in the rule_type_runner\nafter `processAlerts`.\n- I removed `recoveredCurrent` and `activeCurrent` 😌 . This PR\nsimplifies them to be activeAlerts, recoveredAlerts,\ntrackedRecoveredAlerts, and trackedActiveAlerts. trackedRecoveredAlerts\nand trackedActiveAlerts are the alerts that will be stored in the task\nstate.\n- I also updated the logic so that the AAD docs and state match to help\nwith ongoing work to use AAD docs instead of the state.\n- I removed an optimization for the task state to stop tracking a\nrecovered alert if it wasn't flapping and doesn't have state changes. We\nwon't need this optimization with using AAD docs instead of the state.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"eed986162baf239db04fe117e1f045c28ad43c91"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212454","number":212454,"mergeCommit":{"message":"[ResponseOps][OnWeek] Investigate isolating flapping feature in the code (#212454)\n\nPart of https://github.com/elastic/kibana/issues/194222\n\n## Summary\n\nThis PR moves the flapping and alert delay features into two new\nfunctions in the alerts client `determineFlappingAlerts` and\n`determineDelayedAlerts`. They will be called in the rule_type_runner\nafter `processAlerts`.\n- I removed `recoveredCurrent` and `activeCurrent` 😌 . This PR\nsimplifies them to be activeAlerts, recoveredAlerts,\ntrackedRecoveredAlerts, and trackedActiveAlerts. trackedRecoveredAlerts\nand trackedActiveAlerts are the alerts that will be stored in the task\nstate.\n- I also updated the logic so that the AAD docs and state match to help\nwith ongoing work to use AAD docs instead of the state.\n- I removed an optimization for the task state to stop tracking a\nrecovered alert if it wasn't flapping and doesn't have state changes. We\nwon't need this optimization with using AAD docs instead of the state.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"eed986162baf239db04fe117e1f045c28ad43c91"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
88fdb56a9b
|
[8.x] [Obs AI Assistant] remove AdHocInstruction (#212621) (#213892)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] remove AdHocInstruction (#212621)](https://github.com/elastic/kibana/pull/212621) <!--- 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-03-11T10:24:16Z","message":"[Obs AI Assistant] remove AdHocInstruction (#212621)\n\n## Refactor Instruction Handling: Remove Adhoc Instructions and\nStandardize API\nCloses #211190\n\n## Summary \nThis PR removes the concept of *Adhoc Instructions* and standardizes how\ninstructions are handled across the system. The `/complete` API now\nexplicitly accepts **user instructions**, and redundant functions have\nbeen removed or replaced.\n\n## Changes Implemented \n\n### Renamed API Parameter \n- The `/complete` API’s `instructions` parameter is now\n`userInstructions`.\n- Application instructions can no longer be sent via the API (future\nsupport can be added if needed).\n\n### Removed Redundant Functions \n- Deleted `getAdhocInstructions` and `registerAdhocInstruction`. \n- API-passed instructions are now treated as **user instructions**. \n- Updated function calls to use `getInstructions` and\n`registerInstruction` instead.\n\n### Refactored Function Calls \n- Replaced `registerAdhocInstruction` with `registerInstruction`. \n\n## Impact & Benefits \n- **Simplifies** instruction handling by removing unnecessary\ncomplexity.\n- **Aligns** API behavior with internal instruction management.","sha":"56219f1c9016814a701a0f25ce1629307fa0177d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:Obs AI Assistant","v9.1.0","v8.19.0"],"title":"remove AdHocInstruction","number":212621,"url":"https://github.com/elastic/kibana/pull/212621","mergeCommit":{"message":"[Obs AI Assistant] remove AdHocInstruction (#212621)\n\n## Refactor Instruction Handling: Remove Adhoc Instructions and\nStandardize API\nCloses #211190\n\n## Summary \nThis PR removes the concept of *Adhoc Instructions* and standardizes how\ninstructions are handled across the system. The `/complete` API now\nexplicitly accepts **user instructions**, and redundant functions have\nbeen removed or replaced.\n\n## Changes Implemented \n\n### Renamed API Parameter \n- The `/complete` API’s `instructions` parameter is now\n`userInstructions`.\n- Application instructions can no longer be sent via the API (future\nsupport can be added if needed).\n\n### Removed Redundant Functions \n- Deleted `getAdhocInstructions` and `registerAdhocInstruction`. \n- API-passed instructions are now treated as **user instructions**. \n- Updated function calls to use `getInstructions` and\n`registerInstruction` instead.\n\n### Refactored Function Calls \n- Replaced `registerAdhocInstruction` with `registerInstruction`. \n\n## Impact & Benefits \n- **Simplifies** instruction handling by removing unnecessary\ncomplexity.\n- **Aligns** API behavior with internal instruction management.","sha":"56219f1c9016814a701a0f25ce1629307fa0177d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212621","number":212621,"mergeCommit":{"message":"[Obs AI Assistant] remove AdHocInstruction (#212621)\n\n## Refactor Instruction Handling: Remove Adhoc Instructions and\nStandardize API\nCloses #211190\n\n## Summary \nThis PR removes the concept of *Adhoc Instructions* and standardizes how\ninstructions are handled across the system. The `/complete` API now\nexplicitly accepts **user instructions**, and redundant functions have\nbeen removed or replaced.\n\n## Changes Implemented \n\n### Renamed API Parameter \n- The `/complete` API’s `instructions` parameter is now\n`userInstructions`.\n- Application instructions can no longer be sent via the API (future\nsupport can be added if needed).\n\n### Removed Redundant Functions \n- Deleted `getAdhocInstructions` and `registerAdhocInstruction`. \n- API-passed instructions are now treated as **user instructions**. \n- Updated function calls to use `getInstructions` and\n`registerInstruction` instead.\n\n### Refactored Function Calls \n- Replaced `registerAdhocInstruction` with `registerInstruction`. \n\n## Impact & Benefits \n- **Simplifies** instruction handling by removing unnecessary\ncomplexity.\n- **Aligns** API behavior with internal instruction management.","sha":"56219f1c9016814a701a0f25ce1629307fa0177d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
Cauê Marcondes
|
4f396232b4
|
[8.x] [APM] Breakdown Top dependencies API (#211441) (#213790)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Breakdown Top dependencies API (#211441)](https://github.com/elastic/kibana/pull/211441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T16:24:37Z","message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Breakdown Top dependencies API","number":211441,"url":"https://github.com/elastic/kibana/pull/211441","mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}},"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/211441","number":211441,"mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
8e0cf82d81
|
[8.x] Add pendingRecoveredCount field to AAD (#212162) (#213453)
# Backport This will backport the following commits from `main` to `8.x`: - [Add pendingRecoveredCount field to AAD (#212162)](https://github.com/elastic/kibana/pull/212162) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ersin Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T17:50:03Z","message":"Add pendingRecoveredCount field to AAD (#212162)\n\nThis PR adds pendingRecoveredCount field to AAD as a step to make ADD\nsource of truth.\nIn the next step we can build alerts in the alerting task runner from\nAAD rather than task state.","sha":"2bf0827fc6900daa619d1b0596033b21306e721e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"Add pendingRecoveredCount field to AAD","number":212162,"url":"https://github.com/elastic/kibana/pull/212162","mergeCommit":{"message":"Add pendingRecoveredCount field to AAD (#212162)\n\nThis PR adds pendingRecoveredCount field to AAD as a step to make ADD\nsource of truth.\nIn the next step we can build alerts in the alerting task runner from\nAAD rather than task state.","sha":"2bf0827fc6900daa619d1b0596033b21306e721e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212162","number":212162,"mergeCommit":{"message":"Add pendingRecoveredCount field to AAD (#212162)\n\nThis PR adds pendingRecoveredCount field to AAD as a step to make ADD\nsource of truth.\nIn the next step we can build alerts in the alerting task runner from\nAAD rather than task state.","sha":"2bf0827fc6900daa619d1b0596033b21306e721e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com> |
||
|
Kibana Machine
|
c040c0a3ec
|
[8.x] [ResponseOps][Rules] Add filter by rule type ids to get rule tags API (#213546) (#213815)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Rules] Add filter by rule type ids to get rule tags API (#213546)](https://github.com/elastic/kibana/pull/213546) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T18:29:39Z","message":"[ResponseOps][Rules] Add filter by rule type ids to get rule tags API (#213546)\n\n## Summary\n\n- Adds a filter by rule type ids to the `/internal/alerting/rules/_find`\nAPI endpoint, with the same logic as other similar endpoints.\n- Updates unit and API integration tests to cover the new filter.\n\n## To verify\n\n1. Create rules of different types with common and exclusive tags\n2. Use the `Stack Management > Dev Console` to call the endpoint with\ndifferent combinations of rule type ids:\n\n ```\nGET\nkbn:/internal/alerting/rules/_tags?rule_type_ids=[\".es-query\",\".index-threshold\",\n...]\n ```\n4. Verify that the returned tags correspond to the filtered rule types\n\n## Implementation details\n\nAdds the filter to the v1 schema for the get tags endpoint since it's an\nadditive change to an internal API.\n\n## References\n\nCloses #213057\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"f57ff0ad4a33930d8b7d804303cabace7cec40ac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Rules] Add filter by rule type ids to get rule tags API","number":213546,"url":"https://github.com/elastic/kibana/pull/213546","mergeCommit":{"message":"[ResponseOps][Rules] Add filter by rule type ids to get rule tags API (#213546)\n\n## Summary\n\n- Adds a filter by rule type ids to the `/internal/alerting/rules/_find`\nAPI endpoint, with the same logic as other similar endpoints.\n- Updates unit and API integration tests to cover the new filter.\n\n## To verify\n\n1. Create rules of different types with common and exclusive tags\n2. Use the `Stack Management > Dev Console` to call the endpoint with\ndifferent combinations of rule type ids:\n\n ```\nGET\nkbn:/internal/alerting/rules/_tags?rule_type_ids=[\".es-query\",\".index-threshold\",\n...]\n ```\n4. Verify that the returned tags correspond to the filtered rule types\n\n## Implementation details\n\nAdds the filter to the v1 schema for the get tags endpoint since it's an\nadditive change to an internal API.\n\n## References\n\nCloses #213057\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"f57ff0ad4a33930d8b7d804303cabace7cec40ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213546","number":213546,"mergeCommit":{"message":"[ResponseOps][Rules] Add filter by rule type ids to get rule tags API (#213546)\n\n## Summary\n\n- Adds a filter by rule type ids to the `/internal/alerting/rules/_find`\nAPI endpoint, with the same logic as other similar endpoints.\n- Updates unit and API integration tests to cover the new filter.\n\n## To verify\n\n1. Create rules of different types with common and exclusive tags\n2. Use the `Stack Management > Dev Console` to call the endpoint with\ndifferent combinations of rule type ids:\n\n ```\nGET\nkbn:/internal/alerting/rules/_tags?rule_type_ids=[\".es-query\",\".index-threshold\",\n...]\n ```\n4. Verify that the returned tags correspond to the filtered rule types\n\n## Implementation details\n\nAdds the filter to the v1 schema for the get tags endpoint since it's an\nadditive change to an internal API.\n\n## References\n\nCloses #213057\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"f57ff0ad4a33930d8b7d804303cabace7cec40ac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com> |
||
|
Kibana Machine
|
66a2c1aa56
|
[8.x] Attempt to fix custom_threshold_preview_chart flaky test (#212028) (#213778)
# Backport This will backport the following commits from `main` to `8.x`: - [Attempt to fix custom_threshold_preview_chart flaky test (#212028)](https://github.com/elastic/kibana/pull/212028) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T10:48:14Z","message":"Attempt to fix custom_threshold_preview_chart flaky test (#212028)\n\nFixes #209317\n\n## Summary\n\nSummary of\n[Slack](https://elastic.slack.com/archives/C04HT4P1YS3/p1740054800086779)\ndiscussion:\n\nAs shown below, we check if the `Create rule` button exists and then we\ntry to click it:\n```\nconst clickCreateRuleButton = async () => {\n await testSubjects.existOrFail('createRuleButton');\n const createRuleButton = await testSubjects.find('createRuleButton');\n return await createRuleButton.click();\n };\n```\n\nIt seems something goes wrong during click in this case and even after 2\nmins, we don't see the modal:\n```\n[00:03:11] │ debg --- retry.tryForTime error: [data-test-subj=\"ruleTypeModal\"] is not displayed\n...\n[00:05:09] └- ✖ fail: ObservabilityApp Custom threshold preview chart does render the empty chart only once at bootstrap\n```\n\n@dmlemeshko pointed to the implementation that we have for the button\nand the fact that we need to first check if the user is authorized to\nsee this button, and something might have caused the click not to be\nsuccessful even though there is no error reported by WebDriver.\n\n```\nuseEffect(() => {\n setHeaderActions?.([\n ...(authorizedToCreateAnyRules ? [<CreateRuleButton openFlyout={openRuleTypeModal} />] : []),\n <RulesSettingsLink />,\n <RulesListDocLink />,\n ]);\n }, [authorizedToCreateAnyRules]);\n```\n\nLong story short, we will add waiting for the global spinner to\nhopefully make this test less flaky 🤞🏻\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"2f0bad7d39319c315597be0e464b6d41fb4c25ef","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0"],"title":"Attempt to fix custom_threshold_preview_chart flaky test","number":212028,"url":"https://github.com/elastic/kibana/pull/212028","mergeCommit":{"message":"Attempt to fix custom_threshold_preview_chart flaky test (#212028)\n\nFixes #209317\n\n## Summary\n\nSummary of\n[Slack](https://elastic.slack.com/archives/C04HT4P1YS3/p1740054800086779)\ndiscussion:\n\nAs shown below, we check if the `Create rule` button exists and then we\ntry to click it:\n```\nconst clickCreateRuleButton = async () => {\n await testSubjects.existOrFail('createRuleButton');\n const createRuleButton = await testSubjects.find('createRuleButton');\n return await createRuleButton.click();\n };\n```\n\nIt seems something goes wrong during click in this case and even after 2\nmins, we don't see the modal:\n```\n[00:03:11] │ debg --- retry.tryForTime error: [data-test-subj=\"ruleTypeModal\"] is not displayed\n...\n[00:05:09] └- ✖ fail: ObservabilityApp Custom threshold preview chart does render the empty chart only once at bootstrap\n```\n\n@dmlemeshko pointed to the implementation that we have for the button\nand the fact that we need to first check if the user is authorized to\nsee this button, and something might have caused the click not to be\nsuccessful even though there is no error reported by WebDriver.\n\n```\nuseEffect(() => {\n setHeaderActions?.([\n ...(authorizedToCreateAnyRules ? [<CreateRuleButton openFlyout={openRuleTypeModal} />] : []),\n <RulesSettingsLink />,\n <RulesListDocLink />,\n ]);\n }, [authorizedToCreateAnyRules]);\n```\n\nLong story short, we will add waiting for the global spinner to\nhopefully make this test less flaky 🤞🏻\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"2f0bad7d39319c315597be0e464b6d41fb4c25ef"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212028","number":212028,"mergeCommit":{"message":"Attempt to fix custom_threshold_preview_chart flaky test (#212028)\n\nFixes #209317\n\n## Summary\n\nSummary of\n[Slack](https://elastic.slack.com/archives/C04HT4P1YS3/p1740054800086779)\ndiscussion:\n\nAs shown below, we check if the `Create rule` button exists and then we\ntry to click it:\n```\nconst clickCreateRuleButton = async () => {\n await testSubjects.existOrFail('createRuleButton');\n const createRuleButton = await testSubjects.find('createRuleButton');\n return await createRuleButton.click();\n };\n```\n\nIt seems something goes wrong during click in this case and even after 2\nmins, we don't see the modal:\n```\n[00:03:11] │ debg --- retry.tryForTime error: [data-test-subj=\"ruleTypeModal\"] is not displayed\n...\n[00:05:09] └- ✖ fail: ObservabilityApp Custom threshold preview chart does render the empty chart only once at bootstrap\n```\n\n@dmlemeshko pointed to the implementation that we have for the button\nand the fact that we need to first check if the user is authorized to\nsee this button, and something might have caused the click not to be\nsuccessful even though there is no error reported by WebDriver.\n\n```\nuseEffect(() => {\n setHeaderActions?.([\n ...(authorizedToCreateAnyRules ? [<CreateRuleButton openFlyout={openRuleTypeModal} />] : []),\n <RulesSettingsLink />,\n <RulesListDocLink />,\n ]);\n }, [authorizedToCreateAnyRules]);\n```\n\nLong story short, we will add waiting for the global spinner to\nhopefully make this test less flaky 🤞🏻\n\n---------\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"2f0bad7d39319c315597be0e464b6d41fb4c25ef"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> |
||
|
Kibana Machine
|
71d673d0c9
|
[8.x] [APM] Fix service maps when root transaction has a parent.id (#212998) (#213765)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Fix service maps when root transaction has a parent.id (#212998)](https://github.com/elastic/kibana/pull/212998) <!--- 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-03-10T14:57:54Z","message":"[APM] Fix service maps when root transaction has a parent.id (#212998)\n\nfixes [212931](https://github.com/elastic/kibana/issues/212931)\n\n## Summary\n\n>[!WARNING]\n> This can only be merged after\nhttps://github.com/elastic/elasticsearch-serverless/pull/3579. Service\nmap tests running against serverless will fail until the aforementioned\nPR gets merged and deployed. It should happen Thursday/Friday next week\n(13/14 Feb)\n\nFixes a bug on the service map causing it not to build the paths when\nthe root transaction of the trace had a `parent.id`\n\nGlobal service map\n| Before | After |\n|--------|------|\n|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cce72dea-822b-46e2-938c-65ec3f4600da\"\n/>|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/68b344fb-2e75-46b8-9401-9fce08bfb860\"\n/>|\n\n\n`Ad` service map\n\n| Before | After |\n|--------|------|\n|<img width=\"1469\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e960a390-4a38-43d5-9445-853ced34bb15\"\n/>|<img width=\"1459\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/566e3cf0-3805-4bf2-a511-fffed3480332\"\n/>|\n\n\n### How to test\n- Connect to an `edge-obl` cluster\n- Navigate the Application > Services inventory > Service Map\n- Inspect the service map of the `Ad` service\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4a67b8b3af26ea8d7f5c97e6933437122873599f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix service maps when root transaction has a parent.id","number":212998,"url":"https://github.com/elastic/kibana/pull/212998","mergeCommit":{"message":"[APM] Fix service maps when root transaction has a parent.id (#212998)\n\nfixes [212931](https://github.com/elastic/kibana/issues/212931)\n\n## Summary\n\n>[!WARNING]\n> This can only be merged after\nhttps://github.com/elastic/elasticsearch-serverless/pull/3579. Service\nmap tests running against serverless will fail until the aforementioned\nPR gets merged and deployed. It should happen Thursday/Friday next week\n(13/14 Feb)\n\nFixes a bug on the service map causing it not to build the paths when\nthe root transaction of the trace had a `parent.id`\n\nGlobal service map\n| Before | After |\n|--------|------|\n|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cce72dea-822b-46e2-938c-65ec3f4600da\"\n/>|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/68b344fb-2e75-46b8-9401-9fce08bfb860\"\n/>|\n\n\n`Ad` service map\n\n| Before | After |\n|--------|------|\n|<img width=\"1469\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e960a390-4a38-43d5-9445-853ced34bb15\"\n/>|<img width=\"1459\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/566e3cf0-3805-4bf2-a511-fffed3480332\"\n/>|\n\n\n### How to test\n- Connect to an `edge-obl` cluster\n- Navigate the Application > Services inventory > Service Map\n- Inspect the service map of the `Ad` service\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4a67b8b3af26ea8d7f5c97e6933437122873599f"}},"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/212998","number":212998,"mergeCommit":{"message":"[APM] Fix service maps when root transaction has a parent.id (#212998)\n\nfixes [212931](https://github.com/elastic/kibana/issues/212931)\n\n## Summary\n\n>[!WARNING]\n> This can only be merged after\nhttps://github.com/elastic/elasticsearch-serverless/pull/3579. Service\nmap tests running against serverless will fail until the aforementioned\nPR gets merged and deployed. It should happen Thursday/Friday next week\n(13/14 Feb)\n\nFixes a bug on the service map causing it not to build the paths when\nthe root transaction of the trace had a `parent.id`\n\nGlobal service map\n| Before | After |\n|--------|------|\n|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cce72dea-822b-46e2-938c-65ec3f4600da\"\n/>|<img width=\"599\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/68b344fb-2e75-46b8-9401-9fce08bfb860\"\n/>|\n\n\n`Ad` service map\n\n| Before | After |\n|--------|------|\n|<img width=\"1469\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e960a390-4a38-43d5-9445-853ced34bb15\"\n/>|<img width=\"1459\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/566e3cf0-3805-4bf2-a511-fffed3480332\"\n/>|\n\n\n### How to test\n- Connect to an `edge-obl` cluster\n- Navigate the Application > Services inventory > Service Map\n- Inspect the service map of the `Ad` service\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4a67b8b3af26ea8d7f5c97e6933437122873599f"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
Ignacio Rivas
|
e728b2e4a6
|
[UA] Fix skipped functional tests (#212026) | ||
|
Kibana Machine
|
3cae3bab7d
|
[8.x] [ResponseOps][Cases] Fix flaky Cases action Cypress test (#213529) (#213701)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Cases] Fix flaky Cases action Cypress test (#213529)](https://github.com/elastic/kibana/pull/213529) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T10:16:02Z","message":"[ResponseOps][Cases] Fix flaky Cases action Cypress test (#213529)\n\n## Summary\n\n- Fixes the flaky functional test added in #210547 by adding a network\nrequest intercept and clicking on the correct dropdown button\n- Unskips the test file\n\n## References\n\nCloses #211959\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6c281caceb180c5e541ecdcf86d528cd2bafe701","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Cases] Fix flaky Cases action Cypress test","number":213529,"url":"https://github.com/elastic/kibana/pull/213529","mergeCommit":{"message":"[ResponseOps][Cases] Fix flaky Cases action Cypress test (#213529)\n\n## Summary\n\n- Fixes the flaky functional test added in #210547 by adding a network\nrequest intercept and clicking on the correct dropdown button\n- Unskips the test file\n\n## References\n\nCloses #211959\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6c281caceb180c5e541ecdcf86d528cd2bafe701"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213529","number":213529,"mergeCommit":{"message":"[ResponseOps][Cases] Fix flaky Cases action Cypress test (#213529)\n\n## Summary\n\n- Fixes the flaky functional test added in #210547 by adding a network\nrequest intercept and clicking on the correct dropdown button\n- Unskips the test file\n\n## References\n\nCloses #211959\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6c281caceb180c5e541ecdcf86d528cd2bafe701"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com> |
||
|
Kibana Machine
|
6a21b34be9
|
[8.x] Fixing - Failing test: Stateful Observability - Deployment-agnostic A… (#213530) (#213601)
# Backport This will backport the following commits from `main` to `8.x`: - [Fixing - Failing test: Stateful Observability - Deployment-agnostic A… (#213530)](https://github.com/elastic/kibana/pull/213530) <!--- 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-03-07T16:10:09Z","message":"Fixing - Failing test: Stateful Observability - Deployment-agnostic A… (#213530)\n\nCloses [#213209](https://github.com/elastic/kibana/issues/213209)\n\n### Ordering Issue\n- The instruction about `retrieve_elastic_doc` appears before the\n`get_dataset_info` instruction.\n- The content is the same, but the order of instructions has changed,\ncausing a failure in an exact string match.\n### Minor Formatting Differences\n- Even slight variations in spacing, newlines, or indentations can cause\na test failure.\n\n## Solution\nuse `systemMessageSorted` - order of instructions can vary, so we sort to compare them","sha":"5d0e0f48adc176d95a223116e1767eedf324740b","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","v9.1.0","v8.19.0"],"title":"Fixing - Failing test: Stateful Observability - Deployment-agnostic A…","number":213530,"url":"https://github.com/elastic/kibana/pull/213530","mergeCommit":{"message":"Fixing - Failing test: Stateful Observability - Deployment-agnostic A… (#213530)\n\nCloses [#213209](https://github.com/elastic/kibana/issues/213209)\n\n### Ordering Issue\n- The instruction about `retrieve_elastic_doc` appears before the\n`get_dataset_info` instruction.\n- The content is the same, but the order of instructions has changed,\ncausing a failure in an exact string match.\n### Minor Formatting Differences\n- Even slight variations in spacing, newlines, or indentations can cause\na test failure.\n\n## Solution\nuse `systemMessageSorted` - order of instructions can vary, so we sort to compare them","sha":"5d0e0f48adc176d95a223116e1767eedf324740b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213530","number":213530,"mergeCommit":{"message":"Fixing - Failing test: Stateful Observability - Deployment-agnostic A… (#213530)\n\nCloses [#213209](https://github.com/elastic/kibana/issues/213209)\n\n### Ordering Issue\n- The instruction about `retrieve_elastic_doc` appears before the\n`get_dataset_info` instruction.\n- The content is the same, but the order of instructions has changed,\ncausing a failure in an exact string match.\n### Minor Formatting Differences\n- Even slight variations in spacing, newlines, or indentations can cause\na test failure.\n\n## Solution\nuse `systemMessageSorted` - order of instructions can vary, so we sort to compare them","sha":"5d0e0f48adc176d95a223116e1767eedf324740b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
|
Kibana Machine
|
971dd384b0 | skip failing test suite (#202564) | ||
|
Kibana Machine
|
b414e1f3b0
|
[8.x] [Obs AI Assistant] Add test for get_dataset_info (#213231) (#213557)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Add test for `get_dataset_info` (#213231)](https://github.com/elastic/kibana/pull/213231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T12:53:10Z","message":"[Obs AI Assistant] Add test for `get_dataset_info` (#213231)\n\n- Add API test for `get_dataset_info`\n- Add apache synthtrace scenario\n- Search local and remote clusters unless otherwise specified","sha":"175e9066d00a76985bf956b2cf693fb0319b9940","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 AI Assistant","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Add test for `get_dataset_info`","number":213231,"url":"https://github.com/elastic/kibana/pull/213231","mergeCommit":{"message":"[Obs AI Assistant] Add test for `get_dataset_info` (#213231)\n\n- Add API test for `get_dataset_info`\n- Add apache synthtrace scenario\n- Search local and remote clusters unless otherwise specified","sha":"175e9066d00a76985bf956b2cf693fb0319b9940"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213231","number":213231,"mergeCommit":{"message":"[Obs AI Assistant] Add test for `get_dataset_info` (#213231)\n\n- Add API test for `get_dataset_info`\n- Add apache synthtrace scenario\n- Search local and remote clusters unless otherwise specified","sha":"175e9066d00a76985bf956b2cf693fb0319b9940"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Michael Olorunnisola
|
ce7bc436bb
|
[8.x] [Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343) (#213489)
# Backport This will backport the following commits from `main` to `8.x`: - [[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)](https://github.com/elastic/kibana/pull/211343) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T21:09:22Z","message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[Bug][Security Solution] - Reliably persist dataview selections for timeline","number":211343,"url":"https://github.com/elastic/kibana/pull/211343","mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213488","number":213488,"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/211343","number":211343,"mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
elastic-renovate-prod[bot]
|
e2e52c8baa
|
Update dependency @elastic/elasticsearch to ^8.17.1 (8.x) (#213283)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@elastic/elasticsearch](http://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/index.html) ([source](https://redirect.github.com/elastic/elasticsearch-js)) | dependencies | patch | [`^8.17.0` -> `^8.17.1`](https://renovatebot.com/diffs/npm/@elastic%2felasticsearch/8.17.0/8.17.1) | --- ### Release Notes <details> <summary>elastic/elasticsearch-js (@​elastic/elasticsearch)</summary> ### [`v8.17.1`](https://redirect.github.com/elastic/elasticsearch-js/releases/tag/v8.17.1) [Compare Source](https://redirect.github.com/elastic/elasticsearch-js/compare/v8.17.0...v8.17.1) [Changelog](https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/8.17/changelog-client.html) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC54IiwibGFiZWxzIjpbIlRlYW06Q29yZSIsIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
26149129cd
|
[8.x] [Security Solution] Account for missing base rule versions in is_customized calculation (#213250) (#213462)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)](https://github.com/elastic/kibana/pull/213250) <!--- 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-03-06T18:22:17Z","message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Account for missing base rule versions in is_customized calculation","number":213250,"url":"https://github.com/elastic/kibana/pull/213250","mergeCommit":{"message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845"}},"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/213250","number":213250,"mergeCommit":{"message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co> |
||
|
Kibana Machine
|
d91c6b182c
|
[8.x] 🌊 Streams: Move routing into wired object in the API (#213121) (#213454)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Streams: Move routing into wired object in the API (#213121)](https://github.com/elastic/kibana/pull/213121) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T17:52:09Z","message":"🌊 Streams: Move routing into wired object in the API (#213121)\n\nSince we decided we don't want to provide routing for classic streams,\nit doesn't make sense to be on the level of the ingest stream in the\nAPI. This PR moves routing next to fields to make clear that it's only\nsupported for wired streams.","sha":"a81e6925563c0cf9417a7c045c8e797784d8fbb4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"🌊 Streams: Move routing into wired object in the API","number":213121,"url":"https://github.com/elastic/kibana/pull/213121","mergeCommit":{"message":"🌊 Streams: Move routing into wired object in the API (#213121)\n\nSince we decided we don't want to provide routing for classic streams,\nit doesn't make sense to be on the level of the ingest stream in the\nAPI. This PR moves routing next to fields to make clear that it's only\nsupported for wired streams.","sha":"a81e6925563c0cf9417a7c045c8e797784d8fbb4"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213121","number":213121,"mergeCommit":{"message":"🌊 Streams: Move routing into wired object in the API (#213121)\n\nSince we decided we don't want to provide routing for classic streams,\nit doesn't make sense to be on the level of the ingest stream in the\nAPI. This PR moves routing next to fields to make clear that it's only\nsupported for wired streams.","sha":"a81e6925563c0cf9417a7c045c8e797784d8fbb4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> |
||
Lola
|
5b98df8f79
|
[8.x] [Cloud Security] Add upgrade agentless deployment background task (#207143) (#213134)
# Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] Add upgrade agentless deployment background task (#207143)](https://github.com/elastic/kibana/pull/207143) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lola","email":"omolola.akinleye@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T01:56:23Z","message":"[Cloud Security] Add upgrade agentless deployment background task (#207143)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\nThis PR add background task to upgrade Agentless Deployments after\nKibana Stack has been upgrade in ESS. Once the Kibana stack upgrades, the task will do following:\n1. Fetch agentless policies with package policies that have agents\n2. Check if agentless agents version is upgradeable by use `semverLT`\nwhich see if current agent version less than latest available upgrade\nversion and current kibana version\n3. If agent version is upgradedable, then task will calls Agentless\nUpgrade Endpoint to upgrade agentless deployment.\n4. Agent should be upgraded to latest available upgraded version\n\n\n\n\n\n**How to test PR:**\n\nPrerequisite:\nInstall [QAF\nTool](https://docs.elastic.dev/appex-qa/qaf/getting-started)\nCreate EC cloud api key [QAF Elastic\nCloud](https://docs.elastic.dev/appex-qa/qaf/features/ec-deployments)\n\n1. Go to Elastic Cloud and Create ESS Deployment in `8.17.0-SNAPSHOT`\n```qaf elastic-cloud deployments create --environment production --region gcp-us-west2 --stack-version 8.17.0-SNAPSHOT --version-validation --deployment-name <DEPLOYMENT_NAME> ```\n2. Create an Agentless Integration\n3. Upgrade stack to `8.18.0-SNAPSHOT` > `8.19.0-SNAPSHOT`\n4. Run the following QAF command \n```qaf elastic-cloud deployments upgrade <DEPLOYMENT_NAME>\n9.1.0-SNAPSHOT --kb-docker-image\ndocker.elastic.co/kibana-ci/kibana-cloud:9.1.0-SNAPSHOT-5e00106755e7084d1325e784eb27f91db9724c89```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8e31e5fcbb28f485e309fbacf9a2aca9f8d3a2c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport missing","Team:Fleet","release_note:feature","Team:Cloud Security","backport:prev-minor","ci:cloud-deploy","v9.1.0","v8.18.1"],"title":"[Cloud Security] Create upgrade agentless deployment background task","number":207143,"url":"https://github.com/elastic/kibana/pull/207143","mergeCommit":{"message":"[Cloud Security] Add upgrade agentless deployment background task (#207143)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\nThis PR add background task to upgrade Agentless Deployments after\nKibana Stack has been upgrade in ESS. Once the Kibana stack upgrades, the task will do following:\n1. Fetch agentless policies with package policies that have agents\n2. Check if agentless agents version is upgradeable by use `semverLT`\nwhich see if current agent version less than latest available upgrade\nversion and current kibana version\n3. If agent version is upgradedable, then task will calls Agentless\nUpgrade Endpoint to upgrade agentless deployment.\n4. Agent should be upgraded to latest available upgraded version\n\n\n\n\n\n**How to test PR:**\n\nPrerequisite:\nInstall [QAF\nTool](https://docs.elastic.dev/appex-qa/qaf/getting-started)\nCreate EC cloud api key [QAF Elastic\nCloud](https://docs.elastic.dev/appex-qa/qaf/features/ec-deployments)\n\n1. Go to Elastic Cloud and Create ESS Deployment in `8.17.0-SNAPSHOT`\n```qaf elastic-cloud deployments create --environment production --region gcp-us-west2 --stack-version 8.17.0-SNAPSHOT --version-validation --deployment-name <DEPLOYMENT_NAME> ```\n2. Create an Agentless Integration\n3. Upgrade stack to `8.18.0-SNAPSHOT` > `8.19.0-SNAPSHOT`\n4. Run the following QAF command \n```qaf elastic-cloud deployments upgrade <DEPLOYMENT_NAME>\n9.1.0-SNAPSHOT --kb-docker-image\ndocker.elastic.co/kibana-ci/kibana-cloud:9.1.0-SNAPSHOT-5e00106755e7084d1325e784eb27f91db9724c89```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8e31e5fcbb28f485e309fbacf9a2aca9f8d3a2c"}},"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/207143","number":207143,"mergeCommit":{"message":"[Cloud Security] Add upgrade agentless deployment background task (#207143)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\nThis PR add background task to upgrade Agentless Deployments after\nKibana Stack has been upgrade in ESS. Once the Kibana stack upgrades, the task will do following:\n1. Fetch agentless policies with package policies that have agents\n2. Check if agentless agents version is upgradeable by use `semverLT`\nwhich see if current agent version less than latest available upgrade\nversion and current kibana version\n3. If agent version is upgradedable, then task will calls Agentless\nUpgrade Endpoint to upgrade agentless deployment.\n4. Agent should be upgraded to latest available upgraded version\n\n\n\n\n\n**How to test PR:**\n\nPrerequisite:\nInstall [QAF\nTool](https://docs.elastic.dev/appex-qa/qaf/getting-started)\nCreate EC cloud api key [QAF Elastic\nCloud](https://docs.elastic.dev/appex-qa/qaf/features/ec-deployments)\n\n1. Go to Elastic Cloud and Create ESS Deployment in `8.17.0-SNAPSHOT`\n```qaf elastic-cloud deployments create --environment production --region gcp-us-west2 --stack-version 8.17.0-SNAPSHOT --version-validation --deployment-name <DEPLOYMENT_NAME> ```\n2. Create an Agentless Integration\n3. Upgrade stack to `8.18.0-SNAPSHOT` > `8.19.0-SNAPSHOT`\n4. Run the following QAF command \n```qaf elastic-cloud deployments upgrade <DEPLOYMENT_NAME>\n9.1.0-SNAPSHOT --kb-docker-image\ndocker.elastic.co/kibana-ci/kibana-cloud:9.1.0-SNAPSHOT-5e00106755e7084d1325e784eb27f91db9724c89```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f8e31e5fcbb28f485e309fbacf9a2aca9f8d3a2c"}},{"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> |
||
|
Kibana Machine
|
1531e20966
|
[8.x] [Security Solution] Allow prebuilt rules import and export (#212509) (#213420)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Allow prebuilt rules import and export (#212509)](https://github.com/elastic/kibana/pull/212509) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T15:58:33Z","message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","Feature:Rule Import/Export","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Allow prebuilt rules import and export","number":212509,"url":"https://github.com/elastic/kibana/pull/212509","mergeCommit":{"message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4"}},"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/212509","number":212509,"mergeCommit":{"message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
3327518e65
|
[8.x] fix conversation tests (#213338) (#213398)
# Backport This will backport the following commits from `main` to `8.x`: - [fix conversation tests (#213338)](https://github.com/elastic/kibana/pull/213338) <!--- 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-03-06T13:48:36Z","message":"fix conversation tests (#213338)\n\n## Summary\n\nFIX:\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4516","sha":"d2a19bd08a1801f032f4dc58c3df8de4bc69f659","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"fix conversation tests","number":213338,"url":"https://github.com/elastic/kibana/pull/213338","mergeCommit":{"message":"fix conversation tests (#213338)\n\n## Summary\n\nFIX:\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4516","sha":"d2a19bd08a1801f032f4dc58c3df8de4bc69f659"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213338","number":213338,"mergeCommit":{"message":"fix conversation tests (#213338)\n\n## Summary\n\nFIX:\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4516","sha":"d2a19bd08a1801f032f4dc58c3df8de4bc69f659"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
|
Kibana Machine
|
870f4e3728
|
[8.x] [ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822) (#213373)
# Backport This will backport the following commits from `main` to `8.x`: - [[ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822)](https://github.com/elastic/kibana/pull/211822) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T12:52:44Z","message":"[ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822)\n\nCloses #211783\nPart of https://github.com/elastic/kibana/issues/195857\n\n## Summary\n\nThis PR expands the logic to get the dashboard files based on the agent.\nWe have many different ways to ingest data so we want to add more\nmetrics dashboards to the APM metrics tab. The different ingest paths we\nhave:\nClassic APM Agent --> APM Server --> ES\nVanilla OTel SDKs --> APM Server --> ES\nEDOT OTel SDKs --> APM Server --> ES\nClassic APM Agent --> EDOT Collector --> ES\nVanilla OTel SDKs. --> EDOT Collector --> ES\nEDOT OTel SDKs --> EDOT Collector --> ES\nWe agreed on having a dashboard filename pattern to make showing the\ncorrect dashboard easier described\n[here](https://github.com/elastic/kibana/issues/195857#issue-2580733648)\n\nFirst, we determine if the ingest path is through APM Server or EDOT\nCollector by checking the `telemtry.sdk` fields.\n\n## TODOs / Reviewer notes\n- [ ] Currently, we have a fallback to metrics charts which is valid\nonly if we have APM agent so this PR adds an empty state message:\n\"Runtime metrics are not available for this Agent / SDK type.\" in case\nthere is no dashboard for the service language. To be improved in\nhttps://github.com/elastic/kibana/issues/211774 and will be updated in\nthis PR when ready - I will still open it for review as the other logic\ncan be reviewed\n- The dashboards are to be updated (by the agent team so not part of the\nchanges here)\n\n## Testing: \n- Using e2e PoC \n- The available dashboard cases can be found in\n[loadDashboardFile]( |
||
Sandra G
|
c7f294eb74
|
[8.x] [Obs AI Assistant] fix flaky test and add back test in settings (#213196) (#213316)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] fix flaky test and add back test in settings (#213196)](https://github.com/elastic/kibana/pull/213196) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T16:46:02Z","message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0","v8.16.6"],"title":"[Obs AI Assistant] fix flaky test and add back test in settings","number":213196,"url":"https://github.com/elastic/kibana/pull/213196","mergeCommit":{"message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252"}},"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/213196","number":213196,"mergeCommit":{"message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252"}},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213271","number":213271,"state":"MERGED","mergeCommit":{"sha":"b400d81dfeff4274d6a708503c956f3b852cb10c","message":"[8.16] [Obs AI Assistant] fix flaky test and add back test in settings (#213196) (#213271)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Obs AI Assistant] fix flaky test and add back test in settings\n(#213196)](https://github.com/elastic/kibana/pull/213196)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Sandra G <neptunian@users.noreply.github.com>"}},{"url":"https://github.com/elastic/kibana/pull/213272","number":213272,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4e0cf03e7c
|
[8.x] [Siem Migrations] GET /integrations integration Test (#213251) (#213357)
# Backport This will backport the following commits from `main` to `8.x`: - [[Siem Migrations] `GET /integrations` integration Test (#213251)](https://github.com/elastic/kibana/pull/213251) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T11:19:28Z","message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migrations] `GET /integrations` integration Test","number":213251,"url":"https://github.com/elastic/kibana/pull/213251","mergeCommit":{"message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db"}},"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/213251","number":213251,"mergeCommit":{"message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
Zacqary Adam Xeper
|
edc74bab07
|
[8.x] [Response Ops] [Rule Form] Add Rule Form Flyout v2 (#206685) (#213258)
# Backport This will backport the following commits from `main` to `8.x`: - [[Response Ops] [Rule Form] Add Rule Form Flyout v2 (#206685)](https://github.com/elastic/kibana/pull/206685) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Zacqary Adam Xeper","email":"Zacqary@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-04T14:52:58Z","message":"[Response Ops] [Rule Form] Add Rule Form Flyout v2 (#206685)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\nReplaces the create/edit rule flyout with the new rule flyout\r\n\r\n<img width=\"1032\" alt=\"Screenshot 2025-01-14 at 3 12 30 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/9cbcf4f8-1078-4f7e-a55a-aacc2d877a14\"\r\n/>\r\n<img width=\"1383\" alt=\"Screenshot 2025-01-14 at 3 12 52 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/2270d57b-9462-4898-9dd0-41baefcc02d4\"\r\n/>\r\n\r\nRestores the confirmation prompt before canceling or saving a rule\r\nwithout actions defined.\r\n\r\nAlso fixes most of the design papercuts in the Actions step:\r\n\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 06 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/3cf21d43-88e0-4250-b290-a545e1ebdbcf\"\r\n/>\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/00ef3f95-c91b-4bb7-aead-a3e23c02f7df\"\r\n/>\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"367ff8dbec417eaed30fb5f6fdf491642dcd1ebd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:ResponseOps","release_note:feature","Feature:Alerting/RulesManagement","ci:cloud-deploy","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Response Ops] [Rule Form] Add Rule Form Flyout v2","number":206685,"url":"https://github.com/elastic/kibana/pull/206685","mergeCommit":{"message":"[Response Ops] [Rule Form] Add Rule Form Flyout v2 (#206685)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\nReplaces the create/edit rule flyout with the new rule flyout\r\n\r\n<img width=\"1032\" alt=\"Screenshot 2025-01-14 at 3 12 30 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/9cbcf4f8-1078-4f7e-a55a-aacc2d877a14\"\r\n/>\r\n<img width=\"1383\" alt=\"Screenshot 2025-01-14 at 3 12 52 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/2270d57b-9462-4898-9dd0-41baefcc02d4\"\r\n/>\r\n\r\nRestores the confirmation prompt before canceling or saving a rule\r\nwithout actions defined.\r\n\r\nAlso fixes most of the design papercuts in the Actions step:\r\n\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 06 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/3cf21d43-88e0-4250-b290-a545e1ebdbcf\"\r\n/>\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/00ef3f95-c91b-4bb7-aead-a3e23c02f7df\"\r\n/>\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"367ff8dbec417eaed30fb5f6fdf491642dcd1ebd"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206685","number":206685,"mergeCommit":{"message":"[Response Ops] [Rule Form] Add Rule Form Flyout v2 (#206685)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\nReplaces the create/edit rule flyout with the new rule flyout\r\n\r\n<img width=\"1032\" alt=\"Screenshot 2025-01-14 at 3 12 30 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/9cbcf4f8-1078-4f7e-a55a-aacc2d877a14\"\r\n/>\r\n<img width=\"1383\" alt=\"Screenshot 2025-01-14 at 3 12 52 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/2270d57b-9462-4898-9dd0-41baefcc02d4\"\r\n/>\r\n\r\nRestores the confirmation prompt before canceling or saving a rule\r\nwithout actions defined.\r\n\r\nAlso fixes most of the design papercuts in the Actions step:\r\n\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 06 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/3cf21d43-88e0-4250-b290-a545e1ebdbcf\"\r\n/>\r\n<img width=\"494\" alt=\"Screenshot 2025-01-14 at 3 11 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/00ef3f95-c91b-4bb7-aead-a3e23c02f7df\"\r\n/>\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"367ff8dbec417eaed30fb5f6fdf491642dcd1ebd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
004577fe6e
|
[8.x] [Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862) (#213233)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)](https://github.com/elastic/kibana/pull/211862) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T12:14:31Z","message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules","number":211862,"url":"https://github.com/elastic/kibana/pull/211862","mergeCommit":{"message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032"}},"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/211862","number":211862,"mergeCommit":{"message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> |
||
|
Kibana Machine
|
7acab83000
|
[8.x] [Siem Migration] - Start/Stop Translation integration tests (#212030) (#213220)
# Backport This will backport the following commits from `main` to `8.x`: - [[Siem Migration] - Start/Stop Translation integration tests (#212030)](https://github.com/elastic/kibana/pull/212030) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T11:06:06Z","message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migration] - Start/Stop Translation integration tests","number":212030,"url":"https://github.com/elastic/kibana/pull/212030","mergeCommit":{"message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6"}},"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/212030","number":212030,"mergeCommit":{"message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
Robert Oskamp
|
33b3901795
|
[8.x] FTR - optimize service initialization (#212421) (#213213)
# Backport This will backport the following commits from `main` to `8.x`: - [FTR - optimize service initialization (#212421)](https://github.com/elastic/kibana/pull/212421) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T10:35:47Z","message":"FTR - optimize service initialization (#212421)\n\n## Summary\n\nThis PR optimizes the FTR service initialization by not loading UI\nservice for API tests and by removing retries during test user setup\n\n## Changes\n\n- Remove loading of common UI services from common services (UI services\nshould not be loaded for API tests)\n- Move `security` service from `@kbn/ftr-common-functional-ui-services`\nto `@kbn/ftr-common-functional-services` as it should be available to\nAPI tests as well\n- Only try once to delete `testUser` during init (this user usually does\nnot exist on a fresh deployment - and if it does, a single delete\nrequest is enough to get rid of it)\n\n## Benchmark results\n\n**These changes will reduce FTR CI runtime overall by ~100 minutes**\n🚀\nDue to parallel workers in CI, the effective runtime of the whole CI job\nwill be less than that.\n\n- The removal of UI service loading (which includes starting a browser\ninstance) for API tests reduces init time by ~0.5 seconds. With 313 API\nconfigs that are started on CI, this reduces the runtime overall by ~156\nseconds / ~2.6 minutes.\n- The removal of test user delete retries reduces init time by ~10\nseconds. With 589 FTR configs that are started on CI, this reduces the\nruntime overall by ~5890 seconds / ~98 minutes.\n- These numbers have been taken on a local machine and since CI workers\nare usually slower, we should see at least this amount of improvement if\nnot more in CI.","sha":"7a381afb177c81ed4d0704cfcec49e6da7179376","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","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"FTR - optimize service initialization","number":212421,"url":"https://github.com/elastic/kibana/pull/212421","mergeCommit":{"message":"FTR - optimize service initialization (#212421)\n\n## Summary\n\nThis PR optimizes the FTR service initialization by not loading UI\nservice for API tests and by removing retries during test user setup\n\n## Changes\n\n- Remove loading of common UI services from common services (UI services\nshould not be loaded for API tests)\n- Move `security` service from `@kbn/ftr-common-functional-ui-services`\nto `@kbn/ftr-common-functional-services` as it should be available to\nAPI tests as well\n- Only try once to delete `testUser` during init (this user usually does\nnot exist on a fresh deployment - and if it does, a single delete\nrequest is enough to get rid of it)\n\n## Benchmark results\n\n**These changes will reduce FTR CI runtime overall by ~100 minutes**\n🚀\nDue to parallel workers in CI, the effective runtime of the whole CI job\nwill be less than that.\n\n- The removal of UI service loading (which includes starting a browser\ninstance) for API tests reduces init time by ~0.5 seconds. With 313 API\nconfigs that are started on CI, this reduces the runtime overall by ~156\nseconds / ~2.6 minutes.\n- The removal of test user delete retries reduces init time by ~10\nseconds. With 589 FTR configs that are started on CI, this reduces the\nruntime overall by ~5890 seconds / ~98 minutes.\n- These numbers have been taken on a local machine and since CI workers\nare usually slower, we should see at least this amount of improvement if\nnot more in CI.","sha":"7a381afb177c81ed4d0704cfcec49e6da7179376"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212421","number":212421,"mergeCommit":{"message":"FTR - optimize service initialization (#212421)\n\n## Summary\n\nThis PR optimizes the FTR service initialization by not loading UI\nservice for API tests and by removing retries during test user setup\n\n## Changes\n\n- Remove loading of common UI services from common services (UI services\nshould not be loaded for API tests)\n- Move `security` service from `@kbn/ftr-common-functional-ui-services`\nto `@kbn/ftr-common-functional-services` as it should be available to\nAPI tests as well\n- Only try once to delete `testUser` during init (this user usually does\nnot exist on a fresh deployment - and if it does, a single delete\nrequest is enough to get rid of it)\n\n## Benchmark results\n\n**These changes will reduce FTR CI runtime overall by ~100 minutes**\n🚀\nDue to parallel workers in CI, the effective runtime of the whole CI job\nwill be less than that.\n\n- The removal of UI service loading (which includes starting a browser\ninstance) for API tests reduces init time by ~0.5 seconds. With 313 API\nconfigs that are started on CI, this reduces the runtime overall by ~156\nseconds / ~2.6 minutes.\n- The removal of test user delete retries reduces init time by ~10\nseconds. With 589 FTR configs that are started on CI, this reduces the\nruntime overall by ~5890 seconds / ~98 minutes.\n- These numbers have been taken on a local machine and since CI workers\nare usually slower, we should see at least this amount of improvement if\nnot more in CI.","sha":"7a381afb177c81ed4d0704cfcec49e6da7179376"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
9c61f240c2
|
[8.x] [Obs AI Assistant] Add API test for get_alerts_dataset_info tool (#212858) (#213202)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)](https://github.com/elastic/kibana/pull/212858) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T08:09:22Z","message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0"],"title":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool","number":212858,"url":"https://github.com/elastic/kibana/pull/212858","mergeCommit":{"message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3"}},"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/212858","number":212858,"mergeCommit":{"message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Julia
|
50337e1534
|
[8.x] [ResponseOps][MW] Allow users to delete MWs (#211399) (#213161)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][MW] Allow users to delete MWs (#211399)](https://github.com/elastic/kibana/pull/211399) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T15:20:31Z","message":"[ResponseOps][MW] Allow users to delete MWs (#211399)\n\nResolve: https://github.com/elastic/kibana/issues/198559\nResolve: https://github.com/elastic/kibana/issues/205269\n\nHere I used the existing DELETE\n/internal/alerting/rules/maintenance_window/{id} API to delete MWs from\nthe UI.\nI added an action to the MW table so users can delete MWs. And show a\ndelete confirmation modal when users delete a MW from the UI.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6ce22f4a336caa774acd360e3f66b74517d0bad0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][MW] Allow users to delete MWs","number":211399,"url":"https://github.com/elastic/kibana/pull/211399","mergeCommit":{"message":"[ResponseOps][MW] Allow users to delete MWs (#211399)\n\nResolve: https://github.com/elastic/kibana/issues/198559\nResolve: https://github.com/elastic/kibana/issues/205269\n\nHere I used the existing DELETE\n/internal/alerting/rules/maintenance_window/{id} API to delete MWs from\nthe UI.\nI added an action to the MW table so users can delete MWs. And show a\ndelete confirmation modal when users delete a MW from the UI.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6ce22f4a336caa774acd360e3f66b74517d0bad0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211399","number":211399,"mergeCommit":{"message":"[ResponseOps][MW] Allow users to delete MWs (#211399)\n\nResolve: https://github.com/elastic/kibana/issues/198559\nResolve: https://github.com/elastic/kibana/issues/205269\n\nHere I used the existing DELETE\n/internal/alerting/rules/maintenance_window/{id} API to delete MWs from\nthe UI.\nI added an action to the MW table so users can delete MWs. And show a\ndelete confirmation modal when users delete a MW from the UI.\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6ce22f4a336caa774acd360e3f66b74517d0bad0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c3379ecaf8
|
[8.x] [Security Assistant] Fix use default inference endpoint (#212191) (#213183)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Assistant] Fix use default inference endpoint (#212191)](https://github.com/elastic/kibana/pull/212191) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-03-05T01:14:08Z","message":"[Security Assistant] Fix use default inference endpoint (#212191)\n\n## Summary\n\nRemoves internal feature flag responsible for switching to Kibana's\ninternal inference endpoint instead of using a dedicated one.\n\nHow to test:\n\n**Clean cluster:**\n**1. Setup KB**\n**2. Make sure the `.kibana-elastic-ai-assistant-knowledge-base-*` Data\nStream is using default Inference endpoint**\n```\nhttp://localhost:5601/app/management/data/index_management/component_templates/.kibana-elastic-ai-assistant-component-template-knowledge-base\n```\n<img width=\"1656\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/84fda205-6272-4393-8f7d-a449fae2a090\"\n/>\n\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**3. Make sure there is no inference endpoint on the list**\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\nMigration:\n**1. Setup KB on at least 2 Kibana spaces on `main` branch**\n**2. Switch to this PR's branch and start Kibana**\n**3. Make sure there is no inference endpoint on the list**\n```\nhttp://localhost:5601/app/elasticsearch/relevance/inference_endpoints\n```\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure that the Data stream was rolled over**\n```\nhttp://localhost:5601/app/management/data/index_management/indices?filter=know&includeHiddenIndices=true\n```\nShould see two indices per Kibana space:\n<img width=\"1741\" alt=\"Zrzut ekranu 2025-03-3 o 15 37 55\"\nsrc=\"https://github.com/user-attachments/assets/e6da48c8-59e9-43b8-8eac-c2b5e0059954\"\n/>\n\nThe older index per space should have mapping:\n<img width=\"1083\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/01f6e422-77d1-4f8b-8b7e-9c541a7ea47c\"\n/>\n\nNewer index per space:\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e742f042559eee067f71adeb1f1523b2197f3b3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","ci:cloud-deploy","Feature:Security Assistant","ci:project-deploy-security","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Assistant] Fix use default inference endpoint","number":212191,"url":"https://github.com/elastic/kibana/pull/212191","mergeCommit":{"message":"[Security Assistant] Fix use default inference endpoint (#212191)\n\n## Summary\n\nRemoves internal feature flag responsible for switching to Kibana's\ninternal inference endpoint instead of using a dedicated one.\n\nHow to test:\n\n**Clean cluster:**\n**1. Setup KB**\n**2. Make sure the `.kibana-elastic-ai-assistant-knowledge-base-*` Data\nStream is using default Inference endpoint**\n```\nhttp://localhost:5601/app/management/data/index_management/component_templates/.kibana-elastic-ai-assistant-component-template-knowledge-base\n```\n<img width=\"1656\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/84fda205-6272-4393-8f7d-a449fae2a090\"\n/>\n\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**3. Make sure there is no inference endpoint on the list**\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\nMigration:\n**1. Setup KB on at least 2 Kibana spaces on `main` branch**\n**2. Switch to this PR's branch and start Kibana**\n**3. Make sure there is no inference endpoint on the list**\n```\nhttp://localhost:5601/app/elasticsearch/relevance/inference_endpoints\n```\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure that the Data stream was rolled over**\n```\nhttp://localhost:5601/app/management/data/index_management/indices?filter=know&includeHiddenIndices=true\n```\nShould see two indices per Kibana space:\n<img width=\"1741\" alt=\"Zrzut ekranu 2025-03-3 o 15 37 55\"\nsrc=\"https://github.com/user-attachments/assets/e6da48c8-59e9-43b8-8eac-c2b5e0059954\"\n/>\n\nThe older index per space should have mapping:\n<img width=\"1083\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/01f6e422-77d1-4f8b-8b7e-9c541a7ea47c\"\n/>\n\nNewer index per space:\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e742f042559eee067f71adeb1f1523b2197f3b3"}},"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/212191","number":212191,"mergeCommit":{"message":"[Security Assistant] Fix use default inference endpoint (#212191)\n\n## Summary\n\nRemoves internal feature flag responsible for switching to Kibana's\ninternal inference endpoint instead of using a dedicated one.\n\nHow to test:\n\n**Clean cluster:**\n**1. Setup KB**\n**2. Make sure the `.kibana-elastic-ai-assistant-knowledge-base-*` Data\nStream is using default Inference endpoint**\n```\nhttp://localhost:5601/app/management/data/index_management/component_templates/.kibana-elastic-ai-assistant-component-template-knowledge-base\n```\n<img width=\"1656\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/84fda205-6272-4393-8f7d-a449fae2a090\"\n/>\n\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**3. Make sure there is no inference endpoint on the list**\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\nMigration:\n**1. Setup KB on at least 2 Kibana spaces on `main` branch**\n**2. Switch to this PR's branch and start Kibana**\n**3. Make sure there is no inference endpoint on the list**\n```\nhttp://localhost:5601/app/elasticsearch/relevance/inference_endpoints\n```\n<img width=\"1875\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3465df8b-7c0d-4faf-b113-df897694521e\"\n/>\n\n**4. Make sure that the Data stream was rolled over**\n```\nhttp://localhost:5601/app/management/data/index_management/indices?filter=know&includeHiddenIndices=true\n```\nShould see two indices per Kibana space:\n<img width=\"1741\" alt=\"Zrzut ekranu 2025-03-3 o 15 37 55\"\nsrc=\"https://github.com/user-attachments/assets/e6da48c8-59e9-43b8-8eac-c2b5e0059954\"\n/>\n\nThe older index per space should have mapping:\n<img width=\"1083\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/01f6e422-77d1-4f8b-8b7e-9c541a7ea47c\"\n/>\n\nNewer index per space:\n<img width=\"1086\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/19e562ec-da5f-4ec2-ab64-7bfb1d64789c\"\n/>\n\n**4. Make sure Security Labs content exists on KB list and you can add\nand edit Document/Index entry\n```\nhttp://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5e742f042559eee067f71adeb1f1523b2197f3b3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com> |
||
|
Kibana Machine
|
f2f5660f78
|
[8.x] [Observability AI Assistant] duplicate conversations (#208044) (#213167)
# Backport This will backport the following commits from `main` to `8.x`: - [[Observability AI Assistant] duplicate conversations (#208044)](https://github.com/elastic/kibana/pull/208044) <!--- 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-03-04T22:15:37Z","message":"[Observability AI Assistant] duplicate conversations (#208044)\n\nCloses #209382\n\n### Summary:\n\n#### Duplicate Conversation \n- **Readonly** → Public conversations can only be modified by the owner.\n- Duplicated conversations are **owned** by the user who duplicates\nthem.\n- Duplicated conversations are **private** by default `public: false`. \n \n\n |
||
|
Kibana Machine
|
03d92f8285
|
[8.x] 🌊 Streams: Improve integration tests (#213115) (#213159)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Streams: Improve integration tests (#213115)](https://github.com/elastic/kibana/pull/213115) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T20:11:24Z","message":"🌊 Streams: Improve integration tests (#213115)\n\nI noticed that a couple integration tests were not actually validating\nwhether the documents got routed the right way (the number and string\ntests).\n\nThis PR fixes this by introducing a helper that can easily do the same\ncheck we had a couple of times in there.","sha":"ef0c364f11b485c29e4c9d065a93c2a4d12fb5eb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"🌊 Streams: Improve integration tests","number":213115,"url":"https://github.com/elastic/kibana/pull/213115","mergeCommit":{"message":"🌊 Streams: Improve integration tests (#213115)\n\nI noticed that a couple integration tests were not actually validating\nwhether the documents got routed the right way (the number and string\ntests).\n\nThis PR fixes this by introducing a helper that can easily do the same\ncheck we had a couple of times in there.","sha":"ef0c364f11b485c29e4c9d065a93c2a4d12fb5eb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213115","number":213115,"mergeCommit":{"message":"🌊 Streams: Improve integration tests (#213115)\n\nI noticed that a couple integration tests were not actually validating\nwhether the documents got routed the right way (the number and string\ntests).\n\nThis PR fixes this by introducing a helper that can easily do the same\ncheck we had a couple of times in there.","sha":"ef0c364f11b485c29e4c9d065a93c2a4d12fb5eb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> |
||
|
Vitalii Dmyterko
|
38c3e1a402
|
[8.x] [Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature (#211824) (#213128)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature (#211824)](https://github.com/elastic/kibana/pull/211824) <!--- 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-03-04T15:08:41Z","message":"[Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature (#211824)\n\n## Summary\n\n- addresses https://github.com/elastic/kibana/issues/202051\n\nFew observations, based on ticket\n[description](https://github.com/elastic/kibana/issues/202051):\n\n1. User can update assignees in alert(i.e. update any alert details,\nwhich is handled by **SecuritySolution** priv)\n2. User can see suggested users in searchbox\n3. User **can not** see assignees details(name, avatar) in alerts table\ncolumn and alerts flyout(that's where error toast originates from)\n\nWhy this happens?\n2 different APIs used to show users in searchbox and user details in\nalerts table column:\n\n1. API to show users in searchbox:\n[/internal/detection_engine/users/_find](https://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/routes/users/suggest_user_profiles_route.ts#L24)\nIt requires `securitySolution` privilege\n2. API for alerts table cell:\n[/internal/security/user_profile/_bulk_get](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/security/server/routes/user_profile/bulk_get.ts#L20)\nIt requires `bulkGetUserProfiles` privilege\n\nUser was configured with read only Security Feature, that covers only\nfirst API, that's why we see error\n> API [POST /internal/security/user_profile/_bulk_get] is unauthorized\nfor user, this action is granted by the Kibana privileges\n[bulkGetUserProfiles] (403)\n\nHowever `bulkGetUserProfiles` is covered by `Cases` feature already. If\nCases access will be set to read, user would be able to see assignees\ndetails through `/internal/security/user_profile/_bulk_get` API.\nIt happens, because cases API tags include `bulkGetUserProfiles`\nprivilege:\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/cases/common/utils/api_tags.ts#L32,\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/packages/features/src/cases/types.ts#L7\n\nThis PR includes `bulkGetUserProfiles` privilege in Security Feature:\nhttps://github.com/elastic/kibana/pull/211824. Since, it's already\npresent in Cases feature, and user profiles available through Security\nSolution `/internal/detection_engine/users/_find` API","sha":"847be917a653a830670eb2b8f57674fa9b7a1e8d","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:Detections and Resp","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature","number":211824,"url":"https://github.com/elastic/kibana/pull/211824","mergeCommit":{"message":"[Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature (#211824)\n\n## Summary\n\n- addresses https://github.com/elastic/kibana/issues/202051\n\nFew observations, based on ticket\n[description](https://github.com/elastic/kibana/issues/202051):\n\n1. User can update assignees in alert(i.e. update any alert details,\nwhich is handled by **SecuritySolution** priv)\n2. User can see suggested users in searchbox\n3. User **can not** see assignees details(name, avatar) in alerts table\ncolumn and alerts flyout(that's where error toast originates from)\n\nWhy this happens?\n2 different APIs used to show users in searchbox and user details in\nalerts table column:\n\n1. API to show users in searchbox:\n[/internal/detection_engine/users/_find](https://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/routes/users/suggest_user_profiles_route.ts#L24)\nIt requires `securitySolution` privilege\n2. API for alerts table cell:\n[/internal/security/user_profile/_bulk_get](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/security/server/routes/user_profile/bulk_get.ts#L20)\nIt requires `bulkGetUserProfiles` privilege\n\nUser was configured with read only Security Feature, that covers only\nfirst API, that's why we see error\n> API [POST /internal/security/user_profile/_bulk_get] is unauthorized\nfor user, this action is granted by the Kibana privileges\n[bulkGetUserProfiles] (403)\n\nHowever `bulkGetUserProfiles` is covered by `Cases` feature already. If\nCases access will be set to read, user would be able to see assignees\ndetails through `/internal/security/user_profile/_bulk_get` API.\nIt happens, because cases API tags include `bulkGetUserProfiles`\nprivilege:\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/cases/common/utils/api_tags.ts#L32,\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/packages/features/src/cases/types.ts#L7\n\nThis PR includes `bulkGetUserProfiles` privilege in Security Feature:\nhttps://github.com/elastic/kibana/pull/211824. Since, it's already\npresent in Cases feature, and user profiles available through Security\nSolution `/internal/detection_engine/users/_find` API","sha":"847be917a653a830670eb2b8f57674fa9b7a1e8d"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213120","number":213120,"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/211824","number":211824,"mergeCommit":{"message":"[Security Solution][Detection Engine] adds bulkGetUserProfiles privilege to Security Feature (#211824)\n\n## Summary\n\n- addresses https://github.com/elastic/kibana/issues/202051\n\nFew observations, based on ticket\n[description](https://github.com/elastic/kibana/issues/202051):\n\n1. User can update assignees in alert(i.e. update any alert details,\nwhich is handled by **SecuritySolution** priv)\n2. User can see suggested users in searchbox\n3. User **can not** see assignees details(name, avatar) in alerts table\ncolumn and alerts flyout(that's where error toast originates from)\n\nWhy this happens?\n2 different APIs used to show users in searchbox and user details in\nalerts table column:\n\n1. API to show users in searchbox:\n[/internal/detection_engine/users/_find](https://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/routes/users/suggest_user_profiles_route.ts#L24)\nIt requires `securitySolution` privilege\n2. API for alerts table cell:\n[/internal/security/user_profile/_bulk_get](https://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/security/server/routes/user_profile/bulk_get.ts#L20)\nIt requires `bulkGetUserProfiles` privilege\n\nUser was configured with read only Security Feature, that covers only\nfirst API, that's why we see error\n> API [POST /internal/security/user_profile/_bulk_get] is unauthorized\nfor user, this action is granted by the Kibana privileges\n[bulkGetUserProfiles] (403)\n\nHowever `bulkGetUserProfiles` is covered by `Cases` feature already. If\nCases access will be set to read, user would be able to see assignees\ndetails through `/internal/security/user_profile/_bulk_get` API.\nIt happens, because cases API tags include `bulkGetUserProfiles`\nprivilege:\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/platform/plugins/shared/cases/common/utils/api_tags.ts#L32,\nhttps://github.com/elastic/kibana/blob/8.18/x-pack/solutions/security/packages/features/src/cases/types.ts#L7\n\nThis PR includes `bulkGetUserProfiles` privilege in Security Feature:\nhttps://github.com/elastic/kibana/pull/211824. Since, it's already\npresent in Cases feature, and user profiles available through Security\nSolution `/internal/detection_engine/users/_find` API","sha":"847be917a653a830670eb2b8f57674fa9b7a1e8d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
28d6da2c12
|
[8.x] Skip 'No connectors or conversations exist' on serverless (#213078) (#213110)
# Backport This will backport the following commits from `main` to `8.x`: - [Skip `'No connectors or conversations exist'` on serverless (#213078)](https://github.com/elastic/kibana/pull/213078) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-03-04T14:28:12Z","message":"Skip `'No connectors or conversations exist'` on serverless (#213078)\n\n## Summary\n\nFixes\n |
||
Nathan Reese
|
e3a26ae82c
|
[8.x] [maps] globe projection (#212437) (#213026)
# Backport This will backport the following commits from `main` to `8.x`: - [[maps] globe projection (#212437)](https://github.com/elastic/kibana/pull/212437) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T01:31:05Z","message":"[maps] globe projection (#212437)\n\n<img width=\"600\" alt=\"Screenshot 2025-02-25 at 11 35 32 AM\"\nsrc=\"https://github.com/user-attachments/assets/2567e20c-1223-4001-9866-edbe8c534350\"\n/>\n\nPR does the following\n* Updates maplibre to 5.1.1. Maplibre 5.0 introduced the globe\nprojection\n* Updates sample data maps to use new globe projection\n* Existing maps will use existing \"mercator\" projection\n* Adds globe projection to newly created maps\n* Adds `projection` setting, allowing users to switch between classic\n\"mercator\" and new \"globeInterpolate\" projection\n<img width=\"400\" alt=\"Screenshot 2025-02-25 at 11 35 41 AM\"\nsrc=\"https://github.com/user-attachments/assets/5c55003b-dbe9-4adc-835c-0a2911c81074\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"037e8f58e0af20b006243ee1f28b4d1e5414ab8d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Presentation","Feature:Maps","backport:version","v9.1.0","v8.19.0"],"title":"[maps] globe projection","number":212437,"url":"https://github.com/elastic/kibana/pull/212437","mergeCommit":{"message":"[maps] globe projection (#212437)\n\n<img width=\"600\" alt=\"Screenshot 2025-02-25 at 11 35 32 AM\"\nsrc=\"https://github.com/user-attachments/assets/2567e20c-1223-4001-9866-edbe8c534350\"\n/>\n\nPR does the following\n* Updates maplibre to 5.1.1. Maplibre 5.0 introduced the globe\nprojection\n* Updates sample data maps to use new globe projection\n* Existing maps will use existing \"mercator\" projection\n* Adds globe projection to newly created maps\n* Adds `projection` setting, allowing users to switch between classic\n\"mercator\" and new \"globeInterpolate\" projection\n<img width=\"400\" alt=\"Screenshot 2025-02-25 at 11 35 41 AM\"\nsrc=\"https://github.com/user-attachments/assets/5c55003b-dbe9-4adc-835c-0a2911c81074\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"037e8f58e0af20b006243ee1f28b4d1e5414ab8d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212437","number":212437,"mergeCommit":{"message":"[maps] globe projection (#212437)\n\n<img width=\"600\" alt=\"Screenshot 2025-02-25 at 11 35 32 AM\"\nsrc=\"https://github.com/user-attachments/assets/2567e20c-1223-4001-9866-edbe8c534350\"\n/>\n\nPR does the following\n* Updates maplibre to 5.1.1. Maplibre 5.0 introduced the globe\nprojection\n* Updates sample data maps to use new globe projection\n* Existing maps will use existing \"mercator\" projection\n* Adds globe projection to newly created maps\n* Adds `projection` setting, allowing users to switch between classic\n\"mercator\" and new \"globeInterpolate\" projection\n<img width=\"400\" alt=\"Screenshot 2025-02-25 at 11 35 41 AM\"\nsrc=\"https://github.com/user-attachments/assets/5c55003b-dbe9-4adc-835c-0a2911c81074\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"037e8f58e0af20b006243ee1f28b4d1e5414ab8d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Steph Milovic
|
b939da0c96
|
[8.x] [Security Assistant] Conversation pagination refactor (#211831) (#212997)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Assistant] Conversation pagination refactor (#211831)](https://github.com/elastic/kibana/pull/211831) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T20:41:20Z","message":"[Security Assistant] Conversation pagination refactor (#211831)","sha":"095fc222aa541bf50f57c11958c16eb4c04a282c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0"],"title":"[Security Assistant] Conversation pagination refactor","number":211831,"url":"https://github.com/elastic/kibana/pull/211831","mergeCommit":{"message":"[Security Assistant] Conversation pagination refactor (#211831)","sha":"095fc222aa541bf50f57c11958c16eb4c04a282c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211831","number":211831,"mergeCommit":{"message":"[Security Assistant] Conversation pagination refactor (#211831)","sha":"095fc222aa541bf50f57c11958c16eb4c04a282c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |