mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
83660 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
e5bb57656c
|
[8.x] [ES|QL] fix editor menus on safari (#218167) (#218342)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] fix editor menus on safari (#218167)](https://github.com/elastic/kibana/pull/218167) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Drew Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T19:26:27Z","message":"[ES|QL] fix editor menus on safari (#218167)\n\n## Summary\n\nFix https://github.com/elastic/kibana/issues/215405\n\nTooltips still work:\n\n<img width=\"524\" alt=\"Screenshot 2025-04-14 at 1 03 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/5a28d2e4-af75-455f-9df1-691493460cc7\"\n/>\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"7ee7edb5e5165f4537659f271e604528807415b3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] fix editor menus on safari","number":218167,"url":"https://github.com/elastic/kibana/pull/218167","mergeCommit":{"message":"[ES|QL] fix editor menus on safari (#218167)\n\n## Summary\n\nFix https://github.com/elastic/kibana/issues/215405\n\nTooltips still work:\n\n<img width=\"524\" alt=\"Screenshot 2025-04-14 at 1 03 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/5a28d2e4-af75-455f-9df1-691493460cc7\"\n/>\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"7ee7edb5e5165f4537659f271e604528807415b3"}},"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/218167","number":218167,"mergeCommit":{"message":"[ES|QL] fix editor menus on safari (#218167)\n\n## Summary\n\nFix https://github.com/elastic/kibana/issues/215405\n\nTooltips still work:\n\n<img width=\"524\" alt=\"Screenshot 2025-04-14 at 1 03 17 PM\"\nsrc=\"https://github.com/user-attachments/assets/5a28d2e4-af75-455f-9df1-691493460cc7\"\n/>\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"7ee7edb5e5165f4537659f271e604528807415b3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Drew Tate <drew.tate@elastic.co> |
||
Nick Peihl
|
fc686c5527
|
[8.x] [Dashboards] Replace contentClient with getContentClient on DashboardStart server api (#217586) (#217989)
# Backport This will backport the following commits from `main` to `8.x`: - [[Dashboards] Replace contentClient with getContentClient on DashboardStart server api (#217586)](https://github.com/elastic/kibana/pull/217586) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nick Peihl","email":"nick.peihl@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T18:52:38Z","message":"[Dashboards] Replace contentClient with getContentClient on DashboardStart server api (#217586)\n\n## Summary\n\nChanges the DashboardStart server api to provide a getContentClient\nfunction.\n\nIn https://github.com/elastic/kibana/pull/214788, we set the\n`contentClient` returned from the content management register method\nafter start lifecycle of all plugins. This means the `contentClient`\nreturned from the `DashboardStart` contract was undefined. This PR\nchanges the start contract to provide a getContentClient function\ninstead.\n\nOnly one consumer was using the contentClient from DashboardStart and\nthis PR also updates that consumer.","sha":"72d18d8b992c99bb0be42123406453f0379f29d8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:plugin_api_changes","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Dashboards] Replace contentClient with getContentClient on DashboardStart server api","number":217586,"url":"https://github.com/elastic/kibana/pull/217586","mergeCommit":{"message":"[Dashboards] Replace contentClient with getContentClient on DashboardStart server api (#217586)\n\n## Summary\n\nChanges the DashboardStart server api to provide a getContentClient\nfunction.\n\nIn https://github.com/elastic/kibana/pull/214788, we set the\n`contentClient` returned from the content management register method\nafter start lifecycle of all plugins. This means the `contentClient`\nreturned from the `DashboardStart` contract was undefined. This PR\nchanges the start contract to provide a getContentClient function\ninstead.\n\nOnly one consumer was using the contentClient from DashboardStart and\nthis PR also updates that consumer.","sha":"72d18d8b992c99bb0be42123406453f0379f29d8"}},"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/217586","number":217586,"mergeCommit":{"message":"[Dashboards] Replace contentClient with getContentClient on DashboardStart server api (#217586)\n\n## Summary\n\nChanges the DashboardStart server api to provide a getContentClient\nfunction.\n\nIn https://github.com/elastic/kibana/pull/214788, we set the\n`contentClient` returned from the content management register method\nafter start lifecycle of all plugins. This means the `contentClient`\nreturned from the `DashboardStart` contract was undefined. This PR\nchanges the start contract to provide a getContentClient function\ninstead.\n\nOnly one consumer was using the contentClient from DashboardStart and\nthis PR also updates that consumer.","sha":"72d18d8b992c99bb0be42123406453f0379f29d8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
f94c41e8a8
|
[8.x] [Attack Discovery][Scheduling] Fix the attack discovery alert type (#218025) (#218312)
# Backport This will backport the following commits from `main` to `8.x`: - [[Attack Discovery][Scheduling] Fix the attack discovery alert type (#218025)](https://github.com/elastic/kibana/pull/218025) <!--- 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-15T16:18:33Z","message":"[Attack Discovery][Scheduling] Fix the attack discovery alert type (#218025)\n\n## Summary\n\nThis is a fix for the incorrectly generated attack discovery alert\nschema type due to the limitation of the generation tool.","sha":"34df5e3328ed1c88c46d0ab0e2f8024b184e87c3","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] Fix the attack discovery alert type","number":218025,"url":"https://github.com/elastic/kibana/pull/218025","mergeCommit":{"message":"[Attack Discovery][Scheduling] Fix the attack discovery alert type (#218025)\n\n## Summary\n\nThis is a fix for the incorrectly generated attack discovery alert\nschema type due to the limitation of the generation tool.","sha":"34df5e3328ed1c88c46d0ab0e2f8024b184e87c3"}},"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/218025","number":218025,"mergeCommit":{"message":"[Attack Discovery][Scheduling] Fix the attack discovery alert type (#218025)\n\n## Summary\n\nThis is a fix for the incorrectly generated attack discovery alert\nschema type due to the limitation of the generation tool.","sha":"34df5e3328ed1c88c46d0ab0e2f8024b184e87c3"}},{"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
|
8d179fbe61
|
[8.x] [Custom threshold rule] Allow group for ip type fields !! (#216062) (#218337)
# Backport This will backport the following commits from `main` to `8.x`: - [[Custom threshold rule] Allow group for ip type fields !! (#216062)](https://github.com/elastic/kibana/pull/216062) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T18:15:02Z","message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:all-open","Team:obs-ux-management","v9.1.0"],"title":"[Custom threshold rule] Allow group for ip type fields !!","number":216062,"url":"https://github.com/elastic/kibana/pull/216062","mergeCommit":{"message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216062","number":216062,"mergeCommit":{"message":"[Custom threshold rule] Allow group for ip type fields !! (#216062)\n\nAllow group by for ip fields !!\n\n---------\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"83f3d614ccb66bca3aa626a6db39c0f41eb1a9f1"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
d6d6b66cbe
|
[8.x] [Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123) (#218248)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)](https://github.com/elastic/kibana/pull/218123) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T11:45:08Z","message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint","number":218123,"url":"https://github.com/elastic/kibana/pull/218123","mergeCommit":{"message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218123","number":218123,"mergeCommit":{"message":"[Security Solution] Suppress prebuilt rule SO duplicates in review install endpoint (#218123)\n\n## Summary\n\nThis PR makes sure a buggy `security_detection_engine` package doesn't affect a preview installation endpoint. Older security detection rules package versions contain saved object rule duplicates affecting the endpoint.\n\nHaving `security_detection_engine` v`8.17.1` package installed `/internal/detection_engine/prebuilt_rules/status` and `/internal/detection_engine/prebuilt_rules/installation/_review` endpoints return a different number of rules available to install.\n\n## Details\n\nOlder `security_detection_engine` package versions contain rule saved objects duplicates representing the latest version. For example, `8.17.1` version has a rule `Microsoft 365 User Restricted from Sending Email` with `rule_id` = `0136b315-b566-482f-866c-1d8e2477ba16` and the latest version `206`. Since a package may contain multiple historical rule versions it sticks to the following format `<rule_id>_<version>` where `<rule_id>` is the unique rule's UUID and `<version>` it's version. Some older package versions omit `<version>` for the latest rule version. `Microsoft 365 User Restricted from Sending Email` rule mentioned above has two equal assets corresponding to the latest version with the only difference in the saved object id `0136b315-b566-482f-866c-1d8e2477ba16` and `0136b315-b566-482f-866c-1d8e2477ba16_206`.\n\nPrebuilt rules preview endpoint was designed to handle `<rule_id>_<version>` format only. Consequently, it improperly handles older prebuilt rules package version.\n\nThis bug manifested in https://github.com/elastic/kibana/pull/217544 where `security_detection_engine` version has been bumped to `8.18.1`. It resulted in a failed integration test. Further investigation has shown that the test installs an older package version `8.17.1` to assert prebuilt rules upgrade workflow works correctly.\n\nThe fix is implemented in `PrebuiltRuleAssetsClient.fetchAssetsByVersion()` by using `Map` to deduplicate prebuilt rule assets.","sha":"87f8274f4160f4d94f25d19f7d71ec4c35f4431e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
Eyo O. Eyo
|
d9d45e1662
|
[8.x] Fix issue with "Let Us Know" button getting hidden when Management Menu is open (#211728) (#218307)
# Backport This will backport the following commits from `main` to `8.x`: - [Fix issue with "Let Us Know" button getting hidden when Management Menu is open (#211728)](https://github.com/elastic/kibana/pull/211728) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-19T17:55:27Z","message":"Fix issue with \"Let Us Know\" button getting hidden when Management Menu is open (#211728)\n\n## Summary\n\nCloses #210919\n\n## Visuals\n\n\nhttps://github.com/user-attachments/assets/0a2f3306-5e85-42f5-a28f-b3e9ca18f1a4\n\n","sha":"5027fd6d5526506e9befd28fca98e2cf2936944d","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:SharedUX","backport:prev-minor","v9.1.0"],"title":"Fix issue with \"Let Us Know\" button getting hidden when Management Menu is open","number":211728,"url":"https://github.com/elastic/kibana/pull/211728","mergeCommit":{"message":"Fix issue with \"Let Us Know\" button getting hidden when Management Menu is open (#211728)\n\n## Summary\n\nCloses #210919\n\n## Visuals\n\n\nhttps://github.com/user-attachments/assets/0a2f3306-5e85-42f5-a28f-b3e9ca18f1a4\n\n","sha":"5027fd6d5526506e9befd28fca98e2cf2936944d"}},"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/211823","number":211823,"state":"MERGED","mergeCommit":{"sha":"70f1501af556694815b4162fa4834758861b8ad6","message":"[9.0] Fix issue with \"Let Us Know\" button getting hidden when Management Menu is open (#211728) (#211823)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Fix issue with \"Let Us Know\" button getting hidden when Management\nMenu is open (#211728)](https://github.com/elastic/kibana/pull/211728)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Eyo O. Eyo <7893459+eokoneyo@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/211728","number":211728,"mergeCommit":{"message":"Fix issue with \"Let Us Know\" button getting hidden when Management Menu is open (#211728)\n\n## Summary\n\nCloses #210919\n\n## Visuals\n\n\nhttps://github.com/user-attachments/assets/0a2f3306-5e85-42f5-a28f-b3e9ca18f1a4\n\n","sha":"5027fd6d5526506e9befd28fca98e2cf2936944d"}}]}] BACKPORT--> |
||
Marco Vettorello
|
13af80f2d4
|
[8.x] [Charts] Use chartTheme hook everywhere (#217370) (#218147)
# Backport This will backport the following commits from `main` to `8.x`: - [[Charts] Use chartTheme hook everywhere (#217370)](https://github.com/elastic/kibana/pull/217370) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T16:09:15Z","message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ElasticCharts","Team:Visualizations","release_note:skip","Team:obs-ux-infra_services","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Charts] Use chartTheme hook everywhere","number":217370,"url":"https://github.com/elastic/kibana/pull/217370","mergeCommit":{"message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b"}},"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/217370","number":217370,"mergeCommit":{"message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a7c7522b6d
|
[8.x] [ResponseOps][Connectors] throw error for empty correlationId or incidentId (#217639) (#218295)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Connectors] throw error for empty correlationId or incidentId (#217639)](https://github.com/elastic/kibana/pull/217639) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Janki Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T15:10:16Z","message":"[ResponseOps][Connectors] throw error for empty correlationId or incidentId (#217639)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/217004\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":"0aeadb80cae3b64b8044d0a3f5da916d849cc8a6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Actions/ConnectorTypes","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Connectors] throw error for empty correlationId or incidentId","number":217639,"url":"https://github.com/elastic/kibana/pull/217639","mergeCommit":{"message":"[ResponseOps][Connectors] throw error for empty correlationId or incidentId (#217639)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/217004\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":"0aeadb80cae3b64b8044d0a3f5da916d849cc8a6"}},"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/217639","number":217639,"mergeCommit":{"message":"[ResponseOps][Connectors] throw error for empty correlationId or incidentId (#217639)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/217004\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":"0aeadb80cae3b64b8044d0a3f5da916d849cc8a6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com> |
||
|
Kibana Machine
|
0e10b2ea53
|
[8.x] [Streams 🌊] Schema editor bug fixes (#218225) (#218269)
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams 🌊] Schema editor bug fixes (#218225)](https://github.com/elastic/kibana/pull/218225) <!--- 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-15T13:36:09Z","message":"[Streams 🌊] Schema editor bug fixes (#218225)\n\n## 📓 Summary\n\nThese changes address various minor issues reported on the Schema\nEditor.\n\nCloses #217888 \nCloses #217889\nCloses #217891\nCloses #217892\nCloses #217893 \n\n### [Streams 🌊] \"System managed\" appears in the list of field types in\nthe schema editor\n\n<img width=\"659\" alt=\"Screenshot 2025-04-15 at 10 50 37\"\nsrc=\"https://github.com/user-attachments/assets/5f9e832a-e7ea-4e19-9507-2bd3669c7043\"\n/>\n\n### [Streams 🌊] Clicking the link in the schema editor to edit a field\nmapping in the parent stream loads a new page\n\n\nhttps://github.com/user-attachments/assets/de1a1b09-5eca-4143-a822-2de6814333b6\n\n### [Streams 🌊] Saving changes in the schema editor for an inherited\nfield results in error\n\n\nhttps://github.com/user-attachments/assets/603c8a89-6df3-474a-91bc-ee7bbee0f250\n\n### [Streams 🌊] Disable submit button when there is invalid input for\nmapping in the schema editor\n\n\nhttps://github.com/user-attachments/assets/22dfb91a-fa37-4b68-a8c5-c5f3a89a98e5\n\n### Advanced fields mapping simulation and client-side validation\n\n\nhttps://github.com/user-attachments/assets/faf99f86-5074-4587-9cc6-65f39f3595e9\n\n### [Streams 🌊] Increase width in the type filter popup in schema editor\n\n\nhttps://github.com/user-attachments/assets/b6eab484-308b-42dd-887b-560fb91986da","sha":"d36b269e60308a6b0a5db19b2eac047d2fd51f9d","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 🌊] Schema editor bug fixes","number":218225,"url":"https://github.com/elastic/kibana/pull/218225","mergeCommit":{"message":"[Streams 🌊] Schema editor bug fixes (#218225)\n\n## 📓 Summary\n\nThese changes address various minor issues reported on the Schema\nEditor.\n\nCloses #217888 \nCloses #217889\nCloses #217891\nCloses #217892\nCloses #217893 \n\n### [Streams 🌊] \"System managed\" appears in the list of field types in\nthe schema editor\n\n<img width=\"659\" alt=\"Screenshot 2025-04-15 at 10 50 37\"\nsrc=\"https://github.com/user-attachments/assets/5f9e832a-e7ea-4e19-9507-2bd3669c7043\"\n/>\n\n### [Streams 🌊] Clicking the link in the schema editor to edit a field\nmapping in the parent stream loads a new page\n\n\nhttps://github.com/user-attachments/assets/de1a1b09-5eca-4143-a822-2de6814333b6\n\n### [Streams 🌊] Saving changes in the schema editor for an inherited\nfield results in error\n\n\nhttps://github.com/user-attachments/assets/603c8a89-6df3-474a-91bc-ee7bbee0f250\n\n### [Streams 🌊] Disable submit button when there is invalid input for\nmapping in the schema editor\n\n\nhttps://github.com/user-attachments/assets/22dfb91a-fa37-4b68-a8c5-c5f3a89a98e5\n\n### Advanced fields mapping simulation and client-side validation\n\n\nhttps://github.com/user-attachments/assets/faf99f86-5074-4587-9cc6-65f39f3595e9\n\n### [Streams 🌊] Increase width in the type filter popup in schema editor\n\n\nhttps://github.com/user-attachments/assets/b6eab484-308b-42dd-887b-560fb91986da","sha":"d36b269e60308a6b0a5db19b2eac047d2fd51f9d"}},"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/218225","number":218225,"mergeCommit":{"message":"[Streams 🌊] Schema editor bug fixes (#218225)\n\n## 📓 Summary\n\nThese changes address various minor issues reported on the Schema\nEditor.\n\nCloses #217888 \nCloses #217889\nCloses #217891\nCloses #217892\nCloses #217893 \n\n### [Streams 🌊] \"System managed\" appears in the list of field types in\nthe schema editor\n\n<img width=\"659\" alt=\"Screenshot 2025-04-15 at 10 50 37\"\nsrc=\"https://github.com/user-attachments/assets/5f9e832a-e7ea-4e19-9507-2bd3669c7043\"\n/>\n\n### [Streams 🌊] Clicking the link in the schema editor to edit a field\nmapping in the parent stream loads a new page\n\n\nhttps://github.com/user-attachments/assets/de1a1b09-5eca-4143-a822-2de6814333b6\n\n### [Streams 🌊] Saving changes in the schema editor for an inherited\nfield results in error\n\n\nhttps://github.com/user-attachments/assets/603c8a89-6df3-474a-91bc-ee7bbee0f250\n\n### [Streams 🌊] Disable submit button when there is invalid input for\nmapping in the schema editor\n\n\nhttps://github.com/user-attachments/assets/22dfb91a-fa37-4b68-a8c5-c5f3a89a98e5\n\n### Advanced fields mapping simulation and client-side validation\n\n\nhttps://github.com/user-attachments/assets/faf99f86-5074-4587-9cc6-65f39f3595e9\n\n### [Streams 🌊] Increase width in the type filter popup in schema editor\n\n\nhttps://github.com/user-attachments/assets/b6eab484-308b-42dd-887b-560fb91986da","sha":"d36b269e60308a6b0a5db19b2eac047d2fd51f9d"}},{"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> |
||
Anton Dosov
|
cdd4855188
|
[8.x] [TableListView] Remove listing limit warning (#217945) (#218251)
# Backport This will backport the following commits from `main` to `8.x`: - [[TableListView] Remove listing limit warning (#217945)](https://github.com/elastic/kibana/pull/217945) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T11:42:23Z","message":"[TableListView] Remove listing limit warning (#217945)\n\n## Summary\n\nTemporary solution for\n |
||
|
Kibana Machine
|
a657a38eb6
|
[8.x] [Attack Discovery][Scheduling] UI: "Attack Discovery Scheduling" management (#12007) (#217917) (#218267)
# Backport This will backport the following commits from `main` to `8.x`: - [[Attack Discovery][Scheduling] UI: "Attack Discovery Scheduling" management (#12007) (#217917)](https://github.com/elastic/kibana/pull/217917) <!--- 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-15T13:06:06Z","message":"[Attack Discovery][Scheduling] UI: \"Attack Discovery Scheduling\" management (#12007) (#217917)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12007))\n\nThese changes add the attack discovery schedules management table.\n\n\nhttps://github.com/user-attachments/assets/619ad1d6-d919-4a8d-b743-6a73fbfbf318\n\n## Key changes\n\n* UI side API handlers\n* Create schedule workflow\n* Schedules table\n* Enable schedule from the table\n* Disable schedule from the table\n* Delete schedule from the table\n* Pagination and sorting in find schedules API\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"10943319b29f8efddb4fa641cd150083de994f16","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] UI: \"Attack Discovery Scheduling\" management (#12007)","number":217917,"url":"https://github.com/elastic/kibana/pull/217917","mergeCommit":{"message":"[Attack Discovery][Scheduling] UI: \"Attack Discovery Scheduling\" management (#12007) (#217917)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12007))\n\nThese changes add the attack discovery schedules management table.\n\n\nhttps://github.com/user-attachments/assets/619ad1d6-d919-4a8d-b743-6a73fbfbf318\n\n## Key changes\n\n* UI side API handlers\n* Create schedule workflow\n* Schedules table\n* Enable schedule from the table\n* Disable schedule from the table\n* Delete schedule from the table\n* Pagination and sorting in find schedules API\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"10943319b29f8efddb4fa641cd150083de994f16"}},"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/217917","number":217917,"mergeCommit":{"message":"[Attack Discovery][Scheduling] UI: \"Attack Discovery Scheduling\" management (#12007) (#217917)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12007))\n\nThese changes add the attack discovery schedules management table.\n\n\nhttps://github.com/user-attachments/assets/619ad1d6-d919-4a8d-b743-6a73fbfbf318\n\n## Key changes\n\n* UI side API handlers\n* Create schedule workflow\n* Schedules table\n* Enable schedule from the table\n* Disable schedule from the table\n* Delete schedule from the table\n* Pagination and sorting in find schedules API\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"10943319b29f8efddb4fa641cd150083de994f16"}},{"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> |
||
Matthias Wilhelm
|
6099de25ac
|
[8.x] [Data view] Fix allow_hidden usage in the request for fields (#217628) (#218250)
# Backport This will backport the following commits from `main` to `8.x`: - [[Data view] Fix allow_hidden usage in the request for fields (#217628)](https://github.com/elastic/kibana/pull/217628) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T10:11:00Z","message":"[Data view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis PR fixes the missing allowHidden/allow_hidden usage for data views using the \"allow hidden and system indices\" functionality when creating a data view. There are 2 endpoints being requested in Discover: `/fields` & `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields` ignored this parameter internally. This was fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Data view] Fix allow_hidden usage in the request for fields","number":217628,"url":"https://github.com/elastic/kibana/pull/217628","mergeCommit":{"message":"[Data view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis PR fixes the missing allowHidden/allow_hidden usage for data views using the \"allow hidden and system indices\" functionality when creating a data view. There are 2 endpoints being requested in Discover: `/fields` & `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields` ignored this parameter internally. This was fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4"}},"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/217628","number":217628,"mergeCommit":{"message":"[Data view] Fix allow_hidden usage in the request for fields (#217628)\n\nThis PR fixes the missing allowHidden/allow_hidden usage for data views using the \"allow hidden and system indices\" functionality when creating a data view. There are 2 endpoints being requested in Discover: `/fields` & `/fields_for_wildcards`\n\nBoth use `allow_hidden=true`, but `/fields` ignored this parameter internally. This was fixed.","sha":"c25d62739e08d114fcdec495924196a6b9a74fc4"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
b141be6ce2
|
[8.x] Console/fix folding with script (#216817) (#218277)
# Backport This will backport the following commits from `main` to `8.x`: - [Console/fix folding with script (#216817)](https://github.com/elastic/kibana/pull/216817) <!--- 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-15T13:45:23Z","message":"Console/fix folding with script (#216817)\n\nFixes https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR fixes the logic for finding folding ranges by ignoring\nopening/closing markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that the `script` field in the following request is folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n \"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n \"\"\"\n for (field in params['fields']){\n if (!$(field, '').isEmpty()){\n def value = $(field, '');\n def hash = value.sha256();\n\n // Now we need to traverse as deep as needed\n // and write to that field\n // because we do not have a simple\n // set operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n \n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n \"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n ]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the ranges is best-effort without\ncompromising performance. We currently iterate through each line in the\ntext and use regex, but there are some cases which are not covered by\nthis logic; for example, opening parenthesis, followed by a string in\nthe same line would not be foldable. In order to cover all cases\ncorrectly, we would need to iterate through every single character, but\nthat would make the logic much more complex and might affect performance\nif we have a lot of text in the editor, as these folding ranges are\ncomputed on every change in the editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"Console/fix folding with script","number":216817,"url":"https://github.com/elastic/kibana/pull/216817","mergeCommit":{"message":"Console/fix folding with script (#216817)\n\nFixes https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR fixes the logic for finding folding ranges by ignoring\nopening/closing markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that the `script` field in the following request is folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n \"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n \"\"\"\n for (field in params['fields']){\n if (!$(field, '').isEmpty()){\n def value = $(field, '');\n def hash = value.sha256();\n\n // Now we need to traverse as deep as needed\n // and write to that field\n // because we do not have a simple\n // set operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n \n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n \"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n ]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the ranges is best-effort without\ncompromising performance. We currently iterate through each line in the\ntext and use regex, but there are some cases which are not covered by\nthis logic; for example, opening parenthesis, followed by a string in\nthe same line would not be foldable. In order to cover all cases\ncorrectly, we would need to iterate through every single character, but\nthat would make the logic much more complex and might affect performance\nif we have a lot of text in the editor, as these folding ranges are\ncomputed on every change in the editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0"}},"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/216817","number":216817,"mergeCommit":{"message":"Console/fix folding with script (#216817)\n\nFixes https://github.com/elastic/kibana/issues/212902\n\n## Summary\n\nThis PR fixes the logic for finding folding ranges by ignoring\nopening/closing markers inside triple-quote strings.\n\n**How to test:**\n\nVerify that the `script` field in the following request is folded\ncorrectly:\n\n```\nPOST _ingest/pipeline/_simulate\n{\n \"pipeline\": {\n \"processors\": [\n {\n \"script\": {\n \"source\":\n \"\"\"\n for (field in params['fields']){\n if (!$(field, '').isEmpty()){\n def value = $(field, '');\n def hash = value.sha256();\n\n // Now we need to traverse as deep as needed\n // and write to that field\n // because we do not have a simple\n // set operation available\n \n \"SCRIPT\": parts = field.splitOnToken('.');\n \n\n }\n }\n \"\"\",\n \"params\": {\n \"fields\": [\n \"user.name\",\n \"geo.city\",\n \"does.not.exist\",\n \"this.is.quite.a.deep.field\"\n ]\n }\n }\n }\n ]\n }\n}\n```\n\nNote: The logic is for finding the ranges is best-effort without\ncompromising performance. We currently iterate through each line in the\ntext and use regex, but there are some cases which are not covered by\nthis logic; for example, opening parenthesis, followed by a string in\nthe same line would not be foldable. In order to cover all cases\ncorrectly, we would need to iterate through every single character, but\nthat would make the logic much more complex and might affect performance\nif we have a lot of text in the editor, as these folding ranges are\ncomputed on every change in the editor.","sha":"d9477a74d403b57dd527f4744059e8fea48717b0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Anton Dosov
|
214787f501
|
[8.x] [jest] @emotion/babel-preset-css-prop (#216489) (#218121)
# Backport This will backport the following commits from `main` to `8.x`: - [[jest] @emotion/babel-preset-css-prop (#216489)](https://github.com/elastic/kibana/pull/216489) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T12:29:47Z","message":"[jest] @emotion/babel-preset-css-prop (#216489)\n\n## Summary\n\nPartially address https://github.com/elastic/kibana/issues/216459\n\nThis PR adds `@emotion/babel-preset-css-prop` to jest config to improve\njest and emotion integration. There are some tradeoffs: this is a better\nsetup for emotion + testing library, but there are some seemingly\nregressions for enzyme. We think these are right tradeoffs to make,\nsince we optimize for emotion+testing library.\n\n### Main upsides are 😄 \n\n#### 🟢 Fixes snapshots with css prop\n\n`You have tried to stringify object returned from \\`css\\` function. It\nisn't supposed to be used directly (e.g. as value of the \\`className\\`\nprop), but rather handed to emotion so it can handle it (e.g. as value\nof \\`css\\` prop).` is replaced with proper emotion css classname.\n\n\n\n#### 🟢 We will be able to use jest style matchers for emotion\n`toHaveStyleRule`\n\nhttps://emotion.sh/docs/@emotion/jest#tohavestylerule\n\n_they can be used locally now, but we plan to follow up with global\nextend_\n\n### Considerations 🫤 \n\n#### 🟡 jsx doesn't work inside jest.mock function \n\nExample: \n\n```\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(<div></div>), \n | ^\n 28 | }));\n```\n\nFails with an error. `can't read jsx of undefined`. \n\nThis is because babel compiles this into: \n\n```\nimport { jsx as ___EmotionJSX } from '@emotion/react'\n\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(___EmotionJSX.jsx(….)), \n | ^\n 28 | }));\n```\n\nAnd, apparently, due to how jest imports work, __EmotionJSX is not yet\nin the scope.\n\nThe applied workaround is to rewrite to: \n\n```\njest.mock('./components/alert_header_title', () => ({\n AlertHeaderTitle: jest.fn(() => <div></div>), \n }));\n```\n\n\n#### 🟡 euiTheme needs to be available when euiTheme is accessed inside\n`css` function\n\nExample: \n\n```\nDashboardGrid removes panel when removed from container\n TypeError: Cannot read properties of undefined (reading 'size')\n 42 | margin: '-2px',\n 43 | position: 'absolute',\n > 44 | width: euiTheme.size.l,\n```\n\nThe fix was to wrap failing tests with `<EuiProvider/>` \n\n### Drawbacks 😢 \n\nMostly related to Enzyme \n\n#### 🔴 Enzyme shallow snapshot no longer include `css` prop \n\nSince `css` prop is compiled away there are bunch of snapshots that\nlooks like a regression:\n\nExample:\n\n\n\nThis is unfortunate. We've tried `@emotion/jest/enzyme-serializer` but\nit didn't work (likely because enzyme ecosystem no longer supported?)\nIf it is important that the snapshot captures css, we recommend to use\nmount or rtl\n\n#### 🔴 Asserting against `css` prop with shallow render also doesn't\nwork\n\nPossible solution is to use \n\n```\nimport { matchers } from '@emotion/jest';\nexpect.extend(matchers);\n```\n\n(We plan to add these matches globally in a follow up)\n\nand \n\n```\n expect(button).toHaveStyleRule('background-color', '#FFFFFF');\n```\n\n\n\n#### 🔴 Some shallow Enzyme tests `find()` breaks because of code\ntransformations of emotion\n\nExample:\n\n```\nconst component = shallow(\n <MetricVisValue />\n)\n\ncomponent.find('button') // fails because instead of <button/> there is <EmotionInternalCss/> element now \n\n```\n\nSolutions:\n- Use full mount or react testing library \n- Or target by data-test-subj\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"ef0322d8d05be4a2a02b16133a5f8488fe506900","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ExpressionLanguage","release_note:skip","ci:skip-cypress-osquery","Team:obs-ux-infra_services","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[jest] @emotion/babel-preset-css-prop","number":216489,"url":"https://github.com/elastic/kibana/pull/216489","mergeCommit":{"message":"[jest] @emotion/babel-preset-css-prop (#216489)\n\n## Summary\n\nPartially address https://github.com/elastic/kibana/issues/216459\n\nThis PR adds `@emotion/babel-preset-css-prop` to jest config to improve\njest and emotion integration. There are some tradeoffs: this is a better\nsetup for emotion + testing library, but there are some seemingly\nregressions for enzyme. We think these are right tradeoffs to make,\nsince we optimize for emotion+testing library.\n\n### Main upsides are 😄 \n\n#### 🟢 Fixes snapshots with css prop\n\n`You have tried to stringify object returned from \\`css\\` function. It\nisn't supposed to be used directly (e.g. as value of the \\`className\\`\nprop), but rather handed to emotion so it can handle it (e.g. as value\nof \\`css\\` prop).` is replaced with proper emotion css classname.\n\n\n\n#### 🟢 We will be able to use jest style matchers for emotion\n`toHaveStyleRule`\n\nhttps://emotion.sh/docs/@emotion/jest#tohavestylerule\n\n_they can be used locally now, but we plan to follow up with global\nextend_\n\n### Considerations 🫤 \n\n#### 🟡 jsx doesn't work inside jest.mock function \n\nExample: \n\n```\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(<div></div>), \n | ^\n 28 | }));\n```\n\nFails with an error. `can't read jsx of undefined`. \n\nThis is because babel compiles this into: \n\n```\nimport { jsx as ___EmotionJSX } from '@emotion/react'\n\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(___EmotionJSX.jsx(….)), \n | ^\n 28 | }));\n```\n\nAnd, apparently, due to how jest imports work, __EmotionJSX is not yet\nin the scope.\n\nThe applied workaround is to rewrite to: \n\n```\njest.mock('./components/alert_header_title', () => ({\n AlertHeaderTitle: jest.fn(() => <div></div>), \n }));\n```\n\n\n#### 🟡 euiTheme needs to be available when euiTheme is accessed inside\n`css` function\n\nExample: \n\n```\nDashboardGrid removes panel when removed from container\n TypeError: Cannot read properties of undefined (reading 'size')\n 42 | margin: '-2px',\n 43 | position: 'absolute',\n > 44 | width: euiTheme.size.l,\n```\n\nThe fix was to wrap failing tests with `<EuiProvider/>` \n\n### Drawbacks 😢 \n\nMostly related to Enzyme \n\n#### 🔴 Enzyme shallow snapshot no longer include `css` prop \n\nSince `css` prop is compiled away there are bunch of snapshots that\nlooks like a regression:\n\nExample:\n\n\n\nThis is unfortunate. We've tried `@emotion/jest/enzyme-serializer` but\nit didn't work (likely because enzyme ecosystem no longer supported?)\nIf it is important that the snapshot captures css, we recommend to use\nmount or rtl\n\n#### 🔴 Asserting against `css` prop with shallow render also doesn't\nwork\n\nPossible solution is to use \n\n```\nimport { matchers } from '@emotion/jest';\nexpect.extend(matchers);\n```\n\n(We plan to add these matches globally in a follow up)\n\nand \n\n```\n expect(button).toHaveStyleRule('background-color', '#FFFFFF');\n```\n\n\n\n#### 🔴 Some shallow Enzyme tests `find()` breaks because of code\ntransformations of emotion\n\nExample:\n\n```\nconst component = shallow(\n <MetricVisValue />\n)\n\ncomponent.find('button') // fails because instead of <button/> there is <EmotionInternalCss/> element now \n\n```\n\nSolutions:\n- Use full mount or react testing library \n- Or target by data-test-subj\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"ef0322d8d05be4a2a02b16133a5f8488fe506900"}},"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/216489","number":216489,"mergeCommit":{"message":"[jest] @emotion/babel-preset-css-prop (#216489)\n\n## Summary\n\nPartially address https://github.com/elastic/kibana/issues/216459\n\nThis PR adds `@emotion/babel-preset-css-prop` to jest config to improve\njest and emotion integration. There are some tradeoffs: this is a better\nsetup for emotion + testing library, but there are some seemingly\nregressions for enzyme. We think these are right tradeoffs to make,\nsince we optimize for emotion+testing library.\n\n### Main upsides are 😄 \n\n#### 🟢 Fixes snapshots with css prop\n\n`You have tried to stringify object returned from \\`css\\` function. It\nisn't supposed to be used directly (e.g. as value of the \\`className\\`\nprop), but rather handed to emotion so it can handle it (e.g. as value\nof \\`css\\` prop).` is replaced with proper emotion css classname.\n\n\n\n#### 🟢 We will be able to use jest style matchers for emotion\n`toHaveStyleRule`\n\nhttps://emotion.sh/docs/@emotion/jest#tohavestylerule\n\n_they can be used locally now, but we plan to follow up with global\nextend_\n\n### Considerations 🫤 \n\n#### 🟡 jsx doesn't work inside jest.mock function \n\nExample: \n\n```\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(<div></div>), \n | ^\n 28 | }));\n```\n\nFails with an error. `can't read jsx of undefined`. \n\nThis is because babel compiles this into: \n\n```\nimport { jsx as ___EmotionJSX } from '@emotion/react'\n\njest.mock('./components/alert_header_title', () => ({\n > 27 | AlertHeaderTitle: jest.fn().mockReturnValue(___EmotionJSX.jsx(….)), \n | ^\n 28 | }));\n```\n\nAnd, apparently, due to how jest imports work, __EmotionJSX is not yet\nin the scope.\n\nThe applied workaround is to rewrite to: \n\n```\njest.mock('./components/alert_header_title', () => ({\n AlertHeaderTitle: jest.fn(() => <div></div>), \n }));\n```\n\n\n#### 🟡 euiTheme needs to be available when euiTheme is accessed inside\n`css` function\n\nExample: \n\n```\nDashboardGrid removes panel when removed from container\n TypeError: Cannot read properties of undefined (reading 'size')\n 42 | margin: '-2px',\n 43 | position: 'absolute',\n > 44 | width: euiTheme.size.l,\n```\n\nThe fix was to wrap failing tests with `<EuiProvider/>` \n\n### Drawbacks 😢 \n\nMostly related to Enzyme \n\n#### 🔴 Enzyme shallow snapshot no longer include `css` prop \n\nSince `css` prop is compiled away there are bunch of snapshots that\nlooks like a regression:\n\nExample:\n\n\n\nThis is unfortunate. We've tried `@emotion/jest/enzyme-serializer` but\nit didn't work (likely because enzyme ecosystem no longer supported?)\nIf it is important that the snapshot captures css, we recommend to use\nmount or rtl\n\n#### 🔴 Asserting against `css` prop with shallow render also doesn't\nwork\n\nPossible solution is to use \n\n```\nimport { matchers } from '@emotion/jest';\nexpect.extend(matchers);\n```\n\n(We plan to add these matches globally in a follow up)\n\nand \n\n```\n expect(button).toHaveStyleRule('background-color', '#FFFFFF');\n```\n\n\n\n#### 🔴 Some shallow Enzyme tests `find()` breaks because of code\ntransformations of emotion\n\nExample:\n\n```\nconst component = shallow(\n <MetricVisValue />\n)\n\ncomponent.find('button') // fails because instead of <button/> there is <EmotionInternalCss/> element now \n\n```\n\nSolutions:\n- Use full mount or react testing library \n- Or target by data-test-subj\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"ef0322d8d05be4a2a02b16133a5f8488fe506900"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
f2d44152e7
|
[8.x] Synthtrace otel logs scenario (#217988) (#218275)
# Backport This will backport the following commits from `main` to `8.x`: - [Synthtrace otel logs scenario (#217988)](https://github.com/elastic/kibana/pull/217988) <!--- 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-15T13:40:28Z","message":"Synthtrace otel logs scenario (#217988)\n\nOTel is expected to become more common over time. This PR adds a\nsynthtrace scenario to send sample otel logs to an otel data stream.\n\nThis helps testing whether Discover, Streams and so on function\ncorrectly for this category of data.","sha":"f402033eab066275a32e7c93ff5162adda8b7641","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","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"Synthtrace otel logs scenario","number":217988,"url":"https://github.com/elastic/kibana/pull/217988","mergeCommit":{"message":"Synthtrace otel logs scenario (#217988)\n\nOTel is expected to become more common over time. This PR adds a\nsynthtrace scenario to send sample otel logs to an otel data stream.\n\nThis helps testing whether Discover, Streams and so on function\ncorrectly for this category of data.","sha":"f402033eab066275a32e7c93ff5162adda8b7641"}},"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/217988","number":217988,"mergeCommit":{"message":"Synthtrace otel logs scenario (#217988)\n\nOTel is expected to become more common over time. This PR adds a\nsynthtrace scenario to send sample otel logs to an otel data stream.\n\nThis helps testing whether Discover, Streams and so on function\ncorrectly for this category of data.","sha":"f402033eab066275a32e7c93ff5162adda8b7641"}},{"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
|
c35ce48c9b
|
[8.x] fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831) (#218274)
# Backport This will backport the following commits from `main` to `8.x`: - [fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)](https://github.com/elastic/kibana/pull/217831) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T13:38:48Z","message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","Feature:Anomaly Detection","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement","number":217831,"url":"https://github.com/elastic/kibana/pull/217831","mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217831","number":217831,"mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
Dzmitry Lemechko
|
2e306a27f3
|
[8.x] [kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status (#217230) (#218243)
# Backport This will backport the following commits from `main` to `8.x`: - [[kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status (#217230)](https://github.com/elastic/kibana/pull/217230) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T11:05:49Z","message":"[kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status (#217230)\n\n## Summary\n\nFollow-up to #217153\n\n### Problem Description\nIn UI tests, there was no reliable way to determine when the Alerts\ntable content had fully loaded before interacting with it. This could\nlead to flaky tests where interactions occurred before the data was\navailable (rows are not present yet), causing failures or inconsistent\nresults (checking for row with specific content to exist)\n\n\n\n\nQuite often we see tests waiting for global indicator (spinner in the\ntop left corner) to be hidden as a condition for page loading is\ncomplete. This is quite unreliable approach and testing tools have no\nconsistent built-in solution: FTR, Cypress or even Playwright - network\nidle wait is officially marked as\n[discouraged](https://playwright.dev/docs/api/class-page)).\nWe need to help testing tool to interact with UI components in ready\nstate only.\n\n\n### Solution\nTo address this issue, I modified a `data-test-subj` property in the\n`<EuiDataGrid>` component. The property dynamically switches between\n`alertsTableIsLoading` when data is still loading and\n`alertsTableIsLoaded `once the content is available. This allows UI\ntests to wait for precisely `alertsTableIsLoaded` to be in in the DOM\nbefore interacting with the table, ensuring more reliable and stable\ntest execution.\n\n\nPassed 10/10\n<img width=\"538\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e44bae5f-4094-4ed2-89f3-74a52cb2be53\"\n/>","sha":"edf8d6d975f7ae2bd4df8a469bc391ca602ddc1e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status","number":217230,"url":"https://github.com/elastic/kibana/pull/217230","mergeCommit":{"message":"[kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status (#217230)\n\n## Summary\n\nFollow-up to #217153\n\n### Problem Description\nIn UI tests, there was no reliable way to determine when the Alerts\ntable content had fully loaded before interacting with it. This could\nlead to flaky tests where interactions occurred before the data was\navailable (rows are not present yet), causing failures or inconsistent\nresults (checking for row with specific content to exist)\n\n\n\n\nQuite often we see tests waiting for global indicator (spinner in the\ntop left corner) to be hidden as a condition for page loading is\ncomplete. This is quite unreliable approach and testing tools have no\nconsistent built-in solution: FTR, Cypress or even Playwright - network\nidle wait is officially marked as\n[discouraged](https://playwright.dev/docs/api/class-page)).\nWe need to help testing tool to interact with UI components in ready\nstate only.\n\n\n### Solution\nTo address this issue, I modified a `data-test-subj` property in the\n`<EuiDataGrid>` component. The property dynamically switches between\n`alertsTableIsLoading` when data is still loading and\n`alertsTableIsLoaded `once the content is available. This allows UI\ntests to wait for precisely `alertsTableIsLoaded` to be in in the DOM\nbefore interacting with the table, ensuring more reliable and stable\ntest execution.\n\n\nPassed 10/10\n<img width=\"538\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e44bae5f-4094-4ed2-89f3-74a52cb2be53\"\n/>","sha":"edf8d6d975f7ae2bd4df8a469bc391ca602ddc1e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217230","number":217230,"mergeCommit":{"message":"[kbn/response-ops-alerts-table] set data-test-subj for EuiDataGrid based on loading status (#217230)\n\n## Summary\n\nFollow-up to #217153\n\n### Problem Description\nIn UI tests, there was no reliable way to determine when the Alerts\ntable content had fully loaded before interacting with it. This could\nlead to flaky tests where interactions occurred before the data was\navailable (rows are not present yet), causing failures or inconsistent\nresults (checking for row with specific content to exist)\n\n\n\n\nQuite often we see tests waiting for global indicator (spinner in the\ntop left corner) to be hidden as a condition for page loading is\ncomplete. This is quite unreliable approach and testing tools have no\nconsistent built-in solution: FTR, Cypress or even Playwright - network\nidle wait is officially marked as\n[discouraged](https://playwright.dev/docs/api/class-page)).\nWe need to help testing tool to interact with UI components in ready\nstate only.\n\n\n### Solution\nTo address this issue, I modified a `data-test-subj` property in the\n`<EuiDataGrid>` component. The property dynamically switches between\n`alertsTableIsLoading` when data is still loading and\n`alertsTableIsLoaded `once the content is available. This allows UI\ntests to wait for precisely `alertsTableIsLoaded` to be in in the DOM\nbefore interacting with the table, ensuring more reliable and stable\ntest execution.\n\n\nPassed 10/10\n<img width=\"538\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e44bae5f-4094-4ed2-89f3-74a52cb2be53\"\n/>","sha":"edf8d6d975f7ae2bd4df8a469bc391ca602ddc1e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Bailey Cash
|
93b2fd62d9
|
[8.x] [SLO/Test] add new slo definition api test (#216573) (#218160)
# Backport This will backport the following commits from `main` to `8.x`: - [[SLO/Test] add new slo definition api test (#216573)](https://github.com/elastic/kibana/pull/216573) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T22:12:04Z","message":"[SLO/Test] add new slo definition api test (#216573)\n\nCloses #216236 \n\nadd integration tests for the SLO Definition API, specifically to test\nthe changes for the implementation of this\n[issue](https://github.com/elastic/kibana/issues/214260)","sha":"0f402ca31c9fc49039e3ac7464e7d4c19d84d59f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:SharedUX","Team:obs-ux-management","v9.1.0"],"title":"[SLO/Test] add new slo definition api test","number":216573,"url":"https://github.com/elastic/kibana/pull/216573","mergeCommit":{"message":"[SLO/Test] add new slo definition api test (#216573)\n\nCloses #216236 \n\nadd integration tests for the SLO Definition API, specifically to test\nthe changes for the implementation of this\n[issue](https://github.com/elastic/kibana/issues/214260)","sha":"0f402ca31c9fc49039e3ac7464e7d4c19d84d59f"}},"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/216573","number":216573,"mergeCommit":{"message":"[SLO/Test] add new slo definition api test (#216573)\n\nCloses #216236 \n\nadd integration tests for the SLO Definition API, specifically to test\nthe changes for the implementation of this\n[issue](https://github.com/elastic/kibana/issues/214260)","sha":"0f402ca31c9fc49039e3ac7464e7d4c19d84d59f"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
Elena Shostak
|
a6bd5642ba
|
[8.x] Upgraded octokit to 21.1.1 (#211450) (#218266)
# Backport This will backport the following commits from `main` to `8.x`: - [Upgraded octokit to 21.1.1 (#211450)](https://github.com/elastic/kibana/pull/211450) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-18T09:46:38Z","message":"Upgraded octokit to 21.1.1 (#211450)\n\n## Summary\r\n\r\nUpgraded octokit to `21.1.1`","sha":"38439bb7e12313453ff520c3eed2fb334a69640e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v9.0.0","backport:prev-minor","Team:obs-ux-infra_services","v9.1.0"],"title":"Upgraded octokit to 21.1.1","number":211450,"url":"https://github.com/elastic/kibana/pull/211450","mergeCommit":{"message":"Upgraded octokit to 21.1.1 (#211450)\n\n## Summary\r\n\r\nUpgraded octokit to `21.1.1`","sha":"38439bb7e12313453ff520c3eed2fb334a69640e"}},"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/211538","number":211538,"state":"MERGED","mergeCommit":{"sha":"c57a0a25c46f987db2ada76c144753e090972eb6","message":"[9.0] Upgraded octokit to 21.1.1 (#211450) (#211538)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Upgraded octokit to 21.1.1\n(#211450)](https://github.com/elastic/kibana/pull/211450)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Elena Shostak <165678770+elena-shostak@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/211450","number":211450,"mergeCommit":{"message":"Upgraded octokit to 21.1.1 (#211450)\n\n## Summary\r\n\r\nUpgraded octokit to `21.1.1`","sha":"38439bb7e12313453ff520c3eed2fb334a69640e"}}]}] BACKPORT--> |
||
|
Dzmitry Lemechko
|
ffcf9a5f3a
|
[8.x] [FTR] unify custom role name with Scout (#217882) (#218260)
# Backport This will backport the following commits from `main` to `8.x`: - [[FTR] unify custom role name with Scout (#217882)](https://github.com/elastic/kibana/pull/217882) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:21:49Z","message":"[FTR] unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF David added a possibility to spin up MKI project with custom role\nset and ready to use.\n\nOriginally FTR was using reserved name `'customRole'` for internal\nKibana role to be mapped with native custom role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate SAML authentication, but\nthe new framework will allow to run the tests in parallel. That said, we\nneed to support multiple custom role credentials (one pair per worker)\nand for simplicity we decided to use the same keys:\n\nTo run your tests locally against MKI you need to add a new Cloud user\nentry in `user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\": ..., \"password\": ... }, // FTR requires only the first entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ... },\n...\n```\n\nThe test change is minimal:\n<img width=\"559\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","FTR","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[FTR] unify custom role name with Scout","number":217882,"url":"https://github.com/elastic/kibana/pull/217882","mergeCommit":{"message":"[FTR] unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF David added a possibility to spin up MKI project with custom role\nset and ready to use.\n\nOriginally FTR was using reserved name `'customRole'` for internal\nKibana role to be mapped with native custom role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate SAML authentication, but\nthe new framework will allow to run the tests in parallel. That said, we\nneed to support multiple custom role credentials (one pair per worker)\nand for simplicity we decided to use the same keys:\n\nTo run your tests locally against MKI you need to add a new Cloud user\nentry in `user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\": ..., \"password\": ... }, // FTR requires only the first entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ... },\n...\n```\n\nThe test change is minimal:\n<img width=\"559\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218152","number":218152,"state":"MERGED","mergeCommit":{"sha":"086804391acca87ea1baa98e97b1e12886e3e42b","message":"[9.0] [FTR] unify custom role name with Scout (#217882) (#218152)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[FTR] unify custom role name with Scout\n(#217882)](https://github.com/elastic/kibana/pull/217882)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217882","number":217882,"mergeCommit":{"message":"[FTR] unify custom role name with Scout (#217882)\n\n## Summary\n\nIn QAF David added a possibility to spin up MKI project with custom role\nset and ready to use.\n\nOriginally FTR was using reserved name `'customRole'` for internal\nKibana role to be mapped with native custom role in the project.\n\nBoth Scout and FTR use `kbn/test` to simulate SAML authentication, but\nthe new framework will allow to run the tests in parallel. That said, we\nneed to support multiple custom role credentials (one pair per worker)\nand for simplicity we decided to use the same keys:\n\nTo run your tests locally against MKI you need to add a new Cloud user\nentry in `user_roles.json`:\n\n```\n\"custom_role_worker_1\": { \"username\": ..., \"password\": ... }, // FTR requires only the first entry\n\"custom_role_worker_2\": { \"username\": ..., \"password\": ... },\n...\n```\n\nThe test change is minimal:\n<img width=\"559\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/572103a3-13b2-4e6c-b9d2-5e55b03ac51c\"\n/>\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"c4a97e51e3c9040fb0c955913b06aa0e3b5ba791"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
1690529f4d
|
[8.x] [Console] Fix nested sql lexer rules (#217571) (#218238)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Fix nested sql lexer rules (#217571)](https://github.com/elastic/kibana/pull/217571) <!--- 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-15T10:59:27Z","message":"[Console] Fix nested sql lexer rules (#217571)\n\nFixes https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR fixes the SQL lexer rules which, previously, recognized a single\n`/` as a start of comment, which is not a valid SQL syntax. According to\nthe [SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere are only two types of comments - the single-line one that starts\nwith `--` and the multi-line one that starts with `/*` and ends with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that contains the `/` character was\nincorrectly highlighted as a comment and was messing up the highlighting\nof the rest of the request.\n\nTest with the following request. Make sure that the SQL script in the\n`\"query\"` object is highlighted correctly as well as the rest of the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n \"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n \"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n \"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\": 1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n {\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\": [\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\": 999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n {{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n {{#service.name}}({{.}}) OR {{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}} ({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n \"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n }\n },\n \"condition\": {\n \"compare\": {\n \"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n \"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n }\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Fix nested sql lexer rules","number":217571,"url":"https://github.com/elastic/kibana/pull/217571","mergeCommit":{"message":"[Console] Fix nested sql lexer rules (#217571)\n\nFixes https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR fixes the SQL lexer rules which, previously, recognized a single\n`/` as a start of comment, which is not a valid SQL syntax. According to\nthe [SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere are only two types of comments - the single-line one that starts\nwith `--` and the multi-line one that starts with `/*` and ends with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that contains the `/` character was\nincorrectly highlighted as a comment and was messing up the highlighting\nof the rest of the request.\n\nTest with the following request. Make sure that the SQL script in the\n`\"query\"` object is highlighted correctly as well as the rest of the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n \"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n \"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n \"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\": 1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n {\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\": [\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\": 999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n {{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n {{#service.name}}({{.}}) OR {{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}} ({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n \"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n }\n },\n \"condition\": {\n \"compare\": {\n \"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n \"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n }\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca"}},"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/217571","number":217571,"mergeCommit":{"message":"[Console] Fix nested sql lexer rules (#217571)\n\nFixes https://github.com/elastic/kibana/issues/204963\n\n## Summary\n\nThis PR fixes the SQL lexer rules which, previously, recognized a single\n`/` as a start of comment, which is not a valid SQL syntax. According to\nthe [SQL\ndocs](https://docs.oracle.com/cd/B14117_01/server.101/b10759/sql_elements006.htm),\nthere are only two types of comments - the single-line one that starts\nwith `--` and the multi-line one that starts with `/*` and ends with\n`*/`.\n\n**What this fixes:**\nNested SQL script in Console that contains the `/` character was\nincorrectly highlighted as a comment and was messing up the highlighting\nof the rest of the request.\n\nTest with the following request. Make sure that the SQL script in the\n`\"query\"` object is highlighted correctly as well as the rest of the\nrequest.\n\n```\nPUT _watcher/watch/ec_alerts_dependency_check\n{\n \"trigger\": {\n \"schedule\": {\n \"interval\": \"1m\"\n }\n },\n \"input\": {\n \"chain\": {\n \"inputs\": [\n {\n \"initial_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \"body\": {\n \"query\": {\n \"bool\": {\n \"must_not\": [\n {\n \"exists\": {\n \"field\": \"case_id\"\n }\n }\n ]\n }\n },\n \"size\": 1,\n \"_source\": [\"dependent.service.name\"]\n }\n }\n }\n }\n },\n {\n \"dependent_search\": {\n \"search\": {\n \"request\": {\n \"indices\": [\"ec_alerts\"],\n \n \"body\": {\n //\"_source\": [\"alert\",\"service.name\",\"dependend.service.name\"],\n \"size\": 999,\n \"query\": {\n \"query_string\": {\n \"query\": \"\"\"\n {{#ctx.payload.initial_search.hits.hits.0._source.dependent}}\n {{#service.name}}({{.}}) OR {{/service.name}}{{/ctx.payload.initial_search.hits.hits.0._source.dependent}} ({{ctx.payload.initial_search.hits.hits.0._source.dependent.0.service.name.0}})\"\"\",\n \"default_field\": \"service.name\"\n\n }\n }\n }\n }\n }\n }\n }\n ]\n }\n },\n \"condition\": {\n \"compare\": {\n \"ctx.payload.initial_search.hits.total\": {\n \"gt\": 0\n }\n }\n },\n \"actions\": {\n \"log_results\": {\n \"logging\": {\n \"text\": \"Found related alerts: {{ctx.payload.dependent_search.hits.total}}\"\n }\n }\n }\n}\n```","sha":"401b76e5ebb4a82c4121cf9d9b1218dff2be01ca"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
Stratoula Kalafateli
|
4113673dff
|
[8.x] [ES|QL] Identify conflict types (#217656) (#218204)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Identify conflict types (#217656)](https://github.com/elastic/kibana/pull/217656) <!--- 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-15T07:51:41Z","message":"[ES|QL] Identify conflict types (#217656)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215157\n\nThis is fixing the wrong client side validation error that appears here.\n\n```\nFROM kibana_sample_data_ecommerce\n | EVAL customer_id = TO_LONG(customer_id)\n | LOOKUP JOIN customers ON customer_id\n```\n\n<img width=\"588\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/50a9365f-91c6-45c8-ad04-48be5145eb77\"\n/>\n\n\nWe are using the new originalTypes that is being returned by ES to\nidentify if the field is a conflict and turn off the client side\nvalidation for these fields.\n\nThis is not closing the aforementioned issue. It is the first step to\nimprove the join autocomplete experience. The fields retrieval for joins\nis happening by running `from index1, lookup_index` but in case of\nconflicts this is problematic. We could def improve it in the future but\nidentifying for now that this is a conflict, muting the client side\nvalidation and let ES handling the error is better than what we have\nnow.\n\nAs a bonus the field list recognizes them too as conflict now\n\n<img width=\"683\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7edf8cdf-156b-4933-b9dc-225e211bf2ec\"\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\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"685f026c29b5561f0311815acb0017ebcf689f6a","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] Identify conflict types","number":217656,"url":"https://github.com/elastic/kibana/pull/217656","mergeCommit":{"message":"[ES|QL] Identify conflict types (#217656)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215157\n\nThis is fixing the wrong client side validation error that appears here.\n\n```\nFROM kibana_sample_data_ecommerce\n | EVAL customer_id = TO_LONG(customer_id)\n | LOOKUP JOIN customers ON customer_id\n```\n\n<img width=\"588\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/50a9365f-91c6-45c8-ad04-48be5145eb77\"\n/>\n\n\nWe are using the new originalTypes that is being returned by ES to\nidentify if the field is a conflict and turn off the client side\nvalidation for these fields.\n\nThis is not closing the aforementioned issue. It is the first step to\nimprove the join autocomplete experience. The fields retrieval for joins\nis happening by running `from index1, lookup_index` but in case of\nconflicts this is problematic. We could def improve it in the future but\nidentifying for now that this is a conflict, muting the client side\nvalidation and let ES handling the error is better than what we have\nnow.\n\nAs a bonus the field list recognizes them too as conflict now\n\n<img width=\"683\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7edf8cdf-156b-4933-b9dc-225e211bf2ec\"\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\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"685f026c29b5561f0311815acb0017ebcf689f6a"}},"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/217656","number":217656,"mergeCommit":{"message":"[ES|QL] Identify conflict types (#217656)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/215157\n\nThis is fixing the wrong client side validation error that appears here.\n\n```\nFROM kibana_sample_data_ecommerce\n | EVAL customer_id = TO_LONG(customer_id)\n | LOOKUP JOIN customers ON customer_id\n```\n\n<img width=\"588\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/50a9365f-91c6-45c8-ad04-48be5145eb77\"\n/>\n\n\nWe are using the new originalTypes that is being returned by ES to\nidentify if the field is a conflict and turn off the client side\nvalidation for these fields.\n\nThis is not closing the aforementioned issue. It is the first step to\nimprove the join autocomplete experience. The fields retrieval for joins\nis happening by running `from index1, lookup_index` but in case of\nconflicts this is problematic. We could def improve it in the future but\nidentifying for now that this is a conflict, muting the client side\nvalidation and let ES handling the error is better than what we have\nnow.\n\nAs a bonus the field list recognizes them too as conflict now\n\n<img width=\"683\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7edf8cdf-156b-4933-b9dc-225e211bf2ec\"\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\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"685f026c29b5561f0311815acb0017ebcf689f6a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
8cce26f699
|
[8.x] [ES|QL] Map expression traversal and pretty-printing (#218060) (#218231)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Map expression traversal and pretty-printing (#218060)](https://github.com/elastic/kibana/pull/218060) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Vadim Kibana","email":"82822460+vadimkibana@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T10:14:14Z","message":"[ES|QL] Map expression traversal and pretty-printing (#218060)\n\n## Summary\n\n- Adds ability to traverse `map` and `map-entry` AST nodes.\n - In `Walker`\n - And in `Visitor`\n- Adds support for pretty-printing ES|QL maps\n - In `BasicPrettyPrinter`, as well as, in the `WrappingPrettyPrinter`.\n- Supports comments printing in both printers in any place: around maps,\nas well as around any map key and map key value.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"32d77a32d07efc21bb17aa1b3b88fdb39cb2557e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Map expression traversal and pretty-printing","number":218060,"url":"https://github.com/elastic/kibana/pull/218060","mergeCommit":{"message":"[ES|QL] Map expression traversal and pretty-printing (#218060)\n\n## Summary\n\n- Adds ability to traverse `map` and `map-entry` AST nodes.\n - In `Walker`\n - And in `Visitor`\n- Adds support for pretty-printing ES|QL maps\n - In `BasicPrettyPrinter`, as well as, in the `WrappingPrettyPrinter`.\n- Supports comments printing in both printers in any place: around maps,\nas well as around any map key and map key value.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"32d77a32d07efc21bb17aa1b3b88fdb39cb2557e"}},"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/218060","number":218060,"mergeCommit":{"message":"[ES|QL] Map expression traversal and pretty-printing (#218060)\n\n## Summary\n\n- Adds ability to traverse `map` and `map-entry` AST nodes.\n - In `Walker`\n - And in `Visitor`\n- Adds support for pretty-printing ES|QL maps\n - In `BasicPrettyPrinter`, as well as, in the `WrappingPrettyPrinter`.\n- Supports comments printing in both printers in any place: around maps,\nas well as around any map key and map key value.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"32d77a32d07efc21bb17aa1b3b88fdb39cb2557e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vadim Kibana <82822460+vadimkibana@users.noreply.github.com> |
||
|
Kibana Machine
|
7397472f90
|
[8.x] [Infra] Check ML permissions before requesting ML data (#218069) (#218229)
# Backport This will backport the following commits from `main` to `8.x`: - [[Infra] Check ML permissions before requesting ML data (#218069)](https://github.com/elastic/kibana/pull/218069) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T10:02:51Z","message":"[Infra] Check ML permissions before requesting ML data (#218069)\n\nfixes [#189213](https://github.com/elastic/kibana/issues/189213)\n\n## Summary\n\nChecks whether the user has permission to ML before triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a user whose role doesn't have permission to ML, but has\npermission to O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts --live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts View\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[Infra] Check ML permissions before requesting ML data","number":218069,"url":"https://github.com/elastic/kibana/pull/218069","mergeCommit":{"message":"[Infra] Check ML permissions before requesting ML data (#218069)\n\nfixes [#189213](https://github.com/elastic/kibana/issues/189213)\n\n## Summary\n\nChecks whether the user has permission to ML before triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a user whose role doesn't have permission to ML, but has\npermission to O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts --live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts View\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3"}},"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/218069","number":218069,"mergeCommit":{"message":"[Infra] Check ML permissions before requesting ML data (#218069)\n\nfixes [#189213](https://github.com/elastic/kibana/issues/189213)\n\n## Summary\n\nChecks whether the user has permission to ML before triggering requests\nto fetch ML data\n\n\n### How to test\n\n- Create a user whose role doesn't have permission to ML, but has\npermission to O11y apps\n- Run `node scripts/synthtrace infra_hosts_with_apm_hosts --live\n--clean`\n - Navigate to Inventory Infrastructure / Hosts View\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"5423655975924c5e2840f684132fc0447e4bcec3"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
|
Kibana Machine
|
e3826dec77
|
[8.x] [Console] Fix a11y overlay test (#218130) (#218218)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Fix a11y overlay test (#218130)](https://github.com/elastic/kibana/pull/218130) <!--- 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-15T09:07:06Z","message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Fix a11y overlay test","number":218130,"url":"https://github.com/elastic/kibana/pull/218130","mergeCommit":{"message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},"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/218130","number":218130,"mergeCommit":{"message":"[Console] Fix a11y overlay test (#218130)\n\nFixes https://github.com/elastic/kibana/issues/217057\n\n## Summary\n\nThis PR fixes the flaky test for the a11y overlay by adding a `retry`\nand allowing more time for the overlay element to be detected.\n\nFlaky test runner build:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8176","sha":"d5bceb79d06d6688e7d7968be1ae71c6bf13e142"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
015a36b03b
|
[8.x] [ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107) (#218217)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)](https://github.com/elastic/kibana/pull/218107) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T09:06:29Z","message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar","number":218107,"url":"https://github.com/elastic/kibana/pull/218107","mergeCommit":{"message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218107","number":218107,"mergeCommit":{"message":"[ResponseOps][Cases]Horizontal scrolling in cases' comments overflows sidebar (#218107)\n\nCloses https://github.com/elastic/kibana/issues/217994\n\n## Summary\n\nThe comment section containing a table that requires horizontal\nscrolling was being visually pushed to the right due to the presence of\nthe user avatar. To ensure the comment section aligns properly with the\nrest of the content and doesn't overlap the sidebar reserved for\nconnectors and custom fields, the `max-width` property was adjusted\naccordingly.\n\nThe offset comes from: \n- the width of the euiAvatar--m (which uses the `xl` size token)\n- the left padding of the `euiTimelineItemEvent`, which corresponds to\n`euiTheme.size.base` (16px)","sha":"64a2f399d3a1d46809fe7b9b77307ce9e05e583c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co> |
||
|
Kibana Machine
|
2c24a2b657
|
[8.x] [Console] Finishing design touches (#217887) (#218221)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Finishing design touches (#217887)](https://github.com/elastic/kibana/pull/217887) <!--- 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-15T09:08:32Z","message":"[Console] Finishing design touches (#217887)\n\nFixes https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR adds the following small design improvements:\n\n### 1. Ensures that the bottom border of the selection doesn't overlap\nwith the next line by shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot 2025-04-10 at 17 50 35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe also increase the line height a little to ensure that the action\npanel box fits inside a single-line request selection box:\n\n\n<img width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00 07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n### 2. Ensures that the left border of the selection doesn't overlap\nwith the line numbers by shifting the border to the right.\n\nBefore:\n<img width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49 30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50 01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n### 3. Increases the contrast between the selected text and the\nselection blue box by increasing the transparency of the blue selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot 2025-04-10 at 17 51 43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Finishing design touches","number":217887,"url":"https://github.com/elastic/kibana/pull/217887","mergeCommit":{"message":"[Console] Finishing design touches (#217887)\n\nFixes https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR adds the following small design improvements:\n\n### 1. Ensures that the bottom border of the selection doesn't overlap\nwith the next line by shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot 2025-04-10 at 17 50 35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe also increase the line height a little to ensure that the action\npanel box fits inside a single-line request selection box:\n\n\n<img width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00 07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n### 2. Ensures that the left border of the selection doesn't overlap\nwith the line numbers by shifting the border to the right.\n\nBefore:\n<img width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49 30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50 01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n### 3. Increases the contrast between the selected text and the\nselection blue box by increasing the transparency of the blue selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot 2025-04-10 at 17 51 43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f"}},"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/217887","number":217887,"mergeCommit":{"message":"[Console] Finishing design touches (#217887)\n\nFixes https://github.com/elastic/kibana/issues/200195\n\n## Summary\n\nThis PR adds the following small design improvements:\n\n### 1. Ensures that the bottom border of the selection doesn't overlap\nwith the next line by shifting the border up.\n\nBefore:\n<img width=\"1118\" alt=\"Screenshot 2025-04-10 at 17 50 35\"\nsrc=\"https://github.com/user-attachments/assets/085aa499-7842-4bcf-ba97-49706b58c9ad\"\n/>\n\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 05\"\nsrc=\"https://github.com/user-attachments/assets/37f2a6ca-3c0b-4a00-b1cd-117334feb480\"\n/>\n\nWe also increase the line height a little to ensure that the action\npanel box fits inside a single-line request selection box:\n\n\n<img width=\"1136\" alt=\"Screenshot 2025-04-10 at 18 00 07\"\nsrc=\"https://github.com/user-attachments/assets/3f618049-d5d0-46c4-8d1b-5098a00985f5\"\n/>\n\n\n\n\n### 2. Ensures that the left border of the selection doesn't overlap\nwith the line numbers by shifting the border to the right.\n\nBefore:\n<img width=\"740\" alt=\"Screenshot 2025-04-10 at 17 49 30\"\nsrc=\"https://github.com/user-attachments/assets/184599c3-d5e8-40b4-b8f4-a2f40caa2c92\"\n/>\n\n\nNow:\n<img width=\"652\" alt=\"Screenshot 2025-04-10 at 17 50 01\"\nsrc=\"https://github.com/user-attachments/assets/edacd4aa-9478-4d1a-8217-d6d1181e452d\"\n/>\n\n\n### 3. Increases the contrast between the selected text and the\nselection blue box by increasing the transparency of the blue selection\nbox:\n\n\nBefore:\n<img width=\"735\" alt=\"Screenshot 2025-04-10 at 17 51 43\"\nsrc=\"https://github.com/user-attachments/assets/95ff61d9-f4ef-4db9-b3d5-4ed8a64cc792\"\n/>\n\nNow:\n<img width=\"1124\" alt=\"Screenshot 2025-04-10 at 17 51 14\"\nsrc=\"https://github.com/user-attachments/assets/9b80c3a7-a053-49df-bfd2-f00b7765b545\"\n/>\n\n---------\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"4cf7c3c5b8957e4daebe94bcb1c4233c6c236b4f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
5413137e34
|
[8.x] Fix/lens serialize (#218082) (#218211)
# Backport This will backport the following commits from `main` to `8.x`: - [Fix/lens serialize (#218082)](https://github.com/elastic/kibana/pull/218082) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Peter Pisljar","email":"peter.pisljar@elastic.co"},"sourceCommit":{"committedDate":"2025-04-15T08:48:43Z","message":"Fix/lens serialize (#218082)","sha":"1017c22245e4d6a262480bc85c7502ad4d5432d5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"Fix/lens serialize","number":218082,"url":"https://github.com/elastic/kibana/pull/218082","mergeCommit":{"message":"Fix/lens serialize (#218082)","sha":"1017c22245e4d6a262480bc85c7502ad4d5432d5"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218082","number":218082,"mergeCommit":{"message":"Fix/lens serialize (#218082)","sha":"1017c22245e4d6a262480bc85c7502ad4d5432d5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Peter Pisljar <peter.pisljar@elastic.co> |
||
|
Kibana Machine
|
a8c8ab367a
|
[8.x] [ES|QL] Allows to retrieve empty columns (#218085) (#218205)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Allows to retrieve empty columns (#218085)](https://github.com/elastic/kibana/pull/218085) <!--- 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-15T08:28:38Z","message":"[ES|QL] Allows to retrieve empty columns (#218085)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/200039\n\nHere we are asking ES to do a grouping between empty columns and\nnon-empty. The `dropNullColumns: true` in the request does the trick.\n\nIn case of true the response comes as:\n\n```\n// only columns with data\ncolumns: [...]\n// all columns\nall_columns: [...]\n```\n\nWhen the query is empty the columns array comes empty but the\nall_columns has all the columns information. The PR just takes the empty\ncolumns scenario under consideration in order to serve the `all_columns`\ninstead. In that case the text based datasource has the info it needs to\nserve a valid visualization state.\n\n\n<img width=\"990\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7d0b2c58-eda2-4807-9203-36f7da48a6ff\"\n/>\n\n\n<img width=\"814\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8b0ef3bf-14d5-4438-b8fd-a13d346da420\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"3c1f04dbb4483b4d4665c49c9d43430050d0fbe9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","Feature:ES|QL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Allows to retrieve empty columns","number":218085,"url":"https://github.com/elastic/kibana/pull/218085","mergeCommit":{"message":"[ES|QL] Allows to retrieve empty columns (#218085)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/200039\n\nHere we are asking ES to do a grouping between empty columns and\nnon-empty. The `dropNullColumns: true` in the request does the trick.\n\nIn case of true the response comes as:\n\n```\n// only columns with data\ncolumns: [...]\n// all columns\nall_columns: [...]\n```\n\nWhen the query is empty the columns array comes empty but the\nall_columns has all the columns information. The PR just takes the empty\ncolumns scenario under consideration in order to serve the `all_columns`\ninstead. In that case the text based datasource has the info it needs to\nserve a valid visualization state.\n\n\n<img width=\"990\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7d0b2c58-eda2-4807-9203-36f7da48a6ff\"\n/>\n\n\n<img width=\"814\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8b0ef3bf-14d5-4438-b8fd-a13d346da420\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"3c1f04dbb4483b4d4665c49c9d43430050d0fbe9"}},"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/218085","number":218085,"mergeCommit":{"message":"[ES|QL] Allows to retrieve empty columns (#218085)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/200039\n\nHere we are asking ES to do a grouping between empty columns and\nnon-empty. The `dropNullColumns: true` in the request does the trick.\n\nIn case of true the response comes as:\n\n```\n// only columns with data\ncolumns: [...]\n// all columns\nall_columns: [...]\n```\n\nWhen the query is empty the columns array comes empty but the\nall_columns has all the columns information. The PR just takes the empty\ncolumns scenario under consideration in order to serve the `all_columns`\ninstead. In that case the text based datasource has the info it needs to\nserve a valid visualization state.\n\n\n<img width=\"990\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/7d0b2c58-eda2-4807-9203-36f7da48a6ff\"\n/>\n\n\n<img width=\"814\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/8b0ef3bf-14d5-4438-b8fd-a13d346da420\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"3c1f04dbb4483b4d4665c49c9d43430050d0fbe9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
Julia Rechkunova
|
3f4ae8c651
|
[8.x] [Discover] Fix CSV for ES|QL embeddable (#216325) (#216851)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Fix CSV for ES|QL embeddable (#216325)](https://github.com/elastic/kibana/pull/216325) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:14:55Z","message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","v9.0.0","Team:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover] Fix CSV for ES|QL embeddable","number":216325,"url":"https://github.com/elastic/kibana/pull/216325","mergeCommit":{"message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216325","number":216325,"mergeCommit":{"message":"[Discover] Fix CSV for ES|QL embeddable (#216325)\n\n- Closes https://github.com/elastic/kibana/issues/215893\n\n## Summary\n\nThis PR extract the logic from Share > Export > Generate CSV into new\nutils and uses it to fix CSV export for Dashboard panels.\n\n<img width=\"903\" alt=\"Screenshot 2025-04-01 at 12 05 58\"\nsrc=\"https://github.com/user-attachments/assets/20e611d7-b1da-4b50-a8fc-e18ac3db3a55\"\n/>\n\n\n## Testing\n\nPlease test for both data view mode and ES|QL mode. The steps are the\nfollowing:\n1. Save a discover session\n2. Add it to a new dashboard\n3. Save the Dashboard and switch to View mode\n4. Via panel actions, press \"Generate CSV report\"\n5. Compare the CSV results with what is shown in the grid\n6. Add a custom time range to the panel via panel actions \"Settings\"\n7. Generate a CSV report and compare results again\n\nAlso check that reporting still works when generated from Discover page.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"dc78614d29da8f64f77840d3fc02846fcacfe2e5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Tim Sullivan
|
0cc28d0e71
|
[8.x] NavigationItemOpenPanel: remove handling of landing page ("four squares" design) (#210893) (#218133)
# Backport
This will backport the following commits from `main` to `8.x`:
- [NavigationItemOpenPanel: remove handling of landing page ("four
squares" design)
(#210893)](https://github.com/elastic/kibana/pull/210893)
<!--- Backport version: 9.6.6 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Tim
Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-09T14:25:30Z","message":"NavigationItemOpenPanel:
remove handling of landing page (\"four squares\" design)
(#210893)\n\n## Summary\n\nPart of Epic:
https://github.com/elastic/kibana-team/issues/1439\nRequires:
https://github.com/elastic/kibana/issues/212903\n\nChanges:\n1. Moves
the Solution Side Nav away from the \"four squares\" design\npattern:
where clicking the item label opens a landing page and the item\nicon
opens the secondary nav panel. This was a custom component\nimplemented
in the Kibana package, not part of the EUI\n`EuiCollapsibleNavBeta`
component.\n2. Changes some usage of `@emotion/css` to `@emotion/react`
for better\ndeveloper experience\n\n###
Screenshots\n\n<details><summary>Before</summary>\n\n\n
Peter Pisljar
|
8e6d961497
|
[8.x] lens esql generation (#196049) (#209753)
# Backport This will backport the following commits from `main` to `8.x`: - [lens esql generation (#196049)](https://github.com/elastic/kibana/pull/196049) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Peter Pisljar","email":"peter.pisljar@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T08:53:24Z","message":"lens esql generation (#196049)","sha":"762fd8c4d054682d2c969a7d9266289b2e5daa21","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ExpressionLanguage","Team:Visualizations","release_note:skip","backport:skip","v9.1.0"],"title":"lens esql generation","number":196049,"url":"https://github.com/elastic/kibana/pull/196049","mergeCommit":{"message":"lens esql generation (#196049)","sha":"762fd8c4d054682d2c969a7d9266289b2e5daa21"}},"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/196049","number":196049,"mergeCommit":{"message":"lens esql generation (#196049)","sha":"762fd8c4d054682d2c969a7d9266289b2e5daa21"}}]}] BACKPORT--> |
||
Maryam Saeidi
|
a32b7835a1
|
[8.x] Update apm-rum packages (#217800) (#218145)
# Backport This will backport the following commits from `main` to `8.x`: - [Update apm-rum packages (#217800)](https://github.com/elastic/kibana/pull/217800) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-04-10T14:57:06Z","message":"Update apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages mostly to use this feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous version|Current version|Change log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version bump only for package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"Update apm-rum packages","number":217800,"url":"https://github.com/elastic/kibana/pull/217800","mergeCommit":{"message":"Update apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages mostly to use this feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous version|Current version|Change log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version bump only for package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76"}},"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/217800","number":217800,"mergeCommit":{"message":"Update apm-rum packages (#217800)\n\n## Summary \n\nUpdating apm-rum packages mostly to use this feature:\nhttps://github.com/elastic/apm-agent-rum-js/pull/1594\n\n\nChanges\n\n|Package|Previous version|Current version|Change log\n([PR](https://github.com/elastic/apm-agent-rum-js/pull/1599/files))|\n|---|---|---|---|\n|@elastic/apm-rum|^5.16.3|^5.17.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-core|^5.22.1|^5.23.0|add support for adding labels to\ncaptured errors\n([#1594](https://github.com/elastic/apm-agent-rum-js/pull/1594))|\n|@elastic/apm-rum-react|^2.0.5|^2.0.6|version bump only for package\n@elastic/apm-rum-react|","sha":"a616a40f9307cd34c6a28c7192cfee146ca5ad76"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Bailey Cash
|
de6ea00825
|
[8.x] [SLO]: Add filtering to SLO Management table, improve UX (#216040) (#218171)
# Backport This will backport the following commits from `main` to `8.x`: - [[SLO]: Add filtering to SLO Management table, improve UX (#216040)](https://github.com/elastic/kibana/pull/216040) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-03-27T22:36:16Z","message":"[SLO]: Add filtering to SLO Management table, improve UX (#216040)\n\n## Summary\n\nResolves #214258 \n\n- Updates search bar to utilize UnifiedSearchBar\n- Adds ability to filter SLOs by tags (OR operator)\n- Makes improvements to version display\n\n\n\n\n---------\n\nCo-authored-by: kdelemme <kdelemme@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"40e95f00f1b2f3b2ba76f958727e9bea24424679","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-management","v9.1.0"],"title":"[SLO]: Add filtering to SLO Management table, improve UX","number":216040,"url":"https://github.com/elastic/kibana/pull/216040","mergeCommit":{"message":"[SLO]: Add filtering to SLO Management table, improve UX (#216040)\n\n## Summary\n\nResolves #214258 \n\n- Updates search bar to utilize UnifiedSearchBar\n- Adds ability to filter SLOs by tags (OR operator)\n- Makes improvements to version display\n\n\n\n\n---------\n\nCo-authored-by: kdelemme <kdelemme@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"40e95f00f1b2f3b2ba76f958727e9bea24424679"}},"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/216040","number":216040,"mergeCommit":{"message":"[SLO]: Add filtering to SLO Management table, improve UX (#216040)\n\n## Summary\n\nResolves #214258 \n\n- Updates search bar to utilize UnifiedSearchBar\n- Adds ability to filter SLOs by tags (OR operator)\n- Makes improvements to version display\n\n\n\n\n---------\n\nCo-authored-by: kdelemme <kdelemme@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"40e95f00f1b2f3b2ba76f958727e9bea24424679"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Stratoula Kalafateli
|
1761809f29
|
[8.x] [ES|QL] Adds license knowledge to the editor (#217796) (#218096)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Adds license knowledge to the editor (#217796)](https://github.com/elastic/kibana/pull/217796) <!--- 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-14T10:52:10Z","message":"[ES|QL] Adds license knowledge to the editor (#217796)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/216791\n\n- Suggests remote indices if ES license plugin enables it \n\n<img width=\"580\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a237f646-286e-489c-b41b-a1ce7d82440a\"\n/>\n\n\n\n- Doesn't suggest remote indices for basic license\n<img width=\"292\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bc9e512-91ab-4b20-94ce-d1931732567e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"708917df6ea4c60b666d2ed11cb0b3865034b342","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] Adds license knowledge to the editor","number":217796,"url":"https://github.com/elastic/kibana/pull/217796","mergeCommit":{"message":"[ES|QL] Adds license knowledge to the editor (#217796)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/216791\n\n- Suggests remote indices if ES license plugin enables it \n\n<img width=\"580\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a237f646-286e-489c-b41b-a1ce7d82440a\"\n/>\n\n\n\n- Doesn't suggest remote indices for basic license\n<img width=\"292\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bc9e512-91ab-4b20-94ce-d1931732567e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"708917df6ea4c60b666d2ed11cb0b3865034b342"}},"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/217796","number":217796,"mergeCommit":{"message":"[ES|QL] Adds license knowledge to the editor (#217796)\n\n## Summary\n\nPart of https://github.com/elastic/kibana/issues/216791\n\n- Suggests remote indices if ES license plugin enables it \n\n<img width=\"580\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/a237f646-286e-489c-b41b-a1ce7d82440a\"\n/>\n\n\n\n- Doesn't suggest remote indices for basic license\n<img width=\"292\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bc9e512-91ab-4b20-94ce-d1931732567e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"708917df6ea4c60b666d2ed11cb0b3865034b342"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Bailey Cash
|
0da581350d
|
[8.x] [SLO] update default feature flag value for slo management (#216919) (#218162)
# Backport This will backport the following commits from `main` to `8.x`: - [[SLO] update default feature flag value for slo management (#216919)](https://github.com/elastic/kibana/pull/216919) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T13:07:35Z","message":"[SLO] update default feature flag value for slo management (#216919)\n\n## Summary\n\nupdate default feature flag value for slo management, persist flag state\nto callout","sha":"8999324ed563fa1c081d6270a873fdaefbea7732","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-management","v9.1.0"],"title":"[SLO] update default feature flag value for slo management","number":216919,"url":"https://github.com/elastic/kibana/pull/216919","mergeCommit":{"message":"[SLO] update default feature flag value for slo management (#216919)\n\n## Summary\n\nupdate default feature flag value for slo management, persist flag state\nto callout","sha":"8999324ed563fa1c081d6270a873fdaefbea7732"}},"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/216919","number":216919,"mergeCommit":{"message":"[SLO] update default feature flag value for slo management (#216919)\n\n## Summary\n\nupdate default feature flag value for slo management, persist flag state\nto callout","sha":"8999324ed563fa1c081d6270a873fdaefbea7732"}}]}] BACKPORT--> |
||
Jeramy Soucy
|
cb0bdae67d
|
[8.x] Fixes bulk re-encryption for encrypted objects located in all spaces (#217625) (#218178)
# Backport This will backport the following commits from `main` to `8.x`: - [Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)](https://github.com/elastic/kibana/pull/217625) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T19:20:38Z","message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","backport:all-open","v9.1.0"],"title":"Fixes bulk re-encryption for encrypted objects located in all spaces","number":217625,"url":"https://github.com/elastic/kibana/pull/217625","mergeCommit":{"message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217625","number":217625,"mergeCommit":{"message":"Fixes bulk re-encryption for encrypted objects located in all spaces (#217625)\n\nCloses #215534\n\n## Summary\n\nThe Encrypted Saved Objects Key Rotation service makes use of the Saved\nObjects Bulk Update API to re-encrypt objects. Bulk update supports an\noptional 'namespace' parameter, per-object, defining the space to access\na specific object. This allows objects outside of the current space to\nbe affected in the update operation. The Key Rotation service leverages\nthis optional parameter for each object to ensure that the re-encryption\noperation is not limited to the current space.\n\nHowever, should a multi-namespace encrypted object reside in all spaces,\nthe only value in the object's namespaces property is the\n`ALL_NAMESPACES_STRING` constant '*'. As this is not a valid single\nnamespace, the Bulk Update operation will skip updating the object.\n\nPR resolves the issue by only providing a object namespace for objects\nthat do not reside in all spaces. Objects that reside in all spaces can\nbe accessed from the current space without the need for an override.\n\nThis PR also updates unit tests to account for this case.\n\n### Testing\n- [x] Set the encrypted saved objects encryption key to a known value\n(either in kibana.yml or kibana.dev.yml). For example:\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\" \n```\n- [x] Start ES & Kibana\n- [x] You will need to set up a Fleet agent policy and create a\nsynthetics location and monitor. The UI will guide you through this when\nyou navigate to Observability -> Synthetics\n- [x] Create a synthetics parameter, Observability -> Synthetics ->\nSettings, Global Parameters tab. Use anything for a value, but be sure\nto check the `Share across spaces` option.\n- [x] Update the kibana config to change the encryption key, and use the\nold key as a decryption-only key\n```\nxpack.encryptedSavedObjects:\n encryptionKey: \"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\" \n keyRotation:\n decryptionOnlyKeys: [\"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\"] \n```\n- [x] Wait for Kibana to restart\n- [x] Call the key rotation HTTP API as a privileged user (I just used\nthe `elastic` superuser account)\n\n`[you_kibana_endpoint]/api/encrypted_saved_objects/_rotate_key?type=synthetics-param`\n- [x] Verify that 1 out of 1 objects were processed with 0 failures.\n- [x] Repeat these steps from Main and note that 0 of 1 objects\nsucceeded, and there is 1 failure\n\n### Release Note\nFixes an issue where the Saved Objects Rotate Encryption Key API would\nnot affect sharable encrypted object types that exist in all spaces.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1176625dcaf8ec8ca4e4aa0b1324279ab0f2def3"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a58c356711
|
[8.x] [Console] Fix output for empty response body (#218104) (#218184)
# Backport This will backport the following commits from `main` to `8.x`: - [[Console] Fix output for empty response body (#218104)](https://github.com/elastic/kibana/pull/218104) <!--- 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-14T22:06:14Z","message":"[Console] Fix output for empty response body (#218104)\n\nFixes https://github.com/elastic/kibana/issues/217433\n\n## Summary\n\nThis PR fixes the Console output when the response body is an empty\nstring.\n\nIn https://github.com/elastic/kibana/pull/199975, we made Console to\ndisplay an `OK` output if the status code is 200 but response body is\n`null`. Previously, `POST\n/_cluster/voting_config_exclusions?node_names=node` returned `null` and\nso the output was correctly set to `OK` but now the response is an empty\nstring and this case isn't covered correctly. In this PR, we make sure\nto perform the right check at the right point so that both `null` and\nempty strings are covered.\n\nThe test that covers this scenario and had failures:\n |
||
|
Kibana Machine
|
8e52a80c09
|
[8.x] [ES|QL] Clean up trigger chars (#218023) (#218170)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Clean up trigger chars (#218023)](https://github.com/elastic/kibana/pull/218023) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Drew Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T19:19:47Z","message":"[ES|QL] Clean up trigger chars (#218023)\n\n## Summary\n\nThere were several trigger characters on our completion item provider\nthat weren't doing anything. This removes them!\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7dcb22bdec595c618666ae7bc3e218539a3f24c1","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] Clean up trigger chars","number":218023,"url":"https://github.com/elastic/kibana/pull/218023","mergeCommit":{"message":"[ES|QL] Clean up trigger chars (#218023)\n\n## Summary\n\nThere were several trigger characters on our completion item provider\nthat weren't doing anything. This removes them!\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7dcb22bdec595c618666ae7bc3e218539a3f24c1"}},"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/218023","number":218023,"mergeCommit":{"message":"[ES|QL] Clean up trigger chars (#218023)\n\n## Summary\n\nThere were several trigger characters on our completion item provider\nthat weren't doing anything. This removes them!\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7dcb22bdec595c618666ae7bc3e218539a3f24c1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Drew Tate <drew.tate@elastic.co> |
||
|
Kibana Machine
|
8ab1f4101a
|
[8.x] [Detection Engine] Cypress cleanup and simplification (#217276) (#218166)
# Backport This will backport the following commits from `main` to `8.x`: - [[Detection Engine] Cypress cleanup and simplification (#217276)](https://github.com/elastic/kibana/pull/217276) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-14T18:46:47Z","message":"[Detection Engine] Cypress cleanup and simplification (#217276)\n\n## Summary\n\nThis PR attempts to simplify our Cypress tests to focus in on what\nexactly we want a test to be doing. Many of our rule creation cypress\ntests were testing rule creation, rule edit, rule details and more. This\nresults in a lot of flake and us triaging tests that often test things\nother than what we're ultimately trying to answer.\n\nI tried to simplify it so the rule specific tests simply answer - can we\ncreate this rule type in the UI? Then there's a single test for checking\nthe entire flow of create rule -> rule details and check for alerts. The\nFTRs should be ensuring that the rules generate alerts as expected so we\ndon't need to check this for every rule type in cypress.\n\nI also moved alert suppression into it's own folder as there is a lot of\nspecific logic to test around that.","sha":"81c93ca5d1dd714297b04ff80660fbdb6a267582","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":"[Detection Engine] Cypress cleanup and simplification","number":217276,"url":"https://github.com/elastic/kibana/pull/217276","mergeCommit":{"message":"[Detection Engine] Cypress cleanup and simplification (#217276)\n\n## Summary\n\nThis PR attempts to simplify our Cypress tests to focus in on what\nexactly we want a test to be doing. Many of our rule creation cypress\ntests were testing rule creation, rule edit, rule details and more. This\nresults in a lot of flake and us triaging tests that often test things\nother than what we're ultimately trying to answer.\n\nI tried to simplify it so the rule specific tests simply answer - can we\ncreate this rule type in the UI? Then there's a single test for checking\nthe entire flow of create rule -> rule details and check for alerts. The\nFTRs should be ensuring that the rules generate alerts as expected so we\ndon't need to check this for every rule type in cypress.\n\nI also moved alert suppression into it's own folder as there is a lot of\nspecific logic to test around that.","sha":"81c93ca5d1dd714297b04ff80660fbdb6a267582"}},"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/217276","number":217276,"mergeCommit":{"message":"[Detection Engine] Cypress cleanup and simplification (#217276)\n\n## Summary\n\nThis PR attempts to simplify our Cypress tests to focus in on what\nexactly we want a test to be doing. Many of our rule creation cypress\ntests were testing rule creation, rule edit, rule details and more. This\nresults in a lot of flake and us triaging tests that often test things\nother than what we're ultimately trying to answer.\n\nI tried to simplify it so the rule specific tests simply answer - can we\ncreate this rule type in the UI? Then there's a single test for checking\nthe entire flow of create rule -> rule details and check for alerts. The\nFTRs should be ensuring that the rules generate alerts as expected so we\ndon't need to check this for every rule type in cypress.\n\nI also moved alert suppression into it's own folder as there is a lot of\nspecific logic to test around that.","sha":"81c93ca5d1dd714297b04ff80660fbdb6a267582"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com> |
||
elastic-renovate-prod[bot]
|
63a0243739
|
Update dependency selenium-webdriver to ^4.31.0 (8.x) (#216404)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [selenium-webdriver](https://redirect.github.com/SeleniumHQ/selenium/tree/trunk/javascript/selenium-webdriver#readme) ([source](https://redirect.github.com/SeleniumHQ/selenium)) | devDependencies | minor | [`^4.29.0` -> `^4.31.0`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.29.0/4.31.0) | --- ### Release Notes <details> <summary>SeleniumHQ/selenium (selenium-webdriver)</summary> ### [`v4.31.0`]( |
||
|
Kibana Machine
|
48554f91e1
|
[8.x] [Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959) (#218154)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959)](https://github.com/elastic/kibana/pull/217959) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T17:22:38Z","message":"[Security Solution] Fix prebuilt rules force upgrade on Endpoint policy creation (#217959)\n\n**Resolves: https://github.com/elastic/security-team/issues/7216**\n\n## Summary\n\nThis PR updates the Endpoint policy callback to: \n\n- **Install only the Elastic Defend rule if it's missing**, without\nupgrading it to the latest version. Previously, the rule was both\ninstalled and updated whenever an Endpoint policy was created, which\nconflicted with rule customization. Automatic upgrades could erase\nexisting user customizations.\n\n- **Avoid triggering the installation or upgrade of any other prebuilt\nrules** as part of this flow. The Endpoint package policy creation\ncallback\n([source]( |
||
Justin Kambic
|
0ab217af55
|
[8.x] [Synthetics] Only return 404 if screenshot_ref is truly not present (#215241) (#218136)
# Backport This will backport the following commits from `main` to `8.x`: - [[Synthetics] Only return 404 if `screenshot_ref` is truly not present (#215241)](https://github.com/elastic/kibana/pull/215241) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-24T14:50:18Z","message":"[Synthetics] Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n## Summary\n\nRight now we return a 404 anytime that the data we're looking for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts check on the\ndata before returning. It's possible that that data will fail the check,\nand we'd return a 404 anyway. This isn't a very accurate reflection of\nwhat's happening on the server, and could indicate a problem with the\nuser's data.\n\nInstead, we first check if the data returned from Elasticsearch is\n`null`, and if it is we return a 404. Otherwise, we compute the type\ncheck like normal and return the result. In the case where the data\nfails the type check, we instead return a 500 and include the malformed\ndata in the server response.\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"[Synthetics] Only return 404 if `screenshot_ref` is truly not present","number":215241,"url":"https://github.com/elastic/kibana/pull/215241","mergeCommit":{"message":"[Synthetics] Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n## Summary\n\nRight now we return a 404 anytime that the data we're looking for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts check on the\ndata before returning. It's possible that that data will fail the check,\nand we'd return a 404 anyway. This isn't a very accurate reflection of\nwhat's happening on the server, and could indicate a problem with the\nuser's data.\n\nInstead, we first check if the data returned from Elasticsearch is\n`null`, and if it is we return a 404. Otherwise, we compute the type\ncheck like normal and return the result. In the case where the data\nfails the type check, we instead return a 500 and include the malformed\ndata in the server response.\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7"}},"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/215726","number":215726,"state":"MERGED","mergeCommit":{"sha":"349e4472ee62edd72cd062bb2635cb563f61168b","message":"[9.0] [Synthetics] Only return 404 if `screenshot_ref` is truly not present (#215241) (#215726)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Synthetics] Only return 404 if `screenshot_ref` is truly not present\n(#215241)](https://github.com/elastic/kibana/pull/215241)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Justin Kambic <jk@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215241","number":215241,"mergeCommit":{"message":"[Synthetics] Only return 404 if `screenshot_ref` is truly not present (#215241)\n\n## Summary\n\nRight now we return a 404 anytime that the data we're looking for on the\n`screenshot_ref` route is not satisfactory. We do an io-ts check on the\ndata before returning. It's possible that that data will fail the check,\nand we'd return a 404 anyway. This isn't a very accurate reflection of\nwhat's happening on the server, and could indicate a problem with the\nuser's data.\n\nInstead, we first check if the data returned from Elasticsearch is\n`null`, and if it is we return a 404. Otherwise, we compute the type\ncheck like normal and return the result. In the case where the data\nfails the type check, we instead return a 500 and include the malformed\ndata in the server response.\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>","sha":"74f87d99bc1981a533982e103f802d0cbf118fa7"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
595f8db751
|
[8.x] [Vega] Add ability to open links in Vega in new window (#216200) (#218132)
# Backport This will backport the following commits from `main` to `8.x`: - [[Vega] Add ability to open links in Vega in new window (#216200)](https://github.com/elastic/kibana/pull/216200) <!--- 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-14T14:42:32Z","message":"[Vega] Add ability to open links in Vega in new window (#216200)\n\n## Summary\n\nFix #70745 \n\nEnables the option to open the clickable mark links of a Vega\nVisualization in a new tab.\n\nTo achieve this functionality: \n- use the `usermeta.embedOptions.loader` property in the vega chart spec\nto pass the `\"target\": \"_blank\"` configuration:\n```javascript\n\"usermeta\": {\n \"embedOptions\": {\n \"loader\": {\"target\": \"_blank\"}\n }\n }\n``` \n\nLink opens in a new tab:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"f8e688f88135bf7675cfd0c6dfb918e23b6ebbb8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Vega","Team:Visualizations","backport:version","v9.1.0","v8.19.0"],"title":"[Vega] Add ability to open links in Vega in new window","number":216200,"url":"https://github.com/elastic/kibana/pull/216200","mergeCommit":{"message":"[Vega] Add ability to open links in Vega in new window (#216200)\n\n## Summary\n\nFix #70745 \n\nEnables the option to open the clickable mark links of a Vega\nVisualization in a new tab.\n\nTo achieve this functionality: \n- use the `usermeta.embedOptions.loader` property in the vega chart spec\nto pass the `\"target\": \"_blank\"` configuration:\n```javascript\n\"usermeta\": {\n \"embedOptions\": {\n \"loader\": {\"target\": \"_blank\"}\n }\n }\n``` \n\nLink opens in a new tab:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"f8e688f88135bf7675cfd0c6dfb918e23b6ebbb8"}},"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/216200","number":216200,"mergeCommit":{"message":"[Vega] Add ability to open links in Vega in new window (#216200)\n\n## Summary\n\nFix #70745 \n\nEnables the option to open the clickable mark links of a Vega\nVisualization in a new tab.\n\nTo achieve this functionality: \n- use the `usermeta.embedOptions.loader` property in the vega chart spec\nto pass the `\"target\": \"_blank\"` configuration:\n```javascript\n\"usermeta\": {\n \"embedOptions\": {\n \"loader\": {\"target\": \"_blank\"}\n }\n }\n``` \n\nLink opens in a new tab:\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"f8e688f88135bf7675cfd0c6dfb918e23b6ebbb8"}},{"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
|
0b60e4c08a
|
[8.x] [ObsUX][A11y] Fix focus for popover in details flyout (#218095) (#218126)
# Backport This will backport the following commits from `main` to `8.x`: - [[ObsUX][A11y] Fix focus for popover in details flyout (#218095)](https://github.com/elastic/kibana/pull/218095) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-14T14:15:25Z","message":"[ObsUX][A11y] Fix focus for popover in details flyout (#218095)\n\nCloses https://github.com/elastic/kibana/issues/212633\n\n## Summary\n\nFixed navigation by keeping focus on Popover opener element\n\n### How to test\nObservability -> Infrastructure -> Infrastructure inventory page.\n1. Navigate to any square below All button.\n2. Press Enter.\n3. Navigate to infographic for Host IP.\n4. Press Enter.\n5. Press Esc.\n\nExpected result: Navigation continues to next element when Tab key is\npressed.\n\nBEFORE \n\n\n |
||
|
Kibana Machine
|
6350ab9e92
|
[8.x] [ES|QL] Enable suggestions for CHANGE_POINT command (#218100) (#218124)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] Enable suggestions for `CHANGE_POINT` command (#218100)](https://github.com/elastic/kibana/pull/218100) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T14:12:45Z","message":"[ES|QL] Enable suggestions for `CHANGE_POINT` command (#218100)\n\n## Summary\n\nWith the `CHANGE_POINT` command moved to tech preview (PR\nhttps://github.com/elastic/elasticsearch/pull/126407), we can enable\nsuggestions in the editor.","sha":"1a6cea558964a87255d2a00ca58e62d914a55c80","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Enable suggestions for `CHANGE_POINT` command","number":218100,"url":"https://github.com/elastic/kibana/pull/218100","mergeCommit":{"message":"[ES|QL] Enable suggestions for `CHANGE_POINT` command (#218100)\n\n## Summary\n\nWith the `CHANGE_POINT` command moved to tech preview (PR\nhttps://github.com/elastic/elasticsearch/pull/126407), we can enable\nsuggestions in the editor.","sha":"1a6cea558964a87255d2a00ca58e62d914a55c80"}},"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/218100","number":218100,"mergeCommit":{"message":"[ES|QL] Enable suggestions for `CHANGE_POINT` command (#218100)\n\n## Summary\n\nWith the `CHANGE_POINT` command moved to tech preview (PR\nhttps://github.com/elastic/elasticsearch/pull/126407), we can enable\nsuggestions in the editor.","sha":"1a6cea558964a87255d2a00ca58e62d914a55c80"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Bailey Cash
|
a167c9e655
|
[8.x] Add SLO Definition Page (#215423) (#218120)
# Backport This will backport the following commits from `main` to `8.x`: - [Add SLO Definition Page (#215423)](https://github.com/elastic/kibana/pull/215423) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-03-26T12:23:55Z","message":"Add SLO Definition Page (#215423)","sha":"8aa9b82079a3e38548ac5919c623591beb057ac0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:obs-ux-management","v9.1.0"],"title":"Add SLO Definition Page","number":215423,"url":"https://github.com/elastic/kibana/pull/215423","mergeCommit":{"message":"Add SLO Definition Page (#215423)","sha":"8aa9b82079a3e38548ac5919c623591beb057ac0"}},"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/215423","number":215423,"mergeCommit":{"message":"Add SLO Definition Page (#215423)","sha":"8aa9b82079a3e38548ac5919c623591beb057ac0"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
8e6ff32635
|
[8.x] 🌊 Streams: Make deleting orphaned streams work (#218054) (#218117)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Streams: Make deleting orphaned streams work (#218054)](https://github.com/elastic/kibana/pull/218054) <!--- 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-14T13:49:00Z","message":"🌊 Streams: Make deleting orphaned streams work (#218054)\n\nCurrently streams doesn't allow you to delete an orphaned stream because\n`getPipelineTargets` required the data stream to exist.\n\nThis PR fixes the problem by handling the case gracefully.","sha":"e2f0fddfd12d5f0fad09821f6559054190305ac7","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: Make deleting orphaned streams work","number":218054,"url":"https://github.com/elastic/kibana/pull/218054","mergeCommit":{"message":"🌊 Streams: Make deleting orphaned streams work (#218054)\n\nCurrently streams doesn't allow you to delete an orphaned stream because\n`getPipelineTargets` required the data stream to exist.\n\nThis PR fixes the problem by handling the case gracefully.","sha":"e2f0fddfd12d5f0fad09821f6559054190305ac7"}},"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/218054","number":218054,"mergeCommit":{"message":"🌊 Streams: Make deleting orphaned streams work (#218054)\n\nCurrently streams doesn't allow you to delete an orphaned stream because\n`getPipelineTargets` required the data stream to exist.\n\nThis PR fixes the problem by handling the case gracefully.","sha":"e2f0fddfd12d5f0fad09821f6559054190305ac7"}},{"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> |
||
wajihaparvez
|
2d50a33948
|
[Docs] 8.17.5 release notes (#217919)
## Summary Adding 8.17.5 release notes. Rel: [3104](https://github.com/elastic/dev/issues/3104) Closes: [664](https://github.com/elastic/platform-docs-team/issues/664) Preview [here](https://kibana_bk_217919.docs-preview.app.elstc.co/guide/en/kibana/8.x/release-notes-8.17.5.html)  |
||
Elena Stoeva
|
d603f410df
|
[8.x] [Advanced Settings] Move security settings validation config (#216440) (#217086)
# Backport This will backport the following commits from `main` to `8.x`: - [[Advanced Settings] Move security settings validation config (#216440)](https://github.com/elastic/kibana/pull/216440) <!--- 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-03-31T14:59:07Z","message":"[Advanced Settings] Move security settings validation config (#216440)\n\n## Summary\n\nIn https://github.com/elastic/kibana/pull/170234, we added validation on\nthe security solution settings in serverless that is enabled through the\n`xpack.securitySolution.enableUiSettingsValidations` config setting. In\nthis PR, we move this setting to `config/serverless.security.yml` so\nthat it follows the sustainable architecture principles.","sha":"b1b8b190bda17b4d51e2db97814161d67cb44730","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Kibana Management","Team:Kibana Management","release_note:skip","backport missing","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Advanced Settings] Move security settings validation config","number":216440,"url":"https://github.com/elastic/kibana/pull/216440","mergeCommit":{"message":"[Advanced Settings] Move security settings validation config (#216440)\n\n## Summary\n\nIn https://github.com/elastic/kibana/pull/170234, we added validation on\nthe security solution settings in serverless that is enabled through the\n`xpack.securitySolution.enableUiSettingsValidations` config setting. In\nthis PR, we move this setting to `config/serverless.security.yml` so\nthat it follows the sustainable architecture principles.","sha":"b1b8b190bda17b4d51e2db97814161d67cb44730"}},"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/216440","number":216440,"mergeCommit":{"message":"[Advanced Settings] Move security settings validation config (#216440)\n\n## Summary\n\nIn https://github.com/elastic/kibana/pull/170234, we added validation on\nthe security solution settings in serverless that is enabled through the\n`xpack.securitySolution.enableUiSettingsValidations` config setting. In\nthis PR, we move this setting to `config/serverless.security.yml` so\nthat it follows the sustainable architecture principles.","sha":"b1b8b190bda17b4d51e2db97814161d67cb44730"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |