mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 16:03:20 -04:00
84502 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Efe Gürkan YALAMAN
|
9440a3cf05
|
[9.0] [Search] [Synonyms] Synonym Rule flyout update (#213433) (#214414)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search] [Synonyms] Synonym Rule flyout update (#213433)](https://github.com/elastic/kibana/pull/213433) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:35:11Z","message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","ci:project-deploy-elasticsearch","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Search] [Synonyms] Synonym Rule flyout update","number":213433,"url":"https://github.com/elastic/kibana/pull/213433","mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213433","number":213433,"mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214398","number":214398,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214397","number":214397,"state":"OPEN"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Kibana Machine
|
36986a89e7
|
[9.0] [Uptime] Fix skipped a11y tests (#214396) (#214621)
# Backport This will backport the following commits from `main` to `9.0`: - [[Uptime] Fix skipped a11y tests (#214396)](https://github.com/elastic/kibana/pull/214396) <!--- 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-14T17:01:45Z","message":"[Uptime] Fix skipped a11y tests (#214396)\n\n## Summary\n\nResolves #204152.\n\nAttempt to fix the mislabeled element by adding the `figure` role to it.","sha":"631a840db44a26553acca83182ab0071e9db3abb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["skipped-test","release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v9.1.0"],"title":"[Uptime] Fix skipped a11y tests","number":214396,"url":"https://github.com/elastic/kibana/pull/214396","mergeCommit":{"message":"[Uptime] Fix skipped a11y tests (#214396)\n\n## Summary\n\nResolves #204152.\n\nAttempt to fix the mislabeled element by adding the `figure` role to it.","sha":"631a840db44a26553acca83182ab0071e9db3abb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214396","number":214396,"mergeCommit":{"message":"[Uptime] Fix skipped a11y tests (#214396)\n\n## Summary\n\nResolves #204152.\n\nAttempt to fix the mislabeled element by adding the `figure` role to it.","sha":"631a840db44a26553acca83182ab0071e9db3abb"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
|
Kibana Machine
|
60ec42a349
|
[9.0] [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506) (#214618)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)](https://github.com/elastic/kibana/pull/214506) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:41:40Z","message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.18.1"],"title":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations","number":214506,"url":"https://github.com/elastic/kibana/pull/214506","mergeCommit":{"message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19"}},"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/214506","number":214506,"mergeCommit":{"message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Andrew Macri <andrew.macri@elastic.co> |
||
|
Kibana Machine
|
0c817d1b7d
|
[9.0] [Security Solution] Remove bulk crud endpoints schemas (#213244) (#214608)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Remove bulk crud endpoints schemas (#213244)](https://github.com/elastic/kibana/pull/213244) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:15:38Z","message":"[Security Solution] Remove bulk crud endpoints schemas (#213244)\n\n**Partially addresses:** #211808,\nhttps://github.com/elastic/security-docs/issues/5981 (internal)\n**Resolves: #208329**\n\n## Summary\n\nThis is the second part of the migration effort, containing changes for:\n- BULK CRUD (removing, for v.9.0)\n\nThe PR also contains changes for ticket #208329 - as changes for\nremoving of dead code for handling Bulk CRUD endpoints had to be\ncombined together with removing the schema files for Bulk CRUD\nendpoints.\n\nThis PR will be backported only to versions for Kibana v9\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6f71349aa7abd9b5ea413fa6460f14af28b45a6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","APIDocs","Team:Detection Rule Management","backport:version","8.18 candidate","v9.1.0"],"title":"[Security Solution] Remove bulk crud endpoints schemas","number":213244,"url":"https://github.com/elastic/kibana/pull/213244","mergeCommit":{"message":"[Security Solution] Remove bulk crud endpoints schemas (#213244)\n\n**Partially addresses:** #211808,\nhttps://github.com/elastic/security-docs/issues/5981 (internal)\n**Resolves: #208329**\n\n## Summary\n\nThis is the second part of the migration effort, containing changes for:\n- BULK CRUD (removing, for v.9.0)\n\nThe PR also contains changes for ticket #208329 - as changes for\nremoving of dead code for handling Bulk CRUD endpoints had to be\ncombined together with removing the schema files for Bulk CRUD\nendpoints.\n\nThis PR will be backported only to versions for Kibana v9\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6f71349aa7abd9b5ea413fa6460f14af28b45a6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213244","number":213244,"mergeCommit":{"message":"[Security Solution] Remove bulk crud endpoints schemas (#213244)\n\n**Partially addresses:** #211808,\nhttps://github.com/elastic/security-docs/issues/5981 (internal)\n**Resolves: #208329**\n\n## Summary\n\nThis is the second part of the migration effort, containing changes for:\n- BULK CRUD (removing, for v.9.0)\n\nThe PR also contains changes for ticket #208329 - as changes for\nremoving of dead code for handling Bulk CRUD endpoints had to be\ncombined together with removing the schema files for Bulk CRUD\nendpoints.\n\nThis PR will be backported only to versions for Kibana v9\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6f71349aa7abd9b5ea413fa6460f14af28b45a6"}}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
9ebac082ac
|
[9.0] Android dashboard changes (#213734) (#214603)
# Backport This will backport the following commits from `main` to `9.0`: - [Android dashboard changes (#213734)](https://github.com/elastic/kibana/pull/213734) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"César","email":"56847527+LikeTheSalad@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T16:00:34Z","message":"Android dashboard changes (#213734)\n\n## Summary\n\nResolves #213730 \n\n## Overview tab\n\n### Before\n\n\n\n### After\n\n\n\n## Errors tab\n\n### Before\n\n\n\n### After\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e8d0c61cc9075da1a1b85a479652eb0d59f3139","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-infra_services","v9.1.0","backport:8.18"],"title":"Android dashboard changes","number":213734,"url":"https://github.com/elastic/kibana/pull/213734","mergeCommit":{"message":"Android dashboard changes (#213734)\n\n## Summary\n\nResolves #213730 \n\n## Overview tab\n\n### Before\n\n\n\n### After\n\n\n\n## Errors tab\n\n### Before\n\n\n\n### After\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e8d0c61cc9075da1a1b85a479652eb0d59f3139"}},"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/213734","number":213734,"mergeCommit":{"message":"Android dashboard changes (#213734)\n\n## Summary\n\nResolves #213730 \n\n## Overview tab\n\n### Before\n\n\n\n### After\n\n\n\n## Errors tab\n\n### Before\n\n\n\n### After\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e8d0c61cc9075da1a1b85a479652eb0d59f3139"}}]}] BACKPORT--> Co-authored-by: César <56847527+LikeTheSalad@users.noreply.github.com> |
||
|
Kibana Machine
|
9a627af7b2
|
[9.0] [kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185) (#214584)
# Backport This will backport the following commits from `main` to `9.0`: - [[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)](https://github.com/elastic/kibana/pull/214185) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T13:54:08Z","message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"[kbn/server-route-repository] Use appropriate log level based on HTTP status","number":214185,"url":"https://github.com/elastic/kibana/pull/214185","mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}},"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/214185","number":214185,"mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
|
Kibana Machine
|
e874ae42c4
|
[9.0] Update dependency @elastic/charts to v69.1.1 (main) (#213623) (#214585)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @elastic/charts to v69.1.1 (main) (#213623)](https://github.com/elastic/kibana/pull/213623) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T13:58:39Z","message":"Update dependency @elastic/charts to v69.1.1 (main) (#213623)","sha":"f2b5f3fe48564816d97ecd6342e5bb2d7f95f4c0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"Update dependency @elastic/charts to v69.1.1 (main)","number":213623,"url":"https://github.com/elastic/kibana/pull/213623","mergeCommit":{"message":"Update dependency @elastic/charts to v69.1.1 (main) (#213623)","sha":"f2b5f3fe48564816d97ecd6342e5bb2d7f95f4c0"}},"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/213623","number":213623,"mergeCommit":{"message":"Update dependency @elastic/charts to v69.1.1 (main) (#213623)","sha":"f2b5f3fe48564816d97ecd6342e5bb2d7f95f4c0"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
a2f8f80766
|
[9.0] [Security Solution] Batch prebuilt rule installation (#214441) (#214578)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Batch prebuilt rule installation (#214441)](https://github.com/elastic/kibana/pull/214441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T13:39:32Z","message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","performance","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Batch prebuilt rule installation","number":214441,"url":"https://github.com/elastic/kibana/pull/214441","mergeCommit":{"message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0"}},"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/214441","number":214441,"mergeCommit":{"message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co> |
||
elastic-vault-github-plugin-prod[bot]
|
9fabd7f464
|
[9.0] Sync bundled packages with Package Storage (#214474)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2443 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
8422e40447
|
[9.0] [EDR Workflows] Rename enforce_registry_filters advanced option (#214106) (#214550)
# Backport This will backport the following commits from `main` to `9.0`: - [[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)](https://github.com/elastic/kibana/pull/214106) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T10:55:16Z","message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Rename `enforce_registry_filters` advanced option","number":214106,"url":"https://github.com/elastic/kibana/pull/214106","mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}},"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/214106","number":214106,"mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\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] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |
||
|
Kibana Machine
|
6db834f39b
|
[9.0] [Synthetics] Fixed bad loading state for grouped monitor cards (#214428) (#214526)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Fixed bad loading state for grouped monitor cards (#214428)](https://github.com/elastic/kibana/pull/214428) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-03-14T08:50:58Z","message":"[Synthetics] Fixed bad loading state for grouped monitor cards (#214428)\n\nFixes #191649.\n\nThe bad loading state reported in the issue was probably caused by the\n`isLoading` flag passed to the `EuiAccordion` component.\n\nBy checking the source code of the `EuiAccordion` component I found out\nthat that flag changes both `extraActions` and `children` into a loading\nspinner.\n\n\n\nAlso changed the number of rows passed to the `OverviewLoader` component\nto match the `rowSize` set by the user.\n\nHere the final result:\n\n\n\nhttps://github.com/user-attachments/assets/215af2e2-11f7-4cec-b00d-061ec4e60ee6","sha":"67e292e8f9639b2163aae93c6b63d514d71bd4a3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Synthetics] Fixed bad loading state for grouped monitor cards","number":214428,"url":"https://github.com/elastic/kibana/pull/214428","mergeCommit":{"message":"[Synthetics] Fixed bad loading state for grouped monitor cards (#214428)\n\nFixes #191649.\n\nThe bad loading state reported in the issue was probably caused by the\n`isLoading` flag passed to the `EuiAccordion` component.\n\nBy checking the source code of the `EuiAccordion` component I found out\nthat that flag changes both `extraActions` and `children` into a loading\nspinner.\n\n\n\nAlso changed the number of rows passed to the `OverviewLoader` component\nto match the `rowSize` set by the user.\n\nHere the final result:\n\n\n\nhttps://github.com/user-attachments/assets/215af2e2-11f7-4cec-b00d-061ec4e60ee6","sha":"67e292e8f9639b2163aae93c6b63d514d71bd4a3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214428","number":214428,"mergeCommit":{"message":"[Synthetics] Fixed bad loading state for grouped monitor cards (#214428)\n\nFixes #191649.\n\nThe bad loading state reported in the issue was probably caused by the\n`isLoading` flag passed to the `EuiAccordion` component.\n\nBy checking the source code of the `EuiAccordion` component I found out\nthat that flag changes both `extraActions` and `children` into a loading\nspinner.\n\n\n\nAlso changed the number of rows passed to the `OverviewLoader` component\nto match the `rowSize` set by the user.\n\nHere the final result:\n\n\n\nhttps://github.com/user-attachments/assets/215af2e2-11f7-4cec-b00d-061ec4e60ee6","sha":"67e292e8f9639b2163aae93c6b63d514d71bd4a3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
2b0f94a7e3
|
[9.0] [Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287) (#214517)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)](https://github.com/elastic/kibana/pull/214287) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T07:20:37Z","message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\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\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing","number":214287,"url":"https://github.com/elastic/kibana/pull/214287","mergeCommit":{"message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\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\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b"}},"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/214287","number":214287,"mergeCommit":{"message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\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\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> |
||
|
Kibana Machine
|
bfbf5863df
|
[9.0] [Security Solution] UI copy for Upgrade rules confirmation modal (#213981) (#214464)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)](https://github.com/elastic/kibana/pull/213981) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:36:35Z","message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","ui-copy","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] UI copy for Upgrade rules confirmation modal ","number":213981,"url":"https://github.com/elastic/kibana/pull/213981","mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},"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/213981","number":213981,"mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
elastic-renovate-prod[bot]
|
34fb822b5c
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 3f6bcf4 (9.0) (#214507)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `69a0542` -> `3f6bcf4` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
008558a644
|
[9.0] Update dependency @hapi/hapi to ^21.4.0 (main) (#214209) (#214500)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @hapi/hapi to ^21.4.0 (main) (#214209)](https://github.com/elastic/kibana/pull/214209) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T23:45:59Z","message":"Update dependency @hapi/hapi to ^21.4.0 (main) (#214209)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [@hapi/hapi](https://hapi.dev)\n([source](https://redirect.github.com/hapijs/hapi)) | dependencies |\nminor | [`^21.3.12` ->\n`^21.4.0`](https://renovatebot.com/diffs/npm/@hapi%2fhapi/21.3.12/21.4.0)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>hapijs/hapi (@​hapi/hapi)</summary>\n\n###\n[`v21.4.0`](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n[Compare\nSource](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a8777749e7c3023f6526509b8e6b403f3b43d6f6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update dependency @hapi/hapi to ^21.4.0 (main)","number":214209,"url":"https://github.com/elastic/kibana/pull/214209","mergeCommit":{"message":"Update dependency @hapi/hapi to ^21.4.0 (main) (#214209)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [@hapi/hapi](https://hapi.dev)\n([source](https://redirect.github.com/hapijs/hapi)) | dependencies |\nminor | [`^21.3.12` ->\n`^21.4.0`](https://renovatebot.com/diffs/npm/@hapi%2fhapi/21.3.12/21.4.0)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>hapijs/hapi (@​hapi/hapi)</summary>\n\n###\n[`v21.4.0`](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n[Compare\nSource](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a8777749e7c3023f6526509b8e6b403f3b43d6f6"}},"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/214209","number":214209,"mergeCommit":{"message":"Update dependency @hapi/hapi to ^21.4.0 (main) (#214209)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [@hapi/hapi](https://hapi.dev)\n([source](https://redirect.github.com/hapijs/hapi)) | dependencies |\nminor | [`^21.3.12` ->\n`^21.4.0`](https://renovatebot.com/diffs/npm/@hapi%2fhapi/21.3.12/21.4.0)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>hapijs/hapi (@​hapi/hapi)</summary>\n\n###\n[`v21.4.0`](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n[Compare\nSource](https://redirect.github.com/hapijs/hapi/compare/v21.3.12...v21.4.0)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a8777749e7c3023f6526509b8e6b403f3b43d6f6"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
51f7440469
|
[9.0] [Synthetics] Unskip getMonitors api test !! (#214075) (#214491)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Unskip getMonitors api test !! (#214075)](https://github.com/elastic/kibana/pull/214075) <!--- 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-03-13T21:21:30Z","message":"[Synthetics] Unskip getMonitors api test !! (#214075)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/204069 !!\n\nUnskip getMonitors api test !!","sha":"071838129c911af061aa0cf707d16409b36015cf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"[Synthetics] Unskip getMonitors api test !!","number":214075,"url":"https://github.com/elastic/kibana/pull/214075","mergeCommit":{"message":"[Synthetics] Unskip getMonitors api test !! (#214075)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/204069 !!\n\nUnskip getMonitors api test !!","sha":"071838129c911af061aa0cf707d16409b36015cf"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214075","number":214075,"mergeCommit":{"message":"[Synthetics] Unskip getMonitors api test !! (#214075)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/204069 !!\n\nUnskip getMonitors api test !!","sha":"071838129c911af061aa0cf707d16409b36015cf"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
2e4531093e
|
[9.0] [SLOs Annotations] Fix rendering issue with annotations (#214157) (#214490)
# Backport This will backport the following commits from `main` to `9.0`: - [[SLOs Annotations] Fix rendering issue with annotations (#214157)](https://github.com/elastic/kibana/pull/214157) <!--- 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-03-13T21:20:43Z","message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SLOs Annotations] Fix rendering issue with annotations","number":214157,"url":"https://github.com/elastic/kibana/pull/214157","mergeCommit":{"message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715"}},"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/214157","number":214157,"mergeCommit":{"message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
3130f3af28
|
[9.0] [Obs AI Assistant] Forward telemetryMetadata.pluginId to the EIS use case header (#214285) (#214481)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)](https://github.com/elastic/kibana/pull/214285) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T19:29:37Z","message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header","number":214285,"url":"https://github.com/elastic/kibana/pull/214285","mergeCommit":{"message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771"}},"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/214285","number":214285,"mergeCommit":{"message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
6c1aa0a4d9
|
[9.0] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214473)
# Backport This will backport the following commits from `main` to `9.0`: - [[Threat Hunting Investigations] Fix timeline column width bug (#214178)](https://github.com/elastic/kibana/pull/214178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:49:16Z","message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Fix timeline column width bug","number":214178,"url":"https://github.com/elastic/kibana/pull/214178","mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}},"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/214178","number":214178,"mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co> |
||
|
Kibana Machine
|
57c26701f7
|
[9.0] [Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455) (#214469)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)](https://github.com/elastic/kibana/pull/213455) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T18:43:18Z","message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fix session view navigation when in alert preview and add preview banner","number":213455,"url":"https://github.com/elastic/kibana/pull/213455","mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},"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/213455","number":213455,"mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [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- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com> |
||
|
Kibana Machine
|
0afeee0c98
|
[9.0] [SLO]: Include spaceID in SLI documents (#214278) (#214466)
# Backport This will backport the following commits from `main` to `9.0`: - [[SLO]: Include spaceID in SLI documents (#214278)](https://github.com/elastic/kibana/pull/214278) <!--- 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-13T18:39:38Z","message":"[SLO]: Include spaceID in SLI documents (#214278)\n\n## Summary\n\nResolves #213464 \n\n## Release Notes\n\nSpaceId can now be referenced in document-based access filters for roles\nto restrict a user's access to SLI data for spaces where they do not\nhave access.","sha":"22e64dc868c96dc3d00b0b4270c97dc57e0146a3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"[SLO]: Include spaceID in SLI documents ","number":214278,"url":"https://github.com/elastic/kibana/pull/214278","mergeCommit":{"message":"[SLO]: Include spaceID in SLI documents (#214278)\n\n## Summary\n\nResolves #213464 \n\n## Release Notes\n\nSpaceId can now be referenced in document-based access filters for roles\nto restrict a user's access to SLI data for spaces where they do not\nhave access.","sha":"22e64dc868c96dc3d00b0b4270c97dc57e0146a3"}},"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/214278","number":214278,"mergeCommit":{"message":"[SLO]: Include spaceID in SLI documents (#214278)\n\n## Summary\n\nResolves #213464 \n\n## Release Notes\n\nSpaceId can now be referenced in document-based access filters for roles\nto restrict a user's access to SLI data for spaces where they do not\nhave access.","sha":"22e64dc868c96dc3d00b0b4270c97dc57e0146a3"}}]}] BACKPORT--> Co-authored-by: Bailey Cash <bailey.cash@elastic.co> |
||
|
Kibana Machine
|
955d2bbf09
|
[9.0] [Fleet] fix UI bug displaying default agent binary source (#214360) (#214453)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] fix UI bug displaying default agent binary source (#214360)](https://github.com/elastic/kibana/pull/214360) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T17:01:08Z","message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] fix UI bug displaying default agent binary source","number":214360,"url":"https://github.com/elastic/kibana/pull/214360","mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}},"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/214360","number":214360,"mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
5423c53051
|
[9.0] [APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356) (#214421)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)](https://github.com/elastic/kibana/pull/214356) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:20:17Z","message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard","number":214356,"url":"https://github.com/elastic/kibana/pull/214356","mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}},"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/214356","number":214356,"mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
63331c0e8c
|
[9.0] [Docs] Simplify link to PRs in breaking changes and deprecation notices (#214444) (#214459)
# Backport This will backport the following commits from `main` to `9.0`: - [[Docs] Simplify link to PRs in breaking changes and deprecation notices (#214444)](https://github.com/elastic/kibana/pull/214444) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T17:50:58Z","message":"[Docs] Simplify link to PRs in breaking changes and deprecation notices (#214444)\n\nThis PR simplifies the wording in breaking changes and deprecations docs\nto feel less redundant, and re-adds a proper template for adding new\nentries.","sha":"2e80cd19f5dee2e08d96f072a001fd7ff8ac4d08","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","backport:version","v9.1.0"],"title":"[Docs] Simplify link to PRs in breaking changes and deprecation notices","number":214444,"url":"https://github.com/elastic/kibana/pull/214444","mergeCommit":{"message":"[Docs] Simplify link to PRs in breaking changes and deprecation notices (#214444)\n\nThis PR simplifies the wording in breaking changes and deprecations docs\nto feel less redundant, and re-adds a proper template for adding new\nentries.","sha":"2e80cd19f5dee2e08d96f072a001fd7ff8ac4d08"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214444","number":214444,"mergeCommit":{"message":"[Docs] Simplify link to PRs in breaking changes and deprecation notices (#214444)\n\nThis PR simplifies the wording in breaking changes and deprecations docs\nto feel less redundant, and re-adds a proper template for adding new\nentries.","sha":"2e80cd19f5dee2e08d96f072a001fd7ff8ac4d08"}}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
5d103888fe
|
[9.0] [Authz] Added reason for authorization opt-out for logstash routes (#213891) (#214435)
# Backport This will backport the following commits from `main` to `9.0`: - [[Authz] Added reason for authorization opt-out for logstash routes (#213891)](https://github.com/elastic/kibana/pull/213891) <!--- 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-03-13T15:55:22Z","message":"[Authz] Added reason for authorization opt-out for logstash routes (#213891)\n\n## Summary\n\nAdded reason for authorization opt-out for logstash routes.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5d9fd46b2a28bb21c785f3e76e528bf7eb873dc2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"[Authz] Added reason for authorization opt-out for logstash routes","number":213891,"url":"https://github.com/elastic/kibana/pull/213891","mergeCommit":{"message":"[Authz] Added reason for authorization opt-out for logstash routes (#213891)\n\n## Summary\n\nAdded reason for authorization opt-out for logstash routes.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5d9fd46b2a28bb21c785f3e76e528bf7eb873dc2"}},"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/213891","number":213891,"mergeCommit":{"message":"[Authz] Added reason for authorization opt-out for logstash routes (#213891)\n\n## Summary\n\nAdded reason for authorization opt-out for logstash routes.\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5d9fd46b2a28bb21c785f3e76e528bf7eb873dc2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com> |
||
|
Kibana Machine
|
ddcc4993d4
|
[9.0] unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653) (#214433)
# Backport This will backport the following commits from `main` to `9.0`: - [unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)](https://github.com/elastic/kibana/pull/211653) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:56:35Z","message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts","number":211653,"url":"https://github.com/elastic/kibana/pull/211653","mergeCommit":{"message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211653","number":211653,"mergeCommit":{"message":"unskip Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group6/view_edit·ts (#211653)\n\nCloses https://github.com/elastic/kibana/issues/200748\n\nFlaky test runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8023\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c886fb0f7362f18b0abb9a973c7f03b09b701446"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
|
Kibana Machine
|
e8606d3c3d
|
[9.0] unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js (#211310) (#214430)
# Backport This will backport the following commits from `main` to `9.0`: - [unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js (#211310)](https://github.com/elastic/kibana/pull/211310) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:55:41Z","message":"unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js (#211310)\n\nCloses https://github.com/elastic/kibana/issues/209228 and\nhttps://github.com/elastic/kibana/issues/209848\n\nMaps only fetch data for visible area. A smaller screen could result in\nless documents getting returned. This PR resolves the flakyness by\nsetting the screen size before running to ensure the correct screen area\nand consistent results.\n\nFlaky test runner (25)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7887\nFlaky test runner (100)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8027\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"165db29bdcfe3793b0bdc81f95be29a24cc6581f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Presentation","release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js","number":211310,"url":"https://github.com/elastic/kibana/pull/211310","mergeCommit":{"message":"unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js (#211310)\n\nCloses https://github.com/elastic/kibana/issues/209228 and\nhttps://github.com/elastic/kibana/issues/209848\n\nMaps only fetch data for visible area. A smaller screen could result in\nless documents getting returned. This PR resolves the flakyness by\nsetting the screen size before running to ensure the correct screen area\nand consistent results.\n\nFlaky test runner (25)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7887\nFlaky test runner (100)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8027\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"165db29bdcfe3793b0bdc81f95be29a24cc6581f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211310","number":211310,"mergeCommit":{"message":"unskip Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/maps/group4/file_upload/shapefile·js (#211310)\n\nCloses https://github.com/elastic/kibana/issues/209228 and\nhttps://github.com/elastic/kibana/issues/209848\n\nMaps only fetch data for visible area. A smaller screen could result in\nless documents getting returned. This PR resolves the flakyness by\nsetting the screen size before running to ensure the correct screen area\nand consistent results.\n\nFlaky test runner (25)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7887\nFlaky test runner (100)\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8027\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"165db29bdcfe3793b0bdc81f95be29a24cc6581f"}}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
Steph Milovic
|
a42d428264
|
[9.0] [Stack connector] Forward telemetryMetadata.pluginId to EIS use case header (#214269) (#214426)
# Backport This will backport the following commits from `main` to `9.0`: - [[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)](https://github.com/elastic/kibana/pull/214269) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:44:06Z","message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header","number":214269,"url":"https://github.com/elastic/kibana/pull/214269","mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},"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/214269","number":214269,"mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
d248fda7a3
|
[9.0] [Security Solution] remove group from AV workflow insight value (#214327) (#214412)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] remove group from AV workflow insight value (#214327)](https://github.com/elastic/kibana/pull/214327) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Joey F. Poon","email":"joey.poon@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:56:14Z","message":"[Security Solution] remove group from AV workflow insight value (#214327)\n\n## Summary\n\nRemoves group from the incompatible antivirus workflow insight type\nvalue.\n\nResolves:\n- https://github.com/elastic/kibana/issues/213681\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":"448fda4111113155980cc8ad5fe9ed932a9d2bcf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v9.1.0"],"title":"[Security Solution] remove group from AV workflow insight value","number":214327,"url":"https://github.com/elastic/kibana/pull/214327","mergeCommit":{"message":"[Security Solution] remove group from AV workflow insight value (#214327)\n\n## Summary\n\nRemoves group from the incompatible antivirus workflow insight type\nvalue.\n\nResolves:\n- https://github.com/elastic/kibana/issues/213681\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":"448fda4111113155980cc8ad5fe9ed932a9d2bcf"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214327","number":214327,"mergeCommit":{"message":"[Security Solution] remove group from AV workflow insight value (#214327)\n\n## Summary\n\nRemoves group from the incompatible antivirus workflow insight type\nvalue.\n\nResolves:\n- https://github.com/elastic/kibana/issues/213681\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":"448fda4111113155980cc8ad5fe9ed932a9d2bcf"}}]}] BACKPORT--> Co-authored-by: Joey F. Poon <joey.poon@elastic.co> |
||
|
Kibana Machine
|
d130e246a5
|
[9.0] [Security Solution] Hide conflict badges when rule customization is not enabled (#214365) (#214410)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)](https://github.com/elastic/kibana/pull/214365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:52:48Z","message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Hide conflict badges when rule customization is not enabled","number":214365,"url":"https://github.com/elastic/kibana/pull/214365","mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},"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/214365","number":214365,"mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
aa7b941a1b
|
[9.0] [assistant] Call to Action components (#213797) (#214402)
# Backport This will backport the following commits from `main` to `9.0`: - [[assistant] Call to Action components (#213797)](https://github.com/elastic/kibana/pull/213797) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Clint Andrew Hall","email":"clint.hall@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:47:09Z","message":"[assistant] Call to Action components (#213797)\n\n## Summary\n\nThis PR contains new Call to Action components for the AI Assistant, as\npart of the unification effort.\n\n### `@kbn/ai-assistant-cta`\n\nThe Call to Action component, as well as common use case components,\n(e.g. install knowledge base, license upgrade, etc). This package\ncontains both pure components and \"connected\" components, (see\n`@kbn/ai-assistant-component-services`, below.\n\n## Preview\n\n\n[Storybook](https://ci-artifacts.kibana.dev/storybooks/pr-213797/ai_assistant/index.html?path=/story/layout-call-to-action--call-to-action)\n\n### In the Assistant\n\n> This is just a preview, this PR does not include integration into the\nassistants.\n\n<img width=\"1488\" alt=\"Screenshot 2025-03-10 at 1 27 39 PM\"\nsrc=\"https://github.com/user-attachments/assets/62976e51-e429-4f76-8496-28db2e2d2845\"\n/>\n<img width=\"1488\" alt=\"Screenshot 2025-03-10 at 12 50 04 PM\"\nsrc=\"https://github.com/user-attachments/assets/161cf40a-48b4-4188-aa2c-633369c50a37\"\n/>\n\n### Storybook\n\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 19 PM\"\nsrc=\"https://github.com/user-attachments/assets/01bd1ac8-15f6-4abe-8600-d3544fb9b8a1\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 23 PM\"\nsrc=\"https://github.com/user-attachments/assets/94161551-27ba-4d56-9709-06f1a1433b49\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 25 PM\"\nsrc=\"https://github.com/user-attachments/assets/aa4afdb7-1804-4503-a28e-f90468463acd\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 27 PM\"\nsrc=\"https://github.com/user-attachments/assets/1c17f372-52e6-473e-8fd8-1ac1e7605304\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 30 PM\"\nsrc=\"https://github.com/user-attachments/assets/b7474888-c1e1-4a9d-b0d2-bf1c33e8d1d7\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 32 PM\"\nsrc=\"https://github.com/user-attachments/assets/4b35289d-92d0-4ec9-82b1-e64f11c70a19\"\n/>\n<img width=\"1312\" alt=\"Screenshot 2025-03-12 at 10 53 34 PM\"\nsrc=\" |
||
|
Kibana Machine
|
552e828d1c
|
[9.0] [storybook] Fix theme switcher (#214306) (#214399)
# Backport This will backport the following commits from `main` to `9.0`: - [[storybook] Fix theme switcher (#214306)](https://github.com/elastic/kibana/pull/214306) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Clint Andrew Hall","email":"clint.hall@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:38:14Z","message":"[storybook] Fix theme switcher (#214306)\n\n## Summary\n\nBoth Storybook and the theme switcher addon use Amsterdam by default.\nThis PR adds Borealis to the theme switcher and defaults it to Borealis.\n\n## NOTE\n\nThis PR may conflict with #195148 ... it should likely be merged into\nthat PR, or into `main` if the conflict is minor. I leave it to @Ikuni17\nto determine the best path forward.","sha":"9cddd5dcdd5acd9311570d7ec276cec58e719ee1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Feature:Storybook","backport:prev-minor","ci:build-storybooks","v9.1.0"],"title":"[storybook] Fix theme switcher","number":214306,"url":"https://github.com/elastic/kibana/pull/214306","mergeCommit":{"message":"[storybook] Fix theme switcher (#214306)\n\n## Summary\n\nBoth Storybook and the theme switcher addon use Amsterdam by default.\nThis PR adds Borealis to the theme switcher and defaults it to Borealis.\n\n## NOTE\n\nThis PR may conflict with #195148 ... it should likely be merged into\nthat PR, or into `main` if the conflict is minor. I leave it to @Ikuni17\nto determine the best path forward.","sha":"9cddd5dcdd5acd9311570d7ec276cec58e719ee1"}},"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/214306","number":214306,"mergeCommit":{"message":"[storybook] Fix theme switcher (#214306)\n\n## Summary\n\nBoth Storybook and the theme switcher addon use Amsterdam by default.\nThis PR adds Borealis to the theme switcher and defaults it to Borealis.\n\n## NOTE\n\nThis PR may conflict with #195148 ... it should likely be merged into\nthat PR, or into `main` if the conflict is minor. I leave it to @Ikuni17\nto determine the best path forward.","sha":"9cddd5dcdd5acd9311570d7ec276cec58e719ee1"}}]}] BACKPORT--> Co-authored-by: Clint Andrew Hall <clint.hall@elastic.co> |
||
|
Steph Milovic
|
abcfadddd1
|
[9.0] [Security solution] Bedrock region fix (#214251) (#214393)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security solution] Bedrock region fix (#214251)](https://github.com/elastic/kibana/pull/214251) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:01:03Z","message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[Security solution] Bedrock region fix","number":214251,"url":"https://github.com/elastic/kibana/pull/214251","mergeCommit":{"message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","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/214251","number":214251,"mergeCommit":{"message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214388","number":214388,"state":"OPEN"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
2ae824c47e
|
[9.0] [Security Solution] Avoid showing rules update confirmation modal on basic license (#214340) (#214385)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)](https://github.com/elastic/kibana/pull/214340) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T13:47:30Z","message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Avoid showing rules update confirmation modal on basic license","number":214340,"url":"https://github.com/elastic/kibana/pull/214340","mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},"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/214340","number":214340,"mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
4916b1df6f
|
[9.0] [DOCS] Comment out broken link (#214371) (#214387)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Comment out broken link (#214371)](https://github.com/elastic/kibana/pull/214371) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Liam Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T14:00:46Z","message":"[DOCS] Comment out broken link (#214371)\n\nChicken and egg breaking\n |
||
|
Kibana Machine
|
8925280ead
|
[9.0] [Security Solution][Detection Engine] fixes ES|QL cypress tests (#213553) (#214363)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Detection Engine] fixes ES|QL cypress tests (#213553)](https://github.com/elastic/kibana/pull/213553) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T12:40:38Z","message":"[Security Solution][Detection Engine] fixes ES|QL cypress tests (#213553)\n\n## Summary\n\n - addresses:\n - https://github.com/elastic/kibana/issues/184558\n - https://github.com/elastic/kibana/issues/184557\n - https://github.com/elastic/kibana/issues/184556\n\nbfetch was disabled for Kibana, so I removed spying for this request for\nES|QL Cypress tests\n\n\n✅ [Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7999):\n100/100 tests passed.\n\n\n✅ [[Serverless] Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8000):\n100/100 tests passed.","sha":"ee8f9676c7e134ce8a1368dc684cc66d22a2b5c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] fixes ES|QL cypress tests","number":213553,"url":"https://github.com/elastic/kibana/pull/213553","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes ES|QL cypress tests (#213553)\n\n## Summary\n\n - addresses:\n - https://github.com/elastic/kibana/issues/184558\n - https://github.com/elastic/kibana/issues/184557\n - https://github.com/elastic/kibana/issues/184556\n\nbfetch was disabled for Kibana, so I removed spying for this request for\nES|QL Cypress tests\n\n\n✅ [Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7999):\n100/100 tests passed.\n\n\n✅ [[Serverless] Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8000):\n100/100 tests passed.","sha":"ee8f9676c7e134ce8a1368dc684cc66d22a2b5c8"}},"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/213553","number":213553,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes ES|QL cypress tests (#213553)\n\n## Summary\n\n - addresses:\n - https://github.com/elastic/kibana/issues/184558\n - https://github.com/elastic/kibana/issues/184557\n - https://github.com/elastic/kibana/issues/184556\n\nbfetch was disabled for Kibana, so I removed spying for this request for\nES|QL Cypress tests\n\n\n✅ [Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7999):\n100/100 tests passed.\n\n\n✅ [[Serverless] Security Solution Detection Engine -\nCypress](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8000):\n100/100 tests passed.","sha":"ee8f9676c7e134ce8a1368dc684cc66d22a2b5c8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
0bf792894a
|
[9.0] [Dataset Quality] Wrap Discover data view checks in retries (#214172) (#214351)
# Backport This will backport the following commits from `main` to `9.0`: - [[Dataset Quality] Wrap Discover data view checks in retries (#214172)](https://github.com/elastic/kibana/pull/214172) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T11:29:44Z","message":"[Dataset Quality] Wrap Discover data view checks in retries (#214172)\n\n## 📝 Summary\n\nThis wraps the checks for the correct data view after navigation to\nDiscover into retries in the dataset quality functional tests, because\nthese checks recently failed because loading was not yet finished.\n\n🏁 closes https://github.com/elastic/kibana/issues/213751\n🏁 closes https://github.com/elastic/kibana/issues/214029\n🏁 closes https://github.com/elastic/kibana/issues/214183","sha":"535b01527133fa8e575b25be91dd21c718334e8a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-logs","v9.1.0"],"title":"[Dataset Quality] Wrap Discover data view checks in retries","number":214172,"url":"https://github.com/elastic/kibana/pull/214172","mergeCommit":{"message":"[Dataset Quality] Wrap Discover data view checks in retries (#214172)\n\n## 📝 Summary\n\nThis wraps the checks for the correct data view after navigation to\nDiscover into retries in the dataset quality functional tests, because\nthese checks recently failed because loading was not yet finished.\n\n🏁 closes https://github.com/elastic/kibana/issues/213751\n🏁 closes https://github.com/elastic/kibana/issues/214029\n🏁 closes https://github.com/elastic/kibana/issues/214183","sha":"535b01527133fa8e575b25be91dd21c718334e8a"}},"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/214172","number":214172,"mergeCommit":{"message":"[Dataset Quality] Wrap Discover data view checks in retries (#214172)\n\n## 📝 Summary\n\nThis wraps the checks for the correct data view after navigation to\nDiscover into retries in the dataset quality functional tests, because\nthese checks recently failed because loading was not yet finished.\n\n🏁 closes https://github.com/elastic/kibana/issues/213751\n🏁 closes https://github.com/elastic/kibana/issues/214029\n🏁 closes https://github.com/elastic/kibana/issues/214183","sha":"535b01527133fa8e575b25be91dd21c718334e8a"}}]}] BACKPORT--> Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
aec38fb77c
|
Update dependency chromedriver to v134 (9.0) (#214121)
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://redirect.github.com/giggio/node-chromedriver) | devDependencies | major | [`^133.0.2` -> `^134.0.0`](https://renovatebot.com/diffs/npm/chromedriver/133.0.3/134.0.0) | `134.0.2` (+1) | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v134.0.0`](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.3...134.0.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
8247f580d6
|
[9.0] [Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite (#214283) (#214305)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite (#214283)](https://github.com/elastic/kibana/pull/214283) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T00:16:45Z","message":"[Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite (#214283)\n\nskips individual failing test instead of entire test suite","sha":"95068042b1ce9b172fcfd19fd6f5c135e4ce1ac3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","v9.0.0","backport:version","v9.1.0","v9.0.1"],"title":"[Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite","number":214283,"url":"https://github.com/elastic/kibana/pull/214283","mergeCommit":{"message":"[Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite (#214283)\n\nskips individual failing test instead of entire test suite","sha":"95068042b1ce9b172fcfd19fd6f5c135e4ce1ac3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214283","number":214283,"mergeCommit":{"message":"[Security Solution] [Detections] skip individual EQL shard failure test instead of entire suite (#214283)\n\nskips individual failing test instead of entire test suite","sha":"95068042b1ce9b172fcfd19fd6f5c135e4ce1ac3"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
fa04dc0e05
|
[9.0] [Feature Flags] ECS-compliant logger (#214231) (#214304)
# Backport This will backport the following commits from `main` to `9.0`: - [[Feature Flags] ECS-compliant logger (#214231)](https://github.com/elastic/kibana/pull/214231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T23:24:40Z","message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\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":"98986a86a1086d0047d60a14425920b3c5fbc343","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] ECS-compliant logger","number":214231,"url":"https://github.com/elastic/kibana/pull/214231","mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\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":"98986a86a1086d0047d60a14425920b3c5fbc343"}},"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/214231","number":214231,"mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\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":"98986a86a1086d0047d60a14425920b3c5fbc343"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
d34f3a16b0
|
[9.0] [Stack Monitoring] New FTR for "view logs" link (#208351) (#214298)
# Backport This will backport the following commits from `main` to `9.0`: - [[Stack Monitoring] New FTR for "view logs" link (#208351)](https://github.com/elastic/kibana/pull/208351) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T22:35:28Z","message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","FTR","v8.18.0","v8.17.2","v9.1.0"],"title":"[Stack Monitoring] New FTR for \"view logs\" link","number":208351,"url":"https://github.com/elastic/kibana/pull/208351","mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208351","number":208351,"mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co> |
||
|
Kibana Machine
|
40c71ddd0c
|
[9.0] [Feature Flags] Retry provider setup (#214200) (#214288)
# Backport This will backport the following commits from `main` to `9.0`: - [[Feature Flags] Retry provider setup (#214200)](https://github.com/elastic/kibana/pull/214200) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T21:45:38Z","message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\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":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] Retry provider setup","number":214200,"url":"https://github.com/elastic/kibana/pull/214200","mergeCommit":{"message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\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":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}},"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/214200","number":214200,"mergeCommit":{"message":"[Feature Flags] Retry provider setup (#214200)\n\n## Summary\n\nWe identified that on some occasions, the Feature Flags provider times\nout when setting up, and, since we don't restart the Kibana server, it\nnever sets it up.\n\nThis PR adds a retry logic to try to set the provider in case there's an\nerror.\n\ncc @pmuellr as he found out about this bug\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":"1337c11ac3c4c94c828db52a9ab9768ccf9a1c45"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
elastic-renovate-prod[bot]
|
4c3c1f6ad4
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 69a0542 (9.0) (#214061)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `a37e513` -> `69a0542` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
ffc575724f
|
[9.0] [Fleet] Never delete @custom component templates (#214232) (#214279)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] Never delete @custom component templates (#214232)](https://github.com/elastic/kibana/pull/214232) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T19:58:40Z","message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0","backport:8.18"],"title":"[Fleet] Never delete @custom component templates","number":214232,"url":"https://github.com/elastic/kibana/pull/214232","mergeCommit":{"message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}},"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/214232","number":214232,"mergeCommit":{"message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
d356e796c4
|
[9.0] [Dashboards] Add event-annotation-group to saved object privileges (#212926) (#214277)
# Backport This will backport the following commits from `main` to `9.0`: - [[Dashboards] Add event-annotation-group to saved object privileges (#212926)](https://github.com/elastic/kibana/pull/212926) <!--- 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-03-12T19:46:06Z","message":"[Dashboards] Add event-annotation-group to saved object privileges (#212926)\n\nFixes #173320 \n\n## Summary\n\nAdds `event-annotation-group` to Dashboard saved object privileges.\n\nFixes a bug where annotation groups saved to the library can not be\nloaded by users who lack \"Saved Object Management\" privileges. Similar\nto https://github.com/elastic/kibana/pull/173332.\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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"1feeb6f6916f522776b3a060beae06551d8bc21b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","backport:all-open","v9.1.0"],"title":"[Dashboards] Add event-annotation-group to saved object privileges","number":212926,"url":"https://github.com/elastic/kibana/pull/212926","mergeCommit":{"message":"[Dashboards] Add event-annotation-group to saved object privileges (#212926)\n\nFixes #173320 \n\n## Summary\n\nAdds `event-annotation-group` to Dashboard saved object privileges.\n\nFixes a bug where annotation groups saved to the library can not be\nloaded by users who lack \"Saved Object Management\" privileges. Similar\nto https://github.com/elastic/kibana/pull/173332.\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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"1feeb6f6916f522776b3a060beae06551d8bc21b"}},"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/212926","number":212926,"mergeCommit":{"message":"[Dashboards] Add event-annotation-group to saved object privileges (#212926)\n\nFixes #173320 \n\n## Summary\n\nAdds `event-annotation-group` to Dashboard saved object privileges.\n\nFixes a bug where annotation groups saved to the library can not be\nloaded by users who lack \"Saved Object Management\" privileges. Similar\nto https://github.com/elastic/kibana/pull/173332.\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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"1feeb6f6916f522776b3a060beae06551d8bc21b"}}]}] BACKPORT--> Co-authored-by: Nick Peihl <nick.peihl@elastic.co> |
||
|
Kibana Machine
|
17a29840cd
|
[9.0] Alerts table in Rule Preview panel fills container width (#214028) (#214274)
# Backport This will backport the following commits from `main` to `9.0`: - [Alerts table in Rule Preview panel fills container width (#214028)](https://github.com/elastic/kibana/pull/214028) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-12T19:21:33Z","message":"Alerts table in Rule Preview panel fills container width (#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when #206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Feature:Detection Rule Preview","backport:prev-minor","backport:prev-major","Team:Detection Engine","v8.18.0","v9.1.0"],"title":"Alerts table in Rule Preview panel fills container width","number":214028,"url":"https://github.com/elastic/kibana/pull/214028","mergeCommit":{"message":"Alerts table in Rule Preview panel fills container width (#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when #206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214028","number":214028,"mergeCommit":{"message":"Alerts table in Rule Preview panel fills container width (#214028)\n\n## Summary\n\nAddresses https://github.com/elastic/kibana/issues/213706.\n\nI suspect that this stopped working when #206523 removed the\n`FullScreenContainer` from the inner StatefulEventsViewer component;\nthat change combined with the `display:flex` on this parent element\ncaused the table to no longer grow as expected.\n\nLuckily, the fix here was simply not using flexbox on the container.\nSince the table is the only element within this container, I saw no\nreason why flexbox was needed here; testing has confirmed this.\n\n### Screenshot (after fix; see bug for \"before\" image)\n<kbd><img width=\"1709\" alt=\"Screenshot 2025-03-11 at 5 35 43 PM\"\nsrc=\"https://github.com/user-attachments/assets/108be815-00e2-48b7-8821-e63566eefa09\"\n/></kbd>","sha":"01e31ea5f25fe1ca4d8ee30369ba5465f3041498"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
77caf7c24a
|
[9.0] [Threat Hunting Investigations] Improve API docs for notes/timeline (#213584) (#214261)
# Backport This will backport the following commits from `main` to `9.0`: - [[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)](https://github.com/elastic/kibana/pull/213584) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:55:54Z","message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","backport:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Improve API docs for notes/timeline","number":213584,"url":"https://github.com/elastic/kibana/pull/213584","mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}},"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/213584","number":213584,"mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co> |
||
|
Kibana Machine
|
d9006c569d
|
[9.0] [Security Solution] Force upgrading to target version for "Reference URLs" when base version is missing (#214161) (#214255)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Force upgrading to target version for "Reference URLs" when base version is missing (#214161)](https://github.com/elastic/kibana/pull/214161) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:41:32Z","message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing","number":214161,"url":"https://github.com/elastic/kibana/pull/214161","mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214161","number":214161,"mergeCommit":{"message":"[Security Solution] Force upgrading to target version for \"Reference URLs\" when base version is missing (#214161)\n\n**Resolves: https://github.com/elastic/kibana/issues/214171**\n\n## Summary\n\nThis PR fixes an issue with \"references\" field in -AB situations. When\nthe base version is missing we try to merge current and target arrays\nwhich leads to old and potentially broken URLs from the current version\nending up in the result.\n\nNow the behaviour is changed to always force merged version to be equal\nto target (which always has correct URLs).","sha":"07012811b29b487a3b4a664469c7a198355e44bf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
0005307641
|
[9.0] [Lens] Fix interaction perf when rendering annotations (#212888) (#214243)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Fix interaction perf when rendering annotations (#212888)](https://github.com/elastic/kibana/pull/212888) <!--- 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-03-12T17:18:40Z","message":"[Lens] Fix interaction perf when rendering annotations (#212888)\n\n## Summary\n\n- Partially fixing https://github.com/elastic/kibana/issues/212882:\nwithout passing the `markerBody` property (that is `null` if the\nlabel/text is not present) it seems to work fine when not rendering a\ntext decoration).\n- I've added the required unique `key` prop to the\n`TooltipAnnotationDetails` list of details to correctly\nupdate/reconciliate the list","sha":"3803afdbb49c6f787b2fc7ecefb3e59907647ff5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Visualizations","release_note:skip","backport:prev-minor","v9.1.0"],"title":"[Lens] Fix interaction perf when rendering annotations","number":212888,"url":"https://github.com/elastic/kibana/pull/212888","mergeCommit":{"message":"[Lens] Fix interaction perf when rendering annotations (#212888)\n\n## Summary\n\n- Partially fixing https://github.com/elastic/kibana/issues/212882:\nwithout passing the `markerBody` property (that is `null` if the\nlabel/text is not present) it seems to work fine when not rendering a\ntext decoration).\n- I've added the required unique `key` prop to the\n`TooltipAnnotationDetails` list of details to correctly\nupdate/reconciliate the list","sha":"3803afdbb49c6f787b2fc7ecefb3e59907647ff5"}},"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/212888","number":212888,"mergeCommit":{"message":"[Lens] Fix interaction perf when rendering annotations (#212888)\n\n## Summary\n\n- Partially fixing https://github.com/elastic/kibana/issues/212882:\nwithout passing the `markerBody` property (that is `null` if the\nlabel/text is not present) it seems to work fine when not rendering a\ntext decoration).\n- I've added the required unique `key` prop to the\n`TooltipAnnotationDetails` list of details to correctly\nupdate/reconciliate the list","sha":"3803afdbb49c6f787b2fc7ecefb3e59907647ff5"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
|
Kibana Machine
|
f77f11e43c
|
[9.0] Removes BA callout from AI Search Guide (#214195) (#214235)
# Backport This will backport the following commits from `main` to `9.0`: - [Removes BA callout from AI Search Guide (#214195)](https://github.com/elastic/kibana/pull/214195) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T16:56:37Z","message":"Removes BA callout from AI Search Guide (#214195)\n\n## Summary\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-12 at 16 03 57\"\nsrc=\"https://github.com/user-attachments/assets/c51516a9-3cda-4b3d-aa63-e24e37c39359\"\n/>\n\nRemoves a leftover callout from AI Search guide.\nThis page is only reachable if the user is using classic navigation in\nStack.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"455b1cca8d54126c37d53b9173381300567d3943","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v9.1.0","v9.0.1"],"title":"Removes BA callout from AI Search Guide","number":214195,"url":"https://github.com/elastic/kibana/pull/214195","mergeCommit":{"message":"Removes BA callout from AI Search Guide (#214195)\n\n## Summary\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-12 at 16 03 57\"\nsrc=\"https://github.com/user-attachments/assets/c51516a9-3cda-4b3d-aa63-e24e37c39359\"\n/>\n\nRemoves a leftover callout from AI Search guide.\nThis page is only reachable if the user is using classic navigation in\nStack.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"455b1cca8d54126c37d53b9173381300567d3943"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214195","number":214195,"mergeCommit":{"message":"Removes BA callout from AI Search Guide (#214195)\n\n## Summary\n\n<img width=\"1728\" alt=\"Screenshot 2025-03-12 at 16 03 57\"\nsrc=\"https://github.com/user-attachments/assets/c51516a9-3cda-4b3d-aa63-e24e37c39359\"\n/>\n\nRemoves a leftover callout from AI Search guide.\nThis page is only reachable if the user is using classic navigation in\nStack.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"455b1cca8d54126c37d53b9173381300567d3943"}}]}] BACKPORT--> Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co> |