40424 commits

Author	SHA1	Message	Date
Kibana Machine	109901226d	[8.15] [Semantic text] Make semantic text work with non-root level fields (#187154) (#188080) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Semantic text] Make semantic text work with non-root level fields (#187154)](https://github.com/elastic/kibana/pull/187154) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-11T10:35:56Z","message":"[Semantic text] Make semantic text work with non-root level fields (#187154)\n\n## Summary\r\n\r\nThis makes semantic text work with non-root level reference fields. It\r\nalso correctly adds copy_to to existing copy_to fields instead of\r\nreplacing them, and streamlines a lot of the code.\r\n\r\nTo test these changes:\r\n\r\n- Create an index\r\n- Go to the index mappings page at\r\n`app/management/data/index_management/indices/index_details?{yourIndexName}=blah&tab=mappings`\r\n- Add an object field with a text field inside\r\n- Add a semantic text field referencing that text field\r\n- If you're on a Macbook, create a new inference endpoint with the model\r\n`.elser_model_2` instead of using the default inference endpoint.\r\n- Add a second semantic text field referencing that text field\r\n- Save your mappings\r\n- Use JSON view to verify that the newly created text field contains a\r\n`copy_to` field referencing both newly created semantic text fields\r\n- Verify that the newly created semantic text fields are also in the\r\nJSON view\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"460b52077ffa26673b1a40fff87a7ee182f0c9db","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","v8.15.0","v8.16.0"],"title":"[Semantic text] Make semantic text work with non-root level fields","number":187154,"url":"https://github.com/elastic/kibana/pull/187154","mergeCommit":{"message":"[Semantic text] Make semantic text work with non-root level fields (#187154)\n\n## Summary\r\n\r\nThis makes semantic text work with non-root level reference fields. It\r\nalso correctly adds copy_to to existing copy_to fields instead of\r\nreplacing them, and streamlines a lot of the code.\r\n\r\nTo test these changes:\r\n\r\n- Create an index\r\n- Go to the index mappings page at\r\n`app/management/data/index_management/indices/index_details?{yourIndexName}=blah&tab=mappings`\r\n- Add an object field with a text field inside\r\n- Add a semantic text field referencing that text field\r\n- If you're on a Macbook, create a new inference endpoint with the model\r\n`.elser_model_2` instead of using the default inference endpoint.\r\n- Add a second semantic text field referencing that text field\r\n- Save your mappings\r\n- Use JSON view to verify that the newly created text field contains a\r\n`copy_to` field referencing both newly created semantic text fields\r\n- Verify that the newly created semantic text fields are also in the\r\nJSON view\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"460b52077ffa26673b1a40fff87a7ee182f0c9db"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187154","number":187154,"mergeCommit":{"message":"[Semantic text] Make semantic text work with non-root level fields (#187154)\n\n## Summary\r\n\r\nThis makes semantic text work with non-root level reference fields. It\r\nalso correctly adds copy_to to existing copy_to fields instead of\r\nreplacing them, and streamlines a lot of the code.\r\n\r\nTo test these changes:\r\n\r\n- Create an index\r\n- Go to the index mappings page at\r\n`app/management/data/index_management/indices/index_details?{yourIndexName}=blah&tab=mappings`\r\n- Add an object field with a text field inside\r\n- Add a semantic text field referencing that text field\r\n- If you're on a Macbook, create a new inference endpoint with the model\r\n`.elser_model_2` instead of using the default inference endpoint.\r\n- Add a second semantic text field referencing that text field\r\n- Save your mappings\r\n- Use JSON view to verify that the newly created text field contains a\r\n`copy_to` field referencing both newly created semantic text fields\r\n- Verify that the newly created semantic text fields are also in the\r\nJSON view\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"460b52077ffa26673b1a40fff87a7ee182f0c9db"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>	2024-07-11 22:18:07 +10:00
Kibana Machine	85e3486e31	[8.15] [Security Solution][Notes] - fix item per page wrong order in popover (#187967) (#188057) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Notes] - fix item per page wrong order in popover (#187967)](https://github.com/elastic/kibana/pull/187967) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T08:24:10Z","message":"[Security Solution][Notes] - fix item per page wrong order in popover (#187967)","sha":"189fc763f524db771303fa9fac54ad9399c2a52b","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","v8.15.0","v8.16.0"],"title":"[Security Solution][Notes] - fix item per page wrong order in popover","number":187967,"url":"https://github.com/elastic/kibana/pull/187967","mergeCommit":{"message":"[Security Solution][Notes] - fix item per page wrong order in popover (#187967)","sha":"189fc763f524db771303fa9fac54ad9399c2a52b"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187967","number":187967,"mergeCommit":{"message":"[Security Solution][Notes] - fix item per page wrong order in popover (#187967)","sha":"189fc763f524db771303fa9fac54ad9399c2a52b"}}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2024-07-11 20:02:14 +10:00
Kibana Machine	216aa79c5a	[8.15] [Search] Notebooks Telemetry (#188007) (#188055) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Search] Notebooks Telemetry (#188007)](https://github.com/elastic/kibana/pull/188007) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rodney Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T07:40:41Z","message":"[Search] Notebooks Telemetry (#188007)\n\n## Summary\r\n\r\nAdded telemetry tracking with usageCollection for opening notebooks\r\nview, viewing a specific notebook and errors fetching notebooks.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)","sha":"b11e9eeb6d8fd7579d95b2515ab0eb2d64523504","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","v8.15.0","v8.16.0"],"title":"[Search] Notebooks Telemetry","number":188007,"url":"https://github.com/elastic/kibana/pull/188007","mergeCommit":{"message":"[Search] Notebooks Telemetry (#188007)\n\n## Summary\r\n\r\nAdded telemetry tracking with usageCollection for opening notebooks\r\nview, viewing a specific notebook and errors fetching notebooks.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)","sha":"b11e9eeb6d8fd7579d95b2515ab0eb2d64523504"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188007","number":188007,"mergeCommit":{"message":"[Search] Notebooks Telemetry (#188007)\n\n## Summary\r\n\r\nAdded telemetry tracking with usageCollection for opening notebooks\r\nview, viewing a specific notebook and errors fetching notebooks.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)","sha":"b11e9eeb6d8fd7579d95b2515ab0eb2d64523504"}}]}] BACKPORT--> Co-authored-by: Rodney Norris <rodney.norris@elastic.co>	2024-07-11 19:21:50 +10:00
Kibana Machine	f405425068	[8.15] [Security Solution][Notes] - fix notes management page search crash (#187934) (#188047) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Notes] - fix notes management page search crash (#187934)](https://github.com/elastic/kibana/pull/187934) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T06:26:49Z","message":"[Security Solution][Notes] - fix notes management page search crash (#187934)","sha":"2958be7303f40cc055a983760a5a9f45b42386fe","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","v8.15.0","v8.16.0"],"title":"[Security Solution][Notes] - fix notes management page search crash","number":187934,"url":"https://github.com/elastic/kibana/pull/187934","mergeCommit":{"message":"[Security Solution][Notes] - fix notes management page search crash (#187934)","sha":"2958be7303f40cc055a983760a5a9f45b42386fe"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187934","number":187934,"mergeCommit":{"message":"[Security Solution][Notes] - fix notes management page search crash (#187934)","sha":"2958be7303f40cc055a983760a5a9f45b42386fe"}}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2024-07-11 18:20:04 +10:00
Kibana Machine	068466261e	[8.15] [Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts (#187966) (#188048) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts (#187966)](https://github.com/elastic/kibana/pull/187966) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T06:27:30Z","message":"[Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts (#187966)","sha":"cc7588c8cb9cc428e97df6b057a898fa7ceb5383","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","v8.15.0","v8.16.0"],"title":"[Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts","number":187966,"url":"https://github.com/elastic/kibana/pull/187966","mergeCommit":{"message":"[Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts (#187966)","sha":"cc7588c8cb9cc428e97df6b057a898fa7ceb5383"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187966","number":187966,"mergeCommit":{"message":"[Security Solution][Alert details] - do not show Notes tab for Rule creation preview alerts (#187966)","sha":"cc7588c8cb9cc428e97df6b057a898fa7ceb5383"}}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2024-07-11 18:09:23 +10:00
Kibana Machine	494668ea1a	[8.15] [Fleet] Display view in logs button when logs app is available (#187871) (#188000) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Fleet] Display view in logs button when logs app is available (#187871)](https://github.com/elastic/kibana/pull/187871) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-10T15:17:31Z","message":"[Fleet] Display view in logs button when logs app is available (#187871)\n\nCloses https://github.com/elastic/kibana/issues/185711\r\n\r\n## Summary\r\nThis change fixes https://github.com/elastic/kibana/issues/185711, but\r\nwhile working on that I also realised that we should move away from\r\nusing hardcoded urls. So this PR does two things:\r\n- Displays the button only when the user has `authz.fleet.readAgents`\r\nprivilege\r\n- Refactors the button functionality to use the new locators that take\r\ncare of linking to the observability logs/discover app\r\n\r\n### Why the refactor\r\nWhile testing this button, I noticed that the functionality was broken\r\nin some cases, that's because we were manually routing the urls to Logs\r\nUI/Discover apps based if we are in serverless or not.\r\n\r\nI found a PR that already implements this functionality:\r\nhttps://github.com/elastic/kibana/pull/155156\r\nI also found https://github.com/elastic/kibana/pull/154145 that takes\r\ncare of the redirect to the correct app.\r\nSo I'm replacing the current manual functionality with these utilities\r\nso that `getLogsLocatorsFromUrlService` takes care of where the open in\r\nlogs button should link.\r\n\r\n\r\n\r\n### ESS\r\n\r\n\r\n3436cf5a-36c9-425d-a114-e116ddaa1a03\r\n\r\n### Serverless\r\n\r\n84176f09-96a4-4932-9508-5f7682d03aae\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"696bb88d7c33eebfeabec6064ea8a97a2e2bb1bb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.15.0","v8.16.0"],"title":"[Fleet] Display view in logs button when logs app is available","number":187871,"url":"https://github.com/elastic/kibana/pull/187871","mergeCommit":{"message":"[Fleet] Display view in logs button when logs app is available (#187871)\n\nCloses https://github.com/elastic/kibana/issues/185711\r\n\r\n## Summary\r\nThis change fixes https://github.com/elastic/kibana/issues/185711, but\r\nwhile working on that I also realised that we should move away from\r\nusing hardcoded urls. So this PR does two things:\r\n- Displays the button only when the user has `authz.fleet.readAgents`\r\nprivilege\r\n- Refactors the button functionality to use the new locators that take\r\ncare of linking to the observability logs/discover app\r\n\r\n### Why the refactor\r\nWhile testing this button, I noticed that the functionality was broken\r\nin some cases, that's because we were manually routing the urls to Logs\r\nUI/Discover apps based if we are in serverless or not.\r\n\r\nI found a PR that already implements this functionality:\r\nhttps://github.com/elastic/kibana/pull/155156\r\nI also found https://github.com/elastic/kibana/pull/154145 that takes\r\ncare of the redirect to the correct app.\r\nSo I'm replacing the current manual functionality with these utilities\r\nso that `getLogsLocatorsFromUrlService` takes care of where the open in\r\nlogs button should link.\r\n\r\n\r\n\r\n### ESS\r\n\r\n\r\n3436cf5a-36c9-425d-a114-e116ddaa1a03\r\n\r\n### Serverless\r\n\r\n84176f09-96a4-4932-9508-5f7682d03aae\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"696bb88d7c33eebfeabec6064ea8a97a2e2bb1bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187871","number":187871,"mergeCommit":{"message":"[Fleet] Display view in logs button when logs app is available (#187871)\n\nCloses https://github.com/elastic/kibana/issues/185711\r\n\r\n## Summary\r\nThis change fixes https://github.com/elastic/kibana/issues/185711, but\r\nwhile working on that I also realised that we should move away from\r\nusing hardcoded urls. So this PR does two things:\r\n- Displays the button only when the user has `authz.fleet.readAgents`\r\nprivilege\r\n- Refactors the button functionality to use the new locators that take\r\ncare of linking to the observability logs/discover app\r\n\r\n### Why the refactor\r\nWhile testing this button, I noticed that the functionality was broken\r\nin some cases, that's because we were manually routing the urls to Logs\r\nUI/Discover apps based if we are in serverless or not.\r\n\r\nI found a PR that already implements this functionality:\r\nhttps://github.com/elastic/kibana/pull/155156\r\nI also found https://github.com/elastic/kibana/pull/154145 that takes\r\ncare of the redirect to the correct app.\r\nSo I'm replacing the current manual functionality with these utilities\r\nso that `getLogsLocatorsFromUrlService` takes care of where the open in\r\nlogs button should link.\r\n\r\n\r\n\r\n### ESS\r\n\r\n\r\n3436cf5a-36c9-425d-a114-e116ddaa1a03\r\n\r\n### Serverless\r\n\r\n84176f09-96a4-4932-9508-5f7682d03aae\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"696bb88d7c33eebfeabec6064ea8a97a2e2bb1bb"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com>	2024-07-11 03:24:56 +10:00
Kibana Machine	b9e186b0e8	[8.15] [Synthetics] Accept project monitors with &#x60;monitor.url&#x60; of type &#x60;string&#x60; that contains commas (#186112) (#187992) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Synthetics] Accept project monitors with &#x60;monitor.url&#x60; of type &#x60;string&#x60; that contains commas (#186112)](https://github.com/elastic/kibana/pull/186112) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2024-07-10T14:33:36Z","message":"[Synthetics] Accept project monitors with `monitor.url` of type `string` that contains commas (#186112)\n\n## Summary\r\n\r\nResolves #186093.\r\n\r\nResult of an [SDH](https://github.com/elastic/sdh-synthetics/issues/97)\r\nthat lead to a desire to refine Kibana's acceptance criteria for\r\nlightweight project monitors.\r\n\r\nHeartbeat accepts `monitor.url` values of type `string` as a\r\ncomma-delimited list, like:\r\n\r\n`https://elastic.co,https://amazon.com`\r\n\r\nThis is not supported for Synthetics, the design goals of the product\r\ndemand a 1:1 ratio relationship between URL<->Monitor.\r\n\r\nThus the code attempts to handle this parsing. It has the unintended\r\nside effect of rejecting otherwise valid URLs that contain commas.\r\nRather than creating even more sophisticated parsing for this case, this\r\npatch would remove all parsing of string fields, and simply convert them\r\nto a list with one entry, which is what we then store in the monitor's\r\ndefinition.\r\n\r\n_NOTE:_ this also adds a call to `new URL` to attempt to parse the URL\r\nvalue. This wasn't present before, but the Agent team made it clear that\r\nwe should do best-effort checks to ensure that an invalid URL doesn't\r\nactually make it to the point of executing on the service. I've added a\r\nfourth test case to the testing instructions below.\r\n\r\n## Testing\r\n\r\nThere are several cases we must cover to ensure we aren't breaking\r\nanything with this change. We must initiate these checks against both\r\npublic and private locations, as the backend behavior of the two\r\ndiffers.\r\n\r\n- Create a monitor in a list containing a comma. Example:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls:\r\n - \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n\r\n```\r\n\r\n- Create a monitor with the URL defined as a string, containing a comma:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n```\r\n\r\n- Create a monitor with a URL defined as a string, containing a\r\ncomma-delimited list of valid URLs:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Trollface two montiors\r\n id: todos-lightweight-multiple\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/,https://elastic.co\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```\r\n- Create a monitor with a URL defined as a string, containing an invalid\r\nURL:\r\n```yaml\r\n- type: http\r\n name: Unhandled text\r\n id: unhandled-text\r\n enabled: true\r\n urls: \"unhandledtext\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```","sha":"ac91af821fb44da063040b9d0a0b094c18a42092","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","v8.15.0","v8.16.0"],"title":"[Synthetics] Accept project monitors with `monitor.url` of type `string` that contains commas","number":186112,"url":"https://github.com/elastic/kibana/pull/186112","mergeCommit":{"message":"[Synthetics] Accept project monitors with `monitor.url` of type `string` that contains commas (#186112)\n\n## Summary\r\n\r\nResolves #186093.\r\n\r\nResult of an [SDH](https://github.com/elastic/sdh-synthetics/issues/97)\r\nthat lead to a desire to refine Kibana's acceptance criteria for\r\nlightweight project monitors.\r\n\r\nHeartbeat accepts `monitor.url` values of type `string` as a\r\ncomma-delimited list, like:\r\n\r\n`https://elastic.co,https://amazon.com`\r\n\r\nThis is not supported for Synthetics, the design goals of the product\r\ndemand a 1:1 ratio relationship between URL<->Monitor.\r\n\r\nThus the code attempts to handle this parsing. It has the unintended\r\nside effect of rejecting otherwise valid URLs that contain commas.\r\nRather than creating even more sophisticated parsing for this case, this\r\npatch would remove all parsing of string fields, and simply convert them\r\nto a list with one entry, which is what we then store in the monitor's\r\ndefinition.\r\n\r\n_NOTE:_ this also adds a call to `new URL` to attempt to parse the URL\r\nvalue. This wasn't present before, but the Agent team made it clear that\r\nwe should do best-effort checks to ensure that an invalid URL doesn't\r\nactually make it to the point of executing on the service. I've added a\r\nfourth test case to the testing instructions below.\r\n\r\n## Testing\r\n\r\nThere are several cases we must cover to ensure we aren't breaking\r\nanything with this change. We must initiate these checks against both\r\npublic and private locations, as the backend behavior of the two\r\ndiffers.\r\n\r\n- Create a monitor in a list containing a comma. Example:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls:\r\n - \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n\r\n```\r\n\r\n- Create a monitor with the URL defined as a string, containing a comma:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n```\r\n\r\n- Create a monitor with a URL defined as a string, containing a\r\ncomma-delimited list of valid URLs:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Trollface two montiors\r\n id: todos-lightweight-multiple\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/,https://elastic.co\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```\r\n- Create a monitor with a URL defined as a string, containing an invalid\r\nURL:\r\n```yaml\r\n- type: http\r\n name: Unhandled text\r\n id: unhandled-text\r\n enabled: true\r\n urls: \"unhandledtext\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```","sha":"ac91af821fb44da063040b9d0a0b094c18a42092"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186112","number":186112,"mergeCommit":{"message":"[Synthetics] Accept project monitors with `monitor.url` of type `string` that contains commas (#186112)\n\n## Summary\r\n\r\nResolves #186093.\r\n\r\nResult of an [SDH](https://github.com/elastic/sdh-synthetics/issues/97)\r\nthat lead to a desire to refine Kibana's acceptance criteria for\r\nlightweight project monitors.\r\n\r\nHeartbeat accepts `monitor.url` values of type `string` as a\r\ncomma-delimited list, like:\r\n\r\n`https://elastic.co,https://amazon.com`\r\n\r\nThis is not supported for Synthetics, the design goals of the product\r\ndemand a 1:1 ratio relationship between URL<->Monitor.\r\n\r\nThus the code attempts to handle this parsing. It has the unintended\r\nside effect of rejecting otherwise valid URLs that contain commas.\r\nRather than creating even more sophisticated parsing for this case, this\r\npatch would remove all parsing of string fields, and simply convert them\r\nto a list with one entry, which is what we then store in the monitor's\r\ndefinition.\r\n\r\n_NOTE:_ this also adds a call to `new URL` to attempt to parse the URL\r\nvalue. This wasn't present before, but the Agent team made it clear that\r\nwe should do best-effort checks to ensure that an invalid URL doesn't\r\nactually make it to the point of executing on the service. I've added a\r\nfourth test case to the testing instructions below.\r\n\r\n## Testing\r\n\r\nThere are several cases we must cover to ensure we aren't breaking\r\nanything with this change. We must initiate these checks against both\r\npublic and private locations, as the backend behavior of the two\r\ndiffers.\r\n\r\n- Create a monitor in a list containing a comma. Example:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls:\r\n - \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n\r\n```\r\n\r\n- Create a monitor with the URL defined as a string, containing a comma:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Todos Lightweight\r\n id: todos-lightweight\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/?demo=123,345\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n```\r\n\r\n- Create a monitor with a URL defined as a string, containing a\r\ncomma-delimited list of valid URLs:\r\n```yaml\r\nheartbeat.monitors:\r\n- type: http\r\n name: Trollface two montiors\r\n id: todos-lightweight-multiple\r\n enabled: true\r\n urls: \"https://elastic.github.io/synthetics-demo/,https://elastic.co\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```\r\n- Create a monitor with a URL defined as a string, containing an invalid\r\nURL:\r\n```yaml\r\n- type: http\r\n name: Unhandled text\r\n id: unhandled-text\r\n enabled: true\r\n urls: \"unhandledtext\"\r\n schedule: '@every 10s'\r\n timeout: 16s\r\n alert.status.enabled: true\r\n```","sha":"ac91af821fb44da063040b9d0a0b094c18a42092"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co>	2024-07-11 02:11:31 +10:00
Kibana Machine	13f7bf1b5f	[8.15] [Security Solution] [Timelines] Notes table links (#187868) (#187986) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] [Timelines] Notes table links (#187868)](https://github.com/elastic/kibana/pull/187868) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Qualters","email":"56408403+kqualters-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-10T13:55:02Z","message":"[Security Solution] [Timelines] Notes table links (#187868)\n\n## Summary\r\n\r\nThis pr changes the timeline id cell to be a link to open the saved\r\ntimeline a note is a part of if timelineId exists, instead of just\r\nshowing the id as a plain string. Also updates the event column to a\r\nlink that opens a new timeline containing just the event a note is\r\nassociated with.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))","sha":"209b0c52cb905cc0b62db9ef9f425d1119cdc549","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","v8.15.0","v8.16.0"],"title":"[Security Solution] [Timelines] Notes table links","number":187868,"url":"https://github.com/elastic/kibana/pull/187868","mergeCommit":{"message":"[Security Solution] [Timelines] Notes table links (#187868)\n\n## Summary\r\n\r\nThis pr changes the timeline id cell to be a link to open the saved\r\ntimeline a note is a part of if timelineId exists, instead of just\r\nshowing the id as a plain string. Also updates the event column to a\r\nlink that opens a new timeline containing just the event a note is\r\nassociated with.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))","sha":"209b0c52cb905cc0b62db9ef9f425d1119cdc549"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187868","number":187868,"mergeCommit":{"message":"[Security Solution] [Timelines] Notes table links (#187868)\n\n## Summary\r\n\r\nThis pr changes the timeline id cell to be a link to open the saved\r\ntimeline a note is a part of if timelineId exists, instead of just\r\nshowing the id as a plain string. Also updates the event column to a\r\nlink that opens a new timeline containing just the event a note is\r\nassociated with.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))","sha":"209b0c52cb905cc0b62db9ef9f425d1119cdc549"}}]}] BACKPORT--> Co-authored-by: Kevin Qualters <56408403+kqualters-elastic@users.noreply.github.com>	2024-07-11 01:34:57 +10:00
Kibana Machine	4b9a9c375e	[8.15] [Security GenAI] [ Integration Assistant] Add missing ecs fields into the context (#187826) (#187973) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security GenAI] [ Integration Assistant] Add missing ecs fields into the context (#187826)](https://github.com/elastic/kibana/pull/187826) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-10T13:03:10Z","message":"[Security GenAI] [ Integration Assistant] Add missing ecs fields into the context (#187826)","sha":"6f168b5ea9ca2710656eea8cbca766019d6ffc04","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team: SecuritySolution","v8.15.0","v8.16.0"],"title":"[Security GenAI] [ Integration Assistant] Add missing ecs fields into the context","number":187826,"url":"https://github.com/elastic/kibana/pull/187826","mergeCommit":{"message":"[Security GenAI] [ Integration Assistant] Add missing ecs fields into the context (#187826)","sha":"6f168b5ea9ca2710656eea8cbca766019d6ffc04"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187826","number":187826,"mergeCommit":{"message":"[Security GenAI] [ Integration Assistant] Add missing ecs fields into the context (#187826)","sha":"6f168b5ea9ca2710656eea8cbca766019d6ffc04"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>	2024-07-11 01:09:27 +10:00
Kibana Machine	0cc8062cee	[8.15] [Search][Playground] Update UI (#187608) (#187974) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Search][Playground] Update UI (#187608)](https://github.com/elastic/kibana/pull/187608) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yan Savitski","email":"yan.savitski@elastic.co"},"sourceCommit":{"committedDate":"2024-07-10T13:05:59Z","message":"[Search][Playground] Update UI (#187608)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"77267b28ba6be1a85c7a2ee1169db48864b52ef0","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"title":"[Search][Playground] Update UI","number":187608,"url":"https://github.com/elastic/kibana/pull/187608","mergeCommit":{"message":"[Search][Playground] Update UI (#187608)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"77267b28ba6be1a85c7a2ee1169db48864b52ef0"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187608","number":187608,"mergeCommit":{"message":"[Search][Playground] Update UI (#187608)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"77267b28ba6be1a85c7a2ee1169db48864b52ef0"}}]}] BACKPORT--> Co-authored-by: Yan Savitski <yan.savitski@elastic.co>	2024-07-11 00:39:29 +10:00
Gergő Ábrahám	fc2898c058	[Security Solution][EDR Workflows] Enable scan response action feature flag for 8.15 (#187849) ... ## Summary - enables `responseActionScanEnabled` feature flag - updates tests that depend on the feature flag - adds some tests to test with and without FF -> these are coming from the following PR waiting to be merged to `main` - https://github.com/elastic/kibana/pull/187758 - originally wanted to merge and backport the above PR - but we got some blocking test failures on `main`, and i'd like to merge this PR before BC2 is built ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Ashokaditya <ashokaditya@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-11 00:36:29 +10:00
Kibana Machine	2f6d2b9541	[8.15] [Discover] Add functional tests for DocViewer extension (#187742) (#187949) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Discover] Add functional tests for DocViewer extension (#187742)](https://github.com/elastic/kibana/pull/187742) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2024-07-10T10:19:25Z","message":"[Discover] Add functional tests for DocViewer extension (#187742)\n\n- Closes https://github.com/elastic/kibana/issues/186265","sha":"4b19cc7f17c6ebc740402783fee875f547d7d892","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","Project:OneDiscover","v8.16.0"],"title":"[Discover] Add functional tests for DocViewer extension","number":187742,"url":"https://github.com/elastic/kibana/pull/187742","mergeCommit":{"message":"[Discover] Add functional tests for DocViewer extension (#187742)\n\n- Closes https://github.com/elastic/kibana/issues/186265","sha":"4b19cc7f17c6ebc740402783fee875f547d7d892"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187742","number":187742,"mergeCommit":{"message":"[Discover] Add functional tests for DocViewer extension (#187742)\n\n- Closes https://github.com/elastic/kibana/issues/186265","sha":"4b19cc7f17c6ebc740402783fee875f547d7d892"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co>	2024-07-10 21:57:53 +10:00
Kibana Machine	a047529de8	[8.15] [ML] API integration tests for &#x60;/trained_models/model_downloads&#x60; endpoint (#187865) (#187940) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] API integration tests for &#x60;/trained_models/model_downloads&#x60; endpoint (#187865)](https://github.com/elastic/kibana/pull/187865) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-10T09:01:24Z","message":"[ML] API integration tests for `/trained_models/model_downloads` endpoint (#187865)\n\n## Summary\r\n\r\nPart of #182235\r\n\r\nAdds API integration tests for the `GET\r\n/internal/ml/trained_models/model_downloads` endpoint\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"48d4d9ed2c67771a7746422a9203d0008b52b6f9","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","test-api-integration","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] API integration tests for `/trained_models/model_downloads` endpoint","number":187865,"url":"https://github.com/elastic/kibana/pull/187865","mergeCommit":{"message":"[ML] API integration tests for `/trained_models/model_downloads` endpoint (#187865)\n\n## Summary\r\n\r\nPart of #182235\r\n\r\nAdds API integration tests for the `GET\r\n/internal/ml/trained_models/model_downloads` endpoint\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"48d4d9ed2c67771a7746422a9203d0008b52b6f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187865","number":187865,"mergeCommit":{"message":"[ML] API integration tests for `/trained_models/model_downloads` endpoint (#187865)\n\n## Summary\r\n\r\nPart of #182235\r\n\r\nAdds API integration tests for the `GET\r\n/internal/ml/trained_models/model_downloads` endpoint\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"48d4d9ed2c67771a7746422a9203d0008b52b6f9"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>	2024-07-10 20:32:46 +10:00
Carlos Crespo	ae018efb52	[8.15] [Infra] Fix date picker with relative date range (#187739) (#187883) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Infra] Fix date picker with relative date range (#187739)](https://github.com/elastic/kibana/pull/187739) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-09T15:59:17Z","message":"[Infra] Fix date picker with relative date range (#187739)\n\nfixes [187735](https://github.com/elastic/kibana/issues/187735)\r\n\r\n## Summary\r\n\r\nThis PR fixes a problem with the Anomaly Detection component's date\r\npicker when dealing with relative dates\r\n\r\n\r\nc3b036df-e73c-48d5-a27a-6ed75ffbc76a\r\n\r\n\r\n\r\n### How to test\r\n\r\nThe easiest way is to connect to an oblt cluster and create an ML job \r\n\r\n- Navigate to `Infrastructure`\r\n- Click on `Anomaly Detection` menu at the top of the page and create a\r\nML job for hosts\r\n- Follow the same steps from the screen recordings above.","sha":"7c5cf9c76e35925cba7e3bd57cc01d1fffae81a4","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.16.0"],"number":187739,"url":"https://github.com/elastic/kibana/pull/187739","mergeCommit":{"message":"[Infra] Fix date picker with relative date range (#187739)\n\nfixes [187735](https://github.com/elastic/kibana/issues/187735)\r\n\r\n## Summary\r\n\r\nThis PR fixes a problem with the Anomaly Detection component's date\r\npicker when dealing with relative dates\r\n\r\n\r\nc3b036df-e73c-48d5-a27a-6ed75ffbc76a\r\n\r\n\r\n\r\n### How to test\r\n\r\nThe easiest way is to connect to an oblt cluster and create an ML job \r\n\r\n- Navigate to `Infrastructure`\r\n- Click on `Anomaly Detection` menu at the top of the page and create a\r\nML job for hosts\r\n- Follow the same steps from the screen recordings above.","sha":"7c5cf9c76e35925cba7e3bd57cc01d1fffae81a4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187739","number":187739,"mergeCommit":{"message":"[Infra] Fix date picker with relative date range (#187739)\n\nfixes [187735](https://github.com/elastic/kibana/issues/187735)\r\n\r\n## Summary\r\n\r\nThis PR fixes a problem with the Anomaly Detection component's date\r\npicker when dealing with relative dates\r\n\r\n\r\nc3b036df-e73c-48d5-a27a-6ed75ffbc76a\r\n\r\n\r\n\r\n### How to test\r\n\r\nThe easiest way is to connect to an oblt cluster and create an ML job \r\n\r\n- Navigate to `Infrastructure`\r\n- Click on `Anomaly Detection` menu at the top of the page and create a\r\nML job for hosts\r\n- Follow the same steps from the screen recordings above.","sha":"7c5cf9c76e35925cba7e3bd57cc01d1fffae81a4"}}]}] BACKPORT-->	2024-07-10 11:56:36 +02:00
Kibana Machine	e9f1ada196	[8.15] [SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added (#187491) (#187689) ... # Backport This will backport the following commits from `main` to `8.15`: - [[SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added (#187491)](https://github.com/elastic/kibana/pull/187491) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-05T14:51:39Z","message":"[SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added (#187491)\n\n## Summary\r\n\r\nUpdates test so that it fails whenever we add a introduce a new\r\nresponder command.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"fffc684d4e489490ede9726ffe0792206a14be34","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","v8.15.0","v8.16.0"],"title":"[SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added","number":187491,"url":"https://github.com/elastic/kibana/pull/187491","mergeCommit":{"message":"[SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added (#187491)\n\n## Summary\r\n\r\nUpdates test so that it fails whenever we add a introduce a new\r\nresponder command.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"fffc684d4e489490ede9726ffe0792206a14be34"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187491","number":187491,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Update Responder command definition test so that it fails when new commands are added (#187491)\n\n## Summary\r\n\r\nUpdates test so that it fails whenever we add a introduce a new\r\nresponder command.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"fffc684d4e489490ede9726ffe0792206a14be34"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>	2024-07-10 11:53:06 +02:00
Kibana Machine	a98ac324f2	[8.15] [Security Solution] Array of scalar values diff algorithm test plan (#186325) (#187873) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Array of scalar values diff algorithm test plan (#186325)](https://github.com/elastic/kibana/pull/186325) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-09T14:33:04Z","message":"[Security Solution] Array of scalar values diff algorithm test plan (#186325)\n\n## Summary\r\n\r\nRelated ticket: https://github.com/elastic/kibana/issues/180162\r\n\r\nAdds test plan for diff algorithm for arrays of scalar values\r\nimplemented here: https://github.com/elastic/kibana/pull/186323\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0b405a0d656e496775a2c6efa1392ec3ed3fdd4f","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","v8.15.0","v8.16.0"],"title":"[Security Solution] Array of scalar values diff algorithm test plan","number":186325,"url":"https://github.com/elastic/kibana/pull/186325","mergeCommit":{"message":"[Security Solution] Array of scalar values diff algorithm test plan (#186325)\n\n## Summary\r\n\r\nRelated ticket: https://github.com/elastic/kibana/issues/180162\r\n\r\nAdds test plan for diff algorithm for arrays of scalar values\r\nimplemented here: https://github.com/elastic/kibana/pull/186323\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0b405a0d656e496775a2c6efa1392ec3ed3fdd4f"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186325","number":186325,"mergeCommit":{"message":"[Security Solution] Array of scalar values diff algorithm test plan (#186325)\n\n## Summary\r\n\r\nRelated ticket: https://github.com/elastic/kibana/issues/180162\r\n\r\nAdds test plan for diff algorithm for arrays of scalar values\r\nimplemented here: https://github.com/elastic/kibana/pull/186323\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0b405a0d656e496775a2c6efa1392ec3ed3fdd4f"}}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com>	2024-07-10 11:34:39 +02:00
Kibana Machine	85619daf01	[8.15] [Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784) (#187916) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)](https://github.com/elastic/kibana/pull/187784) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rickyanto Ang","email":"rickyangwyn@gmail.com"},"sourceCommit":{"committedDate":"2024-07-09T20:01:00Z","message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com/elastic/kibana/issues/186302\r\nhttps://github.com/elastic/kibana/issues/186315\r\nhttps://github.com/elastic/kibana/issues/186387\r\nhttps://github.com/elastic/kibana/issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","v8.15.0","v8.16.0"],"title":"[Cloud Security]Fix for flaky FTRs caused by duplicate names","number":187784,"url":"https://github.com/elastic/kibana/pull/187784","mergeCommit":{"message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com/elastic/kibana/issues/186302\r\nhttps://github.com/elastic/kibana/issues/186315\r\nhttps://github.com/elastic/kibana/issues/186387\r\nhttps://github.com/elastic/kibana/issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187784","number":187784,"mergeCommit":{"message":"[Cloud Security]Fix for flaky FTRs caused by duplicate names (#187784)\n\n## Summary\r\n\r\nThis PR is to address the following flaky FTRs\r\nhttps://github.com/elastic/kibana/issues/186302\r\nhttps://github.com/elastic/kibana/issues/186315\r\nhttps://github.com/elastic/kibana/issues/186387\r\nhttps://github.com/elastic/kibana/issues/186389\r\n\r\nThe flakiness are being caused by having duplicate names for the\r\nintegration when adding them. We tried adding wait before clicking on\r\nthe Save button however that doesn't seem to work as it starts failing\r\nin the flaky test runner\r\n\r\nThis PR gives the Integration a specific name (not relying on auto\r\nnaming)","sha":"45b0c251913b6978195291a5d317972fe8c83ddb"}}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com>	2024-07-10 07:47:09 +10:00
Kibana Machine	1e231f836d	[8.15] [Cloud Security] fix vulnerability dashboard ftr flaky test (#187790) (#187912) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Cloud Security] fix vulnerability dashboard ftr flaky test (#187790)](https://github.com/elastic/kibana/pull/187790) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lola","email":"omolola.akinleye@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T19:21:19Z","message":"[Cloud Security] fix vulnerability dashboard ftr flaky test (#187790)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\nFix Flaky Vulnerability Dashboard Test","sha":"4b8ba30dd429131a280ec7df9bf21a02480063a4","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","v8.15.0","v8.16.0"],"title":"[Cloud Security] fix vulnerability dashboard ftr flaky test","number":187790,"url":"https://github.com/elastic/kibana/pull/187790","mergeCommit":{"message":"[Cloud Security] fix vulnerability dashboard ftr flaky test (#187790)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\nFix Flaky Vulnerability Dashboard Test","sha":"4b8ba30dd429131a280ec7df9bf21a02480063a4"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187790","number":187790,"mergeCommit":{"message":"[Cloud Security] fix vulnerability dashboard ftr flaky test (#187790)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\r\nFix Flaky Vulnerability Dashboard Test","sha":"4b8ba30dd429131a280ec7df9bf21a02480063a4"}}]}] BACKPORT--> Co-authored-by: Lola <omolola.akinleye@elastic.co>	2024-07-10 06:56:09 +10:00
Kibana Machine	d9269b6b53	[8.15] [Index management] Enable semantic_text feature (#187792) (#187909) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Index management] Enable semantic_text feature (#187792)](https://github.com/elastic/kibana/pull/187792) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saarika Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-09T18:41:27Z","message":"[Index management] Enable semantic_text feature (#187792)\n\nThis PR enables semantic_text feature by default. \r\n\r\nHow to test: \r\n\r\n1. Spin up Serverless or stack instance locally\r\n2. Navigate to index management-> index overview page-> index mappings\r\n3. Click add new field \r\n4. Ensure semantic_text field type is shown in Field type form by\r\ndefault\r\n\r\n\r\nTested in ESS and Serverless locally \r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"799800d26d2edfaef5e424813d9f597774a95c25","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","v8.15.0","v8.16.0"],"title":"[Index management] Enable semantic_text feature ","number":187792,"url":"https://github.com/elastic/kibana/pull/187792","mergeCommit":{"message":"[Index management] Enable semantic_text feature (#187792)\n\nThis PR enables semantic_text feature by default. \r\n\r\nHow to test: \r\n\r\n1. Spin up Serverless or stack instance locally\r\n2. Navigate to index management-> index overview page-> index mappings\r\n3. Click add new field \r\n4. Ensure semantic_text field type is shown in Field type form by\r\ndefault\r\n\r\n\r\nTested in ESS and Serverless locally \r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"799800d26d2edfaef5e424813d9f597774a95c25"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187792","number":187792,"mergeCommit":{"message":"[Index management] Enable semantic_text feature (#187792)\n\nThis PR enables semantic_text feature by default. \r\n\r\nHow to test: \r\n\r\n1. Spin up Serverless or stack instance locally\r\n2. Navigate to index management-> index overview page-> index mappings\r\n3. Click add new field \r\n4. Ensure semantic_text field type is shown in Field type form by\r\ndefault\r\n\r\n\r\nTested in ESS and Serverless locally \r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"799800d26d2edfaef5e424813d9f597774a95c25"}}]}] BACKPORT--> Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com>	2024-07-10 06:21:32 +10:00
Kibana Machine	3577a99946	[8.15] [ResponseOps][Cases] Make custom fields and the cases webhook GA (#187880) (#187902) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ResponseOps][Cases] Make custom fields and the cases webhook GA (#187880)](https://github.com/elastic/kibana/pull/187880) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T17:59:01Z","message":"[ResponseOps][Cases] Make custom fields and the cases webhook GA (#187880)\n\n## Summary\r\n\r\nThis PR makes the custom fields and the cases web hook GA.\r\n\r\n<img width=\"1213\" alt=\"Screenshot 2024-07-09 at 6 51 24 PM\"\r\nsrc=\"a47789a0-e238-4fcb-88cb-edd2531c4046\">\r\n\r\n<img width=\"1275\" alt=\"Screenshot 2024-07-09 at 6 51 15 PM\"\r\nsrc=\"a0bb5904-2ed5-4d65-9e08-74ce193559c4\">\r\n\r\n## Release notes\r\nCases custom fields and the cases webhook are now GA.\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"4f8d54a75427537d3a4bcca11e160c97fcd895e1","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:ResponseOps","Feature:Cases","v8.15.0","v8.16.0"],"title":"[ResponseOps][Cases] Make custom fields and the cases webhook GA","number":187880,"url":"https://github.com/elastic/kibana/pull/187880","mergeCommit":{"message":"[ResponseOps][Cases] Make custom fields and the cases webhook GA (#187880)\n\n## Summary\r\n\r\nThis PR makes the custom fields and the cases web hook GA.\r\n\r\n<img width=\"1213\" alt=\"Screenshot 2024-07-09 at 6 51 24 PM\"\r\nsrc=\"a47789a0-e238-4fcb-88cb-edd2531c4046\">\r\n\r\n<img width=\"1275\" alt=\"Screenshot 2024-07-09 at 6 51 15 PM\"\r\nsrc=\"a0bb5904-2ed5-4d65-9e08-74ce193559c4\">\r\n\r\n## Release notes\r\nCases custom fields and the cases webhook are now GA.\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"4f8d54a75427537d3a4bcca11e160c97fcd895e1"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187880","number":187880,"mergeCommit":{"message":"[ResponseOps][Cases] Make custom fields and the cases webhook GA (#187880)\n\n## Summary\r\n\r\nThis PR makes the custom fields and the cases web hook GA.\r\n\r\n<img width=\"1213\" alt=\"Screenshot 2024-07-09 at 6 51 24 PM\"\r\nsrc=\"a47789a0-e238-4fcb-88cb-edd2531c4046\">\r\n\r\n<img width=\"1275\" alt=\"Screenshot 2024-07-09 at 6 51 15 PM\"\r\nsrc=\"a0bb5904-2ed5-4d65-9e08-74ce193559c4\">\r\n\r\n## Release notes\r\nCases custom fields and the cases webhook are now GA.\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"4f8d54a75427537d3a4bcca11e160c97fcd895e1"}}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>	2024-07-10 05:52:28 +10:00
Kibana Machine	c5a6d94625	[8.15] [ML] Functional tests: unskip anomaly detection results forecast flaky test (#187795) (#187894) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] Functional tests: unskip anomaly detection results forecast flaky test (#187795)](https://github.com/elastic/kibana/pull/187795) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T17:00:36Z","message":"[ML] Functional tests: unskip anomaly detection results forecast flaky test (#187795)\n\n## Summary\r\n\r\nUnskip skipped test due to flakiness:\r\nhttps://github.com/elastic/kibana/issues/164381\r\nInitial investigation appears to indicate something in the testing\r\nenvironment - likely the chrome version. That has been updated since so\r\nletting the CI run to confirm.\r\n\r\nFlaky test runner build:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6494\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"8f95f955e6263ded0abcc62cf3ca53bb018cbe4a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","Feature:Anomaly Detection","release_note:skip","Feature:Functional Testing","v8.15.0","v7.17.23","v8.16.0"],"title":"[ML] Functional tests: unskip anomaly detection results forecast flaky test ","number":187795,"url":"https://github.com/elastic/kibana/pull/187795","mergeCommit":{"message":"[ML] Functional tests: unskip anomaly detection results forecast flaky test (#187795)\n\n## Summary\r\n\r\nUnskip skipped test due to flakiness:\r\nhttps://github.com/elastic/kibana/issues/164381\r\nInitial investigation appears to indicate something in the testing\r\nenvironment - likely the chrome version. That has been updated since so\r\nletting the CI run to confirm.\r\n\r\nFlaky test runner build:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6494\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"8f95f955e6263ded0abcc62cf3ca53bb018cbe4a"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","7.17"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.23","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187795","number":187795,"mergeCommit":{"message":"[ML] Functional tests: unskip anomaly detection results forecast flaky test (#187795)\n\n## Summary\r\n\r\nUnskip skipped test due to flakiness:\r\nhttps://github.com/elastic/kibana/issues/164381\r\nInitial investigation appears to indicate something in the testing\r\nenvironment - likely the chrome version. That has been updated since so\r\nletting the CI run to confirm.\r\n\r\nFlaky test runner build:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6494\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"8f95f955e6263ded0abcc62cf3ca53bb018cbe4a"}}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co>	2024-07-10 04:44:25 +10:00
Saikat Sarkar	ee7fd95214	[8.15] [Inference Endpoints View] Deletion, search and filtering of inference endpoints (#186206) (#187887) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Inference Endpoints View] Deletion, search and filtering of inference endpoints (#186206)](https://github.com/elastic/kibana/pull/186206) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saikat Sarkar","email":"132922331+saikatsarkar056@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-09T14:42:52Z","message":"[Inference Endpoints View] Deletion, search and filtering of inference endpoints (#186206)\n\nThis PR consists of the following changes:\r\n- An option to delete an existing inference endpoint\r\n- Filtering the endpoints based on 'provider' and 'type'\r\n- Search option\r\n- Display the trained models deployment status\r\n- Display additional 3rd party providers (Mistral, Azure OpenAI, Azure\r\nAI Studio)\r\n- Add licensing for gating enterprise licensed users\r\n\r\n### Stack Management\r\n\r\n\r\n\r\n\r\n### Serverless\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>","sha":"ff651f20d247f2ccf64b712131edd346f3ccf1a8","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"number":186206,"url":"https://github.com/elastic/kibana/pull/186206","mergeCommit":{"message":"[Inference Endpoints View] Deletion, search and filtering of inference endpoints (#186206)\n\nThis PR consists of the following changes:\r\n- An option to delete an existing inference endpoint\r\n- Filtering the endpoints based on 'provider' and 'type'\r\n- Search option\r\n- Display the trained models deployment status\r\n- Display additional 3rd party providers (Mistral, Azure OpenAI, Azure\r\nAI Studio)\r\n- Add licensing for gating enterprise licensed users\r\n\r\n### Stack Management\r\n\r\n\r\n\r\n\r\n### Serverless\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>","sha":"ff651f20d247f2ccf64b712131edd346f3ccf1a8"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186206","number":186206,"mergeCommit":{"message":"[Inference Endpoints View] Deletion, search and filtering of inference endpoints (#186206)\n\nThis PR consists of the following changes:\r\n- An option to delete an existing inference endpoint\r\n- Filtering the endpoints based on 'provider' and 'type'\r\n- Search option\r\n- Display the trained models deployment status\r\n- Display additional 3rd party providers (Mistral, Azure OpenAI, Azure\r\nAI Studio)\r\n- Add licensing for gating enterprise licensed users\r\n\r\n### Stack Management\r\n\r\n\r\n\r\n\r\n### Serverless\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>","sha":"ff651f20d247f2ccf64b712131edd346f3ccf1a8"}}]}] BACKPORT-->	2024-07-10 04:10:54 +10:00
Tiago Costa	2193e948b6	skip flaky suite (#187456)	2024-07-09 16:32:24 +01:00
Kibana Machine	f6c1ad83b4	[8.15] [Fleet] Always use a SNAPSHOT version when running elastic-agent docker image (#187777) (#187852) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Fleet] Always use a SNAPSHOT version when running elastic-agent docker image (#187777)](https://github.com/elastic/kibana/pull/187777) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T11:27:20Z","message":"[Fleet] Always use a SNAPSHOT version when running elastic-agent docker image (#187777)","sha":"834f8fdb375d0c7eef0de974ae5c0f0c0f19b60a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","Team:Elastic-Agent-Control-Plane","backport:prev-minor","v8.16.0"],"title":"[Fleet] Always use a SNAPSHOT version when running elastic-agent docker image","number":187777,"url":"https://github.com/elastic/kibana/pull/187777","mergeCommit":{"message":"[Fleet] Always use a SNAPSHOT version when running elastic-agent docker image (#187777)","sha":"834f8fdb375d0c7eef0de974ae5c0f0c0f19b60a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187777","number":187777,"mergeCommit":{"message":"[Fleet] Always use a SNAPSHOT version when running elastic-agent docker image (#187777)","sha":"834f8fdb375d0c7eef0de974ae5c0f0c0f19b60a"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>	2024-07-09 10:25:38 -04:00
Kibana Machine	ca4b2e70d9	[8.15] [ML] Hide ML embeddables from the Add panel flyout when ML feature isn't available (#187639) (#187857) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] Hide ML embeddables from the &quot;Add panel&quot; flyout when ML feature isn&#x27;t available (#187639)](https://github.com/elastic/kibana/pull/187639) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T12:21:20Z","message":"[ML] Hide ML embeddables from the \"Add panel\" flyout when ML feature isn't available (#187639)\n\n## Summary\r\n\r\nFixes #187007 \r\n\r\nHides ML embeddables from the \"Add panel\" flyout when\r\n1. ML feature isn't available for the user role \r\n2. ML is hidden in a current space \r\n\r\n\r\n### How to test \r\n1. Create a custom role with disabled ML privilege and assign it to a\r\nuser\r\n\r\n\r\n\r\n2. Remove ML feature visibility in a current space \r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7997d6fe33cfea1d5e0897c8b95156fe3830b30a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","Feature:Embeddables","v8.15.0","v8.16.0"],"title":"[ML] Hide ML embeddables from the \"Add panel\" flyout when ML feature isn't available","number":187639,"url":"https://github.com/elastic/kibana/pull/187639","mergeCommit":{"message":"[ML] Hide ML embeddables from the \"Add panel\" flyout when ML feature isn't available (#187639)\n\n## Summary\r\n\r\nFixes #187007 \r\n\r\nHides ML embeddables from the \"Add panel\" flyout when\r\n1. ML feature isn't available for the user role \r\n2. ML is hidden in a current space \r\n\r\n\r\n### How to test \r\n1. Create a custom role with disabled ML privilege and assign it to a\r\nuser\r\n\r\n\r\n\r\n2. Remove ML feature visibility in a current space \r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7997d6fe33cfea1d5e0897c8b95156fe3830b30a"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187639","number":187639,"mergeCommit":{"message":"[ML] Hide ML embeddables from the \"Add panel\" flyout when ML feature isn't available (#187639)\n\n## Summary\r\n\r\nFixes #187007 \r\n\r\nHides ML embeddables from the \"Add panel\" flyout when\r\n1. ML feature isn't available for the user role \r\n2. ML is hidden in a current space \r\n\r\n\r\n### How to test \r\n1. Create a custom role with disabled ML privilege and assign it to a\r\nuser\r\n\r\n\r\n\r\n2. Remove ML feature visibility in a current space \r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"7997d6fe33cfea1d5e0897c8b95156fe3830b30a"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>	2024-07-09 14:53:21 +01:00
Kibana Machine	d52cf928b2	[8.15] [ML] Transform: Fix transform stats API call in the transform health alerting rule (#187586) (#187617) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] Transform: Fix transform stats API call in the transform health alerting rule (#187586)](https://github.com/elastic/kibana/pull/187586) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T07:08:08Z","message":"[ML] Transform: Fix transform stats API call in the transform health alerting rule (#187586)\n\n## Summary\r\n\r\nIn rare cases when the list of continuous transform exceeds the allowed\r\nURL length, we fetch stats for all transforms.\r\n\r\nThe elasticsearch client has `transform-id` param as optional, but we\r\nactually have to pass `_all` or `*`. This PR sets the `transform_id`\r\nparam explicitly in this case.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1a8bacc5473534fe8ec254667d561b0bd3c739d5","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Transforms","Feature:Alerting/RuleTypes","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] Transform: Fix transform stats API call in the transform health alerting rule ","number":187586,"url":"https://github.com/elastic/kibana/pull/187586","mergeCommit":{"message":"[ML] Transform: Fix transform stats API call in the transform health alerting rule (#187586)\n\n## Summary\r\n\r\nIn rare cases when the list of continuous transform exceeds the allowed\r\nURL length, we fetch stats for all transforms.\r\n\r\nThe elasticsearch client has `transform-id` param as optional, but we\r\nactually have to pass `_all` or `*`. This PR sets the `transform_id`\r\nparam explicitly in this case.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1a8bacc5473534fe8ec254667d561b0bd3c739d5"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187586","number":187586,"mergeCommit":{"message":"[ML] Transform: Fix transform stats API call in the transform health alerting rule (#187586)\n\n## Summary\r\n\r\nIn rare cases when the list of continuous transform exceeds the allowed\r\nURL length, we fetch stats for all transforms.\r\n\r\nThe elasticsearch client has `transform-id` param as optional, but we\r\nactually have to pass `_all` or `*`. This PR sets the `transform_id`\r\nparam explicitly in this case.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1a8bacc5473534fe8ec254667d561b0bd3c739d5"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-09 22:58:19 +10:00
Kibana Machine	bcdf5e98e3	[8.15] [Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout (#187496) (#187810) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout (#187496)](https://github.com/elastic/kibana/pull/187496) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T00:07:57Z","message":"[Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout (#187496)\n\n## Summary\r\n\r\nFixing bug where ad hoc run task was not getting deleted if running the\r\nlast schedule entry and the run times out.\r\n\r\n## To Verify\r\n1. Create a detection rule\r\n2. Add a delay in the ad hoc task runner\r\n```\r\n--- a/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n+++ b/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n@@ -530,6 +530,7 @@ export class AdHocTaskRunner {\r\n } catch (err) {\r\n runMetrics = asErr(err);\r\n }\r\n+ await new Promise((resolve) => setTimeout(resolve, 3100000));\r\n await this.processAdHocRunResults(runMetrics);\r\n```\r\n3. Schedule a backfill for the rule with only one schedule entry\r\n\r\n```\r\nPOST https://localhost:5601/internal/alerting/rules/backfill/_schedule\r\n[\r\n {\r\n \"rule_id\": <ruleId>,\r\n \"start\": \"2024-07-03T13:05:00.000Z\"\r\n }\r\n]\r\n```\r\n\r\n4. Wait for the run to get cancelled then verify that the task was\r\ndeleted.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c2be810de37479d43661e722e7d7454dacc35c79","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","v8.15.0","v8.16.0"],"title":"[Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout","number":187496,"url":"https://github.com/elastic/kibana/pull/187496","mergeCommit":{"message":"[Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout (#187496)\n\n## Summary\r\n\r\nFixing bug where ad hoc run task was not getting deleted if running the\r\nlast schedule entry and the run times out.\r\n\r\n## To Verify\r\n1. Create a detection rule\r\n2. Add a delay in the ad hoc task runner\r\n```\r\n--- a/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n+++ b/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n@@ -530,6 +530,7 @@ export class AdHocTaskRunner {\r\n } catch (err) {\r\n runMetrics = asErr(err);\r\n }\r\n+ await new Promise((resolve) => setTimeout(resolve, 3100000));\r\n await this.processAdHocRunResults(runMetrics);\r\n```\r\n3. Schedule a backfill for the rule with only one schedule entry\r\n\r\n```\r\nPOST https://localhost:5601/internal/alerting/rules/backfill/_schedule\r\n[\r\n {\r\n \"rule_id\": <ruleId>,\r\n \"start\": \"2024-07-03T13:05:00.000Z\"\r\n }\r\n]\r\n```\r\n\r\n4. Wait for the run to get cancelled then verify that the task was\r\ndeleted.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c2be810de37479d43661e722e7d7454dacc35c79"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187496","number":187496,"mergeCommit":{"message":"[Response Ops][Alerting] Deleting ad hoc run task if the last schedule entry ends in a timeout (#187496)\n\n## Summary\r\n\r\nFixing bug where ad hoc run task was not getting deleted if running the\r\nlast schedule entry and the run times out.\r\n\r\n## To Verify\r\n1. Create a detection rule\r\n2. Add a delay in the ad hoc task runner\r\n```\r\n--- a/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n+++ b/x-pack/plugins/alerting/server/task_runner/ad_hoc_task_runner.ts\r\n@@ -530,6 +530,7 @@ export class AdHocTaskRunner {\r\n } catch (err) {\r\n runMetrics = asErr(err);\r\n }\r\n+ await new Promise((resolve) => setTimeout(resolve, 3100000));\r\n await this.processAdHocRunResults(runMetrics);\r\n```\r\n3. Schedule a backfill for the rule with only one schedule entry\r\n\r\n```\r\nPOST https://localhost:5601/internal/alerting/rules/backfill/_schedule\r\n[\r\n {\r\n \"rule_id\": <ruleId>,\r\n \"start\": \"2024-07-03T13:05:00.000Z\"\r\n }\r\n]\r\n```\r\n\r\n4. Wait for the run to get cancelled then verify that the task was\r\ndeleted.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c2be810de37479d43661e722e7d7454dacc35c79"}}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co>	2024-07-09 08:20:31 -04:00
Sergi Massaneda	056d64a179	[8.15] [Integration-Assistant] Fix categorization ECS types and categories (#187516) (#187838) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Integration-Assistant] Fix categorization ECS types and categories (#187516)](https://github.com/elastic/kibana/pull/187516) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kylie Meli","email":"kylie.geller@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T05:47:54Z","message":"[Integration-Assistant] Fix categorization ECS types and categories (#187516)\n\n## Summary\r\n\r\nThis PR corrects the ECS type and categories constants used in the\r\ncategorization chain.\r\n\r\nI double checked everything against the ECS docs for\r\n[categories](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-category.html)\r\nand\r\n[types](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-type.html).","sha":"27d280893cf4a1f27af8dc89fdb799918850d808","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","v8.15.0","v8.16.0"],"number":187516,"url":"https://github.com/elastic/kibana/pull/187516","mergeCommit":{"message":"[Integration-Assistant] Fix categorization ECS types and categories (#187516)\n\n## Summary\r\n\r\nThis PR corrects the ECS type and categories constants used in the\r\ncategorization chain.\r\n\r\nI double checked everything against the ECS docs for\r\n[categories](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-category.html)\r\nand\r\n[types](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-type.html).","sha":"27d280893cf4a1f27af8dc89fdb799918850d808"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","labelRegex":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187516","number":187516,"mergeCommit":{"message":"[Integration-Assistant] Fix categorization ECS types and categories (#187516)\n\n## Summary\r\n\r\nThis PR corrects the ECS type and categories constants used in the\r\ncategorization chain.\r\n\r\nI double checked everything against the ECS docs for\r\n[categories](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-category.html)\r\nand\r\n[types](https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-type.html).","sha":"27d280893cf4a1f27af8dc89fdb799918850d808"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kylie Meli <kylie.geller@elastic.co>	2024-07-09 12:46:41 +02:00
Kibana Machine	bcee10739e	[8.15] [OTel Onboarding] Adjust linux snippet and warning (#187691) (#187756) ... # Backport This will backport the following commits from `main` to `8.15`: - [[OTel Onboarding] Adjust linux snippet and warning (#187691)](https://github.com/elastic/kibana/pull/187691) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T14:31:42Z","message":"[OTel Onboarding] Adjust linux snippet and warning (#187691)\n\nAddress\r\nhttps://github.com/elastic/observability-dev/issues/3217#issuecomment-2210741356\r\n\r\n<img width=\"1150\" alt=\"Screenshot 2024-07-05 at 17 30 47\"\r\nsrc=\"228b0531-ac16-46d0-bbf1-5c3bb959121a\">","sha":"ae802a5776e8f64e43ef7c6d26024d7cd8117745","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","v8.15.0","v8.16.0"],"title":"[OTel Onboarding] Adjust linux snippet and warning","number":187691,"url":"https://github.com/elastic/kibana/pull/187691","mergeCommit":{"message":"[OTel Onboarding] Adjust linux snippet and warning (#187691)\n\nAddress\r\nhttps://github.com/elastic/observability-dev/issues/3217#issuecomment-2210741356\r\n\r\n<img width=\"1150\" alt=\"Screenshot 2024-07-05 at 17 30 47\"\r\nsrc=\"228b0531-ac16-46d0-bbf1-5c3bb959121a\">","sha":"ae802a5776e8f64e43ef7c6d26024d7cd8117745"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187691","number":187691,"mergeCommit":{"message":"[OTel Onboarding] Adjust linux snippet and warning (#187691)\n\nAddress\r\nhttps://github.com/elastic/observability-dev/issues/3217#issuecomment-2210741356\r\n\r\n<img width=\"1150\" alt=\"Screenshot 2024-07-05 at 17 30 47\"\r\nsrc=\"228b0531-ac16-46d0-bbf1-5c3bb959121a\">","sha":"ae802a5776e8f64e43ef7c6d26024d7cd8117745"}}]}] BACKPORT--> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co>	2024-07-09 20:46:05 +10:00
Kibana Machine	d765ed3550	[8.15] [ML] Removes info callout mentioning ML nodes for serverless environment (#187583) (#187620) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)](https://github.com/elastic/kibana/pull/187583) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T07:19:51Z","message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] Removes info callout mentioning ML nodes for serverless environment ","number":187583,"url":"https://github.com/elastic/kibana/pull/187583","mergeCommit":{"message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187583","number":187583,"mergeCommit":{"message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-09 20:08:29 +10:00
Kibana Machine	28ee74422a	[8.15] [Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466) (#187789) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)](https://github.com/elastic/kibana/pull/187466) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:14:57Z","message":"[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)\n\n## Summary\r\n\r\nEnables tracing Langchain invocations in the integrations assistant\r\nusing the Langsmith settings stored by the Security AI Settings.\r\nThe evaluation settings tab is still under an experimental flag, to see\r\nit:\r\n\r\n```\r\nxpack.securitySolution.enableExperimental: ['assistantModelEvaluation']\r\n```\r\n\r\n### Screenshots\r\n\r\n<img width=\"1317\" alt=\"Settings\"\r\nsrc=\"6aed1ef6-3750-4259-9fe2-b8bf1aed5504\">\r\n\r\nAfter one execution of the integration assistant:\r\n\r\n<img width=\"1240\" alt=\"langsmith\"\r\nsrc=\"dd3dd99c-7c83-4a35-95b2-789e7a341031\">\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"92099b277dc5b1448d14994d280674611ca9e261","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant","number":187466,"url":"https://github.com/elastic/kibana/pull/187466","mergeCommit":{"message":"[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)\n\n## Summary\r\n\r\nEnables tracing Langchain invocations in the integrations assistant\r\nusing the Langsmith settings stored by the Security AI Settings.\r\nThe evaluation settings tab is still under an experimental flag, to see\r\nit:\r\n\r\n```\r\nxpack.securitySolution.enableExperimental: ['assistantModelEvaluation']\r\n```\r\n\r\n### Screenshots\r\n\r\n<img width=\"1317\" alt=\"Settings\"\r\nsrc=\"6aed1ef6-3750-4259-9fe2-b8bf1aed5504\">\r\n\r\nAfter one execution of the integration assistant:\r\n\r\n<img width=\"1240\" alt=\"langsmith\"\r\nsrc=\"dd3dd99c-7c83-4a35-95b2-789e7a341031\">\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"92099b277dc5b1448d14994d280674611ca9e261"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187466","number":187466,"mergeCommit":{"message":"[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)\n\n## Summary\r\n\r\nEnables tracing Langchain invocations in the integrations assistant\r\nusing the Langsmith settings stored by the Security AI Settings.\r\nThe evaluation settings tab is still under an experimental flag, to see\r\nit:\r\n\r\n```\r\nxpack.securitySolution.enableExperimental: ['assistantModelEvaluation']\r\n```\r\n\r\n### Screenshots\r\n\r\n<img width=\"1317\" alt=\"Settings\"\r\nsrc=\"6aed1ef6-3750-4259-9fe2-b8bf1aed5504\">\r\n\r\nAfter one execution of the integration assistant:\r\n\r\n<img width=\"1240\" alt=\"langsmith\"\r\nsrc=\"dd3dd99c-7c83-4a35-95b2-789e7a341031\">\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"92099b277dc5b1448d14994d280674611ca9e261"}}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>	2024-07-09 11:13:57 +02:00
Kibana Machine	a6087390bc	[8.15] [AI Assistant] Add to dashboard (#179329) (#187827) ... # Backport This will backport the following commits from `main` to `8.15`: - [[AI Assistant] Add to dashboard (#179329)](https://github.com/elastic/kibana/pull/179329) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T07:31:54Z","message":"[AI Assistant] Add to dashboard (#179329)\n\nAdds a new functionality in the AI assistant when in dashboards. If the\r\nusers ask for a question which will generate a query then then can use\r\nprompts like:\r\n\r\n- `Create a visualization from this query and add this to a dashboard`\r\n- `Create a metric from this query and add this to a dashboard`\r\n- ....\r\n\r\n\r\n\r\n\r\n\r\n### How it works\r\n- It uses the existing functionality of the assistant to create an ES|QL\r\nquery (if the generated query is wrong is not part of this PR)\r\n- The LLM returns the query to the new `add_to_dashboard` function and\r\nwith the chart type (if the user has added the preference) and the\r\nconfiguration needed for the ConfigBuilder it creates a Lens embeddable\r\nand adds it to the dashboard.\r\n\r\n### How to test\r\n- Go to advanced settings, find the `Observability AI Assistant scope`\r\nsetting and change to Everywhere\r\n- Go to a dahsboard (existing or new)\r\n- Ask a question to the AI such as `I want the 95th percentile of ...\r\nfrom ... index` or `I want the median of butes from the\r\nkibana_sample_data_logs grouped by the top 5 destinations`\r\n- After the ES|QL query has been generated correctly ask AI to create a\r\nchart from this query and add this to the dashboard\r\n\r\n\r\n### important note\r\nAs this is the first real consumer of the build api for ES|QL I have\r\nfixed and various bugs I discovered in the api.\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4013f608c1872b75f4f5601889a478b985479859","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:Obs AI Assistant","Feature:ES|QL","ci:project-deploy-observability","apm:review","v8.15.0","v8.16.0"],"title":"[AI Assistant] Add to dashboard","number":179329,"url":"https://github.com/elastic/kibana/pull/179329","mergeCommit":{"message":"[AI Assistant] Add to dashboard (#179329)\n\nAdds a new functionality in the AI assistant when in dashboards. If the\r\nusers ask for a question which will generate a query then then can use\r\nprompts like:\r\n\r\n- `Create a visualization from this query and add this to a dashboard`\r\n- `Create a metric from this query and add this to a dashboard`\r\n- ....\r\n\r\n\r\n\r\n\r\n\r\n### How it works\r\n- It uses the existing functionality of the assistant to create an ES|QL\r\nquery (if the generated query is wrong is not part of this PR)\r\n- The LLM returns the query to the new `add_to_dashboard` function and\r\nwith the chart type (if the user has added the preference) and the\r\nconfiguration needed for the ConfigBuilder it creates a Lens embeddable\r\nand adds it to the dashboard.\r\n\r\n### How to test\r\n- Go to advanced settings, find the `Observability AI Assistant scope`\r\nsetting and change to Everywhere\r\n- Go to a dahsboard (existing or new)\r\n- Ask a question to the AI such as `I want the 95th percentile of ...\r\nfrom ... index` or `I want the median of butes from the\r\nkibana_sample_data_logs grouped by the top 5 destinations`\r\n- After the ES|QL query has been generated correctly ask AI to create a\r\nchart from this query and add this to the dashboard\r\n\r\n\r\n### important note\r\nAs this is the first real consumer of the build api for ES|QL I have\r\nfixed and various bugs I discovered in the api.\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4013f608c1872b75f4f5601889a478b985479859"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/179329","number":179329,"mergeCommit":{"message":"[AI Assistant] Add to dashboard (#179329)\n\nAdds a new functionality in the AI assistant when in dashboards. If the\r\nusers ask for a question which will generate a query then then can use\r\nprompts like:\r\n\r\n- `Create a visualization from this query and add this to a dashboard`\r\n- `Create a metric from this query and add this to a dashboard`\r\n- ....\r\n\r\n\r\n\r\n\r\n\r\n### How it works\r\n- It uses the existing functionality of the assistant to create an ES|QL\r\nquery (if the generated query is wrong is not part of this PR)\r\n- The LLM returns the query to the new `add_to_dashboard` function and\r\nwith the chart type (if the user has added the preference) and the\r\nconfiguration needed for the ConfigBuilder it creates a Lens embeddable\r\nand adds it to the dashboard.\r\n\r\n### How to test\r\n- Go to advanced settings, find the `Observability AI Assistant scope`\r\nsetting and change to Everywhere\r\n- Go to a dahsboard (existing or new)\r\n- Ask a question to the AI such as `I want the 95th percentile of ...\r\nfrom ... index` or `I want the median of butes from the\r\nkibana_sample_data_logs grouped by the top 5 destinations`\r\n- After the ES|QL query has been generated correctly ask AI to create a\r\nchart from this query and add this to the dashboard\r\n\r\n\r\n### important note\r\nAs this is the first real consumer of the build api for ES|QL I have\r\nfixed and various bugs I discovered in the api.\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4013f608c1872b75f4f5601889a478b985479859"}}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>	2024-07-09 10:49:07 +02:00
Kibana Machine	71c6761a06	[8.15] [ResponseOps][Cases] Edits case template text (#187610) (#187808) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ResponseOps][Cases] Edits case template text (#187610)](https://github.com/elastic/kibana/pull/187610) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T23:42:06Z","message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","ui-copy","v8.15.0","v8.16.0"],"title":"[ResponseOps][Cases] Edits case template text","number":187610,"url":"https://github.com/elastic/kibana/pull/187610","mergeCommit":{"message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187610","number":187610,"mergeCommit":{"message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co>	2024-07-09 09:22:59 +01:00
Kibana Machine	ab6ec61c68	skip failing test suite (#187818)	2024-07-09 09:33:55 +02:00
Kibana Machine	db7098b1d7	[8.15] [Observability Onboarding] Fix onboarding nav (#187498) (#187776) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Observability Onboarding] Fix onboarding nav (#187498)](https://github.com/elastic/kibana/pull/187498) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T16:47:19Z","message":"[Observability Onboarding] Fix onboarding nav (#187498)\n\n## Summary\r\n\r\nAddresses some issues with navigation in the Observability solution\r\nrelated to onboarding.\r\n\r\n### Overview page add data link\r\n\r\n\r\n\r\n\r\n### Overview get started link\r\n\r\nDoesn't render as an anchor because there's a telemetry call inside the\r\nhandler\r\n\r\n\r\n\r\n\r\n### Install Metricbeat link\r\n\r\nTakes user to overview page pre-filtered for `infra`.\r\n\r\n---------\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"62a2faab53a18b0f107e458963bceea897393878","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","ci:project-deploy-observability","Team:obs-ux-management","v8.15.0","Feature: Observability Onboarding","v8.16.0"],"title":"[Observability Onboarding] Fix onboarding nav","number":187498,"url":"https://github.com/elastic/kibana/pull/187498","mergeCommit":{"message":"[Observability Onboarding] Fix onboarding nav (#187498)\n\n## Summary\r\n\r\nAddresses some issues with navigation in the Observability solution\r\nrelated to onboarding.\r\n\r\n### Overview page add data link\r\n\r\n\r\n\r\n\r\n### Overview get started link\r\n\r\nDoesn't render as an anchor because there's a telemetry call inside the\r\nhandler\r\n\r\n\r\n\r\n\r\n### Install Metricbeat link\r\n\r\nTakes user to overview page pre-filtered for `infra`.\r\n\r\n---------\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"62a2faab53a18b0f107e458963bceea897393878"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187498","number":187498,"mergeCommit":{"message":"[Observability Onboarding] Fix onboarding nav (#187498)\n\n## Summary\r\n\r\nAddresses some issues with navigation in the Observability solution\r\nrelated to onboarding.\r\n\r\n### Overview page add data link\r\n\r\n\r\n\r\n\r\n### Overview get started link\r\n\r\nDoesn't render as an anchor because there's a telemetry call inside the\r\nhandler\r\n\r\n\r\n\r\n\r\n### Install Metricbeat link\r\n\r\nTakes user to overview page pre-filtered for `infra`.\r\n\r\n---------\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"62a2faab53a18b0f107e458963bceea897393878"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co>	2024-07-09 09:03:16 +02:00
Kibana Machine	b4cff4dca9	[8.15] Make it clear log stream panels shouldn&#x27;t be used (#187548) (#187760) ... # Backport This will backport the following commits from `main` to `8.15`: - [Make it clear log stream panels shouldn&#x27;t be used (#187548)](https://github.com/elastic/kibana/pull/187548) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T15:11:27Z","message":"Make it clear log stream panels shouldn't be used (#187548)\n\nAs discussed, I looked into making it clearer how to handle the log\r\nstream embeddable panel on dashboards.\r\n\r\nIt's not possible to show an info icon or a badge without bigger\r\nchanges, but there is already a tooltip which can be used for the same\r\npurpose:\r\n\r\n<img width=\"321\" alt=\"Screenshot 2024-07-04 at 11 30 27\"\r\nsrc=\"60de35b5-559f-4670-b2b9-e074a3cb73c8\">\r\n\r\n<img width=\"422\" alt=\"Screenshot 2024-07-04 at 11 31 31\"\r\nsrc=\"3ba2f87c-dc33-4a6b-bf81-2e561e6b7cec\">\r\n\r\nI added the \"deprecated\" to the title instead.\r\n\r\nThere is code to show a \"deprecated\" badge, but it only works for\r\nvisualization types, not for actions (which is how log stream is\r\nintegrated here). Actions currently don't have a notion of deprecation.\r\nIt would be possible to add that, but it doesn't seem worth it to\r\nslightly change how the \"deprecated\" text is rendered.","sha":"bac808a690d58237b3302c706701a81215d963cf","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","apm:review","v8.16.0"],"title":"Make it clear log stream panels shouldn't be used","number":187548,"url":"https://github.com/elastic/kibana/pull/187548","mergeCommit":{"message":"Make it clear log stream panels shouldn't be used (#187548)\n\nAs discussed, I looked into making it clearer how to handle the log\r\nstream embeddable panel on dashboards.\r\n\r\nIt's not possible to show an info icon or a badge without bigger\r\nchanges, but there is already a tooltip which can be used for the same\r\npurpose:\r\n\r\n<img width=\"321\" alt=\"Screenshot 2024-07-04 at 11 30 27\"\r\nsrc=\"60de35b5-559f-4670-b2b9-e074a3cb73c8\">\r\n\r\n<img width=\"422\" alt=\"Screenshot 2024-07-04 at 11 31 31\"\r\nsrc=\"3ba2f87c-dc33-4a6b-bf81-2e561e6b7cec\">\r\n\r\nI added the \"deprecated\" to the title instead.\r\n\r\nThere is code to show a \"deprecated\" badge, but it only works for\r\nvisualization types, not for actions (which is how log stream is\r\nintegrated here). Actions currently don't have a notion of deprecation.\r\nIt would be possible to add that, but it doesn't seem worth it to\r\nslightly change how the \"deprecated\" text is rendered.","sha":"bac808a690d58237b3302c706701a81215d963cf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187548","number":187548,"mergeCommit":{"message":"Make it clear log stream panels shouldn't be used (#187548)\n\nAs discussed, I looked into making it clearer how to handle the log\r\nstream embeddable panel on dashboards.\r\n\r\nIt's not possible to show an info icon or a badge without bigger\r\nchanges, but there is already a tooltip which can be used for the same\r\npurpose:\r\n\r\n<img width=\"321\" alt=\"Screenshot 2024-07-04 at 11 30 27\"\r\nsrc=\"60de35b5-559f-4670-b2b9-e074a3cb73c8\">\r\n\r\n<img width=\"422\" alt=\"Screenshot 2024-07-04 at 11 31 31\"\r\nsrc=\"3ba2f87c-dc33-4a6b-bf81-2e561e6b7cec\">\r\n\r\nI added the \"deprecated\" to the title instead.\r\n\r\nThere is code to show a \"deprecated\" badge, but it only works for\r\nvisualization types, not for actions (which is how log stream is\r\nintegrated here). Actions currently don't have a notion of deprecation.\r\nIt would be possible to add that, but it doesn't seem worth it to\r\nslightly change how the \"deprecated\" text is rendered.","sha":"bac808a690d58237b3302c706701a81215d963cf"}}]}] BACKPORT--> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co>	2024-07-09 09:01:27 +02:00
Tiago Costa	9d6491dbed	skip flaky suite (#187667)	2024-07-09 04:40:44 +01:00
Kibana Machine	b3138be858	[8.15] [OAS][Cases] Add case templates to case configuration APIs (#187613) (#187788) ... <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:10:38Z","message":"[OAS][Cases] Add case templates to case configuration APIs (#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","v8.15.0","v8.16.0"],"title":"[OAS][Cases] Add case templates to case configuration APIs","number":187613,"url":"https://github.com/elastic/kibana/pull/187613","mergeCommit":{"message":"[OAS][Cases] Add case templates to case configuration APIs (#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187613","number":187613,"mergeCommit":{"message":"[OAS][Cases] Add case templates to case configuration APIs (#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6"}}]}] BACKPORT-->	2024-07-09 09:39:16 +10:00
Kibana Machine	17bf446e73	[8.15] [Security solution] Add model parameter to token telemetry (#187783) (#187793) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security solution] Add model parameter to token telemetry (#187783)](https://github.com/elastic/kibana/pull/187783) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:53:25Z","message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security solution] Add model parameter to token telemetry","number":187783,"url":"https://github.com/elastic/kibana/pull/187783","mergeCommit":{"message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187783","number":187783,"mergeCommit":{"message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-08 17:54:15 -04:00
Kibana Machine	d018faaed5	[8.15] [Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942) (#187799) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942)](https://github.com/elastic/kibana/pull/186942) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Candace Park","email":"56409205+parkiino@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-08T19:50:54Z","message":"[Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942)\n\n## Summary\r\n\r\n- [x] Shows a banner with the 2024 AVC results blog link in 2 places:\r\nthe Security homepage and the Elastic Defend integration page info\r\n- [x] Banner will not show again once dismissed\r\n- [x] Unit Tests \r\n\r\nTODO in another pr: have code to remove the avc banner code at the end\r\nof the year\r\n\r\n## Screenshots\r\n<img width=\"1724\" alt=\"image\"\r\nsrc=\"9ac2ca14-525b-44bc-b357-e87f10856f33\">\r\n\r\n<img width=\"1383\" alt=\"image\"\r\nsrc=\"24ef70fe-dfa7-4fc1-bcba-8405aaf4f9ce\">\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Paul Tavares <paul.tavares@elastic.co>","sha":"fe131d47170f463887ce2230105042e8a7a755a2","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","Team:Defend Workflows","auto-backport","v8.15.0"],"number":186942,"url":"https://github.com/elastic/kibana/pull/186942","mergeCommit":{"message":"[Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942)\n\n## Summary\r\n\r\n- [x] Shows a banner with the 2024 AVC results blog link in 2 places:\r\nthe Security homepage and the Elastic Defend integration page info\r\n- [x] Banner will not show again once dismissed\r\n- [x] Unit Tests \r\n\r\nTODO in another pr: have code to remove the avc banner code at the end\r\nof the year\r\n\r\n## Screenshots\r\n<img width=\"1724\" alt=\"image\"\r\nsrc=\"9ac2ca14-525b-44bc-b357-e87f10856f33\">\r\n\r\n<img width=\"1383\" alt=\"image\"\r\nsrc=\"24ef70fe-dfa7-4fc1-bcba-8405aaf4f9ce\">\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Paul Tavares <paul.tavares@elastic.co>","sha":"fe131d47170f463887ce2230105042e8a7a755a2"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Candace Park <56409205+parkiino@users.noreply.github.com>	2024-07-09 07:17:43 +10:00
Kibana Machine	d11287dc97	[8.15] [Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559) (#187779) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)](https://github.com/elastic/kibana/pull/187559) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe McElroy","email":"joseph.mcelroy@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T17:18:12Z","message":"[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)\n\n## Summary\r\n\r\nWork largely based off the work @stephmilovic really nicely put together\r\nin this [draft PR](https://github.com/elastic/kibana/pull/186934)\r\n- Introduce Google Gemini Model support\r\n- Updated bedrock to use the ActionsSimpleChatModel \r\n- Updated the tests\r\n- Made the rewrite question chain more robust\r\n - the prompt is now uses the model specific tags\r\n- the system instruction has been updated to be less wordy, better for\r\nBM25 retrieval\r\n \r\n\r\n4558bc5d-e0c1-4ff6-b68c-800441f7835e\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"0be5528f21fd0442076d3f331c15cc3f34098d17","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"title":"[Search] [Playground] Gemini search playground + Robustness for Question Rewriting","number":187559,"url":"https://github.com/elastic/kibana/pull/187559","mergeCommit":{"message":"[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)\n\n## Summary\r\n\r\nWork largely based off the work @stephmilovic really nicely put together\r\nin this [draft PR](https://github.com/elastic/kibana/pull/186934)\r\n- Introduce Google Gemini Model support\r\n- Updated bedrock to use the ActionsSimpleChatModel \r\n- Updated the tests\r\n- Made the rewrite question chain more robust\r\n - the prompt is now uses the model specific tags\r\n- the system instruction has been updated to be less wordy, better for\r\nBM25 retrieval\r\n \r\n\r\n4558bc5d-e0c1-4ff6-b68c-800441f7835e\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"0be5528f21fd0442076d3f331c15cc3f34098d17"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187559","number":187559,"mergeCommit":{"message":"[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)\n\n## Summary\r\n\r\nWork largely based off the work @stephmilovic really nicely put together\r\nin this [draft PR](https://github.com/elastic/kibana/pull/186934)\r\n- Introduce Google Gemini Model support\r\n- Updated bedrock to use the ActionsSimpleChatModel \r\n- Updated the tests\r\n- Made the rewrite question chain more robust\r\n - the prompt is now uses the model specific tags\r\n- the system instruction has been updated to be less wordy, better for\r\nBM25 retrieval\r\n \r\n\r\n4558bc5d-e0c1-4ff6-b68c-800441f7835e\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"0be5528f21fd0442076d3f331c15cc3f34098d17"}}]}] BACKPORT--> Co-authored-by: Joe McElroy <joseph.mcelroy@elastic.co>	2024-07-09 04:50:36 +10:00
Kibana Machine	12cbac97e5	[8.15] [Fleet] Fix privileges to delete request diagnostics (#187678) (#187757) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Fleet] Fix privileges to delete request diagnostics (#187678)](https://github.com/elastic/kibana/pull/187678) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T14:33:18Z","message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","backport:prev-minor","v8.16.0"],"title":"[Fleet] Fix privileges to delete request diagnostics","number":187678,"url":"https://github.com/elastic/kibana/pull/187678","mergeCommit":{"message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187678","number":187678,"mergeCommit":{"message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-08 14:24:22 -04:00
Kibana Machine	046bccc2e8	[8.15] [Logs UI] Fix fly-out link to the legacy Uptime app (#186328) (#187761) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)](https://github.com/elastic/kibana/pull/186328) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-04T16:28:25Z","message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Logs UI","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Team:obs-ux-management","apm:review","v8.15.0","v8.16.0"],"title":"[Logs UI] Fix fly-out link to the legacy Uptime app","number":186328,"url":"https://github.com/elastic/kibana/pull/186328","mergeCommit":{"message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186328","number":186328,"mergeCommit":{"message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com>	2024-07-08 19:17:52 +02:00
Kibana Machine	828c2cde74	[8.15] [Discover] [ES|QL] Disables sorting for Document view (#187553) (#187731) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Discover] [ES|QL] Disables sorting for Document view (#187553)](https://github.com/elastic/kibana/pull/187553) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T09:14:59Z","message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-minor","Feature:ES|QL","v8.15.0","v8.16.0"],"title":"[Discover] [ES|QL] Disables sorting for Document view","number":187553,"url":"https://github.com/elastic/kibana/pull/187553","mergeCommit":{"message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187553","number":187553,"mergeCommit":{"message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346"}}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>	2024-07-08 12:46:01 +02:00
Gergő Ábrahám	445a9129d5	[EDR Workflows][8.15] Enable process descendant event filtering feature flag for 8.15 (#187627) ... <img width="664" alt="image" src="04472587-23b1-4c9e-8eec-83e10abe6dac">	2024-07-08 19:45:53 +10:00
Kibana Machine	2004c4c933	[8.15] [Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549) (#187661) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)](https://github.com/elastic/kibana/pull/187549) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T11:29:22Z","message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Detection Engine","v8.15.0","v8.16.0"],"title":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384)","number":187549,"url":"https://github.com/elastic/kibana/pull/187549","mergeCommit":{"message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187549","number":187549,"mergeCommit":{"message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>	2024-07-08 19:30:23 +10:00
Kibana Machine	7e0626c9de	[8.15] [Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643) (#187726) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)](https://github.com/elastic/kibana/pull/187643) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-08T07:08:14Z","message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team: SecuritySolution","v8.15.0","v8.16.0"],"title":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs","number":187643,"url":"https://github.com/elastic/kibana/pull/187643","mergeCommit":{"message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187643","number":187643,"mergeCommit":{"message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>	2024-07-08 18:45:39 +10:00
Kerry Gallagher	2490c13086	Revert "[Logs] Add Log Sources advanced setting and client / server access services" (#187477) ... ## Summary This is just a direct revert of https://github.com/elastic/kibana/pull/186468, there are no additional changes. This is to avoid an advanced setting that doesn't do anything in 8.15 (~waiting for the 8.15 branch to be cut~). Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-08 09:28:26 +01:00
Kibana Machine	7f969383ec	[8.15] [ML] Enable anomaly charts Accessibility tests (#187482) (#187675) ... # Backport This will backport the following commits from `main` to `8.15`: - [[ML] Enable anomaly charts Accessibility tests (#187482)](https://github.com/elastic/kibana/pull/187482) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T13:13:35Z","message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] Enable anomaly charts Accessibility tests ","number":187482,"url":"https://github.com/elastic/kibana/pull/187482","mergeCommit":{"message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187482","number":187482,"mergeCommit":{"message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2024-07-08 09:08:34 +02:00
Kibana Machine	6177dab713	[8.15] [Otel Onboarding] Adjust snippet and switch to proper release (#187480) (#187611) ... # Backport This will backport the following commits from `main` to `8.15`: - [[Otel Onboarding] Adjust snippet and switch to proper release (#187480)](https://github.com/elastic/kibana/pull/187480) - https://github.com/elastic/kibana/pull/187674 <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T23:20:44Z","message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding","v8.16.0"],"title":"[Otel Onboarding] Adjust snippet and switch to proper release","number":187480,"url":"https://github.com/elastic/kibana/pull/187480","mergeCommit":{"message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187480","number":187480,"mergeCommit":{"message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0"}}]}] BACKPORT--> --------- Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> Co-authored-by: Joe Reuter <email@johannes-reuter.de>	2024-07-05 14:35:49 -05:00