kibana

mirror of https://github.com/elastic/kibana.git synced 2025-04-19 23:39:42 -04:00

Author	SHA1	Message	Date
Kibana Machine	f5054deba3	[9.0] fix(slo): group by with empty string (#217084 ) (#217110 ) # Backport This will backport the following commits from `main` to `9.0`: - [fix(slo): group by with empty string (#217084)](https://github.com/elastic/kibana/pull/217084) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T20:41:56Z","message":"fix(slo): group by with empty string (#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"fix(slo): group by with empty string","number":217084,"url":"https://github.com/elastic/kibana/pull/217084","mergeCommit":{"message":"fix(slo): group by with empty string (#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217084","number":217084,"mergeCommit":{"message":"fix(slo): group by with empty string (#217084)","sha":"5d16e44e79e58f05894786bb7462ff0e0a1e5e05"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co>	2025-04-03 23:34:52 +01:00
Kibana Machine	3663021e1b	[9.0] [Stack connectors] Fix bedrock `modelId` encoding (#216915 ) (#217062 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Stack connectors] Fix bedrock `modelId` encoding (#216915)](https://github.com/elastic/kibana/pull/216915) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T15:56:14Z","message":"[Stack connectors] Fix bedrock `modelId` encoding (#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","sdh-linked","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Stack connectors] Fix bedrock `modelId` encoding","number":216915,"url":"https://github.com/elastic/kibana/pull/216915","mergeCommit":{"message":"[Stack connectors] Fix bedrock `modelId` encoding (#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216915","number":216915,"mergeCommit":{"message":"[Stack connectors] Fix bedrock `modelId` encoding (#216915)","sha":"1edb366cb984dce3281ed4713f6f564a93bb1c2a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co>	2025-04-03 18:39:09 +01:00
Francesco Fagnani	82a091da5a	[9.0] [Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled (#216824 ) (#217048 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled (#216824)](https://github.com/elastic/kibana/pull/216824) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-03T14:41:18Z","message":"[Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled (#216824)\n\nThis PR closes #212789 by disabling the details button when the user has\nthe inspect es queries flag disabled. When the button is disabled a\ntooltip is shown.\n\n\n\nhttps://github.com/user-attachments/assets/d45d12ac-af03-4eda-8e3d-3dd693839520","sha":"467855caea880451f737de415ee21904e832390a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled","number":216824,"url":"https://github.com/elastic/kibana/pull/216824","mergeCommit":{"message":"[Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled (#216824)\n\nThis PR closes #212789 by disabling the details button when the user has\nthe inspect es queries flag disabled. When the button is disabled a\ntooltip is shown.\n\n\n\nhttps://github.com/user-attachments/assets/d45d12ac-af03-4eda-8e3d-3dd693839520","sha":"467855caea880451f737de415ee21904e832390a"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216824","number":216824,"mergeCommit":{"message":"[Synthetics] When creating a rule the details button is disabled if inspect es queries is disabled (#216824)\n\nThis PR closes #212789 by disabling the details button when the user has\nthe inspect es queries flag disabled. When the button is disabled a\ntooltip is shown.\n\n\n\nhttps://github.com/user-attachments/assets/d45d12ac-af03-4eda-8e3d-3dd693839520","sha":"467855caea880451f737de415ee21904e832390a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217041","number":217041,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-03 18:08:02 +01:00
Kibana Machine	c853073bc2	[9.0] [Docs] Kibana 9.0 release notes (#215772 ) (#217071 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Docs] Kibana 9.0 release notes (#215772)](https://github.com/elastic/kibana/pull/215772) <!--- 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-04-03T16:33:15Z","message":"[Docs] Kibana 9.0 release notes (#215772)\n\nThis PR adds 9.0 GA release notes for Kibana.\n\n- [x] convert the [9.0.0rc1 release\nnotes](https://github.com/elastic/stack-docs/blob/9.0/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc)\ninto markdown to prepare for the release to the new docs site\n- [x] Add anchors `$$kibana-PR$# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[Docs] Kibana 9.0 release notes (#215772)](https://github.com/elastic/kibana/pull/215772){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT to breaking changes for links from\nUpgrade Assistant. cc @lcawl FYI\n- [x] Run release notes tool for post-rc1 changes\n- [x] Reviews\n\n## For reviewers\n\nPreview link:\nhttps://docs-v3-preview.elastic.dev/elastic/kibana/pull/215772/release-notes/\n\nRelease notes are adopting a new structure from 9.0, identical across\nall Elastic products. Pages are broken down as follows:\n- A main page listing all new features, enhancements, and bug fixes.\nEach new release gets added to the same page. (9.1 will be above 9.0,\netc.)\n- Subpages for breaking changes, deprecations, and known issues.\n- There is no longer a \"What's new page\". This is replaced with a link\nto the blog's release announcement from this page, that will be the\n\"home page\" for release notes in the new assembled docs website:\nhttps://staging-website.elastic.co/docs/release-notes/ (not visible in\nthis PR)\n\n---------\n\nCo-authored-by: wajihaparvez <wajiha.parvez@elastic.co>","sha":"8db71f1febe4bfdbcf63dfd5a2c574ed014f44c3","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] Kibana 9.0 release notes","number":215772,"url":"https://github.com/elastic/kibana/pull/215772","mergeCommit":{"message":"[Docs] Kibana 9.0 release notes (#215772)\n\nThis PR adds 9.0 GA release notes for Kibana.\n\n- [x] convert the [9.0.0rc1 release\nnotes](https://github.com/elastic/stack-docs/blob/9.0/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc)\ninto markdown to prepare for the release to the new docs site\n- [x] Add anchors `$$kibana-PR$# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[Docs] Kibana 9.0 release notes (#215772)](https://github.com/elastic/kibana/pull/215772){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT to breaking changes for links from\nUpgrade Assistant. cc @lcawl FYI\n- [x] Run release notes tool for post-rc1 changes\n- [x] Reviews\n\n## For reviewers\n\nPreview link:\nhttps://docs-v3-preview.elastic.dev/elastic/kibana/pull/215772/release-notes/\n\nRelease notes are adopting a new structure from 9.0, identical across\nall Elastic products. Pages are broken down as follows:\n- A main page listing all new features, enhancements, and bug fixes.\nEach new release gets added to the same page. (9.1 will be above 9.0,\netc.)\n- Subpages for breaking changes, deprecations, and known issues.\n- There is no longer a \"What's new page\". This is replaced with a link\nto the blog's release announcement from this page, that will be the\n\"home page\" for release notes in the new assembled docs website:\nhttps://staging-website.elastic.co/docs/release-notes/ (not visible in\nthis PR)\n\n---------\n\nCo-authored-by: wajihaparvez <wajiha.parvez@elastic.co>","sha":"8db71f1febe4bfdbcf63dfd5a2c574ed014f44c3"}},"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/215772","number":215772,"mergeCommit":{"message":"[Docs] Kibana 9.0 release notes (#215772)\n\nThis PR adds 9.0 GA release notes for Kibana.\n\n- [x] convert the [9.0.0rc1 release\nnotes](https://github.com/elastic/stack-docs/blob/9.0/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc)\ninto markdown to prepare for the release to the new docs site\n- [x] Add anchors `$$kibana-PR$# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[Docs] Kibana 9.0 release notes (#215772)](https://github.com/elastic/kibana/pull/215772){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT to breaking changes for links from\nUpgrade Assistant. cc @lcawl FYI\n- [x] Run release notes tool for post-rc1 changes\n- [x] Reviews\n\n## For reviewers\n\nPreview link:\nhttps://docs-v3-preview.elastic.dev/elastic/kibana/pull/215772/release-notes/\n\nRelease notes are adopting a new structure from 9.0, identical across\nall Elastic products. Pages are broken down as follows:\n- A main page listing all new features, enhancements, and bug fixes.\nEach new release gets added to the same page. (9.1 will be above 9.0,\netc.)\n- Subpages for breaking changes, deprecations, and known issues.\n- There is no longer a \"What's new page\". This is replaced with a link\nto the blog's release announcement from this page, that will be the\n\"home page\" for release notes in the new assembled docs website:\nhttps://staging-website.elastic.co/docs/release-notes/ (not visible in\nthis PR)\n\n---------\n\nCo-authored-by: wajihaparvez <wajiha.parvez@elastic.co>","sha":"8db71f1febe4bfdbcf63dfd5a2c574ed014f44c3"}}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>	2025-04-03 17:04:59 +00:00
Kibana Machine	6fdc566ace	[9.0] [scout/security] improve alerting table wait (#216262 ) (#217039 ) # Backport This will backport the following commits from `main` to `9.0`: - [[scout/security] improve alerting table wait (#216262)](https://github.com/elastic/kibana/pull/216262) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T14:37:39Z","message":"[scout/security] improve alerting table wait (#216262)\n\n## Summary\n\nThis PR improves waiting for Alerts table to be loaded.\n\nRelying on the first alert might cause flakiness in the future test\ncases, I changed the rule name to be unique for test run and search\nalert based on its rule name, not the first row.\n\nIf the alert is missing or it has a wrong name, the test will fail with\nclear message:\n\n```\n Error: Alert with rule 'xys' is not displayed\n\n Timed out 10000ms waiting for expect(locator).toBeVisible()\n\n Locator: locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n Expected: visible\n Received: <element(s) not found>\n Call log:\n - Alert with rule 'xys' is not displayed with timeout 10000ms\n - waiting for locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d1707cc872ce95a251e7ba2708e29102ccbc64bf","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","test:scout","v9.1.0","v8.19.0"],"title":"[scout/security] improve alerting table wait","number":216262,"url":"https://github.com/elastic/kibana/pull/216262","mergeCommit":{"message":"[scout/security] improve alerting table wait (#216262)\n\n## Summary\n\nThis PR improves waiting for Alerts table to be loaded.\n\nRelying on the first alert might cause flakiness in the future test\ncases, I changed the rule name to be unique for test run and search\nalert based on its rule name, not the first row.\n\nIf the alert is missing or it has a wrong name, the test will fail with\nclear message:\n\n```\n Error: Alert with rule 'xys' is not displayed\n\n Timed out 10000ms waiting for expect(locator).toBeVisible()\n\n Locator: locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n Expected: visible\n Received: <element(s) not found>\n Call log:\n - Alert with rule 'xys' is not displayed with timeout 10000ms\n - waiting for locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d1707cc872ce95a251e7ba2708e29102ccbc64bf"}},"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/216262","number":216262,"mergeCommit":{"message":"[scout/security] improve alerting table wait (#216262)\n\n## Summary\n\nThis PR improves waiting for Alerts table to be loaded.\n\nRelying on the first alert might cause flakiness in the future test\ncases, I changed the rule name to be unique for test run and search\nalert based on its rule name, not the first row.\n\nIf the alert is missing or it has a wrong name, the test will fail with\nclear message:\n\n```\n Error: Alert with rule 'xys' is not displayed\n\n Timed out 10000ms waiting for expect(locator).toBeVisible()\n\n Locator: locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n Expected: visible\n Received: <element(s) not found>\n Call log:\n - Alert with rule 'xys' is not displayed with timeout 10000ms\n - waiting for locator('div.euiDataGridRow').filter({ hasText: 'xys' })\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d1707cc872ce95a251e7ba2708e29102ccbc64bf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-04-03 17:21:23 +01:00
Kibana Machine	599fe49bd4	[9.0] [ObsUx][A11y] Improve abbreviations spell for screen readers (#216954 ) (#217017 ) # Backport This will backport the following commits from `main` to `9.0`: - [[ObsUx][A11y] Improve abbreviations spell for screen readers (#216954)](https://github.com/elastic/kibana/pull/216954) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-03T12:59:55Z","message":"[ObsUx][A11y] Improve abbreviations spell for screen readers (#216954)\n\nCloses https://github.com/elastic/kibana/issues/194983 \nCloses https://github.com/elastic/kibana/issues/194982\n\n### What was done\n- Add aria-label for elements in the table (links, buttons)\n- Improve the spelling of some abbreviations for screen readers\n\n#### How to test\n- Use any screen reader in Infrastructure inventory table view, and\nhosts tables, navigate through the tables columns titles\n\n\n`fbd27a0b`-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUx][A11y] Improve abbreviations spell for screen readers","number":216954,"url":"https://github.com/elastic/kibana/pull/216954","mergeCommit":{"message":"[ObsUx][A11y] Improve abbreviations spell for screen readers (#216954)\n\nCloses https://github.com/elastic/kibana/issues/194983 \nCloses https://github.com/elastic/kibana/issues/194982\n\n### What was done\n- Add aria-label for elements in the table (links, buttons)\n- Improve the spelling of some abbreviations for screen readers\n\n#### How to test\n- Use any screen reader in Infrastructure inventory table view, and\nhosts tables, navigate through the tables columns titles\n\n\n`fbd27a0b`-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339"}},"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/216954","number":216954,"mergeCommit":{"message":"[ObsUx][A11y] Improve abbreviations spell for screen readers (#216954)\n\nCloses https://github.com/elastic/kibana/issues/194983 \nCloses https://github.com/elastic/kibana/issues/194982\n\n### What was done\n- Add aria-label for elements in the table (links, buttons)\n- Improve the spelling of some abbreviations for screen readers\n\n#### How to test\n- Use any screen reader in Infrastructure inventory table view, and\nhosts tables, navigate through the tables columns titles\n\n\n`fbd27a0b`-c052-45e6-bc98-e2446b97d4ea","sha":"8cf8c7efa93c2f089421dd9ec3775842bc817339"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>	2025-04-03 16:00:39 +01:00
Stratoula Kalafateli	7ce4926655	[9.0] [ES\|QL] Fixes the field controls FT flakiness (#216747 ) (#216981 ) # Backport This will backport the following commits from `main` to `9.0`: - [[ES\|QL] Fixes the field controls FT flakiness (#216747)](https://github.com/elastic/kibana/pull/216747) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:31:48Z","message":"[ES\|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:ES\|QL","backport:version","v9.1.0","v8.19.0"],"title":"[ES\|QL] Fixes the field controls FT flakiness","number":216747,"url":"https://github.com/elastic/kibana/pull/216747","mergeCommit":{"message":"[ES\|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9"}},"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/216747","number":216747,"mergeCommit":{"message":"[ES\|QL] Fixes the field controls FT flakiness (#216747)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216398\n\nI also stabilized the values FT as it was also flaky 🤞 \n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"cf289cbd1e18a3b0798d00f866e446ce3753d8e9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216837","number":216837,"state":"MERGED","mergeCommit":{"sha":"0ccb82963a0987926370cb9eae212270c361838f","message":"[8.x] [ES\|QL] Fixes the field controls FT flakiness (#216747) (#216837)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ES\|QL] Fixes the field controls FT flakiness\n(#216747)](https://github.com/elastic/kibana/pull/216747)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>"}}]}] BACKPORT-->	2025-04-03 14:45:36 +02:00
Arturo Lidueña	de2f174ab5	[9.0] update retrieve_elastic_doc api test (#215237 ) (#216970 ) # Backport This will backport the following commits from `main` to `9.0`: - [update retrieve_elastic_doc api test (#215237)](https://github.com/elastic/kibana/pull/215237) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T17:43:03Z","message":"update retrieve_elastic_doc api test (#215237)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Update test for `retrieve_elastic_doc` function\n\n---------\n\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"50c2237757995eae4797bbf10185de45f32cc1eb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"update retrieve_elastic_doc api test","number":215237,"url":"https://github.com/elastic/kibana/pull/215237","mergeCommit":{"message":"update retrieve_elastic_doc api test (#215237)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Update test for `retrieve_elastic_doc` function\n\n---------\n\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"50c2237757995eae4797bbf10185de45f32cc1eb"}},"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/215237","number":215237,"mergeCommit":{"message":"update retrieve_elastic_doc api test (#215237)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Update test for `retrieve_elastic_doc` function\n\n---------\n\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"50c2237757995eae4797bbf10185de45f32cc1eb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-03 11:17:31 +01:00
Kibana Machine	e658d0ed24	[9.0] [Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly. (#216391 ) (#216953 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly. (#216391)](https://github.com/elastic/kibana/pull/216391) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mashhur","email":"99575341+mashhurs@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-03T07:06:38Z","message":"[Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly. (#216391)\n\n## Summary\nCollection type was set with `agent.type` which conflicts on stack and\nmetricbeat monitorings (same `metricbeat` value). For the stack\nmonitoring, elastic-agent internally utilizes filebat or metricbeat.\nThis change hard codes the `collection_types` corresponding on each\nmonitoring type to categorize monitoring type correctly.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- ~~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- ~~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- ~~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- ~~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [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### Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\": {\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\": \"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n \"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n \"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n \"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n \"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n \"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n \"batch_size_max\": 125,\n \"batch_size_min\": 125,\n \"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\": 10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n \"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\": \"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n \"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n \"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n }\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly.","number":216391,"url":"https://github.com/elastic/kibana/pull/216391","mergeCommit":{"message":"[Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly. (#216391)\n\n## Summary\nCollection type was set with `agent.type` which conflicts on stack and\nmetricbeat monitorings (same `metricbeat` value). For the stack\nmonitoring, elastic-agent internally utilizes filebat or metricbeat.\nThis change hard codes the `collection_types` corresponding on each\nmonitoring type to categorize monitoring type correctly.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- ~~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- ~~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- ~~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- ~~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [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### Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\": {\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\": \"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n \"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n \"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n \"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n \"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n \"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n \"batch_size_max\": 125,\n \"batch_size_min\": 125,\n \"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\": 10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n \"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\": \"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n \"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n \"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n }\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736"}},"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/216391","number":216391,"mergeCommit":{"message":"[Usage collection] Replace `agent.type` with hard coded value to categorize monitoring type correctly. (#216391)\n\n## Summary\nCollection type was set with `agent.type` which conflicts on stack and\nmetricbeat monitorings (same `metricbeat` value). For the stack\nmonitoring, elastic-agent internally utilizes filebat or metricbeat.\nThis change hard codes the `collection_types` corresponding on each\nmonitoring type to categorize monitoring type correctly.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~~\n- ~~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~~\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- ~~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~\n- ~~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~~\n- ~~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~~\n- [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### Identify risks\n\n- [ ] \n\n\n### Example data\n- when stack monitoring\n```\n{\n \"clusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stats\": {\n \"collectionSource\": \"monitoring\",\n \"cacheDetails\": {\n \"updatedAt\": \"2025-03-31T23:07:32.154Z\",\n \"fetchedAt\": \"2025-03-31T23:07:33.349Z\"\n },\n \"cluster_name\": \"logstash\",\n \"timestamp\": \"2025-03-31T23:07:32Z\",\n \"version\": \"9.1.0\",\n \"cluster_uuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"stack_stats\": {\n \"logstash\": {\n \"versions\": [\n {\n \"version\": \"9.1.0\",\n \"count\": 1\n }\n ],\n \"count\": 1,\n \"cluster_stats\": {\n \"pipelines\": {\n \"count\": 1,\n \"batch_size_total\": 125,\n \"batch_size_max\": 125,\n \"batch_size_min\": 125,\n \"batch_size_avg\": 125,\n \"workers_total\": 10,\n \"workers_max\": 10,\n \"workers_min\": 10,\n \"workers_avg\": 10,\n \"sources\": {\n \"file\": true\n }\n },\n \"plugins\": [\n {\n \"name\": \"logstash-input-heartbeat\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-ruby\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-filter-mutate\",\n \"count\": 1\n },\n {\n \"name\": \"logstash-output-stdout\",\n \"count\": 1\n }\n ],\n \"monitoringClusterUuid\": \"WKhHGcv8Rt6nHwKRmKDdAw\",\n \"collection_types\": {\n \"agent\": 1\n },\n \"queues\": {\n \"memory\": 1\n }\n }\n }\n },\n \"cluster_stats\": {}\n }\n }\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c4ad8cbe8c13fb490bf2d3d56077098fa85ff736"}}]}] BACKPORT--> Co-authored-by: Mashhur <99575341+mashhurs@users.noreply.github.com>	2025-04-03 10:34:43 +01:00
Kibana Machine	0ab9cd521e	[9.0] Update LaunchDarkly (main) (#216366 ) (#216930 ) # Backport This will backport the following commits from `main` to `9.0`: - [Update LaunchDarkly (main) (#216366)](https://github.com/elastic/kibana/pull/216366) <!--- 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-04-02T20:52:36Z","message":"Update LaunchDarkly (main) (#216366)","sha":"34ba08d0cbe4b7f93fe39b4b12b5399359e060cf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Security","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update LaunchDarkly (main)","number":216366,"url":"https://github.com/elastic/kibana/pull/216366","mergeCommit":{"message":"Update LaunchDarkly (main) (#216366)","sha":"34ba08d0cbe4b7f93fe39b4b12b5399359e060cf"}},"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/216366","number":216366,"mergeCommit":{"message":"Update LaunchDarkly (main) (#216366)","sha":"34ba08d0cbe4b7f93fe39b4b12b5399359e060cf"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>	2025-04-02 23:34:56 +01:00
Kibana Machine	192213fbad	[9.0] [dashboard] fix State being dropped when editing visualize embeddables (#216901 ) (#216926 ) # Backport This will backport the following commits from `main` to `9.0`: - [[dashboard] fix State being dropped when editing visualize embeddables (#216901)](https://github.com/elastic/kibana/pull/216901) <!--- 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-04-02T20:12:27Z","message":"[dashboard] fix State being dropped when editing visualize embeddables (#216901)\n\nCloses https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve in branch specific patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1) Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add new markdown panel. This takes you to visualize editor. On return\nto dashboard, embeddable state transfer service contains the markdown\nembeddable runtime state. `panels$.value` is `{ markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered with empty\nserializedState and runtimeState from embeddable transfer service.\n3) Click save dashboard. This is where the bug lies. `panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput: { // serializedState\n}}}` but instead, remains unchanged.\n4) Click duplicate panel. New panel is added to `panels$.value`. This\ntriggers unsaved changes to be stored in session storage. Unsaved\nchanges store `panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!! }}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}` is put into session storage\n5) Edit duplicated markdown panel. This takes you to visualize editor.\nOn return to dashboard, embeddable state transfer service contains the\nnew markdown embeddable runtime state for the duplicated panel. This is\nwhere things start to fall apart. The dashboard state is loaded from\nsaved object state and `panels` contains the serialized state for both\n`markdownPanelId` and `duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from dashboard session and replaces dashboard saved\nstate. This causes the first markdown panel to render with empty\nserializedState.\n\n\n### Solution\nThe problem is resolved by updating `panels# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[dashboard] fix State being dropped when editing visualize embeddables (#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT on save. This causes step\n4 to store the current serializedState in unsaved changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","project:embeddableRebuild","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[dashboard] fix State being dropped when editing visualize embeddables","number":216901,"url":"https://github.com/elastic/kibana/pull/216901","mergeCommit":{"message":"[dashboard] fix State being dropped when editing visualize embeddables (#216901)\n\nCloses https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve in branch specific patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1) Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add new markdown panel. This takes you to visualize editor. On return\nto dashboard, embeddable state transfer service contains the markdown\nembeddable runtime state. `panels$.value` is `{ markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered with empty\nserializedState and runtimeState from embeddable transfer service.\n3) Click save dashboard. This is where the bug lies. `panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput: { // serializedState\n}}}` but instead, remains unchanged.\n4) Click duplicate panel. New panel is added to `panels$.value`. This\ntriggers unsaved changes to be stored in session storage. Unsaved\nchanges store `panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!! }}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}` is put into session storage\n5) Edit duplicated markdown panel. This takes you to visualize editor.\nOn return to dashboard, embeddable state transfer service contains the\nnew markdown embeddable runtime state for the duplicated panel. This is\nwhere things start to fall apart. The dashboard state is loaded from\nsaved object state and `panels` contains the serialized state for both\n`markdownPanelId` and `duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from dashboard session and replaces dashboard saved\nstate. This causes the first markdown panel to render with empty\nserializedState.\n\n\n### Solution\nThe problem is resolved by updating `panels# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[dashboard] fix State being dropped when editing visualize embeddables (#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT on save. This causes step\n4 to store the current serializedState in unsaved changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216901","number":216901,"mergeCommit":{"message":"[dashboard] fix State being dropped when editing visualize embeddables (#216901)\n\nCloses https://github.com/elastic/kibana/issues/216886\n\n8.17 and 8.16 resolve in branch specific patch\nhttps://github.com/elastic/kibana/pull/216910\n\n### Problem\n1) Open previously saved empty dashboard. `panels$.value` is `{}`\n2) add new markdown panel. This takes you to visualize editor. On return\nto dashboard, embeddable state transfer service contains the markdown\nembeddable runtime state. `panels$.value` is `{ markdownPanelId: {\nexplicitInput: {}}}`. Markdown panel is rendered with empty\nserializedState and runtimeState from embeddable transfer service.\n3) Click save dashboard. This is where the bug lies. `panels$.value` is\nnot updated to `{ markdownPanelId: { explicitInput: { // serializedState\n}}}` but instead, remains unchanged.\n4) Click duplicate panel. New panel is added to `panels$.value`. This\ntriggers unsaved changes to be stored in session storage. Unsaved\nchanges store `panels$.value` so `{ markdownPanelId: { explicitInput: {\n// empty!!! }}, duplicatedMarkdownPanelId: { explicitInput: {\nserializedState }}}` is put into session storage\n5) Edit duplicated markdown panel. This takes you to visualize editor.\nOn return to dashboard, embeddable state transfer service contains the\nnew markdown embeddable runtime state for the duplicated panel. This is\nwhere things start to fall apart. The dashboard state is loaded from\nsaved object state and `panels` contains the serialized state for both\n`markdownPanelId` and `duplicatedMarkdownPanelId`. Then unsaved changes\nstate is loaded from dashboard session and replaces dashboard saved\nstate. This causes the first markdown panel to render with empty\nserializedState.\n\n\n### Solution\nThe problem is resolved by updating `panels# Backport This will backport the following commits from `main` to `9.0`: {{{{raw}}}} - [[dashboard] fix State being dropped when editing visualize embeddables (#216901)](https://github.com/elastic/kibana/pull/216901){{{{/raw}}}} <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT on save. This causes step\n4 to store the current serializedState in unsaved changes.","sha":"45b7af2fbd55442924deb46166bee3eee42b7c70"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co>	2025-04-02 22:52:34 +01:00
Kibana Machine	558e132557	[9.0] [Status logging] More performant throttling (#216534 ) (#216914 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Status logging] More performant throttling (#216534)](https://github.com/elastic/kibana/pull/216534) <!--- 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-04-02T19:10:47Z","message":"[Status logging] More performant throttling (#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","performance","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Status logging] More performant throttling","number":216534,"url":"https://github.com/elastic/kibana/pull/216534","mergeCommit":{"message":"[Status logging] More performant throttling (#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6"}},"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/216534","number":216534,"mergeCommit":{"message":"[Status logging] More performant throttling (#216534)","sha":"7bf76b0e7a0de7a6b01fccedd2915e36a9b49fb6"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>	2025-04-02 21:59:10 +01:00
Kibana Machine	e7d58ae49b	[9.0] Add autocomplete support for all field types (#216765 ) (#216908 ) # Backport This will backport the following commits from `main` to `9.0`: - [Add autocomplete support for all field types (#216765)](https://github.com/elastic/kibana/pull/216765) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ioana Tagirta","email":"ioanatia@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T17:56:01Z","message":"Add autocomplete support for all field types (#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Add autocomplete support for all field types","number":216765,"url":"https://github.com/elastic/kibana/pull/216765","mergeCommit":{"message":"Add autocomplete support for all field types (#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f"}},"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/216765","number":216765,"mergeCommit":{"message":"Add autocomplete support for all field types (#216765)","sha":"00e776f1666a335c559c39fe98c22af98a672b5f"}}]}] BACKPORT--> Co-authored-by: Ioana Tagirta <ioanatia@users.noreply.github.com>	2025-04-02 20:43:25 +01:00
Tiago Costa	20132c8c8c	[9.0] chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715 ) (#216870 ) # Backport This will backport the following commits from `main` to `9.0`: - [chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715)](https://github.com/elastic/kibana/pull/216715) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T08:27:11Z","message":"chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds are failing\nthe bootstrap on macos machines during bootstrap since early today.\n\nIts usage its contained in a single dev package and therefore this PR\nattempts to port into `hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","ci:collect-apm","ci:all-cypress-suites","backport:prev-minor","backport:prev-major","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","ci:perf-check:start","v9.1.0"],"title":"chore(NA): replaces native-hdr-histogram with hdr-histogram-js","number":216715,"url":"https://github.com/elastic/kibana/pull/216715","mergeCommit":{"message":"chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds are failing\nthe bootstrap on macos machines during bootstrap since early today.\n\nIts usage its contained in a single dev package and therefore this PR\nattempts to port into `hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993"}},"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/216715","number":216715,"mergeCommit":{"message":"chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715)\n\n`native-hdr-histogram` is a native module and its prebuilds are failing\nthe bootstrap on macos machines during bootstrap since early today.\n\nIts usage its contained in a single dev package and therefore this PR\nattempts to port into `hdr-histogram-js`.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"420512a53a9343b96eb47d89bec7c2f5f9b5a993"}}]}] BACKPORT-->	2025-04-02 19:57:24 +01:00
Kibana Machine	d131250dc1	[9.0] Add default metrics dashboard for Node.js OTel (#215735 ) (#216897 ) # Backport This will backport the following commits from `main` to `9.0`: - [Add default metrics dashboard for Node.js OTel (#215735)](https://github.com/elastic/kibana/pull/215735) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Luna","email":"david.luna@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T17:00:46Z","message":"Add default metrics dashboard for Node.js OTel (#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","backport:prev-major","ci:cloud-redeploy","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"Add default metrics dashboard for Node.js OTel","number":215735,"url":"https://github.com/elastic/kibana/pull/215735","mergeCommit":{"message":"Add default metrics dashboard for Node.js OTel (#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb"}},"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/215735","number":215735,"mergeCommit":{"message":"Add default metrics dashboard for Node.js OTel (#215735)","sha":"fba2d2b8090089b06daefaa5932954da832811bb"}}]}] BACKPORT--> Co-authored-by: David Luna <david.luna@elastic.co>	2025-04-02 19:55:11 +01:00
Kibana Machine	c46210f690	[9.0] [Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer (#216642 ) (#216885 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer (#216642)](https://github.com/elastic/kibana/pull/216642) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T15:59:03Z","message":"[Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer (#216642)\n\n- Closes https://github.com/elastic/kibana/issues/214805\n\n## Summary\n\nBy default ES\|QL records don't have `_id` unless it's requested via the\nquery `METADATA`.\nThis PR fixes the JSON view inside DocViewer for ES\|QL records.\nPreviously it was relying on `textBasedHits` which gets updated when\nquery changes hence there is a possibility of loosing the reference to\nthe last viewed record.\n\n## Testing\n\nExample queries:\n```\nFROM kibana_sample_data_ecommerce METADATA _index\nFROM kibana_sample_data_ecommerce METADATA _index, _id\n```\n\n### Checklist\n\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":"43b6cc4c1df1aee03f7d3a52fbab3133c459ea43","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:DataDiscovery","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer","number":216642,"url":"https://github.com/elastic/kibana/pull/216642","mergeCommit":{"message":"[Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer (#216642)\n\n- Closes https://github.com/elastic/kibana/issues/214805\n\n## Summary\n\nBy default ES\|QL records don't have `_id` unless it's requested via the\nquery `METADATA`.\nThis PR fixes the JSON view inside DocViewer for ES\|QL records.\nPreviously it was relying on `textBasedHits` which gets updated when\nquery changes hence there is a possibility of loosing the reference to\nthe last viewed record.\n\n## Testing\n\nExample queries:\n```\nFROM kibana_sample_data_ecommerce METADATA _index\nFROM kibana_sample_data_ecommerce METADATA _index, _id\n```\n\n### Checklist\n\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":"43b6cc4c1df1aee03f7d3a52fbab3133c459ea43"}},"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/216642","number":216642,"mergeCommit":{"message":"[Discover][ES\|QL] Fix JSON view for ES\|QL record in DocViewer (#216642)\n\n- Closes https://github.com/elastic/kibana/issues/214805\n\n## Summary\n\nBy default ES\|QL records don't have `_id` unless it's requested via the\nquery `METADATA`.\nThis PR fixes the JSON view inside DocViewer for ES\|QL records.\nPreviously it was relying on `textBasedHits` which gets updated when\nquery changes hence there is a possibility of loosing the reference to\nthe last viewed record.\n\n## Testing\n\nExample queries:\n```\nFROM kibana_sample_data_ecommerce METADATA _index\nFROM kibana_sample_data_ecommerce METADATA _index, _id\n```\n\n### Checklist\n\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":"43b6cc4c1df1aee03f7d3a52fbab3133c459ea43"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co>	2025-04-02 19:19:43 +01:00
Kibana Machine	d1ba622e36	[9.0] [Synthetics] Fixed layout when monitors are grouped by (#216434 ) (#216882 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Fixed layout when monitors are grouped by (#216434)](https://github.com/elastic/kibana/pull/216434) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-04-02T07:27:10Z","message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[Synthetics] Fixed layout when monitors are grouped by","number":216434,"url":"https://github.com/elastic/kibana/pull/216434","mergeCommit":{"message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216434","number":216434,"mergeCommit":{"message":"[Synthetics] Fixed layout when monitors are grouped by (#216434)\n\nThis PR closes #207560.\n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 01 55\"\nsrc=\"https://github.com/user-attachments/assets/eee8e848-0df5-45af-a53d-8ee3c24a84fc\"\n/>\n\nAfter:\n<img width=\"1512\" alt=\"Screenshot 2025-03-31 at 12 02 19\"\nsrc=\"https://github.com/user-attachments/assets/841b537e-4f55-40e1-b76f-4492812f2da3\"\n/>","sha":"bb397ccd9ee2fa72f168468dbcc2c65daa71a228"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216750","number":216750,"state":"MERGED","mergeCommit":{"sha":"12bb59fa8f48d0c2ac529caad0f58fa09308f365","message":"[8.x] [Synthetics] Fixed layout when monitors are grouped by (#216434) (#216750)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Synthetics] Fixed layout when monitors are grouped by\n(#216434)](https://github.com/elastic/kibana/pull/216434)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>	2025-04-02 18:48:50 +01:00
Kibana Machine	67fb2fb9e4	[9.0] [Discover] Fix `getAdditionalCellActions` FTR tests (#216540 ) (#216860 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)](https://github.com/elastic/kibana/pull/216540) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T14:45:08Z","message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Discover] Fix `getAdditionalCellActions` FTR tests","number":216540,"url":"https://github.com/elastic/kibana/pull/216540","mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216540","number":216540,"mergeCommit":{"message":"[Discover] Fix `getAdditionalCellActions` FTR tests (#216540)\n\n## Summary\n\nThis PR fixes the `getAdditionalCellActions` FTR tests that started\nfailing due to an issue dismissing alerts.\n\nResolves #213300.\nResolves #213422.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d08e5521f28f4459a76b7176b902efbaea023b06"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>	2025-04-02 18:45:37 +01:00
Kibana Machine	70640db81d	[9.0] [Cloud Security] fix cnvm and cspm agentless flaky tests (#216793 ) (#216880 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Cloud Security] fix cnvm and cspm agentless flaky tests (#216793)](https://github.com/elastic/kibana/pull/216793) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Prozorov","email":"alex.prozorov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T15:30:27Z","message":"[Cloud Security] fix cnvm and cspm agentless flaky tests (#216793)\n\n## Summary\n\nThis PR fixes the flakiness of in the following issues -\n[190967](https://github.com/elastic/kibana/issues/190967) and\n[209529](https://github.com/elastic/kibana/issues/209529).\nthe observed issue was that the loader in the page headers sometimes\nremains on the screen even though the modal is already visible. Seems\nlike its stuck sometimes. Therefore changed the check to see if the\n'Launch Cloud formation' button exists instead of relying on the loader\nindicator.\n\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a7860cf6130e389d5efe8b3f49087dd9bc321fb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Cloud Security] fix cnvm and cspm agentless flaky tests","number":216793,"url":"https://github.com/elastic/kibana/pull/216793","mergeCommit":{"message":"[Cloud Security] fix cnvm and cspm agentless flaky tests (#216793)\n\n## Summary\n\nThis PR fixes the flakiness of in the following issues -\n[190967](https://github.com/elastic/kibana/issues/190967) and\n[209529](https://github.com/elastic/kibana/issues/209529).\nthe observed issue was that the loader in the page headers sometimes\nremains on the screen even though the modal is already visible. Seems\nlike its stuck sometimes. Therefore changed the check to see if the\n'Launch Cloud formation' button exists instead of relying on the loader\nindicator.\n\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a7860cf6130e389d5efe8b3f49087dd9bc321fb"}},"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/216793","number":216793,"mergeCommit":{"message":"[Cloud Security] fix cnvm and cspm agentless flaky tests (#216793)\n\n## Summary\n\nThis PR fixes the flakiness of in the following issues -\n[190967](https://github.com/elastic/kibana/issues/190967) and\n[209529](https://github.com/elastic/kibana/issues/209529).\nthe observed issue was that the loader in the page headers sometimes\nremains on the screen even though the modal is already visible. Seems\nlike its stuck sometimes. Therefore changed the check to see if the\n'Launch Cloud formation' button exists instead of relying on the loader\nindicator.\n\n\n### Checklist\n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a7860cf6130e389d5efe8b3f49087dd9bc321fb"}}]}] BACKPORT--> Co-authored-by: Alex Prozorov <alex.prozorov@elastic.co>	2025-04-02 18:27:49 +01:00
Steph Milovic	6c432a835a	[9.0] [Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700 ) (#216872 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)](https://github.com/elastic/kibana/pull/216700) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T15:04:06Z","message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery","number":216700,"url":"https://github.com/elastic/kibana/pull/216700","mergeCommit":{"message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216700","number":216700,"mergeCommit":{"message":"[Security solution] Read `config` from preconfigured connectors in Assistant/Attack Discovery (#216700)","sha":"73974a2f88a2b0971dd94c8775ebc1805f1a2078"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216869","number":216869,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-02 11:25:00 -06:00
Kibana Machine	d6901a94e9	[9.0] [Fleet] Do not allow to edit anything else than namespace for managed policies (#216701 ) (#216871 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] Do not allow to edit anything else than namespace for managed policies (#216701)](https://github.com/elastic/kibana/pull/216701) <!--- 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-04-02T15:06:02Z","message":"[Fleet] Do not allow to edit anything else than namespace for managed policies (#216701)","sha":"a750c7366e930261562a076b621f2b4dcf122b7d","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"],"title":"[Fleet] Do not allow to edit anything else than namespace for managed policies","number":216701,"url":"https://github.com/elastic/kibana/pull/216701","mergeCommit":{"message":"[Fleet] Do not allow to edit anything else than namespace for managed policies (#216701)","sha":"a750c7366e930261562a076b621f2b4dcf122b7d"}},"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/216701","number":216701,"mergeCommit":{"message":"[Fleet] Do not allow to edit anything else than namespace for managed policies (#216701)","sha":"a750c7366e930261562a076b621f2b4dcf122b7d"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>	2025-04-02 17:54:37 +01:00
Cauê Marcondes	27d2fe72e8	[9.0] [APM] Removing file (#216708 ) (#216803 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM] Removing file (#216708)](https://github.com/elastic/kibana/pull/216708) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T20:50:49Z","message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","ci:project-deploy-observability","v9.1.0"],"title":"[APM] Removing file","number":216708,"url":"https://github.com/elastic/kibana/pull/216708","mergeCommit":{"message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216708","number":216708,"mergeCommit":{"message":"[APM] Removing file (#216708)\n\nRemoving a file that was accidentally merged on this\n[PR](https://github.com/elastic/kibana/pull/215819).","sha":"f2aa2012fca9f47db5d5f50600de918c9282f465"}}]}] BACKPORT-->	2025-04-02 18:51:52 +02:00
Julia Rechkunova	6956c54738	[9.0] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143 ) (#216849 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143)](https://github.com/elastic/kibana/pull/210143) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T16:24:43Z","message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-major","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard","number":210143,"url":"https://github.com/elastic/kibana/pull/210143","mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210882","number":210882,"state":"MERGED","mergeCommit":{"sha":"daf2be3efe6458e03e9cb08cedab95c41fbc2129","message":"[8.18] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210882)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Discover Session] Fix "Untitled" export title when\nexporting CSV on a dashboard\n(#210143)](https://github.com/elastic/kibana/pull/210143)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210143","number":210143,"mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210883","number":210883,"state":"MERGED","mergeCommit":{"sha":"2dc7b4f7d9f549907ca21e7d3cf79155d8d71b82","message":"[8.x] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210883)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Discover Session] Fix "Untitled" export title when\nexporting CSV on a dashboard\n(#210143)](https://github.com/elastic/kibana/pull/210143)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210881","number":210881,"state":"MERGED","mergeCommit":{"sha":"bf94e613b9cca71d7071101b5444b6e461ffc20f","message":"[8.17] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210881)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Discover Session] Fix "Untitled" export title when\nexporting CSV on a dashboard\n(#210143)](https://github.com/elastic/kibana/pull/210143)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\n---------\n\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>"}},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210880","number":210880,"state":"MERGED","mergeCommit":{"sha":"90c24f5dd1bf2979e46f5fc2f0e88f40d1f3a3d3","message":"[8.16] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210880)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Discover Session] Fix "Untitled" export title when\nexporting CSV on a dashboard\n(#210143)](https://github.com/elastic/kibana/pull/210143)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\n---------\n\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>	2025-04-02 18:40:22 +02:00
Kibana Machine	b43b00920c	[9.0] Update task state version after execution. (#215559 ) (#216247 ) # Backport This will backport the following commits from `main` to `9.0`: - [Update task state version after execution. (#215559)](https://github.com/elastic/kibana/pull/215559) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ersin Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-27T23:58:41Z","message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"Update task state version after execution.","number":215559,"url":"https://github.com/elastic/kibana/pull/215559","mergeCommit":{"message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215559","number":215559,"mergeCommit":{"message":"Update task state version after execution. (#215559)\n\nThis PR fixes the missing stateVersion update in the `partialUpdate`\nmethod.\n\n\n[update](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/task_manager/server/buffered_task_store.ts#L62)\nmethod already uses the validated task that already has the stateVersion\nfield.\n\nbut the `partialUpdate` misses it.","sha":"6373b0c65a084088f4ac455c59bdc11e72b1b5d7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com>	2025-04-02 17:17:59 +01:00
Kibana Machine	7c0609ef4c	[9.0] [Security Solution] Fix alerts table grouping severity stats not showing badge (#216738 ) (#216847 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)](https://github.com/elastic/kibana/pull/216738) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:42:46Z","message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n\| Before \| After \|\n\| ------------- \| ------------- \|\n\| ![Screenshot 2025-04-01 at 5 00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n\| ![Screenshot 2025-04-01 at 5 05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n\|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5","v8.16.7"],"title":"[Security Solution] Fix alerts table grouping severity stats not showing badge","number":216738,"url":"https://github.com/elastic/kibana/pull/216738","mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n\| Before \| After \|\n\| ------------- \| ------------- \|\n\| ![Screenshot 2025-04-01 at 5 00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n\| ![Screenshot 2025-04-01 at 5 05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n\|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216738","number":216738,"mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n\| Before \| After \|\n\| ------------- \| ------------- \|\n\| ![Screenshot 2025-04-01 at 5 00\n16 PM](https://github.com/user-attachments/assets/c64b8140-4c16-4618-b8b0-0c295e9e35d5)\n\| ![Screenshot 2025-04-01 at 5 05\n48 PM](https://github.com/user-attachments/assets/5b06ee16-b6eb-4d33-9510-75a80c569718)\n\|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2025-04-02 16:46:34 +01:00
Kibana Machine	2c3d0d6863	[9.0] Dev console - improve autocomplete for ES\|QL _query API (#216795 ) (#216835 ) # Backport This will backport the following commits from `main` to `9.0`: - [Dev console - improve autocomplete for ES\|QL _query API (#216795)](https://github.com/elastic/kibana/pull/216795) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ioana Tagirta","email":"ioanatia@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T13:20:44Z","message":"Dev console - improve autocomplete for ES\|QL _query API (#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Dev console - improve autocomplete for ES\|QL _query API","number":216795,"url":"https://github.com/elastic/kibana/pull/216795","mergeCommit":{"message":"Dev console - improve autocomplete for ES\|QL _query API (#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f"}},"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/216795","number":216795,"mergeCommit":{"message":"Dev console - improve autocomplete for ES\|QL _query API (#216795)","sha":"2687a8d73f4e9930052592a837e4aad3a3bb5a0f"}}]}] BACKPORT--> Co-authored-by: Ioana Tagirta <ioanatia@users.noreply.github.com>	2025-04-02 16:30:57 +01:00
Kibana Machine	ae0c91447d	[9.0] [ObsUX][A11y] Add announcement keyboard elements improvements (#216592 ) (#216800 ) # Backport This will backport the following commits from `main` to `9.0`: - [[ObsUX][A11y] Add announcement keyboard elements improvements (#216592)](https://github.com/elastic/kibana/pull/216592) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T11:24:26Z","message":"[ObsUX][A11y] Add announcement keyboard elements improvements (#216592)\n\nCloses https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome elements on the Infrastructure Inventory were not accessible or\ntheir interaction with the keyboard was not properly announced to the\nusers, see issue for steps to reproduce, use a screen reader to test.\n\n### What was done\n\n#### Groupby buttons \n\n- Replace link element by button\n- Add announcement when interacting with the button, i.e., when\nclicking/selecting the `All` button nothing changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n#### Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon, the button didn't\nhave any action, it only shows the selected color for minimum and\nmaximum for the selected color palette\n- Fix ui alignment of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot 2025-04-01 at 08 58 40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54 31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX][A11y] Add announcement keyboard elements improvements","number":216592,"url":"https://github.com/elastic/kibana/pull/216592","mergeCommit":{"message":"[ObsUX][A11y] Add announcement keyboard elements improvements (#216592)\n\nCloses https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome elements on the Infrastructure Inventory were not accessible or\ntheir interaction with the keyboard was not properly announced to the\nusers, see issue for steps to reproduce, use a screen reader to test.\n\n### What was done\n\n#### Groupby buttons \n\n- Replace link element by button\n- Add announcement when interacting with the button, i.e., when\nclicking/selecting the `All` button nothing changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n#### Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon, the button didn't\nhave any action, it only shows the selected color for minimum and\nmaximum for the selected color palette\n- Fix ui alignment of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot 2025-04-01 at 08 58 40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54 31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44"}},"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/216592","number":216592,"mergeCommit":{"message":"[ObsUX][A11y] Add announcement keyboard elements improvements (#216592)\n\nCloses https://github.com/elastic/kibana/issues/216029\n\n## Summary\n\nSome elements on the Infrastructure Inventory were not accessible or\ntheir interaction with the keyboard was not properly announced to the\nusers, see issue for steps to reproduce, use a screen reader to test.\n\n### What was done\n\n#### Groupby buttons \n\n- Replace link element by button\n- Add announcement when interacting with the button, i.e., when\nclicking/selecting the `All` button nothing changes\n\n\nhttps://github.com/user-attachments/assets/da7a973d-26a4-4288-8aea-e1dd7a43ea6f\n\n#### Legend options\n\n- Replace `EuiColorPickerSwatch` button by and icon, the button didn't\nhave any action, it only shows the selected color for minimum and\nmaximum for the selected color palette\n- Fix ui alignment of checkbox elements\n\nBefore\n\n<img width=\"452\" alt=\"Screenshot 2025-04-01 at 08 58 40\"\nsrc=\"https://github.com/user-attachments/assets/66d7e733-8f95-4d76-9eb2-549b8421b888\"\n/>\n\nAfter\n\n<img width=\"585\" alt=\"Screenshot 2025-04-01 at 08 54 31\"\nsrc=\"https://github.com/user-attachments/assets/825a9f84-ddaf-43dc-b136-e268592818c1\"\n/>","sha":"ecd83ce211cdf2dd9bca43c8e6c15473dc8e1c44"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>	2025-04-02 14:11:09 +01:00
Kibana Machine	1be9db400e	[9.0] [ObsUX] [A11y] Fix focus on metadata table content (#216628 ) (#216779 ) # Backport This will backport the following commits from `main` to `9.0`: - [[ObsUX] [A11y] Fix focus on metadata table content (#216628)](https://github.com/elastic/kibana/pull/216628) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-02T09:25:05Z","message":"[ObsUX] [A11y] Fix focus on metadata table content (#216628)\n\nCloses https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost Detail page has a Metadata tab with expandable table rows. These\nrows add content to the page in an unexpected reading order. Content\nshould be expanded underneath the show more / less trigger. Focus should\nstay on the toggle.\n\nBefore\n\n\n`7993abdc`-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ObsUX] [A11y] Fix focus on metadata table content","number":216628,"url":"https://github.com/elastic/kibana/pull/216628","mergeCommit":{"message":"[ObsUX] [A11y] Fix focus on metadata table content (#216628)\n\nCloses https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost Detail page has a Metadata tab with expandable table rows. These\nrows add content to the page in an unexpected reading order. Content\nshould be expanded underneath the show more / less trigger. Focus should\nstay on the toggle.\n\nBefore\n\n\n`7993abdc`-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265"}},"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/216628","number":216628,"mergeCommit":{"message":"[ObsUX] [A11y] Fix focus on metadata table content (#216628)\n\nCloses https://github.com/elastic/kibana/issues/195014\n\n### Summary\n\nHost Detail page has a Metadata tab with expandable table rows. These\nrows add content to the page in an unexpected reading order. Content\nshould be expanded underneath the show more / less trigger. Focus should\nstay on the toggle.\n\nBefore\n\n\n`7993abdc`-b693-4c0f-a161-8533cf6b2e3b","sha":"7b1d7bf08a8e48b0f0f5b57573e250faa7acf265"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>	2025-04-02 12:16:04 +01:00
Kibana Machine	e82175e4c5	[9.0] [scout] Add tests to Scout CLI commands (#216272 ) (#216752 ) # Backport This will backport the following commits from `main` to `9.0`: - [[scout] Add tests to Scout CLI commands (#216272)](https://github.com/elastic/kibana/pull/216272) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cesare de Cal","email":"cesare.decal@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T07:35:49Z","message":"[scout] Add tests to Scout CLI commands (#216272)\n\nDepends on https://github.com/elastic/kibana/pull/216052 being merged. \n\n---\n\nThis is a follow-up PR based on @dmlemeshko's\n[comment](https://github.com/elastic/kibana/pull/216052/files#r2015868889).\n\nThis PR introduces the following changes:\n\n* Adds tests to all Scout CLI commands: `discover-playwright-configs`,\n`run-tests`, `start-server`\n* Some of the tests verify that this change works correctly:\nhttps://github.com/elastic/kibana/pull/216052\n* For each command file it separates the `run` function from the\n`Command` itself to make the `run` handler easier to test.\n\n### Bonus: code coverage\n\nThe `Command`s itself aren't tested (which explains the uncovered lines\nbelow) - happy to receive your feedback on this.\n\n\| File \| % Stmts \| % Branch \| % Funcs \| % Lines \| Uncovered Line #s\n\n\|----------------------------------------------------------------------------------------\|---------\|----------\|---------\|---------\|------------------------------------------------------------------------------------\n\| platform/packages/shared/kbn-scout/src/cli \| 91.89 \| 78.57 \| 66.66 \|\n91.89 \|\n\| config_discovery.ts \| 95.65 \| 90 \| 80 \| 95.65 \| 88\n\| run_tests.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 44\n\| start_server.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 34\n\n### Try it out locally\n\n```shell\nyarn test:jest --config src/platform/packages/shared/kbn-scout/jest.config.js --coverage\n```","sha":"e1b172a2644338b93930fdb760fd8b5e5e5f9915","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","test:scout","v9.1.0","v8.19.0"],"title":"[scout] Add tests to Scout CLI commands","number":216272,"url":"https://github.com/elastic/kibana/pull/216272","mergeCommit":{"message":"[scout] Add tests to Scout CLI commands (#216272)\n\nDepends on https://github.com/elastic/kibana/pull/216052 being merged. \n\n---\n\nThis is a follow-up PR based on @dmlemeshko's\n[comment](https://github.com/elastic/kibana/pull/216052/files#r2015868889).\n\nThis PR introduces the following changes:\n\n* Adds tests to all Scout CLI commands: `discover-playwright-configs`,\n`run-tests`, `start-server`\n* Some of the tests verify that this change works correctly:\nhttps://github.com/elastic/kibana/pull/216052\n* For each command file it separates the `run` function from the\n`Command` itself to make the `run` handler easier to test.\n\n### Bonus: code coverage\n\nThe `Command`s itself aren't tested (which explains the uncovered lines\nbelow) - happy to receive your feedback on this.\n\n\| File \| % Stmts \| % Branch \| % Funcs \| % Lines \| Uncovered Line #s\n\n\|----------------------------------------------------------------------------------------\|---------\|----------\|---------\|---------\|------------------------------------------------------------------------------------\n\| platform/packages/shared/kbn-scout/src/cli \| 91.89 \| 78.57 \| 66.66 \|\n91.89 \|\n\| config_discovery.ts \| 95.65 \| 90 \| 80 \| 95.65 \| 88\n\| run_tests.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 44\n\| start_server.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 34\n\n### Try it out locally\n\n```shell\nyarn test:jest --config src/platform/packages/shared/kbn-scout/jest.config.js --coverage\n```","sha":"e1b172a2644338b93930fdb760fd8b5e5e5f9915"}},"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/216272","number":216272,"mergeCommit":{"message":"[scout] Add tests to Scout CLI commands (#216272)\n\nDepends on https://github.com/elastic/kibana/pull/216052 being merged. \n\n---\n\nThis is a follow-up PR based on @dmlemeshko's\n[comment](https://github.com/elastic/kibana/pull/216052/files#r2015868889).\n\nThis PR introduces the following changes:\n\n* Adds tests to all Scout CLI commands: `discover-playwright-configs`,\n`run-tests`, `start-server`\n* Some of the tests verify that this change works correctly:\nhttps://github.com/elastic/kibana/pull/216052\n* For each command file it separates the `run` function from the\n`Command` itself to make the `run` handler easier to test.\n\n### Bonus: code coverage\n\nThe `Command`s itself aren't tested (which explains the uncovered lines\nbelow) - happy to receive your feedback on this.\n\n\| File \| % Stmts \| % Branch \| % Funcs \| % Lines \| Uncovered Line #s\n\n\|----------------------------------------------------------------------------------------\|---------\|----------\|---------\|---------\|------------------------------------------------------------------------------------\n\| platform/packages/shared/kbn-scout/src/cli \| 91.89 \| 78.57 \| 66.66 \|\n91.89 \|\n\| config_discovery.ts \| 95.65 \| 90 \| 80 \| 95.65 \| 88\n\| run_tests.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 44\n\| start_server.ts \| 85.71 \| 50 \| 50 \| 85.71 \| 34\n\n### Try it out locally\n\n```shell\nyarn test:jest --config src/platform/packages/shared/kbn-scout/jest.config.js --coverage\n```","sha":"e1b172a2644338b93930fdb760fd8b5e5e5f9915"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Cesare de Cal <cesare.decal@elastic.co>	2025-04-02 10:16:54 +01:00
Kibana Machine	30d589862b	[9.0] [FIPS] Skips license check test for FIPS test suite (#216056 ) (#216730 ) # Backport This will backport the following commits from `main` to `9.0`: - [[FIPS] Skips license check test for FIPS test suite (#216056)](https://github.com/elastic/kibana/pull/216056) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T21:23:35Z","message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Core","release_note:skip","v9.0.0","Feature:FIPS","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[FIPS] Skips license check test for FIPS test suite","number":216056,"url":"https://github.com/elastic/kibana/pull/216056","mergeCommit":{"message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216056","number":216056,"mergeCommit":{"message":"[FIPS] Skips license check test for FIPS test suite (#216056)\n\n## Summary\n\nSkips license checking test in FIPS mode. FIPS runs with the platinum\nlicense so having a test which asserts `basic` causes the CI to fail.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1fdf5d450f598e95e367140dbbac0abd24f96ba6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com>	2025-04-02 00:15:06 +01:00
Kibana Machine	20c2db2b90	[9.0] [Index Management] Copy change for index mode field in index templates (#216624 ) (#216650 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Index Management] Copy change for index mode field in index templates (#216624)](https://github.com/elastic/kibana/pull/216624) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T13:31:25Z","message":"[Index Management] Copy change for index mode field in index templates (#216624)\n\n## Summary\n\nThis PR renames the title of the the index mode field from \"Data stream\nindex mode\" to \"Index mode\" since this field is no longer\nenabled/disabled based on the data streams field (since\nhttps://github.com/elastic/kibana/pull/207413).\n\nWe also switch the places of the index mode field and the data retention\nfield, since the data retention field is displayed only when data\nstreams toggle is switched on, so it makes sense that it is next to this\nfield.\n\n<img width=\"1166\" alt=\"Screenshot 2025-04-01 at 11 46 45\"\nsrc=\"`40e46c91`-9120-44eb-b0de-ef700a5eeedd","sha":"c80325db10443d119eb83a0b1b4fd9c88c2699f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Index Management] Copy change for index mode field in index templates","number":216624,"url":"https://github.com/elastic/kibana/pull/216624","mergeCommit":{"message":"[Index Management] Copy change for index mode field in index templates (#216624)\n\n## Summary\n\nThis PR renames the title of the the index mode field from \"Data stream\nindex mode\" to \"Index mode\" since this field is no longer\nenabled/disabled based on the data streams field (since\nhttps://github.com/elastic/kibana/pull/207413).\n\nWe also switch the places of the index mode field and the data retention\nfield, since the data retention field is displayed only when data\nstreams toggle is switched on, so it makes sense that it is next to this\nfield.\n\n<img width=\"1166\" alt=\"Screenshot 2025-04-01 at 11 46 45\"\nsrc=\"`40e46c91`-9120-44eb-b0de-ef700a5eeedd","sha":"c80325db10443d119eb83a0b1b4fd9c88c2699f0"}},"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/216624","number":216624,"mergeCommit":{"message":"[Index Management] Copy change for index mode field in index templates (#216624)\n\n## Summary\n\nThis PR renames the title of the the index mode field from \"Data stream\nindex mode\" to \"Index mode\" since this field is no longer\nenabled/disabled based on the data streams field (since\nhttps://github.com/elastic/kibana/pull/207413).\n\nWe also switch the places of the index mode field and the data retention\nfield, since the data retention field is displayed only when data\nstreams toggle is switched on, so it makes sense that it is next to this\nfield.\n\n<img width=\"1166\" alt=\"Screenshot 2025-04-01 at 11 46 45\"\nsrc=\"`40e46c91`-9120-44eb-b0de-ef700a5eeedd","sha":"c80325db10443d119eb83a0b1b4fd9c88c2699f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>	2025-04-01 21:29:52 +01:00
Cauê Marcondes	cb3c7e9140	[9.0] [APM] Fix query for transaction marks (#215819 ) (#216668 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM] Fix query for transaction marks (#215819)](https://github.com/elastic/kibana/pull/215819) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sunghyun Kim","email":"cqbqdd11519@gmail.com"},"sourceCommit":{"committedDate":"2025-04-01T15:05:42Z","message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","💝community","backport:all-open","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix query for transaction marks","number":215819,"url":"https://github.com/elastic/kibana/pull/215819","mergeCommit":{"message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215819","number":215819,"mergeCommit":{"message":"[APM] Fix query for transaction marks (#215819)\n\n## Summary\n\nThere is a bug in kibana 8.17, where no transaction marks are shown in\nthe APM's transaction waterfall ui.\nThe marks are stored in the field `transaction.marks.agent` of\ndocuments, but kibana apm server is querying `transaction.agent.marks`.\n\nThis PR fixes the field name.\n\n\nI also added `span.id` in the query source to include the marks in the\nresponse, even if there is no `span.links` in the transaction info.\n(I found the case from RUM data with `transaction.marks.agent` but\nwithout `span.links`, so that the response does not include marks\nbecause there is no `source` field in the query result)\n\nI am not sure if it's the right way to fix it, as i have no\nunderstanding about the relationsip between `transaction.marks.agent`\nand `span.links`, so this PR is more like a bug report.\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\nNone","sha":"d4d1c2b6ddf98859e5d36654eab0ca71cefc8808"}}]}] BACKPORT--> Co-authored-by: Sunghyun Kim <cqbqdd11519@gmail.com>	2025-04-01 18:43:53 +01:00
Kibana Machine	1a0df35c78	[9.0] [Security Solution][Endpoint] Un-skip space awareness FTR tests (#216515 ) (#216680 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Endpoint] Un-skip space awareness FTR tests (#216515)](https://github.com/elastic/kibana/pull/216515) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T15:44:19Z","message":"[Security Solution][Endpoint] Un-skip space awareness FTR tests (#216515)\n\n## Summary\n\n- Unskips the Space awareness FTR tests. Unclear why they were failing\nand logs did not provide much information.\n- added some minor info. logs to the data loading part\n\n\nCloses #203898","sha":"ee3e7bfb60bcf471006c0413a0a9e27409a29538","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","v9.1.0"],"title":"[Security Solution][Endpoint] Un-skip space awareness FTR tests","number":216515,"url":"https://github.com/elastic/kibana/pull/216515","mergeCommit":{"message":"[Security Solution][Endpoint] Un-skip space awareness FTR tests (#216515)\n\n## Summary\n\n- Unskips the Space awareness FTR tests. Unclear why they were failing\nand logs did not provide much information.\n- added some minor info. logs to the data loading part\n\n\nCloses #203898","sha":"ee3e7bfb60bcf471006c0413a0a9e27409a29538"}},"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/216515","number":216515,"mergeCommit":{"message":"[Security Solution][Endpoint] Un-skip space awareness FTR tests (#216515)\n\n## Summary\n\n- Unskips the Space awareness FTR tests. Unclear why they were failing\nand logs did not provide much information.\n- added some minor info. logs to the data loading part\n\n\nCloses #203898","sha":"ee3e7bfb60bcf471006c0413a0a9e27409a29538"}}]}] BACKPORT--> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>	2025-04-01 18:24:56 +01:00
Kibana Machine	6c6c7c5077	[9.0] [Vega] Fix update vega spec in functional tests (#216620 ) (#216676 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Vega] Fix update vega spec in functional tests (#216620)](https://github.com/elastic/kibana/pull/216620) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T15:26:17Z","message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Visualizations","release_note:skip","backport:all-open","v9.1.0"],"title":"[Vega] Fix update vega spec in functional tests","number":216620,"url":"https://github.com/elastic/kibana/pull/216620","mergeCommit":{"message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}},"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/216620","number":216620,"mergeCommit":{"message":"[Vega] Fix update vega spec in functional tests (#216620)\n\n## Summary\n\nThis PR fixes a flaky test practice that was causing issues in 7.17\nbranch.\nThe flakiness was introduced long ago when the choosen method to\nupdate/add more content to the Vega Spec was done by manually clicking\nin the Vega spec editor the left border (where the editor shows the line\nnumbers) to select all the text in the editor and go to the last line\nbut a char before the end of the text (right before the closing\nbracket).\n\nThe failure highlighted by\nhttps://github.com/elastic/kibana/issues/213646 where caused the added\n`config` text positioned in the wrong line/column due to the Konami Code\nlike type of functional test operation.\n\n\nThe fix instead provides a more robust method: it takes the written text\nin the editor, parse it to JSON, update the JSON and write it back again\nto the editor.\n\nWill fix the issue https://github.com/elastic/kibana/issues/213646 when\nbackported to 7.17.","sha":"200ec10593480edc3ef7b0d0ea77b29c787d1382"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co>	2025-04-01 18:24:33 +01:00
Kibana Machine	020c8fce78	[9.0] [docs] Add missing mapped pages (#216681 ) (#216694 ) # Backport This will backport the following commits from `main` to `9.0`: - [[docs] Add missing mapped pages (#216681)](https://github.com/elastic/kibana/pull/216681) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Colleen McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T16:24:52Z","message":"[docs] Add missing mapped pages (#216681)\n\nAdd missing mapped pages listed in [Possible invalid redirects to\n8.18](https://docs.google.com/spreadsheets/d/1bQQVc-QwwXDSd24Vw6Q62dnn_9bxsBeAzeWJAdyxdqI/edit?gid=2025227146#gid=2025227146).","sha":"c8fc5e74d9625af9fecc0f7e8a4b0a3a765277bb","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","documentation","backport:version","v9.1.0"],"title":"[docs] Add missing mapped pages","number":216681,"url":"https://github.com/elastic/kibana/pull/216681","mergeCommit":{"message":"[docs] Add missing mapped pages (#216681)\n\nAdd missing mapped pages listed in [Possible invalid redirects to\n8.18](https://docs.google.com/spreadsheets/d/1bQQVc-QwwXDSd24Vw6Q62dnn_9bxsBeAzeWJAdyxdqI/edit?gid=2025227146#gid=2025227146).","sha":"c8fc5e74d9625af9fecc0f7e8a4b0a3a765277bb"}},"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/216681","number":216681,"mergeCommit":{"message":"[docs] Add missing mapped pages (#216681)\n\nAdd missing mapped pages listed in [Possible invalid redirects to\n8.18](https://docs.google.com/spreadsheets/d/1bQQVc-QwwXDSd24Vw6Q62dnn_9bxsBeAzeWJAdyxdqI/edit?gid=2025227146#gid=2025227146).","sha":"c8fc5e74d9625af9fecc0f7e8a4b0a3a765277bb"}}]}] BACKPORT--> Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co>	2025-04-01 17:14:36 +00:00
jennypavlova	29998ee927	[9.0] [APM][OTel] Add url.full fallback (#215397 ) (#216635 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM][OTel] Add url.full fallback (#215397)](https://github.com/elastic/kibana/pull/215397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:50:28Z","message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","ci:project-redeploy","v9.1.0"],"title":"[APM][OTel] Add url.full fallback","number":215397,"url":"https://github.com/elastic/kibana/pull/215397","mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215397","number":215397,"mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n![image](https://github.com/user-attachments/assets/e76f2901-050a-4ee3-b536-a057d45454e2)\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n![image](https://github.com/user-attachments/assets/b9ad8a8b-f89a-449c-a053-a5628c2fa620)\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n![image](https://github.com/user-attachments/assets/93ffac41-9f79-4d09-ab69-ae5c8e782750)","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}}]}] BACKPORT-->	2025-04-01 17:27:14 +01:00
Kibana Machine	b587f643d0	[9.0] [APM] Span links: add tooltip explaining the reason for missing linked span details (#216487 ) (#216660 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM] Span links: add tooltip explaining the reason for missing linked span details (#216487)](https://github.com/elastic/kibana/pull/216487) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T14:39:00Z","message":"[APM] Span links: add tooltip explaining the reason for missing linked span details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching details for the Span Links flyout, it is possible that the\nparent span has not yet been ingested, resulting in an 'Unknown' service\nname which might be misleading to users. To avoid confusion, we decided\nto add tooltip to the icon with explanation.\n\n<img width=\"2558\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n### How to test:\n- use edge-oblt data\n- in Applications go to `accountingservice` service\n- select `orders receive` transaction\n- in trace waterfall click `Span Links` button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72","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"],"title":"[APM] Span links: add tooltip explaining the reason for missing linked span details","number":216487,"url":"https://github.com/elastic/kibana/pull/216487","mergeCommit":{"message":"[APM] Span links: add tooltip explaining the reason for missing linked span details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching details for the Span Links flyout, it is possible that the\nparent span has not yet been ingested, resulting in an 'Unknown' service\nname which might be misleading to users. To avoid confusion, we decided\nto add tooltip to the icon with explanation.\n\n<img width=\"2558\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n### How to test:\n- use edge-oblt data\n- in Applications go to `accountingservice` service\n- select `orders receive` transaction\n- in trace waterfall click `Span Links` button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72"}},"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/216487","number":216487,"mergeCommit":{"message":"[APM] Span links: add tooltip explaining the reason for missing linked span details (#216487)\n\nCloses #214558\n\n### Summary\n\nWhen fetching details for the Span Links flyout, it is possible that the\nparent span has not yet been ingested, resulting in an 'Unknown' service\nname which might be misleading to users. To avoid confusion, we decided\nto add tooltip to the icon with explanation.\n\n<img width=\"2558\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9e29544b-28df-43b2-9987-24c6d90c481e\"\n/>\n\n### How to test:\n- use edge-oblt data\n- in Applications go to `accountingservice` service\n- select `orders receive` transaction\n- in trace waterfall click `Span Links` button","sha":"e7edff9ddcd5e7d80903c8c3139eab87d0aadc72"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>	2025-04-01 17:26:32 +01:00
Julia Bardi	659781ee3b	[9.0][Fleet] Update inputs_with_standalone_docker_agent.ts (#216623 ) Related to https://github.com/elastic/kibana/pull/216591 Fix docker image	2025-04-01 16:43:58 +02:00
Kibana Machine	3afe733159	[9.0] [APM][OTel] Fix spanlink invalid filter (#215322 ) (#216609 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM][OTel] Fix spanlink invalid filter (#215322)](https://github.com/elastic/kibana/pull/215322) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:43:19Z","message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.5"],"title":"[APM][OTel] Fix spanlink invalid filter","number":215322,"url":"https://github.com/elastic/kibana/pull/215322","mergeCommit":{"message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215322","number":215322,"mergeCommit":{"message":"[APM][OTel] Fix spanlink invalid filter (#215322)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/215101\n\nThis PR adds an optional check for `span.id` (this value is always\npopulated) when redirecting to an error within a span link.","sha":"8fc00a088f3be5d0252a18c953444a2518f65f10"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>	2025-04-01 12:25:54 +01:00
Kibana Machine	a215d256df	[9.0] [Fleet] enable flaky test (#216460 ) (#216591 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] enable flaky test (#216460)](https://github.com/elastic/kibana/pull/216460) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T08:29:23Z","message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] enable flaky test","number":216460,"url":"https://github.com/elastic/kibana/pull/216460","mergeCommit":{"message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216460","number":216460,"mergeCommit":{"message":"[Fleet] enable flaky test (#216460)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/184681\n\n\n### Checklist\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"69a7108313fab9520fb1f5f7281b5a17e76e3f92"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>	2025-04-01 11:13:05 +01:00
Kibana Machine	3c0fe5e9d3	[9.0] [Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393 ) (#216586 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)](https://github.com/elastic/kibana/pull/215393) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-01T08:07:08Z","message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Engine","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules","number":215393,"url":"https://github.com/elastic/kibana/pull/215393","mergeCommit":{"message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215393","number":215393,"mergeCommit":{"message":"[Security Solution][Detection Engine] adds spaces telemetry for detection rules (#215393)\n\n## Summary\n\n - addresses https://github.com/elastic/security-team/issues/12000\n - adds telemetry for rules in spaces: \n - number of spaces, detection rules added\n - number of rules in each space\n\n---------\n\nCo-authored-by: Dan Dillinger <ddillinger@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b3d750bc49816de62de75bd550e7aab0066c7b7f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>	2025-04-01 11:09:51 +01:00
Drew Tate	471ef15a70	[9.0] [ES\|QL] Hide "not" operators from suggestions menu (#216355 ) (#216544 ) # Backport This will backport the following commits from `main` to `9.0`: - [[ES\|QL] Hide "not" operators from suggestions menu (#216355)](https://github.com/elastic/kibana/pull/216355) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Drew Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T19:25:08Z","message":"[ES\|QL] Hide \"not\" operators from suggestions menu (#216355)\n\n## Summary\n\nin https://github.com/elastic/kibana/pull/205565 we accidentally removed\nthe behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the\nsuggestions list. We want to show these eventually but right now, it's\nbroken behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES\|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES\|QL] Hide \"not\" operators from suggestions menu","number":216355,"url":"https://github.com/elastic/kibana/pull/216355","mergeCommit":{"message":"[ES\|QL] Hide \"not\" operators from suggestions menu (#216355)\n\n## Summary\n\nin https://github.com/elastic/kibana/pull/205565 we accidentally removed\nthe behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the\nsuggestions list. We want to show these eventually but right now, it's\nbroken behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216355","number":216355,"mergeCommit":{"message":"[ES\|QL] Hide \"not\" operators from suggestions menu (#216355)\n\n## Summary\n\nin https://github.com/elastic/kibana/pull/205565 we accidentally removed\nthe behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the\nsuggestions list. We want to show these eventually but right now, it's\nbroken behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216533","number":216533,"state":"OPEN"}]}] BACKPORT-->	2025-04-01 07:37:38 +02:00
Kibana Machine	effc619a2a	[9.0] [Controls] Fix control styles and invalid selection icon for Borealis (#213851 ) (#216569 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Controls] Fix control styles and invalid selection icon for Borealis (#213851)](https://github.com/elastic/kibana/pull/213851) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Catherine Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T00:04:43Z","message":"[Controls] Fix control styles and invalid selection icon for Borealis (#213851)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210614.\nCloses https://github.com/elastic/kibana/issues/210615.\nCloses https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up to the Borealis updates to fix controls\ncolors/styles. This also fixes the text color of the range slider number\ninputs to match the invalid state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5 54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n#### Dark mode\n![Screenshot 2025-03-10 at 5 33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n#### Options List control with selection that results in no data\n\n![Screenshot 2025-03-10 at 5 49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n#### Range Slider control with valid selection that results in no data\n![Screenshot 2025-03-10 at 5 49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n#### Range Slider control with invalid selection\n![Screenshot 2025-03-10 at 5 48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"96598fc01956c0762ac50d8636c3e78ae5735863","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Platform-Design","Feature:Dashboard","Team:Presentation","loe:small","release_note:skip","impact:medium","backport:version","EUI Visual Refresh","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Controls] Fix control styles and invalid selection icon for Borealis","number":213851,"url":"https://github.com/elastic/kibana/pull/213851","mergeCommit":{"message":"[Controls] Fix control styles and invalid selection icon for Borealis (#213851)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210614.\nCloses https://github.com/elastic/kibana/issues/210615.\nCloses https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up to the Borealis updates to fix controls\ncolors/styles. This also fixes the text color of the range slider number\ninputs to match the invalid state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5 54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n#### Dark mode\n![Screenshot 2025-03-10 at 5 33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n#### Options List control with selection that results in no data\n\n![Screenshot 2025-03-10 at 5 49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n#### Range Slider control with valid selection that results in no data\n![Screenshot 2025-03-10 at 5 49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n#### Range Slider control with invalid selection\n![Screenshot 2025-03-10 at 5 48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"96598fc01956c0762ac50d8636c3e78ae5735863"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213851","number":213851,"mergeCommit":{"message":"[Controls] Fix control styles and invalid selection icon for Borealis (#213851)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210614.\nCloses https://github.com/elastic/kibana/issues/210615.\nCloses https://github.com/elastic/kibana/issues/210616.\n\nThis is a follow up to the Borealis updates to fix controls\ncolors/styles. This also fixes the text color of the range slider number\ninputs to match the invalid state.\n\n#### Light mode\n![Screenshot 2025-03-10 at 5 54\n28 PM](https://github.com/user-attachments/assets/1f3cfe7c-0a0f-4fed-9486-3aaee1b33fb1)\n\n#### Dark mode\n![Screenshot 2025-03-10 at 5 33\n48 PM](https://github.com/user-attachments/assets/dda36740-93fd-4adc-bffe-c12aa4be3b4c)\n\n#### Options List control with selection that results in no data\n\n![Screenshot 2025-03-10 at 5 49\n05 PM](https://github.com/user-attachments/assets/b8b6310b-c600-4703-af28-ee60d16339e0)\n\n#### Range Slider control with valid selection that results in no data\n![Screenshot 2025-03-10 at 5 49\n01 PM](https://github.com/user-attachments/assets/afbf971b-95df-414f-8b99-2e3e0822fc73)\n\n#### Range Slider control with invalid selection\n![Screenshot 2025-03-10 at 5 48\n48 PM](https://github.com/user-attachments/assets/dae00db3-8c94-47e5-a706-b43fa9e0787e)\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"96598fc01956c0762ac50d8636c3e78ae5735863"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Catherine Liu <catherine.liu@elastic.co>	2025-04-01 03:06:47 +01:00
Kibana Machine	2a61432655	[9.0] Update dependency @types/diff to ^7.0.2 (main) (#216427 ) (#216566 ) # Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @types/diff to ^7.0.2 (main) (#216427)](https://github.com/elastic/kibana/pull/216427) <!--- 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-31T22:16:59Z","message":"Update dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n\| devDependencies \| patch \| [`^7.0.1` ->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2) \|\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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"Update dependency @types/diff to ^7.0.2 (main)","number":216427,"url":"https://github.com/elastic/kibana/pull/216427","mergeCommit":{"message":"Update dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n\| devDependencies \| patch \| [`^7.0.1` ->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2) \|\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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535"}},"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/216427","number":216427,"mergeCommit":{"message":"Update dependency @types/diff to ^7.0.2 (main) (#216427)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\|\n[@types/diff](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/diff))\n\| devDependencies \| patch \| [`^7.0.1` ->\n`^7.0.2`](https://renovatebot.com/diffs/npm/@types%2fdiff/7.0.1/7.0.2) \|\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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"5b3db2b69b4670b7dbc0bc6c492bd5661aaf4535"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>	2025-04-01 01:41:06 +01:00
Kibana Machine	688168bdb6	[9.0] Update dependency lru-cache to ^11.1.0 (main) (#216517 ) (#216557 ) # Backport This will backport the following commits from `main` to `9.0`: - [Update dependency lru-cache to ^11.1.0 (main) (#216517)](https://github.com/elastic/kibana/pull/216517) <!--- 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-31T21:58:09Z","message":"Update dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\| [lru-cache](https://redirect.github.com/isaacs/node-lru-cache) \|\ndependencies \| minor \| [`^11.0.2` ->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0) \|\n\n---\n\n### Release Notes\n\n<details>\n<summary>isaacs/node-lru-cache (lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:all-open","v9.1.0"],"title":"Update dependency lru-cache to ^11.1.0 (main)","number":216517,"url":"https://github.com/elastic/kibana/pull/216517","mergeCommit":{"message":"Update dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\| [lru-cache](https://redirect.github.com/isaacs/node-lru-cache) \|\ndependencies \| minor \| [`^11.0.2` ->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0) \|\n\n---\n\n### Release Notes\n\n<details>\n<summary>isaacs/node-lru-cache (lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6"}},"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/216517","number":216517,"mergeCommit":{"message":"Update dependency lru-cache to ^11.1.0 (main) (#216517)\n\nThis PR contains the following updates:\n\n\| Package \| Type \| Update \| Change \|\n\|---\|---\|---\|---\|\n\| [lru-cache](https://redirect.github.com/isaacs/node-lru-cache) \|\ndependencies \| minor \| [`^11.0.2` ->\n`^11.1.0`](https://renovatebot.com/diffs/npm/lru-cache/11.0.2/11.1.0) \|\n\n---\n\n### Release Notes\n\n<details>\n<summary>isaacs/node-lru-cache (lru-cache)</summary>\n\n###\n[`v11.1.0`](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.0)\n\n[Compare\nSource](https://redirect.github.com/isaacs/node-lru-cache/compare/v11.0.2...v11.1.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\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"1846807c25e4e5030b04cca42eef85e40602c0a6"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>	2025-04-01 00:41:09 +01:00
Kibana Machine	eff6a4e353	[9.0] [embeddable] fix race condition in useBatchedPublishingSubjects (#216399 ) (#216527 ) # Backport This will backport the following commits from `main` to `9.0`: - [[embeddable] fix race condition in useBatchedPublishingSubjects (#216399)](https://github.com/elastic/kibana/pull/216399) <!--- 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-31T17:21:56Z","message":"[embeddable] fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses https://github.com/elastic/kibana/issues/214176 and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from chrome 134 to 135 in functional test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed a race\ncondition in `useBatchedPublishingSubjects` where batched observables\ncould emit new values before `useEffect` sets up the subscription. This\nPR resolves this issue by setting up subscription in useRef, which has\nno timing delays.\n\nIn chrome 134, `useBatchedPublishingSubjects` `useEffect` gets called\n(setting up subscription) before lens embeddable emits any changes to\nbatched observables.\n<img width=\"300\" alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn chrome 135, `useBatchedPublishingSubjects` `useEffect` gets called\nafter lens embeddable emits changes to batched observables. This causes\nthe lens embeddable to not render since the `LensEmbeddableComponent`\nhas a stale value for `expressionParams`.\n<img width=\"300\" alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1","v8.17.5","v8.16.7"],"title":"[embeddable] fix race condition in useBatchedPublishingSubjects","number":216399,"url":"https://github.com/elastic/kibana/pull/216399","mergeCommit":{"message":"[embeddable] fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses https://github.com/elastic/kibana/issues/214176 and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from chrome 134 to 135 in functional test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed a race\ncondition in `useBatchedPublishingSubjects` where batched observables\ncould emit new values before `useEffect` sets up the subscription. This\nPR resolves this issue by setting up subscription in useRef, which has\nno timing delays.\n\nIn chrome 134, `useBatchedPublishingSubjects` `useEffect` gets called\n(setting up subscription) before lens embeddable emits any changes to\nbatched observables.\n<img width=\"300\" alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn chrome 135, `useBatchedPublishingSubjects` `useEffect` gets called\nafter lens embeddable emits changes to batched observables. This causes\nthe lens embeddable to not render since the `LensEmbeddableComponent`\nhas a stale value for `expressionParams`.\n<img width=\"300\" alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","9.0","8.17","8.16"],"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/216399","number":216399,"mergeCommit":{"message":"[embeddable] fix race condition in useBatchedPublishingSubjects (#216399)\n\nCloses https://github.com/elastic/kibana/issues/214176 and\nhttps://github.com/elastic/kibana/issues/214853\n\n[upgrade from chrome 134 to 135 in functional test\nrunner](https://github.com/elastic/kibana/issues/213919) revealed a race\ncondition in `useBatchedPublishingSubjects` where batched observables\ncould emit new values before `useEffect` sets up the subscription. This\nPR resolves this issue by setting up subscription in useRef, which has\nno timing delays.\n\nIn chrome 134, `useBatchedPublishingSubjects` `useEffect` gets called\n(setting up subscription) before lens embeddable emits any changes to\nbatched observables.\n<img width=\"300\" alt=\"chrome134\"\nsrc=\"https://github.com/user-attachments/assets/b0356f74-e0c7-4d93-a23a-ace519194d5d\"\n/>\n\nIn chrome 135, `useBatchedPublishingSubjects` `useEffect` gets called\nafter lens embeddable emits changes to batched observables. This causes\nthe lens embeddable to not render since the `LensEmbeddableComponent`\nhas a stale value for `expressionParams`.\n<img width=\"300\" alt=\"chrome135\"\nsrc=\"https://github.com/user-attachments/assets/320bfb7e-8b3f-4b48-a138-1c47c5ff9961\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f408a513dd5fdecf5ebbc4e3265e1b998421d39b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co>	2025-03-31 20:06:24 +01:00
Kibana Machine	bb3ac40a5c	[9.0] [Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239 ) (#216496 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)](https://github.com/elastic/kibana/pull/216239) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-03-31T15:04:28Z","message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:prev-minor","v9.1.0","backport:8.18"],"title":"[Cloud Security] Hide agentless traffic filtering callout in Serverless","number":216239,"url":"https://github.com/elastic/kibana/pull/216239","mergeCommit":{"message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216239","number":216239,"mergeCommit":{"message":"[Cloud Security] Hide agentless traffic filtering callout in Serverless (#216239)","sha":"e86127ab497327dd129feb5bf5dea39aa675cc76"}}]}] BACKPORT--> Co-authored-by: seanrathier <sean.rathier@gmail.com>	2025-03-31 18:13:30 +01:00
Kibana Machine	41bf1ef7b1	[9.0] [Fleet] skip output validation when create/update package policy (#216438 ) (#216497 ) # Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] skip output validation when create/update package policy (#216438)](https://github.com/elastic/kibana/pull/216438) <!--- 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-31T15:07:23Z","message":"[Fleet] skip output validation when create/update package policy (#216438)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/198107\n\nSkip output validation on bump agent policy, it's unnecessary after the\npackage policy create/update logic already does the validation with the\ncorrect integration output.\n\nTo verify:\n- Create an agent policy with a remote ES output as data output\n- Add fleet server integration - expect error as the default remote ES\noutput can't be used with fleet server\n- Change integration output to the ES output - expect creation\nsuccessful\n- Edit fleet server integration (keep ES output) - expect update\nsuccessful\n\n<img width=\"1685\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/42a0365c-1f00-42b6-b685-7797e9c916de\"\n/>\n<img width=\"1714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/af22cea1-d8b3-4d44-a24d-78dff49eeaaa\"\n/>\n<img width=\"1699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aafc7e5c-b9e6-47b8-9001-16e08cf06205\"\n/>\n<img width=\"1704\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e6e7ef47-918a-423f-a54c-11836362d495\"\n/>\n<img width=\"1712\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/128ef119-2178-4971-9e0f-bb773c2f774a\"\n/>\n<img width=\"1707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cd49716d-aa38-42ff-9329-3d97f08f9e7e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"7adc1821d83fa9ed913de1b6624adfc1b7640003","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"],"title":"[Fleet] skip output validation when create/update package policy","number":216438,"url":"https://github.com/elastic/kibana/pull/216438","mergeCommit":{"message":"[Fleet] skip output validation when create/update package policy (#216438)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/198107\n\nSkip output validation on bump agent policy, it's unnecessary after the\npackage policy create/update logic already does the validation with the\ncorrect integration output.\n\nTo verify:\n- Create an agent policy with a remote ES output as data output\n- Add fleet server integration - expect error as the default remote ES\noutput can't be used with fleet server\n- Change integration output to the ES output - expect creation\nsuccessful\n- Edit fleet server integration (keep ES output) - expect update\nsuccessful\n\n<img width=\"1685\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/42a0365c-1f00-42b6-b685-7797e9c916de\"\n/>\n<img width=\"1714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/af22cea1-d8b3-4d44-a24d-78dff49eeaaa\"\n/>\n<img width=\"1699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aafc7e5c-b9e6-47b8-9001-16e08cf06205\"\n/>\n<img width=\"1704\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e6e7ef47-918a-423f-a54c-11836362d495\"\n/>\n<img width=\"1712\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/128ef119-2178-4971-9e0f-bb773c2f774a\"\n/>\n<img width=\"1707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cd49716d-aa38-42ff-9329-3d97f08f9e7e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"7adc1821d83fa9ed913de1b6624adfc1b7640003"}},"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/216438","number":216438,"mergeCommit":{"message":"[Fleet] skip output validation when create/update package policy (#216438)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/198107\n\nSkip output validation on bump agent policy, it's unnecessary after the\npackage policy create/update logic already does the validation with the\ncorrect integration output.\n\nTo verify:\n- Create an agent policy with a remote ES output as data output\n- Add fleet server integration - expect error as the default remote ES\noutput can't be used with fleet server\n- Change integration output to the ES output - expect creation\nsuccessful\n- Edit fleet server integration (keep ES output) - expect update\nsuccessful\n\n<img width=\"1685\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/42a0365c-1f00-42b6-b685-7797e9c916de\"\n/>\n<img width=\"1714\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/af22cea1-d8b3-4d44-a24d-78dff49eeaaa\"\n/>\n<img width=\"1699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aafc7e5c-b9e6-47b8-9001-16e08cf06205\"\n/>\n<img width=\"1704\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e6e7ef47-918a-423f-a54c-11836362d495\"\n/>\n<img width=\"1712\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/128ef119-2178-4971-9e0f-bb773c2f774a\"\n/>\n<img width=\"1707\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cd49716d-aa38-42ff-9329-3d97f08f9e7e\"\n/>\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"7adc1821d83fa9ed913de1b6624adfc1b7640003"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>	2025-03-31 17:57:34 +01:00
Kibana Machine	9e9f9ac37c	[9.0] Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283 ) (#216482 ) # Backport This will backport the following commits from `main` to `9.0`: - [Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283)](https://github.com/elastic/kibana/pull/216283) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mario Rodriguez Molins","email":"mario.rodriguez@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T13:55:14Z","message":"Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the unenrollment inactive agent task to be able to unenroll some\nagents when the number of agents returned by the first\n`getAgentsByKuery` trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d","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":"Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE","number":216283,"url":"https://github.com/elastic/kibana/pull/216283","mergeCommit":{"message":"Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the unenrollment inactive agent task to be able to unenroll some\nagents when the number of agents returned by the first\n`getAgentsByKuery` trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d"}},"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/216283","number":216283,"mergeCommit":{"message":"Fix unenroll inactive agent tasks if first set of agents returned is equal to UNENROLLMENT_BATCH_SIZE (#216283)\n\n## Summary\n\nFix the unenrollment inactive agent task to be able to unenroll some\nagents when the number of agents returned by the first\n`getAgentsByKuery` trigger is equal to the limit of\n`UNENROLLMENT_BATCH_SIZE`.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8728a2328217408e0a377f037486abbc459acd2d"}}]}] BACKPORT--> Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>	2025-03-31 17:06:36 +01:00
Kibana Machine	4f37bc04e7	[9.0] [APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220 ) (#216468 ) # Backport This will backport the following commits from `main` to `9.0`: - [[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)](https://github.com/elastic/kibana/pull/216220) <!--- 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-31T13:07:17Z","message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc","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] Service inventory icons should be visible if the `agentName` is returned","number":216220,"url":"https://github.com/elastic/kibana/pull/216220","mergeCommit":{"message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}},"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/216220","number":216220,"mergeCommit":{"message":"[APM][OTel] Service inventory icons should be visible if the `agentName` is returned (#216220)\n\nCloses #214562 \n\n## Summary\n\nThis PR fixes the issue with the service icons overridden by the merge\nof the service stats\n\n## Testing\nAs this is a bit tricky to test - it needs a bit of refreshing /\nchanging the time range, etc. to reproduce\nThe way to verify the fix is to check the service overview - every\nservice that has an icon there should have an icon in the service\ninventory:\n\n\nhttps://github.com/user-attachments/assets/e401554b-6a39-440b-a52b-a126e42eacd5","sha":"cd8f18eed82722bfee3c27829ba233b381aea0cc"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>	2025-03-31 15:55:22 +01:00

... 2 3 4 5 6 ...

84501 commits