82952 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Francesco Fagnani	42f9afd320	[8.18] [Synthetics] Fix save lens visualization on monitors overview (#216695) (#217347) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Fix save lens visualization on monitors overview (#216695)](https://github.com/elastic/kibana/pull/216695) <!--- 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-07T13:47:53Z","message":"[Synthetics] Fix save lens visualization on monitors overview (#216695)\n\nThis PR closes #212490 by fixing the save lens visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics] Fix save lens visualization on monitors overview","number":216695,"url":"https://github.com/elastic/kibana/pull/216695","mergeCommit":{"message":"[Synthetics] Fix save lens visualization on monitors overview (#216695)\n\nThis PR closes #212490 by fixing the save lens visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},"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/216695","number":216695,"mergeCommit":{"message":"[Synthetics] Fix save lens visualization on monitors overview (#216695)\n\nThis PR closes #212490 by fixing the save lens visualization.\n\n\n\nhttps://github.com/user-attachments/assets/34949692-6b72-41f5-aa61-6c743ea5c5a3","sha":"07994d2706808d7ddf1bf2ca3cdf8a29ac033839"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217329","number":217329,"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-08 08:01:06 -04:00
Miriam	d2b827b1a1	[8.18] [ObsUX][A11y] Add aria-label to group by count (#217302) (#217449) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX][A11y] Add aria-label to group by count (#217302)](https://github.com/elastic/kibana/pull/217302) <!--- 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-07T13:42:12Z","message":"[ObsUX][A11y] Add aria-label to group by count (#217302)\n\nCloses https://github.com/elastic/kibana/issues/194974\n\n### What was done\n\n- for the `All` button a description and spell out was done in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to count number so it spells out the number of type\nof node\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25 51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24 47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572","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 aria-label to group by count","number":217302,"url":"https://github.com/elastic/kibana/pull/217302","mergeCommit":{"message":"[ObsUX][A11y] Add aria-label to group by count (#217302)\n\nCloses https://github.com/elastic/kibana/issues/194974\n\n### What was done\n\n- for the `All` button a description and spell out was done in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to count number so it spells out the number of type\nof node\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25 51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24 47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217328","number":217328,"state":"MERGED","mergeCommit":{"sha":"7fb23f119491bb83b61773c4621c1f380ac3f90f","message":"[9.0] [ObsUX][A11y] Add aria-label to group by count (#217302) (#217328)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[ObsUX][A11y] Add aria-label to group by count\n(#217302)](https://github.com/elastic/kibana/pull/217302)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>"}},{"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/217302","number":217302,"mergeCommit":{"message":"[ObsUX][A11y] Add aria-label to group by count (#217302)\n\nCloses https://github.com/elastic/kibana/issues/194974\n\n### What was done\n\n- for the `All` button a description and spell out was done in\nhttps://github.com/elastic/kibana/pull/216592\n- added aria-label to count number so it spells out the number of type\nof node\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 32\"\nsrc=\"https://github.com/user-attachments/assets/7b0e814f-7713-4a6c-9b6c-2a45bb9b28c5\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 26 15\"\nsrc=\"https://github.com/user-attachments/assets/33ca56d4-09e6-4b5a-be36-7771b1467272\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 25 51\"\nsrc=\"https://github.com/user-attachments/assets/2c8bcf14-6308-4c22-a76a-b8313f2f580e\"\n/>\n<img width=\"460\" alt=\"Screenshot 2025-04-07 at 11 24 47\"\nsrc=\"https://github.com/user-attachments/assets/10497f74-77ba-48a9-ac2d-d3cbdcbeb609\"\n/>","sha":"340c86e5d4b1d48589c62fb5b1fc3a1acc9a5572"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-08 12:08:14 +02:00
Abdul Wahab Zahid	ca96f071c3	[8.18] [Onboarding] Hide card labels in search results (#213417) (#216666) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Onboarding] Hide card labels in search results (#213417)](https://github.com/elastic/kibana/pull/213417) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-07T14:40:39Z","message":"[Onboarding] Hide card labels in search results (#213417)\n\nCloses https://github.com/elastic/kibana/issues/200917\n\nLooking at the code in Fleet search results screen, cards would also\nhave the `Unverified` badges. ([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould return `true` because this specific page doesn't provides\n`packageVerificationKeyId` to the `isPackageUnverified()` function, this\nonly happens on the individual integration details page. Fleet search\njust [hides the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor cards in search results.\n\nThis change aligns Onboarding search results with Fleet search results\nand hides the card labels which fixes the issue with `Unverified` badge\nappearing for installed integrations.\n\n| Before | After |\n| --- | --- |\n|\n\n| \n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Feature: Observability Onboarding","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Onboarding] Hide card labels in search results","number":213417,"url":"https://github.com/elastic/kibana/pull/213417","mergeCommit":{"message":"[Onboarding] Hide card labels in search results (#213417)\n\nCloses https://github.com/elastic/kibana/issues/200917\n\nLooking at the code in Fleet search results screen, cards would also\nhave the `Unverified` badges. ([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould return `true` because this specific page doesn't provides\n`packageVerificationKeyId` to the `isPackageUnverified()` function, this\nonly happens on the individual integration details page. Fleet search\njust [hides the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor cards in search results.\n\nThis change aligns Onboarding search results with Fleet search results\nand hides the card labels which fixes the issue with `Unverified` badge\nappearing for installed integrations.\n\n| Before | After |\n| --- | --- |\n|\n\n| \n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213579","number":213579,"state":"MERGED","mergeCommit":{"sha":"ff5042eb811c5eb1eb6bccc797feec06f52e1e32","message":"[9.0] [Onboarding] Hide card labels in search results (#213417) (#213579)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Onboarding] Hide card labels in search results\n(#213417)](https://github.com/elastic/kibana/pull/213417)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>"}},{"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/213417","number":213417,"mergeCommit":{"message":"[Onboarding] Hide card labels in search results (#213417)\n\nCloses https://github.com/elastic/kibana/issues/200917\n\nLooking at the code in Fleet search results screen, cards would also\nhave the `Unverified` badges. ([this\ncheck](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/card_utils.tsx#L101)\nwould return `true` because this specific page doesn't provides\n`packageVerificationKeyId` to the `isPackageUnverified()` function, this\nonly happens on the individual integration details page. Fleet search\njust [hides the\nbadges](https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/public/applications/integrations/sections/epm/screens/home/available_packages.tsx#L188)\nfor cards in search results.\n\nThis change aligns Onboarding search results with Fleet search results\nand hides the card labels which fixes the issue with `Unverified` badge\nappearing for installed integrations.\n\n| Before | After |\n| --- | --- |\n|\n\n| \n|","sha":"33f71ae678e833b4c91325e40f47d819e1edb08d"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>	2025-04-08 12:07:20 +02:00
Abdul Wahab Zahid	406ef5cb98	[8.18] [Obs Onboarding] Add page rendering performance monitoring (#213769) (#216762) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Obs Onboarding] Add page rendering performance monitoring (#213769)](https://github.com/elastic/kibana/pull/213769) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-18T08:50:38Z","message":"[Obs Onboarding] Add page rendering performance monitoring (#213769)\n\nCloses https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis change add logic for triggering [the page rendering performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n* Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n* Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1. Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the above mentioned onboarding screens\n4. Observe `kibana:plugin_render_time` EBT event emitted in the Network\ntab of the dev tools\n\nEvents emitted from local Kibana end up in the Staging Telemetry\ncluster, there is a [dedicated rendering performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding events can be filtered using `observabilityOnboarding`\napplication ID. (note that it takes some time for events to be indexed\nand they appear in the cluster with a significant delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Feature: Observability Onboarding","backport:version","v9.1.0"],"title":"[Obs Onboarding] Add page rendering performance monitoring","number":213769,"url":"https://github.com/elastic/kibana/pull/213769","mergeCommit":{"message":"[Obs Onboarding] Add page rendering performance monitoring (#213769)\n\nCloses https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis change add logic for triggering [the page rendering performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n* Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n* Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1. Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the above mentioned onboarding screens\n4. Observe `kibana:plugin_render_time` EBT event emitted in the Network\ntab of the dev tools\n\nEvents emitted from local Kibana end up in the Staging Telemetry\ncluster, there is a [dedicated rendering performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding events can be filtered using `observabilityOnboarding`\napplication ID. (note that it takes some time for events to be indexed\nand they appear in the cluster with a significant delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4"}},"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/213769","number":213769,"mergeCommit":{"message":"[Obs Onboarding] Add page rendering performance monitoring (#213769)\n\nCloses https://github.com/elastic/observability-dev/issues/4238 🔒\nCloses https://github.com/elastic/observability-dev/issues/3513 🔒\n\nThis change add logic for triggering [the page rendering performance\nmetrics](https://docs.elastic.dev/kibana-dev-docs/tutorial/performance/adding_custom_performance_metrics#report-kibanaplugin_render_time-metric-event)\nfor:\n* Onboarding home screen\n* Host auto-detect flow\n* Host OTel flow\n* Host K8S flow\n* K8S OTel flow\n* Firehose flow\n\n## How to test\n1. Run Kibana locally\n2. Open browser dev tools\n3. Navigate to one of the above mentioned onboarding screens\n4. Observe `kibana:plugin_render_time` EBT event emitted in the Network\ntab of the dev tools\n\nEvents emitted from local Kibana end up in the Staging Telemetry\ncluster, there is a [dedicated rendering performance\ndashboard](f240fff6-fac9-491b-81d1-ac39006c5c94?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-24h%2Fh,to:now))),\nonboarding events can be filtered using `observabilityOnboarding`\napplication ID. (note that it takes some time for events to be indexed\nand they appear in the cluster with a significant delay)","sha":"68a25a423ee8a5270e72ca89b38515c0e293cbd4"}}]}] BACKPORT--> --------- Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-04-08 12:06:54 +02:00
Kibana Machine	4bc4c3a08f	[8.18] [ci] Minor quick-checks updates (#215856) (#217444) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ci] Minor quick-checks updates (#215856)](https://github.com/elastic/kibana/pull/215856) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-04-08T07:26:14Z","message":"[ci] Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node scripts/prettier_topology_check` occasionally breaks with\n`.gitignore` not being available, it's required for a globby call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2 - some scripts are run together by `yarn kbn run-in-packages` - this\nscript only logs AFTER a script finished successfully; when a script\nlike this fails, the failing script is not logged. This change logs\nbefore to see what the error is. (ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[ci] Minor quick-checks updates","number":215856,"url":"https://github.com/elastic/kibana/pull/215856","mergeCommit":{"message":"[ci] Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node scripts/prettier_topology_check` occasionally breaks with\n`.gitignore` not being available, it's required for a globby call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2 - some scripts are run together by `yarn kbn run-in-packages` - this\nscript only logs AFTER a script finished successfully; when a script\nlike this fails, the failing script is not logged. This change logs\nbefore to see what the error is. (ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e"}},"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/215856","number":215856,"mergeCommit":{"message":"[ci] Minor quick-checks updates (#215856)\n\n## Summary\n1 - `node scripts/prettier_topology_check` occasionally breaks with\n`.gitignore` not being available, it's required for a globby call.\n(https://buildkite.com/elastic/kibana-on-merge/builds/64944#0195c874-c2b0-436c-9752-91a6118dde9d)\n\n2 - some scripts are run together by `yarn kbn run-in-packages` - this\nscript only logs AFTER a script finished successfully; when a script\nlike this fails, the failing script is not logged. This change logs\nbefore to see what the error is. (ref:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1742824259264329)","sha":"08c5f0799d2ed1a23f0b12adbaad1e49235fc30e"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>	2025-04-08 11:11:47 +02:00
Kibana Machine	b59647e5ef	[8.18] [Security Assistant] Don't cache MLClient (#217408) (#217416) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Security Assistant] Don't cache MLClient (#217408)](https://github.com/elastic/kibana/pull/217408) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-04-07T23:25:45Z","message":"[Security Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[Security Assistant] Don't cache MLClient","number":217408,"url":"https://github.com/elastic/kibana/pull/217408","mergeCommit":{"message":"[Security Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0"}},"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/217408","number":217408,"mergeCommit":{"message":"[Security Assistant] Don't cache MLClient (#217408)\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\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":"17440896f98dc76ea532f771caa6b82b9cc853a0"}}]}] BACKPORT--> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>	2025-04-08 03:10:18 +02:00
Kibana Machine	6d142b805e	skip failing test suite (#213821)	2025-04-07 21:30:11 +02:00
Julia Rechkunova	f5554b642c	[8.18] [ES|QL] Fix CSV report time range when exporting from Discover (#216792) (#217181) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fix CSV report time range when exporting from Discover (#216792)](https://github.com/elastic/kibana/pull/216792) <!--- 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-04T10:54:45Z","message":"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\n\n- Closes https://github.com/elastic/kibana/issues/216605\n\n## Summary\n\nThis PR makes sure to use the absolute time range when generating a CSV\nreport in ES|QL mode.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a","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","Feature:ES|QL","Feature:Reporting:CSV","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fix CSV report time range when exporting from Discover","number":216792,"url":"https://github.com/elastic/kibana/pull/216792","mergeCommit":{"message":"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\n\n- Closes https://github.com/elastic/kibana/issues/216605\n\n## Summary\n\nThis PR makes sure to use the absolute time range when generating a CSV\nreport in ES|QL mode.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217174","number":217174,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216792","number":216792,"mergeCommit":{"message":"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\n\n- Closes https://github.com/elastic/kibana/issues/216605\n\n## Summary\n\nThis PR makes sure to use the absolute time range when generating a CSV\nreport in ES|QL mode.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-07 15:29:04 -03:00
Georgii Gorbachev	78a86c6f03	[8.18] [Security Solution] Improve documentation for version and revision fields (#216074) (#217341) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Improve documentation for `version` and `revision` fields (#216074)](https://github.com/elastic/kibana/pull/216074) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-31T18:06:13Z","message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","APIDocs","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","9.1 candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Improve documentation for `version` and `revision` fields","number":216074,"url":"https://github.com/elastic/kibana/pull/216074","mergeCommit":{"message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216074","number":216074,"mergeCommit":{"message":"[Security Solution] Improve documentation for `version` and `revision` fields (#216074)\n\n**Resolves: https://github.com/elastic/security-docs/issues/3545**\n\n## Summary\n\nI am fixing documentation for the version and revision fields.\nI used this page as the base documentation:\nhttps://docs.elastic.dev/security-solution/dev-docs/detections/rule-versions\n\nThe changes:\n- by marking the RuleVersion as read-only I am making sure we are\nproperly documenting that this field is not to be used in the request.\nIt is only returned in the response.\n- by introducing RuleRevision type and marking it as read-only, I am\ndoing the same for this field, saying that this field is not supposed to\nbe used in the request.\n- I am not changing any code in the app, as the ticket says we shouldn't\ndo any breaking changes and the update of the version should not cause\n400 error. Basically current behavior is kept: users can still update\nthe version to whatever value they want, including going backwards, and\nthe changes to revision field is completely ignored.\n- I am adding a condensed description of these fields.\n\nI wanted to introduce an internal link between these two fields, but I\ncouldn't make it work in Bump.sh (even though this should work, normal\nMarkdown links) so I abandoned this idea.\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip2)\nwhere I deployed the generated bundled doc.\n\nScreenshots:\n\n<img width=\"664\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34d82eb2-f7f0-4369-ad8e-2fd3c1f35447\"\n/>\n\n<img width=\"660\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/dc7772af-0185-4850-816e-60be003775d6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63575a8320a7e021df79727ad66ed4cf01dd1e5f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216531","number":216531,"state":"MERGED","mergeCommit":{"sha":"a75155043b5f8cfd97907734b49ccd3ea1f9bca3","message":"[8.x] [Security Solution] Improve documentation for `version` and `revision` fields (#216074) (#216531)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Improve documentation for `version` and\n`revision` fields\n(#216074)](https://github.com/elastic/kibana/pull/216074)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>	2025-04-07 18:17:27 +02:00
Sergi Massaneda	dd7dae0f16	[8.18] [Security Solution] Onboarding check inference endpoint (#217150) (#217335) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Onboarding check inference endpoint (#217150)](https://github.com/elastic/kibana/pull/217150) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T13:43:39Z","message":"[Security Solution] Onboarding check inference endpoint (#217150)\n\n## Summary\n\nThis PR checks that the inference endpoint exists before showing the\ninference connector in the list of selectable connectors.\n\nAlso, it removes code duplication by centralizing the implementation in\nthe /common/connectors directory of the onboarding cards\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Onboarding check inference endpoint","number":217150,"url":"https://github.com/elastic/kibana/pull/217150","mergeCommit":{"message":"[Security Solution] Onboarding check inference endpoint (#217150)\n\n## Summary\n\nThis PR checks that the inference endpoint exists before showing the\ninference connector in the list of selectable connectors.\n\nAlso, it removes code duplication by centralizing the implementation in\nthe /common/connectors directory of the onboarding cards\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c"}},"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/217150","number":217150,"mergeCommit":{"message":"[Security Solution] Onboarding check inference endpoint (#217150)\n\n## Summary\n\nThis PR checks that the inference endpoint exists before showing the\ninference connector in the list of selectable connectors.\n\nAlso, it removes code duplication by centralizing the implementation in\nthe /common/connectors directory of the onboarding cards\n\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b934f903499d1affd1986fedb0529f51d5c818c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-07 17:59:41 +02:00
Kibana Machine	2334c67609	[8.18] [Synthetics] Fixed alert count in monitor details (#216761) (#217337) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Fixed alert count in monitor details (#216761)](https://github.com/elastic/kibana/pull/216761) <!--- 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-07T13:47:40Z","message":"[Synthetics] Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328 \n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38 42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38 21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[Synthetics] Fixed alert count in monitor details","number":216761,"url":"https://github.com/elastic/kibana/pull/216761","mergeCommit":{"message":"[Synthetics] Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328 \n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38 42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38 21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},"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/216761","number":216761,"mergeCommit":{"message":"[Synthetics] Fixed alert count in monitor details (#216761)\n\nThis PR closes #191328 \n\nBefore:\n<img width=\"1512\" alt=\"Screenshot 2025-04-02 at 10 38 42\"\nsrc=\"https://github.com/user-attachments/assets/d4c9c744-afdf-4d1b-8bd9-9447c0945258\"\n/>\n\nAfter:\n<img width=\"758\" alt=\"Screenshot 2025-04-02 at 10 38 21\"\nsrc=\"https://github.com/user-attachments/assets/c2692a44-db8c-461b-803c-d1834646d514\"\n/>","sha":"aa37d539fb2ea9340a9ac100a91ea36b2424e5c0"}},{"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: Francesco Fagnani <fagnani.francesco@gmail.com>	2025-04-07 17:52:06 +02:00
Abdul Wahab Zahid	1ffaddb6a8	[8.18] [Performance] Refactor TTFMP query from, to fields (#213911) (#217091) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Performance] Refactor TTFMP query `from`, `to` fields (#213911)](https://github.com/elastic/kibana/pull/213911) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-03-20T10:40:24Z","message":"[Performance] Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana forwards `query_range_secs` and `query_offset_secs` to\nmark the selected time range when reporting TTFMP event. This format\ncaused some challenges to identify `from`, `to` date offsets in\nvisualizations.\n\nTo simplify, the PR renames and sends the three fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with -ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset to `0` (now), with -ve for past and +ve\nfor future dates\n- `query_range_secs` same as previously sent\n\n_This approach is followed after a discussion, and based on the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest date -> QueryFrom\nNewest date -> QueryTo\nDuration -> QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in the EBT indexer to ingest in the\ntop level of the document, eventually removing the need to create\nruntime fields in data views for visualizations.\n\nAlso, runtime fields in data views should be updated to reflect this\nchange. For backward compatibility, the runtime fields can cater both\nthe old and new field names conditionally.\n\n### Testing\n- Ensure that the TTFMP events are correctly reporting the date ranges.\n\n### Example\n\n","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","v9.1.0","v8.19.0"],"title":"[Performance] Refactor TTFMP query `from`, `to` fields","number":213911,"url":"https://github.com/elastic/kibana/pull/213911","mergeCommit":{"message":"[Performance] Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana forwards `query_range_secs` and `query_offset_secs` to\nmark the selected time range when reporting TTFMP event. This format\ncaused some challenges to identify `from`, `to` date offsets in\nvisualizations.\n\nTo simplify, the PR renames and sends the three fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with -ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset to `0` (now), with -ve for past and +ve\nfor future dates\n- `query_range_secs` same as previously sent\n\n_This approach is followed after a discussion, and based on the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest date -> QueryFrom\nNewest date -> QueryTo\nDuration -> QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in the EBT indexer to ingest in the\ntop level of the document, eventually removing the need to create\nruntime fields in data views for visualizations.\n\nAlso, runtime fields in data views should be updated to reflect this\nchange. For backward compatibility, the runtime fields can cater both\nthe old and new field names conditionally.\n\n### Testing\n- Ensure that the TTFMP events are correctly reporting the date ranges.\n\n### Example\n\n","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e"}},"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/213911","number":213911,"mergeCommit":{"message":"[Performance] Refactor TTFMP query `from`, `to` fields (#213911)\n\nCurrently Kibana forwards `query_range_secs` and `query_offset_secs` to\nmark the selected time range when reporting TTFMP event. This format\ncaused some challenges to identify `from`, `to` date offsets in\nvisualizations.\n\nTo simplify, the PR renames and sends the three fields explicitly:\n- `query_from_offset_secs` offset to `0` (now), with -ve for past and\n+ve for future dates\n- `query_to_offset_secs` offset to `0` (now), with -ve for past and +ve\nfor future dates\n- `query_range_secs` same as previously sent\n\n_This approach is followed after a discussion, and based on the\n[gist](https://gist.github.com/andrewvc/1f04a57a336d768e4ec5ff2eff06ba54)\nexcerpt:_\n\n```\nEarliest date -> QueryFrom\nNewest date -> QueryTo\nDuration -> QueryRange\n```\n\n### Indexing\nThese fields then should be mapped in the EBT indexer to ingest in the\ntop level of the document, eventually removing the need to create\nruntime fields in data views for visualizations.\n\nAlso, runtime fields in data views should be updated to reflect this\nchange. For backward compatibility, the runtime fields can cater both\nthe old and new field names conditionally.\n\n### Testing\n- Ensure that the TTFMP events are correctly reporting the date ranges.\n\n### Example\n\n","sha":"e6e78ac6d83fe9c4a83785c717fb1b7f3fedbf0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217090","number":217090,"state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217089","number":217089,"branch":"9.0","state":"OPEN"}]}] BACKPORT-->	2025-04-07 18:46:29 +03:00
Kibana Machine	b5d0c87af1	[8.18] [APM][OTel] Fix layers issue for ESQL visualization by adding textBased layers (#216358) (#217321) ... # Backport This will backport the following commits from `main` to `8.18`: - [[APM][OTel] Fix layers issue for ESQL visualization by adding `textBased` layers (#216358)](https://github.com/elastic/kibana/pull/216358) <!--- 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-07T13:20:12Z","message":"[APM][OTel] Fix layers issue for ESQL visualization by adding `textBased` layers (#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue with the ESQL visualization by supporting\n`textBased` layers. For testing, there is a link to the serverless env\nof this PR and it should be tested EDOT Java SDK as shown in [the\nscreenshot in this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by: Jonas Kunz <j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd","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:cloud-redeploy","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Fix layers issue for ESQL visualization by adding `textBased` layers","number":216358,"url":"https://github.com/elastic/kibana/pull/216358","mergeCommit":{"message":"[APM][OTel] Fix layers issue for ESQL visualization by adding `textBased` layers (#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue with the ESQL visualization by supporting\n`textBased` layers. For testing, there is a link to the serverless env\nof this PR and it should be tested EDOT Java SDK as shown in [the\nscreenshot in this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by: Jonas Kunz <j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd"}},"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/216358","number":216358,"mergeCommit":{"message":"[APM][OTel] Fix layers issue for ESQL visualization by adding `textBased` layers (#216358)\n\nCloses #215675 \n\n## Summary\n\nThis PR fixes the issue with the ESQL visualization by supporting\n`textBased` layers. For testing, there is a link to the serverless env\nof this PR and it should be tested EDOT Java SDK as shown in [the\nscreenshot in this\ncomment](https://github.com/elastic/kibana/pull/216358#pullrequestreview-2728718952)\n\n---------\n\nCo-authored-by: Jonas Kunz <j+github@kunzj.de>","sha":"523fa7689cb5edabf613ee46fbce647609b22bdd"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>	2025-04-07 17:27:25 +02:00
Robert Jaszczurek	a9a1667338	[8.18] [ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178) (#217316) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178)](https://github.com/elastic/kibana/pull/217178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-07T10:06:30Z","message":"[ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178)\n\nIt fixes an issue where adding the `Change Point Detection` embeddable\ndidn't work properly.\nThe bug was introduced in https://github.com/elastic/kibana/pull/197943\nThe main cause was the use of `<ChangePointDetectionContextProvider>`\nwhich calls `timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work, `this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this is not the case within dashboards.\nHowever, we do not actually need the `ChangePointDetectionContext`\ninside the embeddable, so this PR removes its usage.\nA functional test has been added to cover adding the Change Point\nembeddable from the dashboards app. It's a very simple test that does\nnot verify the embeddable's functionality, but it could be improved in a\nfollow-up.\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:ML/AIOps","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5"],"title":"[ML] AIOps: Change Point Detection in Dashboards embeddable fix","number":217178,"url":"https://github.com/elastic/kibana/pull/217178","mergeCommit":{"message":"[ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178)\n\nIt fixes an issue where adding the `Change Point Detection` embeddable\ndidn't work properly.\nThe bug was introduced in https://github.com/elastic/kibana/pull/197943\nThe main cause was the use of `<ChangePointDetectionContextProvider>`\nwhich calls `timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work, `this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this is not the case within dashboards.\nHowever, we do not actually need the `ChangePointDetectionContext`\ninside the embeddable, so this PR removes its usage.\nA functional test has been added to cover adding the Change Point\nembeddable from the dashboards app. It's a very simple test that does\nnot verify the embeddable's functionality, but it could be improved in a\nfollow-up.\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f"}},"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/217178","number":217178,"mergeCommit":{"message":"[ML] AIOps: Change Point Detection in Dashboards embeddable fix (#217178)\n\nIt fixes an issue where adding the `Change Point Detection` embeddable\ndidn't work properly.\nThe bug was introduced in https://github.com/elastic/kibana/pull/197943\nThe main cause was the use of `<ChangePointDetectionContextProvider>`\nwhich calls `timefilter.getActiveBounds()`. However, for\n`getActiveBounds` to work, `this.isTimeRangeSelectorEnabled()` must\nreturn true. By default, this is not the case within dashboards.\nHowever, we do not actually need the `ChangePointDetectionContext`\ninside the embeddable, so this PR removes its usage.\nA functional test has been added to cover adding the Change Point\nembeddable from the dashboards app. It's a very simple test that does\nnot verify the embeddable's functionality, but it could be improved in a\nfollow-up.\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d35988152d9e95e26908046ea3540d34e47cf92f"}},{"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,"url":"https://github.com/elastic/kibana/pull/217315","number":217315,"state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-04-07 16:07:33 +02:00
Georgii Gorbachev	0e90f2d2f2	[8.18] [Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367) (#217305) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)](https://github.com/elastic/kibana/pull/212367) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T13:43:02Z","message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","APIDocs","Team:Detection Rule Management","backport:version","8.18 candidate","v9.1.0","v8.19.0"],"title":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs","number":212367,"url":"https://github.com/elastic/kibana/pull/212367","mergeCommit":{"message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212367","number":212367,"mergeCommit":{"message":"[Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367)\n\n**Partially resolves: #211808**\n\n## Summary\n\nThis is the first part of the migration effort, containing changes for:\n- CRUD endpoints\n- BULK Actions\n- Export / Import Rule\n- Find Rule\n- List Tags\n- Get Status\n- Install Rule\n\nI migrated the examples and the description of the fields. Some of the\nfields contained description that was very similar to the legacy, then I\ndidn't change it. I only modified the descriptions where it was\nvaluable.\n\nI also discovered some problems. For example the value for the 'query'\nfield, always shows 'EQL query to execute'. I reported this to the docs\nteam, in the 'next-api-reference' channel.\n\nAnother issue was with 'related_integrations field', which also didn't\nshow the long description. I also wrote about it to the docs team\n[here](https://elastic.slack.com/archives/C05UL5YC06B/p1740137094701209).\nIn this PR I decided to try moving the description one level up, where\nit renders properly.\n\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas/doc/kibana_wip/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b01257343335ad7ea5d40577c7e10deb94db19b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216734","number":216734,"state":"MERGED","mergeCommit":{"sha":"9c8b23ad7b5cf5025506e1d51fa22d7de7194305","message":"[8.x] [Security Solution] Migrate legacy Detections API docs to OpenAPI specs (#212367) (#216734)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Migrate legacy Detections API docs to OpenAPI\nspecs (#212367)](https://github.com/elastic/kibana/pull/212367)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-04-07 15:55:08 +02:00
Kibana Machine	331691bd1c	[8.18] [ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979) (#217296) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979)](https://github.com/elastic/kibana/pull/216979) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-07T09:54:11Z","message":"[ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979)\n\nCloses https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n- Applied changes to improve layout stability: removed the `word-break\n`and limited the outer flex item to `max-width: 75%`, as suggested in\nthe ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.5"],"title":"[ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor","number":216979,"url":"https://github.com/elastic/kibana/pull/216979","mergeCommit":{"message":"[ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979)\n\nCloses https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n- Applied changes to improve layout stability: removed the `word-break\n`and limited the outer flex item to `max-width: 75%`, as suggested in\nthe ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a"}},"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/216979","number":216979,"mergeCommit":{"message":"[ResponseOps][Cases] Support horizontal scrolling for tables inside the markdown editor (#216979)\n\nCloses https://github.com/elastic/kibana/issues/216421\n\n## Summary\n\n- Applied changes to improve layout stability: removed the `word-break\n`and limited the outer flex item to `max-width: 75%`, as suggested in\nthe ticket\n\n\nhttps://github.com/user-attachments/assets/607e9867-e10c-4118-9567-580549708806\n\n---------\n\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"48c19a50706a0eea9d83d7229d5cc8a3d12a703a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>	2025-04-07 13:43:48 +02:00
Aleh Zasypkin	f632a1800d	[8.18] chore(deps): upgrade tar-fs from 2.1.1 to 2.1.2 (#217173) (#217207) ... # Backport This will backport the following commits from `main` to `8.18`: - [chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)](https://github.com/elastic/kibana/pull/217173) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-04-04T14:18:38Z","message":"chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n## Summary\n\nUpgrade `tar-fs` from `2.1.1` to `2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","backport:all-open","v9.1.0"],"title":"chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2`","number":217173,"url":"https://github.com/elastic/kibana/pull/217173","mergeCommit":{"message":"chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n## Summary\n\nUpgrade `tar-fs` from `2.1.1` to `2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81"}},"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/217173","number":217173,"mergeCommit":{"message":"chore(deps): upgrade `tar-fs` from `2.1.1` to `2.1.2` (#217173)\n\n## Summary\n\nUpgrade `tar-fs` from `2.1.1` to `2.1.2`.","sha":"a0b0de16c8a54e0979f699a44911a83de5c1cf81"}},{"url":"https://github.com/elastic/kibana/pull/217204","number":217204,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/217205","number":217205,"branch":"9.0","state":"OPEN"}]}] BACKPORT-->	2025-04-04 17:36:21 +01:00
Kevin Delemme	a0f92a2a00	[8.18] fix(slo): group by with empty string (#217084) (#217206) ... # Backport This will backport the following commits from `main` to `8.18`: - [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","v9.0.0","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","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/217110","number":217110,"state":"MERGED","mergeCommit":{"sha":"f5054deba36b1843262c64d27c8d0827f96b50bc","message":"[9.0] fix(slo): group by with empty string (#217084) (#217110)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [fix(slo): group by with empty string\n(#217084)](https://github.com/elastic/kibana/pull/217084)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Kevin Delemme <kevin.delemme@elastic.co>"}},{"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":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-04 17:13:07 +01:00
Kibana Machine	bedbfb7b16	[8.18] [SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693) (#217192) ... # Backport This will backport the following commits from `main` to `8.18`: - [[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)](https://github.com/elastic/kibana/pull/216693) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jesus Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-04T13:37:06Z","message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","backport:current-major","v9.1.0"],"title":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception","number":216693,"url":"https://github.com/elastic/kibana/pull/216693","mergeCommit":{"message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}},"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/216693","number":216693,"mergeCommit":{"message":"[SO migration] Move to previous step in update mappings wait when it fails with search_phase_execution_exception (#216693)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/207096\n\nThis continues the work in https://github.com/elastic/kibana/pull/213979\n\nSometimes ES returns a 200 response containing an error field when we\nwait for the update mappings task. This case wasn't being handled. This\nPR handles that case, when we find a `search_phase_execution_exception`\nin the ES response we return a retryable error that sends us back to the\nupdate mappings state. It does it for both migration algorithms, the\npriority is ZDT but seemed like a nice to have in both.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [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":"49380143432b654cf1b849d8c77b3abc2fb3aeb4"}}]}] BACKPORT--> Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com>	2025-04-04 16:45:54 +01:00
Kibana Machine	9112209a0e	[8.18] [ObsUX][A11y] Add aria-label to "Show all" links (#217076) (#217175) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX][A11y] Add aria-label to "Show all" links (#217076)](https://github.com/elastic/kibana/pull/217076) <!--- 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-04T12:07:58Z","message":"[ObsUX][A11y] Add aria-label to \"Show all\" links (#217076)\n\nCloses https://github.com/elastic/kibana/issues/194973\n\n## Summary\n\nThere are multiple links that say \"Show all\" but do not provide context\nto answer all of what?\n\n### What was done\nAdded aria-label to all the \"Show all links\"\n\n### How to test\nUse screen reader to see the context of the link\n\nEXAMPLES\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 45 47\"\nsrc=\"https://github.com/user-attachments/assets/8e8b33f8-d2f1-45b5-99ed-e9306a832d9c\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 03\"\nsrc=\"https://github.com/user-attachments/assets/e23cce5c-dca0-41ec-9221-0c32dbc8eb0d\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 45\"\nsrc=\"https://github.com/user-attachments/assets/c7fe658c-5ab2-4665-a187-671ba7b49bfd\"\n/>","sha":"faae1423f02daec2c6e0b723dc42892f9460c0b7","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 aria-label to \"Show all\" links","number":217076,"url":"https://github.com/elastic/kibana/pull/217076","mergeCommit":{"message":"[ObsUX][A11y] Add aria-label to \"Show all\" links (#217076)\n\nCloses https://github.com/elastic/kibana/issues/194973\n\n## Summary\n\nThere are multiple links that say \"Show all\" but do not provide context\nto answer all of what?\n\n### What was done\nAdded aria-label to all the \"Show all links\"\n\n### How to test\nUse screen reader to see the context of the link\n\nEXAMPLES\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 45 47\"\nsrc=\"https://github.com/user-attachments/assets/8e8b33f8-d2f1-45b5-99ed-e9306a832d9c\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 03\"\nsrc=\"https://github.com/user-attachments/assets/e23cce5c-dca0-41ec-9221-0c32dbc8eb0d\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 45\"\nsrc=\"https://github.com/user-attachments/assets/c7fe658c-5ab2-4665-a187-671ba7b49bfd\"\n/>","sha":"faae1423f02daec2c6e0b723dc42892f9460c0b7"}},"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/217076","number":217076,"mergeCommit":{"message":"[ObsUX][A11y] Add aria-label to \"Show all\" links (#217076)\n\nCloses https://github.com/elastic/kibana/issues/194973\n\n## Summary\n\nThere are multiple links that say \"Show all\" but do not provide context\nto answer all of what?\n\n### What was done\nAdded aria-label to all the \"Show all links\"\n\n### How to test\nUse screen reader to see the context of the link\n\nEXAMPLES\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 45 47\"\nsrc=\"https://github.com/user-attachments/assets/8e8b33f8-d2f1-45b5-99ed-e9306a832d9c\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 03\"\nsrc=\"https://github.com/user-attachments/assets/e23cce5c-dca0-41ec-9221-0c32dbc8eb0d\"\n/>\n\n<img width=\"1232\" alt=\"Screenshot 2025-04-03 at 17 46 45\"\nsrc=\"https://github.com/user-attachments/assets/c7fe658c-5ab2-4665-a187-671ba7b49bfd\"\n/>","sha":"faae1423f02daec2c6e0b723dc42892f9460c0b7"}},{"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-04 14:57:24 +01:00
Gonçalo Rica Pais da Silva	3650b998ed	[8.18] [APM] Do not rely on rendered items directly to update dependent requests (#216312) (#217161) ... # Backport This will backport the following commits from `main` to `8.18`: - [[APM] Do not rely on rendered items directly to update dependent requests (#216312)](https://github.com/elastic/kibana/pull/216312) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-04-03T18:23:09Z","message":"[APM] Do not rely on rendered items directly to update dependent requests (#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for particular cases. In some\ncases, when the page updates with some new criteria/filters, requests\nthat were being managed by `ManagedTable` would fire at least twice,\nwith the first one getting aborted and then resent. This PR removes that\nbehaviour by not storing the dependent data in a `renderedItems` state\nand instead depending directly on the request data itself and storing\ninstead the indices of the rendered items. This removes the edge-case\nwhere `renderedItems` would cause the affected requests from firing\nmultiple times, due to object equality not being the same for the\nrendered items array between renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability -> Applications -> Service Inventory\n* Select a service with more than one environment\n* Go to Errors tab and open the browser dev tools\n* Change the environment on the service to update the errors tab\n\n**Expected behaviour**: The `detailed_statistics` request should only\nfire once, both on page load and on update (such as changing the service\nenvironment).\n\nThis should apply to the Service Inventory page as well, and anything\nmaking use of the `TransactionsTable` component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","apm","backport:prev-major","Team:obs-ux-infra_services","v8.17.0","v9.1.0"],"title":"[APM] Do not rely on rendered items directly to update dependent requests","number":216312,"url":"https://github.com/elastic/kibana/pull/216312","mergeCommit":{"message":"[APM] Do not rely on rendered items directly to update dependent requests (#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for particular cases. In some\ncases, when the page updates with some new criteria/filters, requests\nthat were being managed by `ManagedTable` would fire at least twice,\nwith the first one getting aborted and then resent. This PR removes that\nbehaviour by not storing the dependent data in a `renderedItems` state\nand instead depending directly on the request data itself and storing\ninstead the indices of the rendered items. This removes the edge-case\nwhere `renderedItems` would cause the affected requests from firing\nmultiple times, due to object equality not being the same for the\nrendered items array between renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability -> Applications -> Service Inventory\n* Select a service with more than one environment\n* Go to Errors tab and open the browser dev tools\n* Change the environment on the service to update the errors tab\n\n**Expected behaviour**: The `detailed_statistics` request should only\nfire once, both on page load and on update (such as changing the service\nenvironment).\n\nThis should apply to the Service Inventory page as well, and anything\nmaking use of the `TransactionsTable` component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.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/216312","number":216312,"mergeCommit":{"message":"[APM] Do not rely on rendered items directly to update dependent requests (#216312)\n\n## Summary\n\nThis PR fixes some wonky request handling for particular cases. In some\ncases, when the page updates with some new criteria/filters, requests\nthat were being managed by `ManagedTable` would fire at least twice,\nwith the first one getting aborted and then resent. This PR removes that\nbehaviour by not storing the dependent data in a `renderedItems` state\nand instead depending directly on the request data itself and storing\ninstead the indices of the rendered items. This removes the edge-case\nwhere `renderedItems` would cause the affected requests from firing\nmultiple times, due to object equality not being the same for the\nrendered items array between renders.\n\nCloses #216144\n\n## How to test\n\n* Go to Observability -> Applications -> Service Inventory\n* Select a service with more than one environment\n* Go to Errors tab and open the browser dev tools\n* Change the environment on the service to update the errors tab\n\n**Expected behaviour**: The `detailed_statistics` request should only\nfire once, both on page load and on update (such as changing the service\nenvironment).\n\nThis should apply to the Service Inventory page as well, and anything\nmaking use of the `TransactionsTable` component.","sha":"0cff949bb444002efdf12f55eba6b2970f9c6b4f"}}]}] BACKPORT-->	2025-04-04 14:24:41 +01:00
Kibana Machine	919468ffce	[8.18] [CI] Allow using elastic-images-qa through PR label or env var (#216878) (#217140) ... # Backport This will backport the following commits from `main` to `8.18`: - [[CI] Allow using `elastic-images-qa` through PR label or env var (#216878)](https://github.com/elastic/kibana/pull/216878) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-04-04T08:05:30Z","message":"[CI] Allow using `elastic-images-qa` through PR label or env var (#216878)\n\n## Summary\nCurrently, if you'd like to test something on Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite all references to\n`elastic-images-qa` for the PR jobs; once done with testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a helpful tool for us to test with WIP VM images, we'd be able\nto add a label to the PR, and it would automatically grab the QA images,\nwithout any temporary commits.\n\nJobs in https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave ran with an elastic-qa image. ✅","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","ci:use-qa-image","v9.1.0"],"title":"[CI] Allow using `elastic-images-qa` through PR label or env var","number":216878,"url":"https://github.com/elastic/kibana/pull/216878","mergeCommit":{"message":"[CI] Allow using `elastic-images-qa` through PR label or env var (#216878)\n\n## Summary\nCurrently, if you'd like to test something on Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite all references to\n`elastic-images-qa` for the PR jobs; once done with testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a helpful tool for us to test with WIP VM images, we'd be able\nto add a label to the PR, and it would automatically grab the QA images,\nwithout any temporary commits.\n\nJobs in https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave ran with an elastic-qa image. ✅","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1"}},"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/216878","number":216878,"mergeCommit":{"message":"[CI] Allow using `elastic-images-qa` through PR label or env var (#216878)\n\n## Summary\nCurrently, if you'd like to test something on Kibana's VM image, you'd\nhave to build a VM image to -qa, then rewrite all references to\n`elastic-images-qa` for the PR jobs; once done with testing, we'd undo\nthe changes to `elastic-images-prod`.\n\nThis is a helpful tool for us to test with WIP VM images, we'd be able\nto add a label to the PR, and it would automatically grab the QA images,\nwithout any temporary commits.\n\nJobs in https://buildkite.com/elastic/kibana-pull-request/builds/289599\nhave ran with an elastic-qa image. ✅","sha":"9f8503e0b34f1c3f79232f04869f0a3ca6ebd2a1"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>	2025-04-04 10:54:23 +01:00
Kibana Machine	520f969b39	[8.18] [Synthetics] Fixed layout when monitors are grouped by (#216434) (#217104) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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","v9.0.0","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","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":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216882","number":216882,"state":"MERGED","mergeCommit":{"sha":"d1ba622e36b556b4dcea64cf410474cfbfef3946","message":"[9.0] [Synthetics] Fixed layout when monitors are grouped by (#216434) (#216882)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\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":"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":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>	2025-04-03 22:48:58 +01:00
Julia Rechkunova	92e2cc7532	[8.18] [Discover][ES|QL] Fix JSON view for ES|QL record in DocViewer (#216642) (#216968) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216885","number":216885,"state":"MERGED","mergeCommit":{"sha":"c46210f690903907c9addd3fcea567bbddf71c3c","message":"[9.0] [Discover][ES|QL] Fix JSON view for ES|QL record in DocViewer (#216642) (#216885)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Discover][ES|QL] Fix JSON view for ES|QL record in DocViewer\n(#216642)](https://github.com/elastic/kibana/pull/216642)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co>"}},{"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,"url":"https://github.com/elastic/kibana/pull/216966","number":216966,"state":"OPEN"}]}] BACKPORT-->	2025-04-03 16:21:22 -03:00
Kibana Machine	d67cb8cec8	[8.18] [Stack connectors] Fix bedrock modelId encoding (#216915) (#217060) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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:44:11 +01:00
Nicolas Chaulet	177ad44060	[8.18] [Fleet] allow alpha, beta, rc suffixes in agent versions (#211787) (#217044) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] allow alpha, beta, rc suffixes in agent versions (#211787)](https://github.com/elastic/kibana/pull/211787) <!--- 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-02-19T20:37:28Z","message":"[Fleet] allow alpha, beta, rc suffixes in agent versions (#211787)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen `9.0.0` comes out, that should show up as latest. For example,\n`8.0.0` versions come back in this order:\n<img width=\"462\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:version","v9.1.0","v8.19.0","backport:8.18","v8.18.1"],"title":"[Fleet] Do not allow alpha, beta, rc suffixes in agent versions","number":211787,"url":"https://github.com/elastic/kibana/pull/211787","mergeCommit":{"message":"[Fleet] allow alpha, beta, rc suffixes in agent versions (#211787)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen `9.0.0` comes out, that should show up as latest. For example,\n`8.0.0` versions come back in this order:\n<img width=\"462\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211849","number":211849,"state":"MERGED","mergeCommit":{"sha":"1f98cbfdb28c12848820484a5ad4d51156f70136","message":"[9.0] [Fleet] allow alpha, beta, rc suffixes in agent versions (#211787) (#211849)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] allow alpha, beta, rc suffixes in agent versions\n(#211787)](https://github.com/elastic/kibana/pull/211787)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211787","number":211787,"mergeCommit":{"message":"[Fleet] allow alpha, beta, rc suffixes in agent versions (#211787)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/211777\n\nAdd agent flyout should show `9.0.0-beta1` now:\n<img width=\"2540\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/86259eea-5858-4d06-8989-8fadb3a57f96\"\n/>\n\nWhen `9.0.0` comes out, that should show up as latest. For example,\n`8.0.0` versions come back in this order:\n<img width=\"462\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c5204806-3cf7-4c65-bb60-21d176f24f17\"\n/>\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"ba2caf92c6e70d94d9743ff7628400750cb35d51"}},{"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"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>	2025-04-03 17:36:36 +01:00
Kevin Delemme	81f21ca312	[8.18] [SLO]: Optional groupings for slo summary (#209910) (#217040) ... # Backport This will backport the following commits from `main` to `8.18`: - [[SLO]: Optional groupings for slo summary (#209910)](https://github.com/elastic/kibana/pull/209910) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T23:18:56Z","message":"[SLO]: Optional groupings for slo summary (#209910)\n\n## Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO summary optional to fix schema validation\r\nissues with SLOs without groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n## Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field. All SLOs should\r\nstill be able to be grouped despite this distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","Team:obs-ux-management","v9.1.0","v8.19.0"],"title":"[SLO]: Optional groupings for slo summary","number":209910,"url":"https://github.com/elastic/kibana/pull/209910","mergeCommit":{"message":"[SLO]: Optional groupings for slo summary (#209910)\n\n## Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO summary optional to fix schema validation\r\nissues with SLOs without groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n## Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field. All SLOs should\r\nstill be able to be grouped despite this distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209934","number":209934,"state":"MERGED","mergeCommit":{"sha":"442136fc09962861c11ab8476813f6dccdf1fce7","message":"[9.0] [SLO]: Optional groupings for slo summary (#209910) (#209934)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[SLO]: Optional groupings for slo summary\n(#209910)](https://github.com/elastic/kibana/pull/209910)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Bailey Cash <bailey.cash@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209910","number":209910,"mergeCommit":{"message":"[SLO]: Optional groupings for slo summary (#209910)\n\n## Summary\r\n\r\nResolves #209159\r\n\r\nMake groupings property in SLO summary optional to fix schema validation\r\nissues with SLOs without groups.\r\n\r\n## Release Notes\r\n\r\nFixed bug that caused issues with loading SLOs by status, SLI type, or\r\ninstance id.\r\n\r\n## Testing\r\n\r\nCreate a SLO without an entry in the \"group by\" field. All SLOs should\r\nstill be able to be grouped despite this distinction.","sha":"02fc0a725d24064f4b5da5a06440a5fb2ac04521"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209933","number":209933,"state":"MERGED","mergeCommit":{"sha":"a37d63bf115a8f408fd91e6ef2da84a81e7b9abe","message":"[8.x] [SLO]: Optional groupings for slo summary (#209910) (#209933)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[SLO]: Optional groupings for slo summary\n(#209910)](https://github.com/elastic/kibana/pull/209910)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Bailey Cash <bailey.cash@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Bailey Cash <bailey.cash@elastic.co>	2025-04-03 17:28:30 +01:00
Kibana Machine	dd5db61860	[8.18] [ObsUx][A11y] Improve abbreviations spell for screen readers (#216954) (#217015) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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\nfbd27a0b-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\nfbd27a0b-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\nfbd27a0b-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:21:51 +01:00
Miriam	99662f5f87	[8.18] [ObsUX][A11y] Add announcement keyboard elements improvements (#216592) (#216987) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216800","number":216800,"state":"MERGED","mergeCommit":{"sha":"ae0c91447de0f4cc021be66dbd66751d3d0ead48","message":"[9.0] [ObsUX][A11y] Add announcement keyboard elements improvements (#216592) (#216800)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[ObsUX][A11y] Add announcement keyboard elements improvements\n(#216592)](https://github.com/elastic/kibana/pull/216592)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>"}},{"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-->	2025-04-03 13:43:34 +01:00
Kibana Machine	fb48a0196d	[8.18] [ObsUX][A11y] Add area label to comparison drop down (#215664) (#215715) ... # Backport This will backport the following commits from `main` to `8.18`: - [[ObsUX][A11y] Add area label to comparison drop down (#215664)](https://github.com/elastic/kibana/pull/215664) <!--- 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-03-24T13:59:22Z","message":"[ObsUX][A11y] Add area label to comparison drop down (#215664)\n\nCloses https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51 01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49 51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd","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 area label to comparison drop down","number":215664,"url":"https://github.com/elastic/kibana/pull/215664","mergeCommit":{"message":"[ObsUX][A11y] Add area label to comparison drop down (#215664)\n\nCloses https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51 01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49 51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd"}},"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/215664","number":215664,"mergeCommit":{"message":"[ObsUX][A11y] Add area label to comparison drop down (#215664)\n\nCloses https://github.com/elastic/kibana/issues/210254\n\nBefore\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 51 01\"\nsrc=\"https://github.com/user-attachments/assets/872ca24d-8087-4261-bdf0-19107b13d01a\"\n/>\n\nAfter\n\n<img width=\"1494\" alt=\"Screenshot 2025-03-24 at 10 49 51\"\nsrc=\"https://github.com/user-attachments/assets/6d840f70-41b3-4891-ab91-cf99f3c6a93e\"\n/>","sha":"a55e3253e70d74735ab474c65f013b6172d0a8fd"}},{"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 13:28:22 +01:00
Kibana Machine	8a0d757fe4	[8.18] [APM] Span links: add tooltip explaining the reason for missing linked span details (#216487) (#216957) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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","v9.0.0","backport:prev-minor","backport:prev-major","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":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216660","number":216660,"state":"MERGED","mergeCommit":{"sha":"b587f643d0bcc489d7a11886a81296723da00616","message":"[9.0] [APM] Span links: add tooltip explaining the reason for missing linked span details (#216487) (#216660)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[APM] Span links: add tooltip explaining the reason for missing\nlinked span details\n(#216487)](https://github.com/elastic/kibana/pull/216487)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/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-03 10:19:00 +01:00
Kibana Machine	462fad4086	[8.18] [Usage collection] Replace agent.type with hard coded value to categorize monitoring type correctly. (#216391) (#216951) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 09:54:02 +01:00
Kibana Machine	bd8c979f98	[8.18] [dashboard] fix State being dropped when editing visualize embeddables (#216901) (#216924) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 `8.18`: {{{{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 `8.18`: {{{{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 `8.18`: {{{{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 23:01:47 +01:00
Kibana Machine	03589f4a90	[8.18] [Status logging] More performant throttling (#216534) (#216912) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 22:00:32 +01:00
Kibana Machine	40e03461f0	[8.18] Add autocomplete support for all field types (#216765) (#216906) ... # Backport This will backport the following commits from `main` to `8.18`: - [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:51:30 +01:00
Kibana Machine	5ae0c07bee	[8.18] Add default metrics dashboard for Node.js OTel (#215735) (#216895) ... # Backport This will backport the following commits from `main` to `8.18`: - [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 20:03:44 +01:00
Tiago Costa	241562a3d5	[8.18] chore(NA): replaces native-hdr-histogram with hdr-histogram-js (#216715) (#216875) ... # Backport This will backport the following commits from `main` to `8.18`: - [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"}},{"url":"https://github.com/elastic/kibana/pull/216870","number":216870,"branch":"9.0","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/216874","number":216874,"branch":"8.x","state":"OPEN"}]}] BACKPORT-->	2025-04-02 18:46:08 +01:00
Steph Milovic	40db38b0f9	[8.18] [Security solution] Read config from preconfigured connectors in Assistant/Attack Discovery (#216700) (#216873) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 18:26:12 +01:00
Kibana Machine	fd9c9794eb	[8.18] Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927) (#216866) ... # Backport This will backport the following commits from `main` to `8.18`: - [Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)](https://github.com/elastic/kibana/pull/213927) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Miguel Garzón","email":"mgarzon@uottawa.ca"},"sourceCommit":{"committedDate":"2025-03-21T09:32:14Z","message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","backport missing","backport:prev-major","backport:version","v9.1.0","v8.19.0"],"title":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes","number":213927,"url":"https://github.com/elastic/kibana/pull/213927","mergeCommit":{"message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213927","number":213927,"mergeCommit":{"message":"Updates datafeeds for supplied security anomaly detection jobs to exclude Elastic Agent and Beats processes (#213927)\n\nAs described in https://github.com/elastic/security-team/issues/11532,\nwe have added filters to exclude any processing related to the elastic\nendpoint agents.","sha":"35588ecdbb852d54b3f7e38bc3b737099a11758f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Miguel Garzón <mgarzon@uottawa.ca>	2025-04-02 17:45:46 +01:00
Kibana Machine	fb8150da8e	[8.18] [Discover] Fix getAdditionalCellActions FTR tests (#216540) (#216858) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 17:37:46 +01:00
Kibana Machine	dff8933d48	[8.18] [Security Solution] Fix alerts table grouping severity stats not showing badge (#216738) (#216845) ... # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)](https://github.com/elastic/kibana/pull/216738) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-04-02T13:42:46Z","message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1","v8.17.5","v8.16.7"],"title":"[Security Solution] Fix alerts table grouping severity stats not showing badge","number":216738,"url":"https://github.com/elastic/kibana/pull/216738","mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0","8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216738","number":216738,"mergeCommit":{"message":"[Security Solution] Fix alerts table grouping severity stats not showing badge (#216738)\n\n## Summary\n\nThis PR fixes an issue introduced by [this\nPR](https://github.com/elastic/kibana/pull/184635) back in `8.16`. I\ndon't think anyone noticed the problem until now...\n\nIn the PR linked above, the name of the property responsible to render\ncustom components in the group stats section of the alerts table\ngrouping was changed from `renderer` to `component` but there was (at\nleast) one usage that had not been updated. Because that usage wasn't\ncorrectly typed and there was no unit tests to verify the behavior, the\nissue went unnoticed...\n\n### Notes\n\nThis whole code should be refactored eventually. This is not the purpose\nof this PR. This only focuses on fixing the issue, adding proper types\nand unit tests.\n\n| Before | After |\n| ------------- | ------------- |\n| \n| \n|\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"c1939bb6478bc1f64046680bf77346549517921f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2025-04-02 16:46:31 +01:00
Kibana Machine	65df0cb8da	[8.18] Dev console - improve autocomplete for ES|QL _query API (#216795) (#216833) ... # Backport This will backport the following commits from `main` to `8.18`: - [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:58 +01:00
Hannah Mudge	dad960ba36	[8.18] [controls] remove id from explicit input (#211851) (#216702) ... # Backport This will backport the following commits from `main` to `8.18`: - [[controls] remove id from explicit input (#211851)](https://github.com/elastic/kibana/pull/211851) <!--- 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-03T21:31:42Z","message":"[controls] remove id from explicit input (#211851)\n\nPart of `EmbeddableInput` type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part of this effort\nis removing `id` key from `controlConfig/explicitInput`.\n\nWhile investigating this PR, I found it odd that\n`ControlGroupApi.serializeState` returned controls in shape `[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason this works\nis that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut` adds `id` to each object in `controls`. This PR\nalso resolves this and updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[ { id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","project:embeddableRebuild","backport:version","v9.1.0","v8.19.0"],"title":"[controls] remove id from explicit input","number":211851,"url":"https://github.com/elastic/kibana/pull/211851","mergeCommit":{"message":"[controls] remove id from explicit input (#211851)\n\nPart of `EmbeddableInput` type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part of this effort\nis removing `id` key from `controlConfig/explicitInput`.\n\nWhile investigating this PR, I found it odd that\n`ControlGroupApi.serializeState` returned controls in shape `[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason this works\nis that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut` adds `id` to each object in `controls`. This PR\nalso resolves this and updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[ { id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e"}},"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/211851","number":211851,"mergeCommit":{"message":"[controls] remove id from explicit input (#211851)\n\nPart of `EmbeddableInput` type removal.\n\nPR removes `EmbeddableInput` from controls plugin. Part of this effort\nis removing `id` key from `controlConfig/explicitInput`.\n\nWhile investigating this PR, I found it odd that\n`ControlGroupApi.serializeState` returned controls in shape `[ { ...rest\n} ]` while `ControlGroupFactory.deserializeState` expected to receive\ncontrols in the shape `[ { id, ...rest }]`. The only reason this works\nis that\nsrc/platform/plugins/shared/dashboard/server/content_management/v3/transform_utils.ts\n`controlGroupInputOut` adds `id` to each object in `controls`. This PR\nalso resolves this and updates `ControlGroupApi.serializeState` to\nreturn controls in shape `[ { id, ...rest } ]`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"decf5feba554df9c14301d4f47bba969d2bd727e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212994","number":212994,"state":"MERGED","mergeCommit":{"sha":"8cea348178264f1e994ac2e71814c2ec63bc7fd7","message":"[8.x] [controls] remove id from explicit input (#211851) (#212994)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[controls] remove id from explicit input\n(#211851)](https://github.com/elastic/kibana/pull/211851)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Nathan Reese <reese.nathan@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Nathan Reese <reese.nathan@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-04-02 08:30:00 -06:00
Kibana Machine	efa90a360d	[8.18] [Vega] Fix update vega spec in functional tests (#216620) (#216673) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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-02 09:56:26 +01:00
Kibana Machine	b9e6f3d0e6	[8.18] [FIPS] Skips license check test for FIPS test suite (#216056) (#216728) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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:11:32 +01:00
Cauê Marcondes	3f72e2f823	[8.18] [APM] Fix query for transaction marks (#215819) (#216679) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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 20:42:45 +01:00
jennypavlova	71bbb4774e	[8.18] [APM][OTel] Add url.full fallback (#215397) (#216639) ... # Backport This will backport the following commits from `main` to `8.18`: - [[APM][OTel] Add url.full fallback (#215397)](https://github.com/elastic/kibana/pull/215397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-04-01T09:50:28Z","message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","ci:build-serverless-image","ci:project-deploy-observability","Team:obs-ux-infra_services","ci:project-redeploy","v9.1.0"],"title":"[APM][OTel] Add url.full fallback","number":215397,"url":"https://github.com/elastic/kibana/pull/215397","mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215397","number":215397,"mergeCommit":{"message":"[APM][OTel] Add url.full fallback (#215397)\n\n## Summary\n\nThis PR fixes the missing URL in the transaction summary \n\n## Testing [_UPDATED_]\n- [SOLVED ✅ ⬇️ ] ~~This is tricky to test ( I am trying to create a\nserverless instance from this PR and it should make it easier)~~\n- Testing on serverless (the env linked in the PR) \n - EDOT service (I run locally in Docker and connect to the env): \n<img width=\"1904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c3a7ab56-5b8f-42a5-8033-55ccbb915b40\"\n/>\n\n - Other generated service (from the env):\n\n\n \n- In the meantime \n - using synthtrace: Case to run/expectation\n- `node scripts/synthtrace otel_edot_simple_trace.ts` / The trace\nsummary should be visible\n \n\n\n\n- `node scripts/synthtrace simple_trace.ts` / The trace summary should\nstill be visible (using `url.full` in this case)\n \n\n","sha":"a987209d3fc6c10153181781bdf1c8c829ceba04"}}]}] BACKPORT-->	2025-04-01 18:50:40 +01:00
florent-leborgne	89ab8e4aff	[8.18] [Docs] Add note about runtime fields and data views (#216617) (#216669) ... # Backport This will backport the following commits from `8.x` to `8.18`: - [[Docs] Add note about runtime fields and data views (#216617)](https://github.com/elastic/kibana/pull/216617) <!--- 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-01T15:37:58Z","message":"[Docs] Add note about runtime fields and data views (#216617)\n\nReproduce https://github.com/elastic/kibana/pull/159636","sha":"2d7bbd76f621b42457ddbf1c2377a6e4f6a717db","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.16.0","backport:version","v8.17.0","v8.18.0","v8.19.0"],"title":"[Docs] Add note about runtime fields and data views","number":216617,"url":"https://github.com/elastic/kibana/pull/216617","mergeCommit":{"message":"[Docs] Add note about runtime fields and data views (#216617)\n\nReproduce https://github.com/elastic/kibana/pull/159636","sha":"2d7bbd76f621b42457ddbf1c2377a6e4f6a717db"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.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":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-01 16:12:54 +00:00
Julia Bardi	0c716056b3	[8.18][Fleet] Update inputs_with_standalone_docker_agent.ts (#216622) ... Related to https://github.com/elastic/kibana/pull/216589 Fix docker image	2025-04-01 16:44:05 +02:00
Kibana Machine	43968cbe58	[8.18] [APM][OTel] Fix spanlink invalid filter (#215322) (#216607) ... # Backport This will backport the following commits from `main` to `8.18`: - [[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:43:54 +01:00