mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
46023 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
999fbecaaa
|
[8.x] [Entity Analytics][Entity Store] Fix error callout placement on engine status page (#216228) (#216854)
# Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics][Entity Store] Fix error callout placement on engine status page (#216228)](https://github.com/elastic/kibana/pull/216228) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"mark.hopkin@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T14:29:24Z","message":"[Entity Analytics][Entity Store] Fix error callout placement on engine status page (#216228)\n\n## Summary\n\nThe error callouts were getting squished to the side, I have moved them\nto be in their respective engine section.\n\n**Before**\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 11 05 38\"\nsrc=\"https://github.com/user-attachments/assets/c244acd1-a75e-4b43-a509-8bff9966b31e\"\n/>\n\n\n**After**\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 19 39 53\"\nsrc=\"https://github.com/user-attachments/assets/2b0dd9ad-568a-4e9c-aad7-6922b2085d69\"\n/>\n\nBonus refactor:\n\nI have added type definitions for the error object keys on the engine\nstatus object and moved the error callout to a common component as it's\nnow used in 3 places.\n\n\n## Test Steps\n\nthe easies way to test this is to try and init the entity store in a\nspace that is lobger than 45 chars long.\n\n- create a space with a very long name e.g\n'this_is_a_very_long_space_name_indeed_hello_world_123456789'\n- enable the entity store from the entity analytics dashboard (it should\nerror)\n- navigate to the entity store management page to see the error\ncallouts.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5bfa0564ae8af7479e27b2cddb7a91d279f0f963","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Entity Analytics","backport:version","v9.1.0","v8.19.0"],"title":"[Entity Analytics][Entity Store] Fix error callout placement on engine status page","number":216228,"url":"https://github.com/elastic/kibana/pull/216228","mergeCommit":{"message":"[Entity Analytics][Entity Store] Fix error callout placement on engine status page (#216228)\n\n## Summary\n\nThe error callouts were getting squished to the side, I have moved them\nto be in their respective engine section.\n\n**Before**\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 11 05 38\"\nsrc=\"https://github.com/user-attachments/assets/c244acd1-a75e-4b43-a509-8bff9966b31e\"\n/>\n\n\n**After**\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 19 39 53\"\nsrc=\"https://github.com/user-attachments/assets/2b0dd9ad-568a-4e9c-aad7-6922b2085d69\"\n/>\n\nBonus refactor:\n\nI have added type definitions for the error object keys on the engine\nstatus object and moved the error callout to a common component as it's\nnow used in 3 places.\n\n\n## Test Steps\n\nthe easies way to test this is to try and init the entity store in a\nspace that is lobger than 45 chars long.\n\n- create a space with a very long name e.g\n'this_is_a_very_long_space_name_indeed_hello_world_123456789'\n- enable the entity store from the entity analytics dashboard (it should\nerror)\n- navigate to the entity store management page to see the error\ncallouts.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5bfa0564ae8af7479e27b2cddb7a91d279f0f963"}},"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/216228","number":216228,"mergeCommit":{"message":"[Entity Analytics][Entity Store] Fix error callout placement on engine status page (#216228)\n\n## Summary\n\nThe error callouts were getting squished to the side, I have moved them\nto be in their respective engine section.\n\n**Before**\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 11 05 38\"\nsrc=\"https://github.com/user-attachments/assets/c244acd1-a75e-4b43-a509-8bff9966b31e\"\n/>\n\n\n**After**\n<img width=\"1728\" alt=\"Screenshot 2025-03-27 at 19 39 53\"\nsrc=\"https://github.com/user-attachments/assets/2b0dd9ad-568a-4e9c-aad7-6922b2085d69\"\n/>\n\nBonus refactor:\n\nI have added type definitions for the error object keys on the engine\nstatus object and moved the error callout to a common component as it's\nnow used in 3 places.\n\n\n## Test Steps\n\nthe easies way to test this is to try and init the entity store in a\nspace that is lobger than 45 chars long.\n\n- create a space with a very long name e.g\n'this_is_a_very_long_space_name_indeed_hello_world_123456789'\n- enable the entity store from the entity analytics dashboard (it should\nerror)\n- navigate to the entity store management page to see the error\ncallouts.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5bfa0564ae8af7479e27b2cddb7a91d279f0f963"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co> |
||
|
Kibana Machine
|
491ac998f4
|
[8.x] [Security solution] Read config from preconfigured connectors in Assistant/Attack Discovery (#216700) (#216869)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)](https://github.com/elastic/kibana/pull/216700) <!--- 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-04-02T15:04:06Z","message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078","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","v8.18.1","v9.0.1"],"title":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery","number":216700,"url":"https://github.com/elastic/kibana/pull/216700","mergeCommit":{"message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216700","number":216700,"mergeCommit":{"message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
Cauê Marcondes
|
f60d054e64
|
[8.x] [APM] Removing file (#216708) (#216805)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Removing file (#216708)](https://github.com/elastic/kibana/pull/216708) <!--- 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-04-01T20:50:49Z","message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","ci:project-deploy-observability","v9.1.0"],"title":"[APM] Removing file","number":216708,"url":"https://github.com/elastic/kibana/pull/216708","mergeCommit":{"message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465"}},"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/216708","number":216708,"mergeCommit":{"message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
8b40248527
|
[8.x] Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927) (#216867)
# Backport This will backport the following commits from `main` to `8.x`: - [Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)](https://github.com/elastic/kibana/pull/213927) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miguel Garzón","email":"mgarzon@uottawa.ca"},"sourceCommit":{"committedDate":"2025-03-21T09:32:14Z","message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","backport missing","backport:prev-major","backport:version","v9.1.0","v8.19.0"],"title":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes","number":213927,"url":"https://github.com/elastic/kibana/pull/213927","mergeCommit":{"message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},"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/213927","number":213927,"mergeCommit":{"message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Miguel Garzón <mgarzon@uottawa.ca> |
||
|
Kibana Machine
|
6e7c49674e
|
[8.x] [Discover] Fix getAdditionalCellActions FTR tests (#216540) (#216859)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)](https://github.com/elastic/kibana/pull/216540) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T14:45:08Z","message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [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":"d08e5521f28f4459a76b7176b902efbaea023b06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Discover] Fix `getAdditionalCellActions` FTR tests","number":216540,"url":"https://github.com/elastic/kibana/pull/216540","mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [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":"d08e5521f28f4459a76b7176b902efbaea023b06"}},"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/216540","number":216540,"mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [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":"d08e5521f28f4459a76b7176b902efbaea023b06"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
f5f8a860fa
|
[8.x] Update task state version after execution. (#215559) (#216246)
# Backport This will backport the following commits from `main` to `8.x`: - [Update task state version after execution. (#215559)](https://github.com/elastic/kibana/pull/215559) <!--- 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-27T23:58:41Z","message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"Update task state version after execution.","number":215559,"url":"https://github.com/elastic/kibana/pull/215559","mergeCommit":{"message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7"}},"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/215559","number":215559,"mergeCommit":{"message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7"}},{"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> |
||
Robert Jaszczurek
|
37f5562b73
|
[8.x] [ML] Replace Legacy Base Theme Usage (#216307) (#216838)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Replace Legacy Base Theme Usage (#216307)](https://github.com/elastic/kibana/pull/216307) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T12:47:42Z","message":"[ML] Replace Legacy Base Theme Usage (#216307)\n\nFix for: https://github.com/elastic/kibana/issues/213974\nReplacing legacy base theme with appropriate theme from the charts hook.\n\n\n| Before | After |\n| ------------- | ------------- |\n| <img width=\"404\" alt=\"decision_path_before_light\"\nsrc=\"https://github.com/user-attachments/assets/217cb07d-65a2-4ac0-948b-9950af1e2663\"\n/> |\n (#216812)
# Backport This will backport the following commits from `main` to `8.x`: - [[Lens] Replace the inline quick function documentation icon and popover with tooltips (#216204)](https://github.com/elastic/kibana/pull/216204) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Andreana Malama","email":"72010092+andrimal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T12:22:47Z","message":"[Lens] Replace the inline quick function documentation icon and popover with tooltips (#216204)\n\n## Summary\n\nFix #152522 \n\nThis PR replaces the inline quick function documentation icon and\npopover (screenshot 1) with simple tooltips for every function\n(screenshot 2).\n<img width=\"670\" alt=\"Screenshot 2025-03-31 at 8 15 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/f98d065b-a82b-4807-9375-79994dab9117\"\n/>\n<img width=\"635\" alt=\"Screenshot 2025-03-31 at 8 14 12 PM\"\nsrc=\"https://github.com/user-attachments/assets/a3788318-27b5-4435-abf8-157dc9efd1df\"\n/>\n\nIf a function is disabled then the tooltip should show the\ndisabled-reason and not the documentation:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"40e02f1745a534604f829ffd9eb7b17dbcc22314","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0"],"title":"[Lens] Replace the inline quick function documentation icon and popover with tooltips","number":216204,"url":"https://github.com/elastic/kibana/pull/216204","mergeCommit":{"message":"[Lens] Replace the inline quick function documentation icon and popover with tooltips (#216204)\n\n## Summary\n\nFix #152522 \n\nThis PR replaces the inline quick function documentation icon and\npopover (screenshot 1) with simple tooltips for every function\n(screenshot 2).\n<img width=\"670\" alt=\"Screenshot 2025-03-31 at 8 15 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/f98d065b-a82b-4807-9375-79994dab9117\"\n/>\n<img width=\"635\" alt=\"Screenshot 2025-03-31 at 8 14 12 PM\"\nsrc=\"https://github.com/user-attachments/assets/a3788318-27b5-4435-abf8-157dc9efd1df\"\n/>\n\nIf a function is disabled then the tooltip should show the\ndisabled-reason and not the documentation:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"40e02f1745a534604f829ffd9eb7b17dbcc22314"}},"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/216204","number":216204,"mergeCommit":{"message":"[Lens] Replace the inline quick function documentation icon and popover with tooltips (#216204)\n\n## Summary\n\nFix #152522 \n\nThis PR replaces the inline quick function documentation icon and\npopover (screenshot 1) with simple tooltips for every function\n(screenshot 2).\n<img width=\"670\" alt=\"Screenshot 2025-03-31 at 8 15 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/f98d065b-a82b-4807-9375-79994dab9117\"\n/>\n<img width=\"635\" alt=\"Screenshot 2025-03-31 at 8 14 12 PM\"\nsrc=\"https://github.com/user-attachments/assets/a3788318-27b5-4435-abf8-157dc9efd1df\"\n/>\n\nIf a function is disabled then the tooltip should show the\ndisabled-reason and not the documentation:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"40e02f1745a534604f829ffd9eb7b17dbcc22314"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Andreana Malama <72010092+andrimal@users.noreply.github.com> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Kibana Machine
|
3dd2138d0f
|
[8.x] [Security Solution] Fix alerts table grouping severity stats not showing badge (#216738) (#216846)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)](https://github.com/elastic/kibana/pull/216738) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:42:46Z","message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5","v8.16.7"],"title":"[Security Solution] Fix alerts table grouping severity stats not showing badge","number":216738,"url":"https://github.com/elastic/kibana/pull/216738","mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216738","number":216738,"mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
0dcd49bed0
|
[8.x] [Streams 🌊] Enrichment - Add Schema editor on simulation outcome (#215824) (#216836)
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams 🌊] Enrichment - Add Schema editor on simulation outcome (#215824)](https://github.com/elastic/kibana/pull/215824) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2025-04-02T13:22:18Z","message":"[Streams 🌊] Enrichment - Add Schema editor on simulation outcome (#215824)\n\n## 📓 Summary\n\nCloses https://github.com/elastic/streams-program/issues/70\n\nThis work embed the Schema Editor into the enrichment part, such that\ndetected fields during the simulation can be directly mapped and saved\nwith the newly created processors.\n\n\nhttps://github.com/user-attachments/assets/09a3fe48-4bfc-4501-8c2c-133b1290d884\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9268afecf7935c2cdfb97e07f110a51968446557","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams 🌊] Enrichment - Add Schema editor on simulation outcome","number":215824,"url":"https://github.com/elastic/kibana/pull/215824","mergeCommit":{"message":"[Streams 🌊] Enrichment - Add Schema editor on simulation outcome (#215824)\n\n## 📓 Summary\n\nCloses https://github.com/elastic/streams-program/issues/70\n\nThis work embed the Schema Editor into the enrichment part, such that\ndetected fields during the simulation can be directly mapped and saved\nwith the newly created processors.\n\n\nhttps://github.com/user-attachments/assets/09a3fe48-4bfc-4501-8c2c-133b1290d884\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9268afecf7935c2cdfb97e07f110a51968446557"}},"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/215824","number":215824,"mergeCommit":{"message":"[Streams 🌊] Enrichment - Add Schema editor on simulation outcome (#215824)\n\n## 📓 Summary\n\nCloses https://github.com/elastic/streams-program/issues/70\n\nThis work embed the Schema Editor into the enrichment part, such that\ndetected fields during the simulation can be directly mapped and saved\nwith the newly created processors.\n\n\nhttps://github.com/user-attachments/assets/09a3fe48-4bfc-4501-8c2c-133b1290d884\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9268afecf7935c2cdfb97e07f110a51968446557"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com> |
||
|
Kibana Machine
|
d845a3c59d
|
[8.x] [Lens] Suggest area charts (#216265) (#216816)
# Backport This will backport the following commits from `main` to `8.x`: - [[Lens] Suggest area charts (#216265)](https://github.com/elastic/kibana/pull/216265) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Andreana Malama","email":"72010092+andrimal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T12:24:39Z","message":"[Lens] Suggest area charts (#216265)\n\n## Summary\n\nFix #166362\n\nThis PR contains the following changes in order to include area charts\nin the xy chart suggestions:\n\n- If the current visualization is a `bar_stacked ` chart -> suggest an\n`area_stacked ` chart\n- If the current visualization is a `line ` chart -> suggest an `area`\nchart\n\n<img width=\"1203\" alt=\"Screenshot 2025-03-28 at 11 17 33 AM\"\nsrc=\"https://github.com/user-attachments/assets/6a588c0d-0530-47e8-8ac9-81def7eeeb63\"\n/>\n<img width=\"1195\" alt=\"Screenshot 2025-03-28 at 11 17 58 AM\"\nsrc=\"https://github.com/user-attachments/assets/87219b61-2aa2-4aca-8df2-6e64986f7de4\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"2989154605717a71bcbce1e239cea4d8da9f9a05","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0"],"title":"[Lens] Suggest area charts","number":216265,"url":"https://github.com/elastic/kibana/pull/216265","mergeCommit":{"message":"[Lens] Suggest area charts (#216265)\n\n## Summary\n\nFix #166362\n\nThis PR contains the following changes in order to include area charts\nin the xy chart suggestions:\n\n- If the current visualization is a `bar_stacked ` chart -> suggest an\n`area_stacked ` chart\n- If the current visualization is a `line ` chart -> suggest an `area`\nchart\n\n<img width=\"1203\" alt=\"Screenshot 2025-03-28 at 11 17 33 AM\"\nsrc=\"https://github.com/user-attachments/assets/6a588c0d-0530-47e8-8ac9-81def7eeeb63\"\n/>\n<img width=\"1195\" alt=\"Screenshot 2025-03-28 at 11 17 58 AM\"\nsrc=\"https://github.com/user-attachments/assets/87219b61-2aa2-4aca-8df2-6e64986f7de4\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"2989154605717a71bcbce1e239cea4d8da9f9a05"}},"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/216265","number":216265,"mergeCommit":{"message":"[Lens] Suggest area charts (#216265)\n\n## Summary\n\nFix #166362\n\nThis PR contains the following changes in order to include area charts\nin the xy chart suggestions:\n\n- If the current visualization is a `bar_stacked ` chart -> suggest an\n`area_stacked ` chart\n- If the current visualization is a `line ` chart -> suggest an `area`\nchart\n\n<img width=\"1203\" alt=\"Screenshot 2025-03-28 at 11 17 33 AM\"\nsrc=\"https://github.com/user-attachments/assets/6a588c0d-0530-47e8-8ac9-81def7eeeb63\"\n/>\n<img width=\"1195\" alt=\"Screenshot 2025-03-28 at 11 17 58 AM\"\nsrc=\"https://github.com/user-attachments/assets/87219b61-2aa2-4aca-8df2-6e64986f7de4\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [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- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"2989154605717a71bcbce1e239cea4d8da9f9a05"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Andreana Malama <72010092+andrimal@users.noreply.github.com> |
||
|
Kibana Machine
|
ed5ad481db
|
[8.x] [Security Solution][Detection Engine] Simplify searchAfterBulkCreate (#216498) (#216813)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Detection Engine] Simplify searchAfterBulkCreate (#216498)](https://github.com/elastic/kibana/pull/216498) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T12:23:02Z","message":"[Security Solution][Detection Engine] Simplify searchAfterBulkCreate (#216498)\n\n## Summary\n\nLong ago, we did multiple searches on each \"page\" of results to search\nfor both docs with the timestamp override and default `@timestamp`. We\nthen merged the results together before attempting to bulk create\nalerts. We no longer do this, instead we have a simpler process that\njust does one query per page so there's no need to merge search results\ntogether.\n\nWe also used to build the `tuple` inside `searchAfterBulkCreate`, so we\nhad logic to verify if the tuple was created correctly. The time range\ntuple is now calculated in the shared security wrapper, which is\nresponsible for any error handling. The TS types tell us that `tuple`\nand its subcomponents can't be null, we don't need to check in\n`searchAfterBulkCreate`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e303fb3d20d01f7351fa5b767eab5908b06eec3c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection Engine","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] Simplify searchAfterBulkCreate","number":216498,"url":"https://github.com/elastic/kibana/pull/216498","mergeCommit":{"message":"[Security Solution][Detection Engine] Simplify searchAfterBulkCreate (#216498)\n\n## Summary\n\nLong ago, we did multiple searches on each \"page\" of results to search\nfor both docs with the timestamp override and default `@timestamp`. We\nthen merged the results together before attempting to bulk create\nalerts. We no longer do this, instead we have a simpler process that\njust does one query per page so there's no need to merge search results\ntogether.\n\nWe also used to build the `tuple` inside `searchAfterBulkCreate`, so we\nhad logic to verify if the tuple was created correctly. The time range\ntuple is now calculated in the shared security wrapper, which is\nresponsible for any error handling. The TS types tell us that `tuple`\nand its subcomponents can't be null, we don't need to check in\n`searchAfterBulkCreate`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e303fb3d20d01f7351fa5b767eab5908b06eec3c"}},"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/216498","number":216498,"mergeCommit":{"message":"[Security Solution][Detection Engine] Simplify searchAfterBulkCreate (#216498)\n\n## Summary\n\nLong ago, we did multiple searches on each \"page\" of results to search\nfor both docs with the timestamp override and default `@timestamp`. We\nthen merged the results together before attempting to bulk create\nalerts. We no longer do this, instead we have a simpler process that\njust does one query per page so there's no need to merge search results\ntogether.\n\nWe also used to build the `tuple` inside `searchAfterBulkCreate`, so we\nhad logic to verify if the tuple was created correctly. The time range\ntuple is now calculated in the shared security wrapper, which is\nresponsible for any error handling. The TS types tell us that `tuple`\nand its subcomponents can't be null, we don't need to check in\n`searchAfterBulkCreate`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e303fb3d20d01f7351fa5b767eab5908b06eec3c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
Kibana Machine
|
b421fe725b
|
[8.x] Retry release to fix flaky tests (#216781) (#216798)
# Backport This will backport the following commits from `main` to `8.x`: - [Retry release to fix flaky tests (#216781)](https://github.com/elastic/kibana/pull/216781) <!--- 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-04-02T11:21:20Z","message":"Retry release to fix flaky tests (#216781)\n\nRelated to https://github.com/elastic/kibana/pull/216397\nCloses https://github.com/elastic/kibana/issues/216763\n\nThis change ensures that we do not send the `release` request and\n`extendTtl` request simultaneously in `withLock`. This caused a conflict\ncausing tests to fail:\n\n```\n └-> \"before all\" hook for \"should return the result of the callback\"\n │ERROR Failed to release lock \"my_lock_with_ttl_extension\": version_conflict_engine_exception\n │ \tRoot causes:\n │ \t\tversion_conflict_engine_exception: [my_lock_with_ttl_extension]: version conflict, required seqNo [43], primary term [1]. current document has seqNo [44] and primary term [1]\n```\n\nFlaky tests:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8142","sha":"7275d2e8bd834303898e3f95c5fd1ab734e92947","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"Retry release to fix flaky tests","number":216781,"url":"https://github.com/elastic/kibana/pull/216781","mergeCommit":{"message":"Retry release to fix flaky tests (#216781)\n\nRelated to https://github.com/elastic/kibana/pull/216397\nCloses https://github.com/elastic/kibana/issues/216763\n\nThis change ensures that we do not send the `release` request and\n`extendTtl` request simultaneously in `withLock`. This caused a conflict\ncausing tests to fail:\n\n```\n └-> \"before all\" hook for \"should return the result of the callback\"\n │ERROR Failed to release lock \"my_lock_with_ttl_extension\": version_conflict_engine_exception\n │ \tRoot causes:\n │ \t\tversion_conflict_engine_exception: [my_lock_with_ttl_extension]: version conflict, required seqNo [43], primary term [1]. current document has seqNo [44] and primary term [1]\n```\n\nFlaky tests:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8142","sha":"7275d2e8bd834303898e3f95c5fd1ab734e92947"}},"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/216781","number":216781,"mergeCommit":{"message":"Retry release to fix flaky tests (#216781)\n\nRelated to https://github.com/elastic/kibana/pull/216397\nCloses https://github.com/elastic/kibana/issues/216763\n\nThis change ensures that we do not send the `release` request and\n`extendTtl` request simultaneously in `withLock`. This caused a conflict\ncausing tests to fail:\n\n```\n └-> \"before all\" hook for \"should return the result of the callback\"\n │ERROR Failed to release lock \"my_lock_with_ttl_extension\": version_conflict_engine_exception\n │ \tRoot causes:\n │ \t\tversion_conflict_engine_exception: [my_lock_with_ttl_extension]: version conflict, required seqNo [43], primary term [1]. current document has seqNo [44] and primary term [1]\n```\n\nFlaky tests:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8142","sha":"7275d2e8bd834303898e3f95c5fd1ab734e92947"}},{"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> |
||
|
Kibana Machine
|
766a251242
|
[8.x] [Streams 🌊] Add warning for dotted field names (#216154) (#216796)
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams 🌊] Add warning for dotted field names (#216154)](https://github.com/elastic/kibana/pull/216154) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2025-04-02T11:12:34Z","message":"[Streams 🌊] Add warning for dotted field names (#216154)\n\n## 📓 Summary\n\nCloses #215887 \n\nUntil the access to dotted fields is not supported, we'll warn the user\nabout the unreliability of the simulation outcome when using those\nfields in processor. configurations.\n\nThe unsupported fields that will make the warning appear are derived by\nthe sample docs, deriving a list of existing fields that have some\nnested dot-separated field names.\n\n\nhttps://github.com/user-attachments/assets/46228821-601c-4a32-995c-1699be6c4ce3\n\n## 🧪 Test\n\nTo reproduce it, ingest docs manually with\n```tsx\nPOST logs-mytest.otel-default/_doc\n{\n \"body\": {\n \"text\": \"This is the message\"\n },\n \"severity_text\": \"WARN\",\n \"resource\": {\n \"attributes\": {\n \"host.name\": \"my-host\",\n \"host.arch\": \"arm\"\n }\n }\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>","sha":"9797e95289125967d6c5bc2d66bb70b927a50b8d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams 🌊] Add warning for dotted field names","number":216154,"url":"https://github.com/elastic/kibana/pull/216154","mergeCommit":{"message":"[Streams 🌊] Add warning for dotted field names (#216154)\n\n## 📓 Summary\n\nCloses #215887 \n\nUntil the access to dotted fields is not supported, we'll warn the user\nabout the unreliability of the simulation outcome when using those\nfields in processor. configurations.\n\nThe unsupported fields that will make the warning appear are derived by\nthe sample docs, deriving a list of existing fields that have some\nnested dot-separated field names.\n\n\nhttps://github.com/user-attachments/assets/46228821-601c-4a32-995c-1699be6c4ce3\n\n## 🧪 Test\n\nTo reproduce it, ingest docs manually with\n```tsx\nPOST logs-mytest.otel-default/_doc\n{\n \"body\": {\n \"text\": \"This is the message\"\n },\n \"severity_text\": \"WARN\",\n \"resource\": {\n \"attributes\": {\n \"host.name\": \"my-host\",\n \"host.arch\": \"arm\"\n }\n }\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>","sha":"9797e95289125967d6c5bc2d66bb70b927a50b8d"}},"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/216154","number":216154,"mergeCommit":{"message":"[Streams 🌊] Add warning for dotted field names (#216154)\n\n## 📓 Summary\n\nCloses #215887 \n\nUntil the access to dotted fields is not supported, we'll warn the user\nabout the unreliability of the simulation outcome when using those\nfields in processor. configurations.\n\nThe unsupported fields that will make the warning appear are derived by\nthe sample docs, deriving a list of existing fields that have some\nnested dot-separated field names.\n\n\nhttps://github.com/user-attachments/assets/46228821-601c-4a32-995c-1699be6c4ce3\n\n## 🧪 Test\n\nTo reproduce it, ingest docs manually with\n```tsx\nPOST logs-mytest.otel-default/_doc\n{\n \"body\": {\n \"text\": \"This is the message\"\n },\n \"severity_text\": \"WARN\",\n \"resource\": {\n \"attributes\": {\n \"host.name\": \"my-host\",\n \"host.arch\": \"arm\"\n }\n }\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>","sha":"9797e95289125967d6c5bc2d66bb70b927a50b8d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com> |
||
Sonia Sanz Vivas
|
3a0e251f55
|
[UA] Update the styling of Elasticsearch and Kibana cards (#216604)
Fixes https://github.com/elastic/kibana/issues/211502 ## Summary This PR introduces some UI changes in the Upgrade Assistant deprecation cards. Since the `EuiStat` component had an `isLoading` prop and this component is no longer used, the loading state is now handled with some spinner. No changes have been made for the error state. Also removed the `_deprecation_issues_panel.scss` file since this css classes are not longer needed. |
||
|
Kibana Machine
|
f24bc22bfd
|
[8.x] [Lens] Disable Collapse by for metric chart when primary metric is not numeric (#216179) (#216787)
# Backport This will backport the following commits from `main` to `8.x`: - [[Lens] Disable Collapse by for metric chart when primary metric is not numeric (#216179)](https://github.com/elastic/kibana/pull/216179) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T09:58:24Z","message":"[Lens] Disable Collapse by for metric chart when primary metric is not numeric (#216179)\n\n## Summary\n\nFix part of #214593 \n\nThis PR fixes the Metric chart side of the `Collapse by` problem.\nIn shorts:\n* The `Collapse by` control disappears when the primary metric is not\nnumeric\n * while the UI hides it the state still holds it.\n* the `toExpression` is responsible to evaluate the current state and\nfind if `collapseFn` is compatible before adding it\n* The `Collapse by` control has moved into the Data section of the\npanel, aligning the Metric chart to the rest\n\n<img width=\"1057\" alt=\"Screenshot 2025-04-01 at 18 57 31\"\nsrc=\"https://github.com/user-attachments/assets/1d441329-3611-4452-a40d-54ea25964166\"\n/>\n<img width=\"1056\" alt=\"Screenshot 2025-04-01 at 18 57 12\"\nsrc=\"https://github.com/user-attachments/assets/66111c2a-957d-44dc-8361-45300df99662\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1a555fdc864b40183dab5d83e9cc31a517b1b120","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0"],"title":"[Lens] Disable Collapse by for metric chart when primary metric is not numeric","number":216179,"url":"https://github.com/elastic/kibana/pull/216179","mergeCommit":{"message":"[Lens] Disable Collapse by for metric chart when primary metric is not numeric (#216179)\n\n## Summary\n\nFix part of #214593 \n\nThis PR fixes the Metric chart side of the `Collapse by` problem.\nIn shorts:\n* The `Collapse by` control disappears when the primary metric is not\nnumeric\n * while the UI hides it the state still holds it.\n* the `toExpression` is responsible to evaluate the current state and\nfind if `collapseFn` is compatible before adding it\n* The `Collapse by` control has moved into the Data section of the\npanel, aligning the Metric chart to the rest\n\n<img width=\"1057\" alt=\"Screenshot 2025-04-01 at 18 57 31\"\nsrc=\"https://github.com/user-attachments/assets/1d441329-3611-4452-a40d-54ea25964166\"\n/>\n<img width=\"1056\" alt=\"Screenshot 2025-04-01 at 18 57 12\"\nsrc=\"https://github.com/user-attachments/assets/66111c2a-957d-44dc-8361-45300df99662\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1a555fdc864b40183dab5d83e9cc31a517b1b120"}},"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/216179","number":216179,"mergeCommit":{"message":"[Lens] Disable Collapse by for metric chart when primary metric is not numeric (#216179)\n\n## Summary\n\nFix part of #214593 \n\nThis PR fixes the Metric chart side of the `Collapse by` problem.\nIn shorts:\n* The `Collapse by` control disappears when the primary metric is not\nnumeric\n * while the UI hides it the state still holds it.\n* the `toExpression` is responsible to evaluate the current state and\nfind if `collapseFn` is compatible before adding it\n* The `Collapse by` control has moved into the Data section of the\npanel, aligning the Metric chart to the rest\n\n<img width=\"1057\" alt=\"Screenshot 2025-04-01 at 18 57 31\"\nsrc=\"https://github.com/user-attachments/assets/1d441329-3611-4452-a40d-54ea25964166\"\n/>\n<img width=\"1056\" alt=\"Screenshot 2025-04-01 at 18 57 12\"\nsrc=\"https://github.com/user-attachments/assets/66111c2a-957d-44dc-8361-45300df99662\"\n/>\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1a555fdc864b40183dab5d83e9cc31a517b1b120"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Kibana Machine
|
5814ace20b
|
[8.x] [ObsUX] [A11y] Fix focus on metadata table content (#216628) (#216778)
# Backport This will backport the following commits from `main` to `8.x`: - [[ObsUX] [A11y] Fix focus on metadata table content (#216628)](https://github.com/elastic/kibana/pull/216628) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T09:25:05Z","message":"[ObsUX] [A11y] Fix focus on metadata table content (#216628)\n\nCloses https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost Detail page has a Metadata tab with expandable table rows. These\nrows add content to the page in an unexpected reading order. Content\nshould be expanded underneath the show more / less trigger. Focus should\nstay on the toggle.\n\nBefore\n\n\n |
||
Ignacio Rivas
|
78472d3709
|
[UA] Enable a11y tests (#216599) | ||
|
Kibana Machine
|
54c692f815
|
[8.x] [Streams 🌊] Improve definition narrowing and reduntant requests (#215897) (#216754)
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams 🌊] Improve definition narrowing and reduntant requests (#215897)](https://github.com/elastic/kibana/pull/215897) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T14:10:57Z","message":"[Streams 🌊] Improve definition narrowing and reduntant requests (#215897)\n\n## 📓 Summary\n\nThese changes lift the check against the definition existence and\nnarrows its value for the react context consumers.\n\nIt also fixes reduntant requests for the AI connectors used for the grok\nparsing suggestions.\n\n@flash1293 I'd expect to use the AI capabilities across more places for\nthe enrichment experience, we should probably lift the AI capabilities\nas part of the page initialization at a certain point, although it's not\nneeded yet 👌","sha":"13b536aed87710e60adf9a7cc3df852a4fb50542","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams 🌊] Improve definition narrowing and reduntant requests","number":215897,"url":"https://github.com/elastic/kibana/pull/215897","mergeCommit":{"message":"[Streams 🌊] Improve definition narrowing and reduntant requests (#215897)\n\n## 📓 Summary\n\nThese changes lift the check against the definition existence and\nnarrows its value for the react context consumers.\n\nIt also fixes reduntant requests for the AI connectors used for the grok\nparsing suggestions.\n\n@flash1293 I'd expect to use the AI capabilities across more places for\nthe enrichment experience, we should probably lift the AI capabilities\nas part of the page initialization at a certain point, although it's not\nneeded yet 👌","sha":"13b536aed87710e60adf9a7cc3df852a4fb50542"}},"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/215897","number":215897,"mergeCommit":{"message":"[Streams 🌊] Improve definition narrowing and reduntant requests (#215897)\n\n## 📓 Summary\n\nThese changes lift the check against the definition existence and\nnarrows its value for the react context consumers.\n\nIt also fixes reduntant requests for the AI connectors used for the grok\nparsing suggestions.\n\n@flash1293 I'd expect to use the AI capabilities across more places for\nthe enrichment experience, we should probably lift the AI capabilities\nas part of the page initialization at a certain point, although it's not\nneeded yet 👌","sha":"13b536aed87710e60adf9a7cc3df852a4fb50542"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com> |
||
|
Kibana Machine
|
60be77eff8
|
[8.x] [Obs AI Assistant] Distributed lock manager (#216397) (#216737)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Distributed lock manager (#216397)](https://github.com/elastic/kibana/pull/216397) <!--- 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-04-01T22:26:00Z","message":"[Obs AI Assistant] Distributed lock manager (#216397)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/238\n\n\nThis introduces a lightweight library for managing distributed locks\nusing Elasticsearch. It lets developers coordinate operations across\nmultiple Kibana instances by ensuring that only one client holds a given\nlock at a time. The library uses an Elasticsearch index with TTL-based\nlocks.\n\nUsage:\n\n```ts\nconst lockManagerService = new LockManagerService(coreSetup, logger);\nlockManagerService.withLock('my_lock', () => {\n // perform operation\n});\n```","sha":"f4980d0fa3f90e8f3fddf5b3eb50102158d9ef80","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Distributed lock manager","number":216397,"url":"https://github.com/elastic/kibana/pull/216397","mergeCommit":{"message":"[Obs AI Assistant] Distributed lock manager (#216397)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/238\n\n\nThis introduces a lightweight library for managing distributed locks\nusing Elasticsearch. It lets developers coordinate operations across\nmultiple Kibana instances by ensuring that only one client holds a given\nlock at a time. The library uses an Elasticsearch index with TTL-based\nlocks.\n\nUsage:\n\n```ts\nconst lockManagerService = new LockManagerService(coreSetup, logger);\nlockManagerService.withLock('my_lock', () => {\n // perform operation\n});\n```","sha":"f4980d0fa3f90e8f3fddf5b3eb50102158d9ef80"}},"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/216397","number":216397,"mergeCommit":{"message":"[Obs AI Assistant] Distributed lock manager (#216397)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/238\n\n\nThis introduces a lightweight library for managing distributed locks\nusing Elasticsearch. It lets developers coordinate operations across\nmultiple Kibana instances by ensuring that only one client holds a given\nlock at a time. The library uses an Elasticsearch index with TTL-based\nlocks.\n\nUsage:\n\n```ts\nconst lockManagerService = new LockManagerService(coreSetup, logger);\nlockManagerService.withLock('my_lock', () => {\n // perform operation\n});\n```","sha":"f4980d0fa3f90e8f3fddf5b3eb50102158d9ef80"}},{"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> |
||
|
Kibana Machine
|
1eefc484ac
|
[8.x] [ML] Anomalies table: Enhances display for anomaly time function values (#216142) (#216755)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomalies table: Enhances display for anomaly time function values (#216142)](https://github.com/elastic/kibana/pull/216142) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T07:59:30Z","message":"[ML] Anomalies table: Enhances display for anomaly time function values (#216142)\n\nIntroducing tooltips and `+1` / `-1` subscripts for date values to\nimprove readability for the values of `time_of_day` anomaly detection\nfunction.\n\nFix for: https://github.com/elastic/kibana/issues/213882\nIt turns out the formatting was correct for the screenshot provided in\nthe issue as the upper bound is pointing to the next day.\n\n\n\n\nFormat following these changes:\n\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e510e533a4bc7f701467e34131064aaa207133ab","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","Team:ML","backport:version","v9.1.0","v8.19.0"],"title":"[ML] Anomalies table: Enhances display for anomaly time function values","number":216142,"url":"https://github.com/elastic/kibana/pull/216142","mergeCommit":{"message":"[ML] Anomalies table: Enhances display for anomaly time function values (#216142)\n\nIntroducing tooltips and `+1` / `-1` subscripts for date values to\nimprove readability for the values of `time_of_day` anomaly detection\nfunction.\n\nFix for: https://github.com/elastic/kibana/issues/213882\nIt turns out the formatting was correct for the screenshot provided in\nthe issue as the upper bound is pointing to the next day.\n\n\n\n\nFormat following these changes:\n\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e510e533a4bc7f701467e34131064aaa207133ab"}},"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/216142","number":216142,"mergeCommit":{"message":"[ML] Anomalies table: Enhances display for anomaly time function values (#216142)\n\nIntroducing tooltips and `+1` / `-1` subscripts for date values to\nimprove readability for the values of `time_of_day` anomaly detection\nfunction.\n\nFix for: https://github.com/elastic/kibana/issues/213882\nIt turns out the formatting was correct for the screenshot provided in\nthe issue as the upper bound is pointing to the next day.\n\n\n\n\nFormat following these changes:\n\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e510e533a4bc7f701467e34131064aaa207133ab"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
Stratoula Kalafateli
|
5b382c2fd5
|
[8.x] [ES|QL] Updates functions definitions manually (#216422) (#216746)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Updates functions definitions manually (#216422)](https://github.com/elastic/kibana/pull/216422) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T05:34:26Z","message":"[ES|QL] Updates functions definitions manually (#216422)\n\n## Summary\n\nManually updates the functions definitions.","sha":"a694b83c42ab3b619886b69d5095a0a13e4a06da","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Updates functions definitions manually","number":216422,"url":"https://github.com/elastic/kibana/pull/216422","mergeCommit":{"message":"[ES|QL] Updates functions definitions manually (#216422)\n\n## Summary\n\nManually updates the functions definitions.","sha":"a694b83c42ab3b619886b69d5095a0a13e4a06da"}},"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/216422","number":216422,"mergeCommit":{"message":"[ES|QL] Updates functions definitions manually (#216422)\n\n## Summary\n\nManually updates the functions definitions.","sha":"a694b83c42ab3b619886b69d5095a0a13e4a06da"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
12bb59fa8f
|
[8.x] [Synthetics] Fixed layout when monitors are grouped by (#216434) (#216750)
# Backport This will backport the following commits from `main` to `8.x`: - [[Synthetics] Fixed layout when monitors are grouped by (#216434)](https://github.com/elastic/kibana/pull/216434) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-02T07:27:10Z","message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Synthetics] Fixed layout when monitors are grouped by","number":216434,"url":"https://github.com/elastic/kibana/pull/216434","mergeCommit":{"message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228"}},"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/216434","number":216434,"mergeCommit":{"message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
Georgiana-Andreea Onoleață
|
8ebca65915
|
[8.x] [ResponseOps] Replace SCSS with CSS-in-JS (#214092) (#216640)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps] Replace SCSS with CSS-in-JS (#214092)](https://github.com/elastic/kibana/pull/214092) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T12:48:37Z","message":"[ResponseOps] Replace SCSS with CSS-in-JS (#214092)\n\nCloses https://github.com/elastic/kibana/issues/208303\n\n## Summary\n\n- This PR removes SCSS (Sass) from RO plugins and replaces it with\n`@emotion/react ` as recommended.","sha":"67c35302e36c6a557c8138697986c171d23e81b4","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","scss-removal"],"title":"[ResponseOps] Replace SCSS with CSS-in-JS","number":214092,"url":"https://github.com/elastic/kibana/pull/214092","mergeCommit":{"message":"[ResponseOps] Replace SCSS with CSS-in-JS (#214092)\n\nCloses https://github.com/elastic/kibana/issues/208303\n\n## Summary\n\n- This PR removes SCSS (Sass) from RO plugins and replaces it with\n`@emotion/react ` as recommended.","sha":"67c35302e36c6a557c8138697986c171d23e81b4"}},"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/214092","number":214092,"mergeCommit":{"message":"[ResponseOps] Replace SCSS with CSS-in-JS (#214092)\n\nCloses https://github.com/elastic/kibana/issues/208303\n\n## Summary\n\n- This PR removes SCSS (Sass) from RO plugins and replaces it with\n`@emotion/react ` as recommended.","sha":"67c35302e36c6a557c8138697986c171d23e81b4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Davis Plumlee
|
9c8b23ad7b
|
[8.x] [Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367) (#216734)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)](https://github.com/elastic/kibana/pull/212367) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T13:43:02Z","message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","APIDocs","Team:Detection Rule Management","backport:version","8.18 candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs","number":212367,"url":"https://github.com/elastic/kibana/pull/212367","mergeCommit":{"message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212367","number":212367,"mergeCommit":{"message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
6cc646b1d2
|
[8.x] [Security Solution][Detection Engine] Simplify rule preview route (#216384) (#216732)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Detection Engine] Simplify rule preview route (#216384)](https://github.com/elastic/kibana/pull/216384) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T21:31:58Z","message":"[Security Solution][Detection Engine] Simplify rule preview route (#216384)\n\n## Summary\n\nRefactors `runExecutors` to take a `SecurityAlertType` instead of an\nalerting framework `RuleType` and moves the logic to convert the\n`SecurityAlertType` into a `RuleType` into `runExecutors`. This makes\nthe signature of `runExecutors` much simpler and reduces a lot of the\nduplication in the `switch` below.","sha":"74722fd11b646a883c47c75b4d2ef88ebf5f457d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection Engine","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] Simplify rule preview route","number":216384,"url":"https://github.com/elastic/kibana/pull/216384","mergeCommit":{"message":"[Security Solution][Detection Engine] Simplify rule preview route (#216384)\n\n## Summary\n\nRefactors `runExecutors` to take a `SecurityAlertType` instead of an\nalerting framework `RuleType` and moves the logic to convert the\n`SecurityAlertType` into a `RuleType` into `runExecutors`. This makes\nthe signature of `runExecutors` much simpler and reduces a lot of the\nduplication in the `switch` below.","sha":"74722fd11b646a883c47c75b4d2ef88ebf5f457d"}},"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/216384","number":216384,"mergeCommit":{"message":"[Security Solution][Detection Engine] Simplify rule preview route (#216384)\n\n## Summary\n\nRefactors `runExecutors` to take a `SecurityAlertType` instead of an\nalerting framework `RuleType` and moves the logic to convert the\n`SecurityAlertType` into a `RuleType` into `runExecutors`. This makes\nthe signature of `runExecutors` much simpler and reduces a lot of the\nduplication in the `switch` below.","sha":"74722fd11b646a883c47c75b4d2ef88ebf5f457d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
Kibana Machine
|
4f8e104a6e
|
[8.x] [FIPS] Skips license check test for FIPS test suite (#216056) (#216729)
# Backport This will backport the following commits from `main` to `8.x`: - [[FIPS] Skips license check test for FIPS test suite (#216056)](https://github.com/elastic/kibana/pull/216056) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T21:23:35Z","message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Core","release_note:skip","v9.0.0","Feature:FIPS","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[FIPS] Skips license check test for FIPS test suite","number":216056,"url":"https://github.com/elastic/kibana/pull/216056","mergeCommit":{"message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},"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/216056","number":216056,"mergeCommit":{"message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},{"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: Sid <siddharthmantri1@gmail.com> |
||
|
Ignacio Rivas
|
5477873daf
|
[UA] Fix hardcoded docs path (#216595) | ||
|
Cauê Marcondes
|
93dafef6ae
|
[8.x] [APM] Fix query for transaction marks (#215819) (#216677)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Fix query for transaction marks (#215819)](https://github.com/elastic/kibana/pull/215819) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sunghyun Kim","email":"cqbqdd11519@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T15:05:42Z","message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","💝community","backport:all-open","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix query for transaction marks","number":215819,"url":"https://github.com/elastic/kibana/pull/215819","mergeCommit":{"message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}},"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/215819","number":215819,"mergeCommit":{"message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}}]}] BACKPORT--> Co-authored-by: Sunghyun Kim <cqbqdd11519@gmail.com> |
||
|
Georgiana-Andreea Onoleață
|
ecfc47e88b
|
[8.x] [ResponseOps] - fixes for a11y issues (#216129) (#216665)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps] - fixes for a11y issues (#216129)](https://github.com/elastic/kibana/pull/216129) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T14:31:00Z","message":"[ResponseOps] - fixes for a11y issues (#216129)\n\nCloses https://github.com/elastic/kibana/issues/205857\nCloses https://github.com/elastic/kibana/issues/205846\nCloses https://github.com/elastic/kibana/issues/205700\n\n## Summary\n\n- added the missing aria-labels\n\n- related to https://github.com/elastic/kibana/issues/205846:\n- \"Columns dialog in Alerts tab. Only drag handle is announced with\ninstructions, column names (Rule, Assignees...) are not announced.\" -\nEUI team has opened a related issue to address this:\nhttps://github.com/elastic/eui/issues/8516\n\n- related to https://github.com/elastic/kibana/issues/205700: \n- \"When reaching Description field - navigation instantly goes to \"Bold\nbutton\". No announcement about Description field itself\". This issue\nwill be fixed after fixing the EuiMarkdown toolbar focus one:\nhttps://github.com/elastic/eui/issues/3500","sha":"469e109edc84baf583f53983695c49abab3ac1fa","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] - fixes for a11y issues ","number":216129,"url":"https://github.com/elastic/kibana/pull/216129","mergeCommit":{"message":"[ResponseOps] - fixes for a11y issues (#216129)\n\nCloses https://github.com/elastic/kibana/issues/205857\nCloses https://github.com/elastic/kibana/issues/205846\nCloses https://github.com/elastic/kibana/issues/205700\n\n## Summary\n\n- added the missing aria-labels\n\n- related to https://github.com/elastic/kibana/issues/205846:\n- \"Columns dialog in Alerts tab. Only drag handle is announced with\ninstructions, column names (Rule, Assignees...) are not announced.\" -\nEUI team has opened a related issue to address this:\nhttps://github.com/elastic/eui/issues/8516\n\n- related to https://github.com/elastic/kibana/issues/205700: \n- \"When reaching Description field - navigation instantly goes to \"Bold\nbutton\". No announcement about Description field itself\". This issue\nwill be fixed after fixing the EuiMarkdown toolbar focus one:\nhttps://github.com/elastic/eui/issues/3500","sha":"469e109edc84baf583f53983695c49abab3ac1fa"}},"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/216129","number":216129,"mergeCommit":{"message":"[ResponseOps] - fixes for a11y issues (#216129)\n\nCloses https://github.com/elastic/kibana/issues/205857\nCloses https://github.com/elastic/kibana/issues/205846\nCloses https://github.com/elastic/kibana/issues/205700\n\n## Summary\n\n- added the missing aria-labels\n\n- related to https://github.com/elastic/kibana/issues/205846:\n- \"Columns dialog in Alerts tab. Only drag handle is announced with\ninstructions, column names (Rule, Assignees...) are not announced.\" -\nEUI team has opened a related issue to address this:\nhttps://github.com/elastic/eui/issues/8516\n\n- related to https://github.com/elastic/kibana/issues/205700: \n- \"When reaching Description field - navigation instantly goes to \"Bold\nbutton\". No announcement about Description field itself\". This issue\nwill be fixed after fixing the EuiMarkdown toolbar focus one:\nhttps://github.com/elastic/eui/issues/3500","sha":"469e109edc84baf583f53983695c49abab3ac1fa"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
442330ad94
|
[8.x] 🌊 Streams: Selectors for derived samples (#213638) (#216611)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Streams: Selectors for derived samples (#213638)](https://github.com/elastic/kibana/pull/213638) <!--- 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-04-01T09:47:31Z","message":"🌊 Streams: Selectors for derived samples (#213638)\n\nSimplified massively from first state and just plugging in reselect in\nplaces where that's suitable (here to calculate the currently relevant\nsample documents).\n\nAlso does a drive-by layout fix.\n\n~Introduces a new xstate helper for derived data.~\n\n~In most cases, the actor and state machine model of xstate is great,\nbut for derived data using pure functions, the semantics of the\n`useMemo` hook with defined dependencies is often easier to understand\nand eliminates the risk of forgetting to update the derived data\ncorrectly in some cases.~\n\n~It's about using the right tool for the right job - you don't need to\nchoose between the dependency list of useMemo and the actor model of\nxstate, you can use what fits the case, without compromising\nperformance.~\n\n~This is the API:~\n```ts\nconst myActorContext = withMemoizedSelectors(\n createActorContext(myMachine),\n {\n derivedView: createSelector(\n [\n (ctx: MyContextType) => {\n return ctx.dependency1;\n },\n (ctx: MyContextType) =>\n ctx.dependency2,\n ],\n (dependency1, dependency2) => {\n return // expensive calculation only running when necessary\n }\n ),\n },\n (context) => (context.subMachine ? [context.subMachine] : []) // optional subscribe to changes of submachines as well\n);\n\n\n// in react use useMemoizedSelector hook\n// this will cause the component to rerender if the selector is returning a new value\nmyActorContext.useMemoizedSelector('derivedView')\n```\n\n~This is using reselect to declare the dependencies similar to a react\nuseMemo hook - the actual selector will only run if the dependencies\nchange, leading to similar semantics as useMemo, with the additional\nbenefit that if the value is used in multiple places, it's still just\ncalculated once. The component calling `withMemoizedSelectors` only\nre-renders if the value returned by the selector changes. The selector\nitself only re-runs if one of the declared dependencies changes.~\n\n~Everything is type-safe by capturing the types of the reselect selector\nobject via inferred type param and using it in the `useMemoizedSelector`\ntype.~","sha":"c5e0b05454b124949de754556ec8ba5289445ab3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"🌊 Streams: Selectors for derived samples","number":213638,"url":"https://github.com/elastic/kibana/pull/213638","mergeCommit":{"message":"🌊 Streams: Selectors for derived samples (#213638)\n\nSimplified massively from first state and just plugging in reselect in\nplaces where that's suitable (here to calculate the currently relevant\nsample documents).\n\nAlso does a drive-by layout fix.\n\n~Introduces a new xstate helper for derived data.~\n\n~In most cases, the actor and state machine model of xstate is great,\nbut for derived data using pure functions, the semantics of the\n`useMemo` hook with defined dependencies is often easier to understand\nand eliminates the risk of forgetting to update the derived data\ncorrectly in some cases.~\n\n~It's about using the right tool for the right job - you don't need to\nchoose between the dependency list of useMemo and the actor model of\nxstate, you can use what fits the case, without compromising\nperformance.~\n\n~This is the API:~\n```ts\nconst myActorContext = withMemoizedSelectors(\n createActorContext(myMachine),\n {\n derivedView: createSelector(\n [\n (ctx: MyContextType) => {\n return ctx.dependency1;\n },\n (ctx: MyContextType) =>\n ctx.dependency2,\n ],\n (dependency1, dependency2) => {\n return // expensive calculation only running when necessary\n }\n ),\n },\n (context) => (context.subMachine ? [context.subMachine] : []) // optional subscribe to changes of submachines as well\n);\n\n\n// in react use useMemoizedSelector hook\n// this will cause the component to rerender if the selector is returning a new value\nmyActorContext.useMemoizedSelector('derivedView')\n```\n\n~This is using reselect to declare the dependencies similar to a react\nuseMemo hook - the actual selector will only run if the dependencies\nchange, leading to similar semantics as useMemo, with the additional\nbenefit that if the value is used in multiple places, it's still just\ncalculated once. The component calling `withMemoizedSelectors` only\nre-renders if the value returned by the selector changes. The selector\nitself only re-runs if one of the declared dependencies changes.~\n\n~Everything is type-safe by capturing the types of the reselect selector\nobject via inferred type param and using it in the `useMemoizedSelector`\ntype.~","sha":"c5e0b05454b124949de754556ec8ba5289445ab3"}},"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/213638","number":213638,"mergeCommit":{"message":"🌊 Streams: Selectors for derived samples (#213638)\n\nSimplified massively from first state and just plugging in reselect in\nplaces where that's suitable (here to calculate the currently relevant\nsample documents).\n\nAlso does a drive-by layout fix.\n\n~Introduces a new xstate helper for derived data.~\n\n~In most cases, the actor and state machine model of xstate is great,\nbut for derived data using pure functions, the semantics of the\n`useMemo` hook with defined dependencies is often easier to understand\nand eliminates the risk of forgetting to update the derived data\ncorrectly in some cases.~\n\n~It's about using the right tool for the right job - you don't need to\nchoose between the dependency list of useMemo and the actor model of\nxstate, you can use what fits the case, without compromising\nperformance.~\n\n~This is the API:~\n```ts\nconst myActorContext = withMemoizedSelectors(\n createActorContext(myMachine),\n {\n derivedView: createSelector(\n [\n (ctx: MyContextType) => {\n return ctx.dependency1;\n },\n (ctx: MyContextType) =>\n ctx.dependency2,\n ],\n (dependency1, dependency2) => {\n return // expensive calculation only running when necessary\n }\n ),\n },\n (context) => (context.subMachine ? [context.subMachine] : []) // optional subscribe to changes of submachines as well\n);\n\n\n// in react use useMemoizedSelector hook\n// this will cause the component to rerender if the selector is returning a new value\nmyActorContext.useMemoizedSelector('derivedView')\n```\n\n~This is using reselect to declare the dependencies similar to a react\nuseMemo hook - the actual selector will only run if the dependencies\nchange, leading to similar semantics as useMemo, with the additional\nbenefit that if the value is used in multiple places, it's still just\ncalculated once. The component calling `withMemoizedSelectors` only\nre-renders if the value returned by the selector changes. The selector\nitself only re-runs if one of the declared dependencies changes.~\n\n~Everything is type-safe by capturing the types of the reselect selector\nobject via inferred type param and using it in the `useMemoizedSelector`\ntype.~","sha":"c5e0b05454b124949de754556ec8ba5289445ab3"}},{"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> |
||
|
Kibana Machine
|
c374d67494
|
[8.x] [Index Management] Copy change for index mode field in index templates (#216624) (#216649)
# Backport This will backport the following commits from `main` to `8.x`: - [[Index Management] Copy change for index mode field in index templates (#216624)](https://github.com/elastic/kibana/pull/216624) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T13:31:25Z","message":"[Index Management] Copy change for index mode field in index templates (#216624)\n\n## Summary\n\nThis PR renames the title of the the index mode field from \"Data stream\nindex mode\" to \"Index mode\" since this field is no longer\nenabled/disabled based on the data streams field (since\nhttps://github.com/elastic/kibana/pull/207413).\n\nWe also switch the places of the index mode field and the data retention\nfield, since the data retention field is displayed only when data\nstreams toggle is switched on, so it makes sense that it is next to this\nfield.\n\n<img width=\"1166\" alt=\"Screenshot 2025-04-01 at 11 46 45\"\nsrc=\" |
||
jennypavlova
|
5c3aeabe36
|
[8.x] [APM][OTel] Add url.full fallback (#215397) (#216636)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM][OTel] Add url.full fallback (#215397)](https://github.com/elastic/kibana/pull/215397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:50:28Z","message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","ci:project-redeploy","v9.1.0"],"title":"[APM][OTel] Add url.full fallback","number":215397,"url":"https://github.com/elastic/kibana/pull/215397","mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}},"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/215397","number":215397,"mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
d9e5ea6f26
|
[8.x] [Streams] fixes the interval type used for the date histogram (#216258) (#216626)
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams] fixes the interval type used for the date histogram (#216258)](https://github.com/elastic/kibana/pull/216258) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Luca Wintergerst","email":"luca.wintergerst@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T11:24:01Z","message":"[Streams] fixes the interval type used for the date histogram (#216258)\n\n## Summary\ncloses https://github.com/elastic/streams-program/issues/225\n\nThe date histogram was hard coded to the fixed interval, which is not\nsuitable for all time ranges that `getCalculateAutoTimeExpression`\nreturns. This adds some logic to choose the correct agg setting.\nI am not sure if this is the cleanest way to solve this, but Lens is\ndoing something similar:\n\n\nhttps://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/lens/public/datasources/form_based/operations/definitions/date_histogram.tsx#L50\n\nBefore:\n\nAfter:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"30ad456181fa745d8e1ac6e1c93742ea9a4022ec","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams] fixes the interval type used for the date histogram","number":216258,"url":"https://github.com/elastic/kibana/pull/216258","mergeCommit":{"message":"[Streams] fixes the interval type used for the date histogram (#216258)\n\n## Summary\ncloses https://github.com/elastic/streams-program/issues/225\n\nThe date histogram was hard coded to the fixed interval, which is not\nsuitable for all time ranges that `getCalculateAutoTimeExpression`\nreturns. This adds some logic to choose the correct agg setting.\nI am not sure if this is the cleanest way to solve this, but Lens is\ndoing something similar:\n\n\nhttps://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/lens/public/datasources/form_based/operations/definitions/date_histogram.tsx#L50\n\nBefore:\n\nAfter:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"30ad456181fa745d8e1ac6e1c93742ea9a4022ec"}},"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/216258","number":216258,"mergeCommit":{"message":"[Streams] fixes the interval type used for the date histogram (#216258)\n\n## Summary\ncloses https://github.com/elastic/streams-program/issues/225\n\nThe date histogram was hard coded to the fixed interval, which is not\nsuitable for all time ranges that `getCalculateAutoTimeExpression`\nreturns. This adds some logic to choose the correct agg setting.\nI am not sure if this is the cleanest way to solve this, but Lens is\ndoing something similar:\n\n\nhttps://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/lens/public/datasources/form_based/operations/definitions/date_histogram.tsx#L50\n\nBefore:\n\nAfter:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"30ad456181fa745d8e1ac6e1c93742ea9a4022ec"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Luca Wintergerst <luca.wintergerst@elastic.co> |
||
|
Kibana Machine
|
009adee75e
|
[8.x] [Attack Discovery][Scheduling] Decouple AD generation logic from the postAttackDiscoveryRoute (#12036) (#216274) (#216625)
# Backport This will backport the following commits from `main` to `8.x`: - [[Attack Discovery][Scheduling] Decouple AD generation logic from the `postAttackDiscoveryRoute` (#12036) (#216274)](https://github.com/elastic/kibana/pull/216274) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T11:00:41Z","message":"[Attack Discovery][Scheduling] Decouple AD generation logic from the `postAttackDiscoveryRoute` (#12036) (#216274)\n\n## Summary\n\nThese changes decouple the core attack discovery generation\nfunctionality from the `POST\n/internal/elastic_assistant/attack_discovery` route.\n\nThis will allow us to use this functionality within the upcoming attack\ndiscovery schedule execution handler ([internal\nlink](https://github.com/elastic/security-team/issues/12004)).\n\nThere are no changes in the business logic of the attack discovery\ngeneration process and everything should continue working as before.","sha":"437065d9c81181f740033ad5db7bfab4ce6e679f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0"],"title":"[Attack Discovery][Scheduling] Decouple AD generation logic from the `postAttackDiscoveryRoute` (#12036)","number":216274,"url":"https://github.com/elastic/kibana/pull/216274","mergeCommit":{"message":"[Attack Discovery][Scheduling] Decouple AD generation logic from the `postAttackDiscoveryRoute` (#12036) (#216274)\n\n## Summary\n\nThese changes decouple the core attack discovery generation\nfunctionality from the `POST\n/internal/elastic_assistant/attack_discovery` route.\n\nThis will allow us to use this functionality within the upcoming attack\ndiscovery schedule execution handler ([internal\nlink](https://github.com/elastic/security-team/issues/12004)).\n\nThere are no changes in the business logic of the attack discovery\ngeneration process and everything should continue working as before.","sha":"437065d9c81181f740033ad5db7bfab4ce6e679f"}},"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/216274","number":216274,"mergeCommit":{"message":"[Attack Discovery][Scheduling] Decouple AD generation logic from the `postAttackDiscoveryRoute` (#12036) (#216274)\n\n## Summary\n\nThese changes decouple the core attack discovery generation\nfunctionality from the `POST\n/internal/elastic_assistant/attack_discovery` route.\n\nThis will allow us to use this functionality within the upcoming attack\ndiscovery schedule execution handler ([internal\nlink](https://github.com/elastic/security-team/issues/12004)).\n\nThere are no changes in the business logic of the attack discovery\ngeneration process and everything should continue working as before.","sha":"437065d9c81181f740033ad5db7bfab4ce6e679f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
3a1f8398fb
|
[8.x] 🌊 Streams: Restore orphaned streams functionality (#215517) (#216621)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Streams: Restore orphaned streams functionality (#215517)](https://github.com/elastic/kibana/pull/215517) <!--- 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-04-01T10:33:36Z","message":"🌊 Streams: Restore orphaned streams functionality (#215517)\n\nThere were a couple places where our UI and API would break on orphaned\nstreams (classic data streams that exist in the streams API but the\nunderlying data stream got deleted by the user). As discussed in\nhttps://github.com/elastic/streams-program/discussions/212 , we should\nhandle this case gracefully. This PR makes sure that the UI doesn't fail\nanywhere\n\n##\n`x-pack/platform/packages/shared/kbn-streams-schema/src/models/ingest/lifecycle/index.ts`\n\nAn unwired ingest stream effective lifecycle can also be an error if the\ndata stream doesn't exist. This was part of the typescript type, but not\nthe schema, so using our generated typeguards would fail.\n\n## `x-pack/platform/plugins/shared/streams/server/lib/streams/client.ts`\n\n`client.ensureStream` would not actually do what it claimed - it would\nnot throw if the stream didn't exist at all. Adjusted the logic so it\ndoes.\n\n##\n`x-pack/platform/plugins/shared/streams/server/routes/internal/streams/crud/route.ts`\n\n_details endpoint would throw if the data stream doesn't exist, but it\ncan just do the search and report a doc count of 0\n\n## All the other changes\n\nThis is more of a tangent, but I noticed that on switching to the\nmanagement tab it would reload the stream definition because it was a\ndifferent route, so the component holding the `useStreamsAppFetch` would\nremount.\n\nI fixed this by making the detail route a parent and the individual tabs\nchildren. It's a little awkward because the management tab is the only\none having subtabs. I moved the handling of this into the\n`StreamDetailViewContent` component because it wouldn't play well with\nour typing of routes otherwise, but the behavior is the same as before,\nwith the difference that the stream definition is not reloaded if not\nnecessary.\n\nAlso added some api-level tests to make sure it stays that way.","sha":"cc15d3ed656ea57b9ccc88f47e7a979649273088","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"🌊 Streams: Restore orphaned streams functionality","number":215517,"url":"https://github.com/elastic/kibana/pull/215517","mergeCommit":{"message":"🌊 Streams: Restore orphaned streams functionality (#215517)\n\nThere were a couple places where our UI and API would break on orphaned\nstreams (classic data streams that exist in the streams API but the\nunderlying data stream got deleted by the user). As discussed in\nhttps://github.com/elastic/streams-program/discussions/212 , we should\nhandle this case gracefully. This PR makes sure that the UI doesn't fail\nanywhere\n\n##\n`x-pack/platform/packages/shared/kbn-streams-schema/src/models/ingest/lifecycle/index.ts`\n\nAn unwired ingest stream effective lifecycle can also be an error if the\ndata stream doesn't exist. This was part of the typescript type, but not\nthe schema, so using our generated typeguards would fail.\n\n## `x-pack/platform/plugins/shared/streams/server/lib/streams/client.ts`\n\n`client.ensureStream` would not actually do what it claimed - it would\nnot throw if the stream didn't exist at all. Adjusted the logic so it\ndoes.\n\n##\n`x-pack/platform/plugins/shared/streams/server/routes/internal/streams/crud/route.ts`\n\n_details endpoint would throw if the data stream doesn't exist, but it\ncan just do the search and report a doc count of 0\n\n## All the other changes\n\nThis is more of a tangent, but I noticed that on switching to the\nmanagement tab it would reload the stream definition because it was a\ndifferent route, so the component holding the `useStreamsAppFetch` would\nremount.\n\nI fixed this by making the detail route a parent and the individual tabs\nchildren. It's a little awkward because the management tab is the only\none having subtabs. I moved the handling of this into the\n`StreamDetailViewContent` component because it wouldn't play well with\nour typing of routes otherwise, but the behavior is the same as before,\nwith the difference that the stream definition is not reloaded if not\nnecessary.\n\nAlso added some api-level tests to make sure it stays that way.","sha":"cc15d3ed656ea57b9ccc88f47e7a979649273088"}},"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/215517","number":215517,"mergeCommit":{"message":"🌊 Streams: Restore orphaned streams functionality (#215517)\n\nThere were a couple places where our UI and API would break on orphaned\nstreams (classic data streams that exist in the streams API but the\nunderlying data stream got deleted by the user). As discussed in\nhttps://github.com/elastic/streams-program/discussions/212 , we should\nhandle this case gracefully. This PR makes sure that the UI doesn't fail\nanywhere\n\n##\n`x-pack/platform/packages/shared/kbn-streams-schema/src/models/ingest/lifecycle/index.ts`\n\nAn unwired ingest stream effective lifecycle can also be an error if the\ndata stream doesn't exist. This was part of the typescript type, but not\nthe schema, so using our generated typeguards would fail.\n\n## `x-pack/platform/plugins/shared/streams/server/lib/streams/client.ts`\n\n`client.ensureStream` would not actually do what it claimed - it would\nnot throw if the stream didn't exist at all. Adjusted the logic so it\ndoes.\n\n##\n`x-pack/platform/plugins/shared/streams/server/routes/internal/streams/crud/route.ts`\n\n_details endpoint would throw if the data stream doesn't exist, but it\ncan just do the search and report a doc count of 0\n\n## All the other changes\n\nThis is more of a tangent, but I noticed that on switching to the\nmanagement tab it would reload the stream definition because it was a\ndifferent route, so the component holding the `useStreamsAppFetch` would\nremount.\n\nI fixed this by making the detail route a parent and the individual tabs\nchildren. It's a little awkward because the management tab is the only\none having subtabs. I moved the handling of this into the\n`StreamDetailViewContent` component because it wouldn't play well with\nour typing of routes otherwise, but the behavior is the same as before,\nwith the difference that the stream definition is not reloaded if not\nnecessary.\n\nAlso added some api-level tests to make sure it stays that way.","sha":"cc15d3ed656ea57b9ccc88f47e7a979649273088"}},{"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> |
||
|
Kibana Machine
|
deadd71f65
|
[8.x] [Fleet] enable flaky test (#216460) (#216590)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] enable flaky test (#216460)](https://github.com/elastic/kibana/pull/216460) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T08:29:23Z","message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\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":"69a7108313fab9520fb1f5f7281b5a17e76e3f92","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] enable flaky test","number":216460,"url":"https://github.com/elastic/kibana/pull/216460","mergeCommit":{"message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\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":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}},"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/216460","number":216460,"mergeCommit":{"message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\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":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}}]}] BACKPORT--> --------- Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
db3250bf8a
|
[8.x] [APM][OTel] Fix spanlink invalid filter (#215322) (#216608)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM][OTel] Fix spanlink invalid filter (#215322)](https://github.com/elastic/kibana/pull/215322) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:43:19Z","message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.5"],"title":"[APM][OTel] Fix spanlink invalid filter","number":215322,"url":"https://github.com/elastic/kibana/pull/215322","mergeCommit":{"message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18","8.17"],"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/215322","number":215322,"mergeCommit":{"message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
20425bc726
|
[8.x] [A11y][APM] Add aria-label to fold traces button (#216485) (#216600)
# Backport This will backport the following commits from `main` to `8.x`: - [[A11y][APM] Add `aria-label` to fold traces button (#216485)](https://github.com/elastic/kibana/pull/216485) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:06:55Z","message":"[A11y][APM] Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes #212228\n\nThis PR adds `aria-label` to the fold/unfold traces button.\n\n\n","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v9.1.0","v8.19.0"],"title":"[A11y][APM] Add `aria-label` to fold traces button","number":216485,"url":"https://github.com/elastic/kibana/pull/216485","mergeCommit":{"message":"[A11y][APM] Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes #212228\n\nThis PR adds `aria-label` to the fold/unfold traces button.\n\n\n","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba"}},"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/216485","number":216485,"mergeCommit":{"message":"[A11y][APM] Add `aria-label` to fold traces button (#216485)\n\n## Summary\n\nFixes #212228\n\nThis PR adds `aria-label` to the fold/unfold traces button.\n\n\n","sha":"54ce010161e754d43f8eac60cf4b8a1c7f621cba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
5561abe7fc
|
[8.x] [A11y][APM] Add aria-label to technical preview badge (#216483) (#216601)
# Backport This will backport the following commits from `main` to `8.x`: - [[A11y][APM] Add `aria-label` to technical preview badge (#216483)](https://github.com/elastic/kibana/pull/216483) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:08:27Z","message":"[A11y][APM] Add `aria-label` to technical preview badge (#216483)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis PR adds the `aria-label` prop so screen readers work with this\ntooltip text.\n\n","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v9.1.0","v8.19.0"],"title":"[A11y][APM] Add `aria-label` to technical preview badge","number":216483,"url":"https://github.com/elastic/kibana/pull/216483","mergeCommit":{"message":"[A11y][APM] Add `aria-label` to technical preview badge (#216483)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis PR adds the `aria-label` prop so screen readers work with this\ntooltip text.\n\n","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0"}},"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/216483","number":216483,"mergeCommit":{"message":"[A11y][APM] Add `aria-label` to technical preview badge (#216483)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/212093\n\nThis PR adds the `aria-label` prop so screen readers work with this\ntooltip text.\n\n","sha":"8767adc6222f5201a37bf6ed84ac4418d05b57a0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
e04403d7ba
|
[8.x] [Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393) (#216585)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)](https://github.com/elastic/kibana/pull/215393) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T08:07:08Z","message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f","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 Engine","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules","number":215393,"url":"https://github.com/elastic/kibana/pull/215393","mergeCommit":{"message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f"}},"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/215393","number":215393,"mergeCommit":{"message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
Antonio
|
7747f294a9
|
[8.x] [ResponseOps] Fix connector test (#208754) (#216587)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps] Fix connector test (#208754)](https://github.com/elastic/kibana/pull/208754) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-31T08:11:15Z","message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","backport missing","backport:prev-major","v8.18.0","v8.16.4","v8.17.2","v9.1.0"],"title":"[ResponseOps] Fix connector test","number":208754,"url":"https://github.com/elastic/kibana/pull/208754","mergeCommit":{"message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209061","number":209061,"state":"MERGED","mergeCommit":{"sha":"e67cc7a182ce649b1d08140dfacf2e2b1f56238d","message":"[8.18] [ResponseOps] Fix connector test (#208754) (#209061)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[ResponseOps] Fix connector test\n(#208754)](https://github.com/elastic/kibana/pull/208754)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Antonio <antonio.coelho@elastic.co>"}},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209058","number":209058,"state":"MERGED","mergeCommit":{"sha":"c2c44902042a48f2baf6fcc43191df210398f6a2","message":"[8.16] [ResponseOps] Fix connector test (#208754) (#209058)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[ResponseOps] Fix connector test\n(#208754)](https://github.com/elastic/kibana/pull/208754)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Antonio <antonio.coelho@elastic.co>"}},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209060","number":209060,"state":"MERGED","mergeCommit":{"sha":"c9595ceb0ba80b9d3d50ceb92a2e75564d3bfd2f","message":"[8.17] [ResponseOps] Fix connector test (#208754) (#209060)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[ResponseOps] Fix connector test\n(#208754)](https://github.com/elastic/kibana/pull/208754)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Antonio <antonio.coelho@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208754","number":208754,"mergeCommit":{"message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5"}}]}] BACKPORT--> |
||
Sergi Romeu
|
a89751c170
|
[8.x] [A11y][APM] Change tpm abbreviation to trace per minute for screen-readers (#216282) (#216581)
# Backport This will backport the following commits from `main` to `8.x`: - [[A11y][APM] Change tpm abbreviation to trace per minute for screen-readers (#216282)](https://github.com/elastic/kibana/pull/216282) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T15:36:26Z","message":"[A11y][APM] Change tpm abbreviation to trace per minute for screen-readers (#216282)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/194984\n\nThis PR uses the `EuiScreenReaderOnly` component to spell out trace per\nminute instead of its abbreviation for screen readers\n\n---------\n\nCo-authored-by: jennypavlova <jennypavlova94@gmail.com>","sha":"a23c6d066210bc4f29bd900e67c04387ed633f5a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","apm","Team:obs-ux-infra_services","backport:version","a11y","v9.1.0","v8.19.0"],"title":"[A11y][APM] Change tpm abbreviation to trace per minute for screen-readers","number":216282,"url":"https://github.com/elastic/kibana/pull/216282","mergeCommit":{"message":"[A11y][APM] Change tpm abbreviation to trace per minute for screen-readers (#216282)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/194984\n\nThis PR uses the `EuiScreenReaderOnly` component to spell out trace per\nminute instead of its abbreviation for screen readers\n\n---------\n\nCo-authored-by: jennypavlova <jennypavlova94@gmail.com>","sha":"a23c6d066210bc4f29bd900e67c04387ed633f5a"}},"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/216282","number":216282,"mergeCommit":{"message":"[A11y][APM] Change tpm abbreviation to trace per minute for screen-readers (#216282)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/194984\n\nThis PR uses the `EuiScreenReaderOnly` component to spell out trace per\nminute instead of its abbreviation for screen readers\n\n---------\n\nCo-authored-by: jennypavlova <jennypavlova94@gmail.com>","sha":"a23c6d066210bc4f29bd900e67c04387ed633f5a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Julian Gernun
|
992fd3a9ca
|
[8.x] [Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145) (#216473)
# Backport Closes https://github.com/elastic/kibana/issues/202328 This will backport the following commits from `main` to `8.x`: - [[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)](https://github.com/elastic/kibana/pull/216145) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-28T11:43:25Z","message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Response Ops][Flaky Tests] Remove duplicated click creating connector","number":216145,"url":"https://github.com/elastic/kibana/pull/216145","mergeCommit":{"message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216281","number":216281,"state":"MERGED","mergeCommit":{"sha":"391a07f3d1ba07910a5dc2b38ded98a9468c86e5","message":"[9.0] [Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145) (#216281)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Response Ops][Flaky Tests] Remove duplicated click creating\nconnector (#216145)](https://github.com/elastic/kibana/pull/216145)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216280","number":216280,"state":"MERGED","mergeCommit":{"sha":"24c65a5dcc93040cd5900b6c85175a20be7e2fb0","message":"[8.18] [Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145) (#216280)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Response Ops][Flaky Tests] Remove duplicated click creating\nconnector (#216145)](https://github.com/elastic/kibana/pull/216145)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216145","number":216145,"mergeCommit":{"message":"[Response Ops][Flaky Tests] Remove duplicated click creating connector (#216145)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202328\n\nThe test itself wasn't failing but the setup was. The test failing does\nso because it's the first one in the test suite. We are trying to click\non the flyout save button twice one right after the other. What I think\nis happening is that the first one manages to close the flyout before\nthe second click gets the chance to trigger.\n\nAlso the image in CI is this where we can see the flyout is closed\nalready but it's still trying to close it\n\n","sha":"e16ba346e39df1843b45017137d4c894c357bb13"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
5011aafb0e
|
[8.x] [Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity (#215699) (#216119)
# Backport This will backport the following commits from `main` to `8.x`: - [[Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity (#215699)](https://github.com/elastic/kibana/pull/215699) <!--- 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-27T02:31:01Z","message":"[Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity (#215699)\n\nCloses https://github.com/elastic/kibana/issues/214801\n\n## Summary\n\nIn the recall and score function and score suggestions function we refer\nto both Elasticsearch score and LLM score as `score`. This is confusing\nand difficult to differentiate.\n\nThis PR renames the `score` property based on the context of the score\nto either `esScore` or `llmScore`.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"34cf355080b3e4ea346da4c86801f4fb4f6824cd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity","number":215699,"url":"https://github.com/elastic/kibana/pull/215699","mergeCommit":{"message":"[Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity (#215699)\n\nCloses https://github.com/elastic/kibana/issues/214801\n\n## Summary\n\nIn the recall and score function and score suggestions function we refer\nto both Elasticsearch score and LLM score as `score`. This is confusing\nand difficult to differentiate.\n\nThis PR renames the `score` property based on the context of the score\nto either `esScore` or `llmScore`.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"34cf355080b3e4ea346da4c86801f4fb4f6824cd"}},"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/215699","number":215699,"mergeCommit":{"message":"[Obs AI Assistant] Rename score properties to esScore and llmScore for more clarity (#215699)\n\nCloses https://github.com/elastic/kibana/issues/214801\n\n## Summary\n\nIn the recall and score function and score suggestions function we refer\nto both Elasticsearch score and LLM score as `score`. This is confusing\nand difficult to differentiate.\n\nThis PR renames the `score` property based on the context of the score\nto either `esScore` or `llmScore`.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"34cf355080b3e4ea346da4c86801f4fb4f6824cd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
seanrathier
|
15dfadbcf7
|
[8.x] [Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239) (#216546)
# Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)](https://github.com/elastic/kibana/pull/216239) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-03-31T15:04:28Z","message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76","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:Cloud Security","backport:prev-minor","v9.1.0","backport:8.18"],"title":"[Cloud Security] Hide agentless traffic filtering callout in Serverless","number":216239,"url":"https://github.com/elastic/kibana/pull/216239","mergeCommit":{"message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216496","number":216496,"state":"MERGED","mergeCommit":{"sha":"bb3ac40a5cf5cb62248f8ae25562064af8ea3330","message":"[9.0] [Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239) (#216496)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Cloud Security] Hide agentless traffic filtering callout in\nServerless (#216239)](https://github.com/elastic/kibana/pull/216239)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: seanrathier <sean.rathier@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216239","number":216239,"mergeCommit":{"message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}}]}] BACKPORT--> |
||
Meghan Murphy
|
5b07825d6c
|
[Search] enable enterpriseSearch plugin in Security (#216234)
## Summary This PR enables Enterprise Search in 8.x for Security spaces so that connectors and crawlers are available. ### Closes https://github.com/elastic/search-team/issues/9281 <img width="1899" alt="Screenshot 2025-03-27 at 4 27 02 PM" src="https://github.com/user-attachments/assets/d3ab37f3-c6b4-4bdb-8650-0b71feffe4bc" /> <img width="1903" alt="Screenshot 2025-03-27 at 4 27 09 PM" src="https://github.com/user-attachments/assets/eb0043c6-7781-4024-bc36-7f6cb11d2269" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a75155043b
|
[8.x] [Security Solution] Improve documentation for version and revision fields (#216074) (#216531)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Improve documentation for `version` and `revision` fields (#216074)](https://github.com/elastic/kibana/pull/216074) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T18:06:13Z","message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","APIDocs","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","9.1 candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Improve documentation for `version` and `revision` fields","number":216074,"url":"https://github.com/elastic/kibana/pull/216074","mergeCommit":{"message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216074","number":216074,"mergeCommit":{"message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
3832386eaf
|
[8.x] [Lens] Show drag and drop options in the in-line editor (#215892) (#216518)
# Backport This will backport the following commits from `main` to `8.x`: - [[Lens] Show drag and drop options in the in-line editor (#215892)](https://github.com/elastic/kibana/pull/215892) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maria Iriarte","email":"106958839+mariairiartef@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-25T17:04:09Z","message":"[Lens] Show drag and drop options in the in-line editor (#215892)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215441\n\nAdds the euiYScroll styles only to the Lens Editor app, not to the Lens\nin-line editor.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Screen recording\n\n\nhttps://github.com/user-attachments/assets/3e86bcb8-f79d-4b96-91f8-e04d53a510ad","sha":"f62960c1d872e7dffef0a64ef94f3b3470b4b158","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport missing","backport:version","v9.1.0","v8.19.0"],"title":"[Lens] Show drag and drop options in the in-line editor","number":215892,"url":"https://github.com/elastic/kibana/pull/215892","mergeCommit":{"message":"[Lens] Show drag and drop options in the in-line editor (#215892)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215441\n\nAdds the euiYScroll styles only to the Lens Editor app, not to the Lens\nin-line editor.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Screen recording\n\n\nhttps://github.com/user-attachments/assets/3e86bcb8-f79d-4b96-91f8-e04d53a510ad","sha":"f62960c1d872e7dffef0a64ef94f3b3470b4b158"}},"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/215892","number":215892,"mergeCommit":{"message":"[Lens] Show drag and drop options in the in-line editor (#215892)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215441\n\nAdds the euiYScroll styles only to the Lens Editor app, not to the Lens\nin-line editor.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Screen recording\n\n\nhttps://github.com/user-attachments/assets/3e86bcb8-f79d-4b96-91f8-e04d53a510ad","sha":"f62960c1d872e7dffef0a64ef94f3b3470b4b158"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maria Iriarte <106958839+mariairiartef@users.noreply.github.com> |
||
Arturo Lidueña
|
3a77581d58
|
[8.x] [obs AI Assistant] fix title_conversation failing test (#216112) (#216511)
# Backport This will backport the following commits from `main` to `8.x`: - [[obs AI Assistant] fix title_conversation failing test (#216112)](https://github.com/elastic/kibana/pull/216112) <!--- 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-31T14:56:32Z","message":"[obs AI Assistant] fix title_conversation failing test (#216112)\n\nCloses #215952\n\n[obs AI Assistant] fix title_conversation failing test","sha":"3c9593b1a62aaa34922f27b2689699f2e545f37f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"[obs AI Assistant] fix title_conversation failing test","number":216112,"url":"https://github.com/elastic/kibana/pull/216112","mergeCommit":{"message":"[obs AI Assistant] fix title_conversation failing test (#216112)\n\nCloses #215952\n\n[obs AI Assistant] fix title_conversation failing test","sha":"3c9593b1a62aaa34922f27b2689699f2e545f37f"}},"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/216112","number":216112,"mergeCommit":{"message":"[obs AI Assistant] fix title_conversation failing test (#216112)\n\nCloses #215952\n\n[obs AI Assistant] fix title_conversation failing test","sha":"3c9593b1a62aaa34922f27b2689699f2e545f37f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |