mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
34554 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
165abc4d3d
|
[8.16] [ResponseOps][Rules] Add loading state to rule params data views selector (#203654) (#204422)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Rules] Add loading state to rule params data views selector (#203654)](https://github.com/elastic/kibana/pull/203654) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-16T15:43:13Z","message":"[ResponseOps][Rules] Add loading state to rule params data views selector (#203654)\n\n## Summary\r\n\r\nIntroduces a loading state in the data views select popover and renders\r\na loading indicator when DVs are not available yet. This makes sure that\r\neven if the `savedObjectsClient.find` call of the data views service\r\ntakes a long time, we don't show an empty popover in the meantime.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5bbe0c68-3ceb-4d7f-91fd-357db4caa5c1\r\n\r\n## References\r\n\r\nFixes #198502 \r\n\r\n## Release note\r\n\r\nFix race condition in alerting rules data view selector","sha":"713d4bbcb2d9f5e707d06c1d298287edd3e694d0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","backport:all-open"],"title":"[ResponseOps][Rules] Add loading state to rule params data views selector","number":203654,"url":"https://github.com/elastic/kibana/pull/203654","mergeCommit":{"message":"[ResponseOps][Rules] Add loading state to rule params data views selector (#203654)\n\n## Summary\r\n\r\nIntroduces a loading state in the data views select popover and renders\r\na loading indicator when DVs are not available yet. This makes sure that\r\neven if the `savedObjectsClient.find` call of the data views service\r\ntakes a long time, we don't show an empty popover in the meantime.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5bbe0c68-3ceb-4d7f-91fd-357db4caa5c1\r\n\r\n## References\r\n\r\nFixes #198502 \r\n\r\n## Release note\r\n\r\nFix race condition in alerting rules data view selector","sha":"713d4bbcb2d9f5e707d06c1d298287edd3e694d0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203654","number":203654,"mergeCommit":{"message":"[ResponseOps][Rules] Add loading state to rule params data views selector (#203654)\n\n## Summary\r\n\r\nIntroduces a loading state in the data views select popover and renders\r\na loading indicator when DVs are not available yet. This makes sure that\r\neven if the `savedObjectsClient.find` call of the data views service\r\ntakes a long time, we don't show an empty popover in the meantime.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/5bbe0c68-3ceb-4d7f-91fd-357db4caa5c1\r\n\r\n## References\r\n\r\nFixes #198502 \r\n\r\n## Release note\r\n\r\nFix race condition in alerting rules data view selector","sha":"713d4bbcb2d9f5e707d06c1d298287edd3e694d0"}}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com> |
||
José Luis González
|
24a47e8a2b
|
[8.16] [Search] Web crawler name consistency (#202738) Manual backport (#204202)
Manual Backport This will backport the following commits from main to 8.16: Automatic backport were failing and using the CLI backport tool was addind many other unnecesary files. So then doing it manually. https://github.com/elastic/kibana/pull/202738 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
c6ebceb178
|
[8.16] [Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014) (#204306)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)](https://github.com/elastic/kibana/pull/204014) <!--- 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-12-14T08:54:54Z","message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v8.16.3","v8.17.1"],"title":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303)","number":204014,"url":"https://github.com/elastic/kibana/pull/204014","mergeCommit":{"message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204014","number":204014,"mergeCommit":{"message":"[Security Solution] AI Assistant: LLM Connector model chooser bug. New chat does not use connector's model (#199303) (#204014)\n\n## Summary\r\n\r\nThe PR fixes [this bug](https://github.com/elastic/kibana/issues/199303)\r\n\r\nThe issue happens with some of the locally setup LLMs (like\r\n[Ollama](https://github.com/ollama/ollama)) which requires the correct\r\n`model` to be passed as part of the [chat completions\r\nAPI](https://github.com/ollama/ollama/blob/main/docs/api.md#generate-a-chat-completion).\r\n\r\nWe had a bug in our code when on new conversation creation we would not\r\npass all the connectors configuration and only `connectorId` and\r\n`actionTypeId` would be passed. Here is the old code implementation:\r\n\r\n```\r\nconst newConversation = await createConversation({\r\n title: NEW_CHAT,\r\n ...(currentConversation?.apiConfig != null &&\r\n currentConversation?.apiConfig?.actionTypeId != null\r\n ? {\r\n apiConfig: {\r\n connectorId: currentConversation.apiConfig.connectorId,\r\n actionTypeId: currentConversation.apiConfig.actionTypeId,\r\n ...(newSystemPrompt?.id != null ? { defaultSystemPromptId: newSystemPrompt.id } : {}),\r\n },\r\n }\r\n : {}),\r\n});\r\n```\r\n\r\nand thus the new conversation would not have the complete connector\r\nconfiguration which would cause to use default model (`gpt-4o`) as a\r\nmodel we pass to the LLM.\r\n\r\nAlso, I updated the default body that we use on the Test connector page,\r\nto make sure that we send a model parameter to the LLM in case of `Open\r\nAI > Other (OpenAI Compatible Service)` kind of connectors.\r\n\r\n### Testing notes\r\n\r\nSteps to reproduce:\r\n1. Install\r\n[Ollama](https://github.com/ollama/ollama?tab=readme-ov-file#ollama)\r\nlocally\r\n2. Setup an OpenAI connector using Other (OpenAI Compatible Service)\r\nprovider\r\n3. Open AI Assistant and select created Ollama connector to chat\r\n4. Create a \"New Chat\"\r\n5. The Ollama connector should be selected\r\n6. Send a message to LLM (for example \"hello world\")\r\n\r\nExpected: there should be no errors saying `ActionsClientChatOpenAI: an\r\nerror occurred while running the action - Unexpected API Error: - 404\r\nmodel \"gpt-4o\" not found, try pulling it first`","sha":"7e4e8592f45ceca822c4f34d18e9f047cfe3cde0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
natasha-moore-elastic
|
cbcb1cb562
|
[8.16] [DOCS] Adds conceptual content to API docs (#202305) (#204108)
# Backport This will backport the following commits from `main` to `8.16`: - [[DOCS] Adds conceptual content to API docs (#202305)](https://github.com/elastic/kibana/pull/202305) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"natasha-moore-elastic","email":"137783811+natasha-moore-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-12T16:53:29Z","message":"[DOCS] Adds conceptual content to API docs (#202305)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/security-docs-internal/issues/49.\r\n\r\nIn order to retire asciidoc API docs, we first need to move over any\r\nrelevant content from those docs to the API reference site. This PR adds\r\nthe relevant conceptual information from:\r\n\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/exceptions-api-overview.html\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/lists-api-overview.html\r\n- https://www.elastic.co/guide/en/security/master/rule-api-overview.html\r\n\r\n### Previews:\r\nBump previews expire after 30min, so I'm providing screenshots below:\r\n\r\nDetections preview:\r\n\r\n\r\n\r\nExceptions preview:\r\n\r\n\r\n\r\nLists preview:\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cebcf01d35b84308e1ca9eabed694864a9e39ed9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","Feature:Detection Rules","docs","Team:Detections and Resp","Feature:Rule Exceptions","APIDocs","Team:Detection Rule Management","Team:Detection Engine","backport:version","v8.17.0","v8.16.2"],"number":202305,"url":"https://github.com/elastic/kibana/pull/202305","mergeCommit":{"message":"[DOCS] Adds conceptual content to API docs (#202305)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/security-docs-internal/issues/49.\r\n\r\nIn order to retire asciidoc API docs, we first need to move over any\r\nrelevant content from those docs to the API reference site. This PR adds\r\nthe relevant conceptual information from:\r\n\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/exceptions-api-overview.html\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/lists-api-overview.html\r\n- https://www.elastic.co/guide/en/security/master/rule-api-overview.html\r\n\r\n### Previews:\r\nBump previews expire after 30min, so I'm providing screenshots below:\r\n\r\nDetections preview:\r\n\r\n\r\n\r\nExceptions preview:\r\n\r\n\r\n\r\nLists preview:\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cebcf01d35b84308e1ca9eabed694864a9e39ed9"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202305","number":202305,"mergeCommit":{"message":"[DOCS] Adds conceptual content to API docs (#202305)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/security-docs-internal/issues/49.\r\n\r\nIn order to retire asciidoc API docs, we first need to move over any\r\nrelevant content from those docs to the API reference site. This PR adds\r\nthe relevant conceptual information from:\r\n\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/exceptions-api-overview.html\r\n-\r\nhttps://www.elastic.co/guide/en/security/master/lists-api-overview.html\r\n- https://www.elastic.co/guide/en/security/master/rule-api-overview.html\r\n\r\n### Previews:\r\nBump previews expire after 30min, so I'm providing screenshots below:\r\n\r\nDetections preview:\r\n\r\n\r\n\r\nExceptions preview:\r\n\r\n\r\n\r\nLists preview:\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cebcf01d35b84308e1ca9eabed694864a9e39ed9"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
2e175b9d3f
|
[8.16] [Search] Add ML as required plugin to Search Assistant (#204009) (#204035)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search] Add ML as required plugin to Search Assistant (#204009)](https://github.com/elastic/kibana/pull/204009) <!--- 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-12-12T14:20:09Z","message":"[Search] Add ML as required plugin to Search Assistant (#204009)\n\n## Summary\r\n\r\nThis adds the `ml` plugin as required to the Search Assistant so that we\r\ndon't need users to navigate to an ml-based plugin to initiate the\r\nknowledge base.","sha":"16d45f503a886b13b9fbc04a8cd20bb7e0f14ece","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Search","backport:prev-major"],"title":"[Search] Add ML as required plugin to Search Assistant","number":204009,"url":"https://github.com/elastic/kibana/pull/204009","mergeCommit":{"message":"[Search] Add ML as required plugin to Search Assistant (#204009)\n\n## Summary\r\n\r\nThis adds the `ml` plugin as required to the Search Assistant so that we\r\ndon't need users to navigate to an ml-based plugin to initiate the\r\nknowledge base.","sha":"16d45f503a886b13b9fbc04a8cd20bb7e0f14ece"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204009","number":204009,"mergeCommit":{"message":"[Search] Add ML as required plugin to Search Assistant (#204009)\n\n## Summary\r\n\r\nThis adds the `ml` plugin as required to the Search Assistant so that we\r\ndon't need users to navigate to an ml-based plugin to initiate the\r\nknowledge base.","sha":"16d45f503a886b13b9fbc04a8cd20bb7e0f14ece"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
53495ac1c2
|
[8.16] [Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation (#203545) (#203985)
# Backport This will backport the following commits from `main` to `8.16`: - [[Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation (#203545)](https://github.com/elastic/kibana/pull/203545) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-12T10:23:24Z","message":"[Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation (#203545)\n\nCloses #197401\r\n\r\n### Summary\r\n\r\nThis PR adds ability to preserve `kuery` filters when switching between\r\npages in Universal Profiling using `solution navigation`. The missing\r\nfilters were considered regression in comparison to `classic\r\nnavigation`.\r\n\r\n### Testing\r\n\r\nExpected behavior with **classic navigation** for comparison:\r\n\r\n\r\nBefore with **solution navigation**:\r\n\r\n\r\nAfter with **solution navigation**:\r\n","sha":"881cdc142b3014f964a7b69fc8b29b85211fcbfa","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","ci:project-deploy-observability"],"title":"[Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation","number":203545,"url":"https://github.com/elastic/kibana/pull/203545","mergeCommit":{"message":"[Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation (#203545)\n\nCloses #197401\r\n\r\n### Summary\r\n\r\nThis PR adds ability to preserve `kuery` filters when switching between\r\npages in Universal Profiling using `solution navigation`. The missing\r\nfilters were considered regression in comparison to `classic\r\nnavigation`.\r\n\r\n### Testing\r\n\r\nExpected behavior with **classic navigation** for comparison:\r\n\r\n\r\nBefore with **solution navigation**:\r\n\r\n\r\nAfter with **solution navigation**:\r\n","sha":"881cdc142b3014f964a7b69fc8b29b85211fcbfa"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203545","number":203545,"mergeCommit":{"message":"[Profiling] Preserve `kuery` filters when switching between Universal Profiling pages in new solution navigation (#203545)\n\nCloses #197401\r\n\r\n### Summary\r\n\r\nThis PR adds ability to preserve `kuery` filters when switching between\r\npages in Universal Profiling using `solution navigation`. The missing\r\nfilters were considered regression in comparison to `classic\r\nnavigation`.\r\n\r\n### Testing\r\n\r\nExpected behavior with **classic navigation** for comparison:\r\n\r\n\r\nBefore with **solution navigation**:\r\n\r\n\r\nAfter with **solution navigation**:\r\n","sha":"881cdc142b3014f964a7b69fc8b29b85211fcbfa"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com> |
||
Devin W. Hurley
|
d2dd29eb85
|
[8.16] [Security Solution] Fixes exception item comment validation on newline chars \n (#202063) (#203709)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Fixes exception item comment validation on newline chars `\n` (#202063)](https://github.com/elastic/kibana/pull/202063) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2024-12-10T22:19:32Z","message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:fix","v9.0.0","Team:Detections and Resp","Feature:Rule Exceptions","backport:version","v8.18.0","v8.16.2","v8.17.1"],"number":202063,"url":"https://github.com/elastic/kibana/pull/202063","mergeCommit":{"message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202063","number":202063,"mergeCommit":{"message":"[Security Solution] Fixes exception item comment validation on newline chars `\\n` (#202063)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/201820\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"35aeac104359eae81a233d0b8a9acaa97119d006"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
6fa6e0ae7c
|
[8.16] [Synthetics] Monitors sync request, retry on huge payload !! (#202467) (#203666)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Monitors sync request, retry on huge payload !! (#202467)](https://github.com/elastic/kibana/pull/202467) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-03T12:04:42Z","message":"[Synthetics] Monitors sync request, retry on huge payload !! (#202467)\n\n## Summary\r\n\r\nMonitors sync request, retry on huge payload by splitting the payload !!\r\n\r\nRequests will be tried recursively by splitting payload in half !!","sha":"839a927a94be5614f743c67c8384e2832c684de6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-management","v8.18.0","v8.16.3","v8.17.1"],"title":"[Synthetics] Monitors sync request, retry on huge payload !!","number":202467,"url":"https://github.com/elastic/kibana/pull/202467","mergeCommit":{"message":"[Synthetics] Monitors sync request, retry on huge payload !! (#202467)\n\n## Summary\r\n\r\nMonitors sync request, retry on huge payload by splitting the payload !!\r\n\r\nRequests will be tried recursively by splitting payload in half !!","sha":"839a927a94be5614f743c67c8384e2832c684de6"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202467","number":202467,"mergeCommit":{"message":"[Synthetics] Monitors sync request, retry on huge payload !! (#202467)\n\n## Summary\r\n\r\nMonitors sync request, retry on huge payload by splitting the payload !!\r\n\r\nRequests will be tried recursively by splitting payload in half !!","sha":"839a927a94be5614f743c67c8384e2832c684de6"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202694","number":202694,"state":"MERGED","mergeCommit":{"sha":"39bfdec15636f5aa76687911e79e57bba323174b","message":"[8.x] [Synthetics] Monitors sync request, retry on huge payload !! (#202467) (#202694)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Synthetics] Monitors sync request, retry on huge payload !!\n(#202467)](https://github.com/elastic/kibana/pull/202467)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Shahzad\",\"email\":\"shahzad31comp@gmail.com\"},\"sourceCommit\":{\"committedDate\":\"2024-12-03T12:04:42Z\",\"message\":\"[Synthetics]\nMonitors sync request, retry on huge payload !! (#202467)\\n\\n##\nSummary\\r\\n\\r\\nMonitors sync request, retry on huge payload by splitting\nthe payload !!\\r\\n\\r\\nRequests will be tried recursively by splitting\npayload in half\n!!\",\"sha\":\"839a927a94be5614f743c67c8384e2832c684de6\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"ci:project-deploy-observability\",\"Team:obs-ux-management\",\"backport:version\",\"v8.18.0\"],\"title\":\"[Synthetics]\nMonitors sync request, retry on huge payload\n!!\",\"number\":202467,\"url\":\"https://github.com/elastic/kibana/pull/202467\",\"mergeCommit\":{\"message\":\"[Synthetics]\nMonitors sync request, retry on huge payload !! (#202467)\\n\\n##\nSummary\\r\\n\\r\\nMonitors sync request, retry on huge payload by splitting\nthe payload !!\\r\\n\\r\\nRequests will be tried recursively by splitting\npayload in half\n!!\",\"sha\":\"839a927a94be5614f743c67c8384e2832c684de6\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/202467\",\"number\":202467,\"mergeCommit\":{\"message\":\"[Synthetics]\nMonitors sync request, retry on huge payload !! (#202467)\\n\\n##\nSummary\\r\\n\\r\\nMonitors sync request, retry on huge payload by splitting\nthe payload !!\\r\\n\\r\\nRequests will be tried recursively by splitting\npayload in half\n!!\",\"sha\":\"839a927a94be5614f743c67c8384e2832c684de6\"}},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
466cdf5347
|
[8.16] [APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios (#203590) (#203646)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios (#203590)](https://github.com/elastic/kibana/pull/203590) <!--- Backport version: 9.4.3 --> ### 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-12-10T16:52:33Z","message":"[APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios (#203590)\n\ncloses [203571](https://github.com/elastic/kibana/issues/203571)\r\n\r\n## Summary\r\n\r\nKibana 9.0 requires all request made with `axios` have the request\r\nheader `x-elastic-internal-origin` set to `Kibana` to avoid appearing as\r\nan “external” integration. Any [requests without it will be blocked in\r\nKibana\r\n9.0](https://docs.google.com/document/d/1W7csjn6QYjrBjmbXMzSz_JUD4KcmWz8jTTtAWFwgUJM/edit?tab=t.0#heading=h.brxkig5phxcz)","sha":"cc6dc2ac2be199aea47477d17648a7336c33ff7d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.9.0","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios","number":203590,"url":"https://github.com/elastic/kibana/pull/203590","mergeCommit":{"message":"[APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios (#203590)\n\ncloses [203571](https://github.com/elastic/kibana/issues/203571)\r\n\r\n## Summary\r\n\r\nKibana 9.0 requires all request made with `axios` have the request\r\nheader `x-elastic-internal-origin` set to `Kibana` to avoid appearing as\r\nan “external” integration. Any [requests without it will be blocked in\r\nKibana\r\n9.0](https://docs.google.com/document/d/1W7csjn6QYjrBjmbXMzSz_JUD4KcmWz8jTTtAWFwgUJM/edit?tab=t.0#heading=h.brxkig5phxcz)","sha":"cc6dc2ac2be199aea47477d17648a7336c33ff7d"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203590","number":203590,"mergeCommit":{"message":"[APM][Profiling] Add x-elastic-internal-origin: Kibana header to agentless axios (#203590)\n\ncloses [203571](https://github.com/elastic/kibana/issues/203571)\r\n\r\n## Summary\r\n\r\nKibana 9.0 requires all request made with `axios` have the request\r\nheader `x-elastic-internal-origin` set to `Kibana` to avoid appearing as\r\nan “external” integration. Any [requests without it will be blocked in\r\nKibana\r\n9.0](https://docs.google.com/document/d/1W7csjn6QYjrBjmbXMzSz_JUD4KcmWz8jTTtAWFwgUJM/edit?tab=t.0#heading=h.brxkig5phxcz)","sha":"cc6dc2ac2be199aea47477d17648a7336c33ff7d"}},{"branch":"8.9","label":"v8.9.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
|
Kibana Machine
|
7bcb2627ea
|
[8.16] [Index management] Fix a11y focus order in index mappings page (#203361) (#203626)
# Backport This will backport the following commits from `main` to `8.16`: - [[Index management] Fix a11y focus order in index mappings page (#203361)](https://github.com/elastic/kibana/pull/203361) <!--- 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-12-10T15:46:20Z","message":"[Index management] Fix a11y focus order in index mappings page (#203361)\n\n## Summary\r\n\r\nFix a11y focus order in index mappings page. When new field is in\r\npending state and after closing edit pending field Flyout.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/dbdf59e5-0ebd-47e0-9b5e-19ab1556e771\r\n\r\n### Test instructions \r\n#### Adding a field\r\n1. Add new field in index mappings page by navigating via tab \r\n2. Notice that type fields combo box is focused\r\n3. Add field and click to Add field button again with in pending fields\r\nform\r\n4. Notice focus is on new create field form\r\n\r\n#### Edit field in pending state\r\n1. Add new fields via tab key\r\n2. click on edit field \r\n3. Try closing, updating and cancelling in the edit field flyout form\r\n4. Notice after edit field flyout is closed, focus is on the pending\r\nfields form","sha":"4b0c0e92693ad759e3ce45b4b259c9908ddd0d51","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major","v8.16.0","v8.17.0"],"title":"[Index management] Fix a11y focus order in index mappings page ","number":203361,"url":"https://github.com/elastic/kibana/pull/203361","mergeCommit":{"message":"[Index management] Fix a11y focus order in index mappings page (#203361)\n\n## Summary\r\n\r\nFix a11y focus order in index mappings page. When new field is in\r\npending state and after closing edit pending field Flyout.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/dbdf59e5-0ebd-47e0-9b5e-19ab1556e771\r\n\r\n### Test instructions \r\n#### Adding a field\r\n1. Add new field in index mappings page by navigating via tab \r\n2. Notice that type fields combo box is focused\r\n3. Add field and click to Add field button again with in pending fields\r\nform\r\n4. Notice focus is on new create field form\r\n\r\n#### Edit field in pending state\r\n1. Add new fields via tab key\r\n2. click on edit field \r\n3. Try closing, updating and cancelling in the edit field flyout form\r\n4. Notice after edit field flyout is closed, focus is on the pending\r\nfields form","sha":"4b0c0e92693ad759e3ce45b4b259c9908ddd0d51"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203361","number":203361,"mergeCommit":{"message":"[Index management] Fix a11y focus order in index mappings page (#203361)\n\n## Summary\r\n\r\nFix a11y focus order in index mappings page. When new field is in\r\npending state and after closing edit pending field Flyout.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/dbdf59e5-0ebd-47e0-9b5e-19ab1556e771\r\n\r\n### Test instructions \r\n#### Adding a field\r\n1. Add new field in index mappings page by navigating via tab \r\n2. Notice that type fields combo box is focused\r\n3. Add field and click to Add field button again with in pending fields\r\nform\r\n4. Notice focus is on new create field form\r\n\r\n#### Edit field in pending state\r\n1. Add new fields via tab key\r\n2. click on edit field \r\n3. Try closing, updating and cancelling in the edit field flyout form\r\n4. Notice after edit field flyout is closed, focus is on the pending\r\nfields form","sha":"4b0c0e92693ad759e3ce45b4b259c9908ddd0d51"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com> |
||
|
Kibana Machine
|
371ae4de45
|
[8.16] [Observability Onboarding] Show existing data callout in Firehose flow (#203072) (#203565)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] Show existing data callout in Firehose flow (#203072)](https://github.com/elastic/kibana/pull/203072) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-12-10T13:07:11Z","message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding"],"title":"[Observability Onboarding] Show existing data callout in Firehose flow","number":203072,"url":"https://github.com/elastic/kibana/pull/203072","mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203072","number":203072,"mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> |
||
Jill Guyonnet
|
ebe4505b7a
|
[8.16] [Fleet] Fix disabling logic for "View Agents" button in agent activity (#202968) (#203386)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] Fix disabling logic for "View Agents" button in agent activity (#202968)](https://github.com/elastic/kibana/pull/202968) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T15:43:40Z","message":"[Fleet] Fix disabling logic for \"View Agents\" button in agent activity (#202968)\n\n## Summary\r\n\r\nI came across a small bug while testing Fleet agents activity: the \"View\r\nAgents\" button is currently always disabled for agent policy changes.\r\nThis is because agent policy data has been modified to be fetched with\r\n`noAgentCount: true` by default.\r\n\r\nAs getting the agent count involves a performance concern, this PR fixes\r\nthe logic that disables the \"View Agents\" button for policy change\r\nactions instead. The behaviour is not as follows:\r\n* For tag updates actions: button not showed (no change)\r\n* For policy change actions\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n* Otherwise: enable button and show tooltip saying that these are the\r\nagents _currently_ assigned to the policy (existing behaviour, known\r\nlimitation)\r\n* For other types of actions (no change)\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n * Otherwise: enable button, no tooltip\r\n\r\n### Screenshots\r\n\r\n\r\n\r\n\r\n\r\n","sha":"7caa33993a1a167ab30d72bfa0f1bec81a021376","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor"],"number":202968,"url":"https://github.com/elastic/kibana/pull/202968","mergeCommit":{"message":"[Fleet] Fix disabling logic for \"View Agents\" button in agent activity (#202968)\n\n## Summary\r\n\r\nI came across a small bug while testing Fleet agents activity: the \"View\r\nAgents\" button is currently always disabled for agent policy changes.\r\nThis is because agent policy data has been modified to be fetched with\r\n`noAgentCount: true` by default.\r\n\r\nAs getting the agent count involves a performance concern, this PR fixes\r\nthe logic that disables the \"View Agents\" button for policy change\r\nactions instead. The behaviour is not as follows:\r\n* For tag updates actions: button not showed (no change)\r\n* For policy change actions\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n* Otherwise: enable button and show tooltip saying that these are the\r\nagents _currently_ assigned to the policy (existing behaviour, known\r\nlimitation)\r\n* For other types of actions (no change)\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n * Otherwise: enable button, no tooltip\r\n\r\n### Screenshots\r\n\r\n\r\n\r\n\r\n\r\n","sha":"7caa33993a1a167ab30d72bfa0f1bec81a021376"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202968","number":202968,"mergeCommit":{"message":"[Fleet] Fix disabling logic for \"View Agents\" button in agent activity (#202968)\n\n## Summary\r\n\r\nI came across a small bug while testing Fleet agents activity: the \"View\r\nAgents\" button is currently always disabled for agent policy changes.\r\nThis is because agent policy data has been modified to be fetched with\r\n`noAgentCount: true` by default.\r\n\r\nAs getting the agent count involves a performance concern, this PR fixes\r\nthe logic that disables the \"View Agents\" button for policy change\r\nactions instead. The behaviour is not as follows:\r\n* For tag updates actions: button not showed (no change)\r\n* For policy change actions\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n* Otherwise: enable button and show tooltip saying that these are the\r\nagents _currently_ assigned to the policy (existing behaviour, known\r\nlimitation)\r\n* For other types of actions (no change)\r\n* If `action.nbAgentsActionCreated > 10000`: disable button and show\r\ntooltip explaining why it's disabled\r\n * Otherwise: enable button, no tooltip\r\n\r\n### Screenshots\r\n\r\n\r\n\r\n\r\n\r\n","sha":"7caa33993a1a167ab30d72bfa0f1bec81a021376"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
4fa7135580
|
[8.16] [Session management] update cleanup query to allow partial search results for PIT query (#203413) (#203538)
# Backport This will backport the following commits from `main` to `8.16`: - [[Session management] update cleanup query to allow partial search results for PIT query (#203413)](https://github.com/elastic/kibana/pull/203413) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2024-12-10T11:01:57Z","message":"[Session management] update cleanup query to allow partial search results for PIT query (#203413)\n\nCloses https://github.com/elastic/kibana/issues/203440\r\n\r\n### Summary\r\nUpdate session cleanup task by adding the partial search results flag to\r\nthe PIT query as well and not just the search query.\r\n\r\n#### Notes \r\nIn the previous “fix”, the partial search results flag was incorrectly\r\nadded to the search query that depended on the PIT query. However, the\r\ncorrect way is to set the flag when we openPointInTimeQuery which is\r\nthen used in the subsequent search query\r\n\r\n### Release notes\r\nFixes error with opening point in time query for session deletion by now\r\naccounting for partial results.\r\n\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"91fec7a69b4db5c1d5835add148b86c3732b02a7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","v9.0.0","Feature:Security/Session Management","backport:prev-major"],"title":"[Session management] update cleanup query to allow partial search results for PIT query","number":203413,"url":"https://github.com/elastic/kibana/pull/203413","mergeCommit":{"message":"[Session management] update cleanup query to allow partial search results for PIT query (#203413)\n\nCloses https://github.com/elastic/kibana/issues/203440\r\n\r\n### Summary\r\nUpdate session cleanup task by adding the partial search results flag to\r\nthe PIT query as well and not just the search query.\r\n\r\n#### Notes \r\nIn the previous “fix”, the partial search results flag was incorrectly\r\nadded to the search query that depended on the PIT query. However, the\r\ncorrect way is to set the flag when we openPointInTimeQuery which is\r\nthen used in the subsequent search query\r\n\r\n### Release notes\r\nFixes error with opening point in time query for session deletion by now\r\naccounting for partial results.\r\n\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"91fec7a69b4db5c1d5835add148b86c3732b02a7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203413","number":203413,"mergeCommit":{"message":"[Session management] update cleanup query to allow partial search results for PIT query (#203413)\n\nCloses https://github.com/elastic/kibana/issues/203440\r\n\r\n### Summary\r\nUpdate session cleanup task by adding the partial search results flag to\r\nthe PIT query as well and not just the search query.\r\n\r\n#### Notes \r\nIn the previous “fix”, the partial search results flag was incorrectly\r\nadded to the search query that depended on the PIT query. However, the\r\ncorrect way is to set the flag when we openPointInTimeQuery which is\r\nthen used in the subsequent search query\r\n\r\n### Release notes\r\nFixes error with opening point in time query for session deletion by now\r\naccounting for partial results.\r\n\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"91fec7a69b4db5c1d5835add148b86c3732b02a7"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com> |
||
|
Kibana Machine
|
bbd8c83cea
|
[8.16] [OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096) (#203467)
# Backport This will backport the following commits from `main` to `8.16`: - [[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)](https://github.com/elastic/kibana/pull/203096) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Faisal Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T16:07:58Z","message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes https://github.com/elastic/kibana/issues/199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","v8.18.0"],"title":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid","number":203096,"url":"https://github.com/elastic/kibana/pull/203096","mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes https://github.com/elastic/kibana/issues/199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203096","number":203096,"mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096)\n\n## Summary\r\n\r\nIt fixes https://github.com/elastic/kibana/issues/199273 by validating\r\nthe query before passing it to the preview chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/203134","number":203134,"state":"MERGED","mergeCommit":{"sha":"a70bdf01cd8208c0f2358a98f5fcc5d10ac0a7d6","message":"[8.x] [OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is invalid (#203096) (#203134)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is\ninvalid (#203096)](https://github.com/elastic/kibana/pull/203096)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Faisal\nKanout\",\"email\":\"faisal.kanout@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-05T16:07:58Z\",\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"backport:prev-minor\",\"ci:project-deploy-observability\",\"Team:obs-ux-infra_services\",\"Team:obs-ux-management\"],\"title\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is\ninvalid\",\"number\":203096,\"url\":\"https://github.com/elastic/kibana/pull/203096\",\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/203096\",\"number\":203096,\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][ALERTING]\nFix APM rule error msg when KQL filter is invalid (#203096)\\n\\n##\nSummary\\r\\n\\r\\nIt fixes https://github.com/elastic/kibana/issues/199273\nby validating\\r\\nthe query before passing it to the preview\nchart\",\"sha\":\"f1109cfccedfd386263a00207df81c766cfaf6e4\"}}]}] BACKPORT-->\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co> |
||
|
Kibana Machine
|
011e63083b
|
[8.16] [Search][Connectors] Disable setup options after creating configuration (#203374) (#203393)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search][Connectors] Disable setup options after creating configuration (#203374)](https://github.com/elastic/kibana/pull/203374) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2024-12-09T11:15:54Z","message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.17.0","v8.18.0","v8.16.2","v8.16.3"],"title":"[Search][Connectors] Disable setup options after creating configuration","number":203374,"url":"https://github.com/elastic/kibana/pull/203374","mergeCommit":{"message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203374","number":203374,"mergeCommit":{"message":"[Search][Connectors] Disable setup options after creating configuration (#203374)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ and _Self-managed_ setup options\r\nafter clicking the _Generate configuration_ button in order to avoid the\r\nerror described in this ticket\r\nhttps://github.com/elastic/search-team/issues/8665 when changing\r\ndeployment method after generating the config.\r\n\r\n","sha":"9b6af1c1887f83d821d6fc639715ad4be593fea7"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: José Luis González <joseluisgj@gmail.com> |
||
Julia Bardi
|
f3f31f43f9
|
[8.16][Fleet] fix schema validation to allow undefined/null (#202732) (#202879)
Backport https://github.com/elastic/kibana/pull/202732 to 8.16 Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
7ff64237f1
|
[8.16] [Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613) (#202892)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)](https://github.com/elastic/kibana/pull/201613) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-12-04T10:49:47Z","message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability"],"title":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow","number":201613,"url":"https://github.com/elastic/kibana/pull/201613","mergeCommit":{"message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201613","number":201613,"mergeCommit":{"message":"[Observability Onboarding] Prevent showing duplcated AWS services in Firehose flow (#201613)\n\nCloses #200931 \r\n\r\nSwitched to using AWS service list as a base to showing the detected\r\nservices in the UI instead of the list of populated indices as multiple\r\nindices can be related to a single service.\r\n\r\n### How to test\r\n\r\n1. Go to Firehose flow `/observabilityOnboarding/firehose`\r\n2. Open Kibana dev tools in another tab\r\n3. Ingest documents related into multiple data streams which related to\r\na single AWS service:\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```\r\n4. Make sure you see only one entry for the service appear in the\r\nFirehose flow","sha":"a2fb9b736cd8007a0ba04b9b1051d7988c690b5b"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> |
||
|
Kibana Machine
|
62674ce4e7
|
[8.16] [Search][a11y] Fix table row screen reader error (#203136) (#203217)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search][a11y] Fix table row screen reader error (#203136)](https://github.com/elastic/kibana/pull/203136) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Navarone Feekery","email":"13634519+navarone-feekery@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-06T09:10:26Z","message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major"],"title":"[Search][a11y] Fix table row screen reader error","number":203136,"url":"https://github.com/elastic/kibana/pull/203136","mergeCommit":{"message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203136","number":203136,"mergeCommit":{"message":"[Search][a11y] Fix table row screen reader error (#203136)\n\n## Closes https://github.com/elastic/kibana/issues/199113\r\n\r\nAllows errors in the table row to be read by screen readers.","sha":"1a9893bd6f7fd3fb94b08459e05921a00d86b8c5"}}]}] BACKPORT--> Co-authored-by: Navarone Feekery <13634519+navarone-feekery@users.noreply.github.com> |
||
|
Kibana Machine
|
392068aa9b
|
[8.16] [Automatic Import] Restrict unsupported log formats (#202994) (#203174)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Restrict unsupported log formats (#202994)](https://github.com/elastic/kibana/pull/202994) <!--- 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-12-05T19:18:08Z","message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic Import] Restrict unsupported log formats","number":202994,"url":"https://github.com/elastic/kibana/pull/202994","mergeCommit":{"message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202994","number":202994,"mergeCommit":{"message":"[Automatic Import] Restrict unsupported log formats (#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Gonçalo Rica Pais da Silva
|
2dcd9bc848
|
[8.16] [Infra] Exclude frozen/cold data tiers from source queries (#201804) (#202924)
# Backport This will backport the following commits from `main` to `8.16`: - [[Infra] Exclude frozen/cold data tiers from source queries (#201804)](https://github.com/elastic/kibana/pull/201804) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T18:23:13Z","message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","v8.16.0"],"number":201804,"url":"https://github.com/elastic/kibana/pull/201804","mergeCommit":{"message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201804","number":201804,"mergeCommit":{"message":"[Infra] Exclude frozen/cold data tiers from source queries (#201804)\n\nCloses #201568 \r\n\r\n## Summary\r\n\r\nAdds the exclude data tiers settings to the\r\n`/api/metrics/source/hasData` and `/api/metrics/source/{sourceId}`\r\nrequests. Also applies it to the `getIndexStatus` API call.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ac3b60ee907436aeee35fc59df7c30bcb9d66bc8"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/202788","number":202788,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/202789","number":202789,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Milosz Marcinkowski
|
7d08846ecb
|
[8.16] [APM] Time spent by span type chart rendering problems (#202755) (#203075)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM] `Time spent by span type` chart rendering problems (#202755)](https://github.com/elastic/kibana/pull/202755) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-05T10:08:05Z","message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"number":202755,"url":"https://github.com/elastic/kibana/pull/202755","mergeCommit":{"message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202755","number":202755,"mergeCommit":{"message":"[APM] `Time spent by span type` chart rendering problems (#202755)\n\nCloses #202343\r\n\r\n## Summary\r\n\r\nThis PR solves the following issues in `Time spent by span type` chart:\r\n- limits percentages between 0% and 100% (converts negative values to\r\n0%),\r\n\r\nbefore: \r\n<img width=\"1134\" alt=\"Screenshot 2024-12-04 at 15 28 18\"\r\nsrc=\"https://github.com/user-attachments/assets/73285e87-3aef-4b2d-8e2a-7e3ec87680f3\">\r\nafter:\r\n<img width=\"1135\" alt=\"Screenshot 2024-12-04 at 15 30 25\"\r\nsrc=\"https://github.com/user-attachments/assets/ae25cb85-d31a-490a-96c7-d4475952c734\">\r\n\r\n---\r\n\r\n- rounds percentage to 8 decimal points to prevent scientific notation\r\nin charts (poor readability)\r\n\r\nbefore: \r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 36 54\"\r\nsrc=\"https://github.com/user-attachments/assets/528cda4b-ae84-4dbd-9d3f-88896e63a369\">\r\nafter:\r\n<img width=\"1132\" alt=\"Screenshot 2024-12-04 at 14 35 39\"\r\nsrc=\"https://github.com/user-attachments/assets/9a0bdce9-6d66-4aaf-a131-18644eab1892\">","sha":"ab9de649fe32b22b4f847d190be73fbf229a1ac8"}},{"url":"https://github.com/elastic/kibana/pull/203066","number":203066,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
d3c6743f47
|
[8.16] Add prompt for connector configuration being in editable mode (#202463) (#203115)
# Backport This will backport the following commits from `main` to `8.16`: - [Add prompt for connector configuration being in editable mode (#202463)](https://github.com/elastic/kibana/pull/202463) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Artem Shelkovnikov","email":"artem.shelkovnikov@elastic.co"},"sourceCommit":{"committedDate":"2024-12-05T14:44:16Z","message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major"],"title":"Add prompt for connector configuration being in editable mode","number":202463,"url":"https://github.com/elastic/kibana/pull/202463","mergeCommit":{"message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202463","number":202463,"mergeCommit":{"message":"Add prompt for connector configuration being in editable mode (#202463)\n\n### Closes https://github.com/elastic/search-team/issues/8547\r\n## Summary\r\n\r\nUser creates connectors following a set of steps. During configuration\r\nstep they are able to open configuration form and then click \"Next\" -\r\nconfiguration will not be saved and user will not be prompted about it.\r\n\r\nThis change adds a prompt for this step - if the configuration is in\r\neditable state, the prompt will be shown. It does not check that the\r\nform was edited, however, and it's on purpose. I'm open to changing it\r\nto only prompt if any value changed, but I feel that it's important to\r\nprompt even if no values were entered, just to confirm with the user\r\nthat they want to move on without specifying any values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}}]}] BACKPORT--> Co-authored-by: Artem Shelkovnikov <artem.shelkovnikov@elastic.co> |
||
|
Kibana Machine
|
a93125e9ed
|
[8.16] [Synthetics] Fix overview trends for read-only user !! (#202914) (#202988)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fix overview trends for read-only user !! (#202914)](https://github.com/elastic/kibana/pull/202914) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-04T17:24:07Z","message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.17.0","v8.18.0","v8.16.3"],"title":"[Synthetics] Fix overview trends for read-only user !!","number":202914,"url":"https://github.com/elastic/kibana/pull/202914","mergeCommit":{"message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202914","number":202914,"mergeCommit":{"message":"[Synthetics] Fix overview trends for read-only user !! (#202914)\n\n## Summary\r\n\r\nFix overview trends for read-only user , we wrongly assume that this\r\n`POST` route needs write permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
916efdcbdc
|
[8.16] [Discover] Support "Inspect" in saved search embeddables (#202947) (#203090)
# Backport This will backport the following commits from `main` to `8.16`: - [[Discover] Support "Inspect" in saved search embeddables (#202947)](https://github.com/elastic/kibana/pull/202947) <!--- 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-12-05T12:04:01Z","message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:DataDiscovery","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Discover] Support \"Inspect\" in saved search embeddables","number":202947,"url":"https://github.com/elastic/kibana/pull/202947","mergeCommit":{"message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202947","number":202947,"mergeCommit":{"message":"[Discover] Support \"Inspect\" in saved search embeddables (#202947)\n\n- Closes https://github.com/elastic/kibana/issues/202301\r\n\r\n## Summary\r\n\r\nThis PR enables \"Inspect\" option for saved search Dashboard panels.\r\n\r\n<img width=\"1619\" alt=\"Screenshot 2024-12-04 at 16 02 33\"\r\nsrc=\"https://github.com/user-attachments/assets/a1eab597-4683-4069-b48f-b33b977db578\">\r\n<img width=\"1620\" alt=\"Screenshot 2024-12-04 at 16 02 43\"\r\nsrc=\"https://github.com/user-attachments/assets/0dc734c3-f930-4397-9b68-69d959400924\">\r\n<img width=\"1618\" alt=\"Screenshot 2024-12-04 at 16 03 03\"\r\nsrc=\"https://github.com/user-attachments/assets/460d8432-dc14-480e-b49d-81ab743815d2\">\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\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3f0008ab5d38fd070b121e2e710ec6fff6efcd07"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Janki Salvi
|
886f509607
|
[8.16] [ResponseOps][Cases] Fix edit cases settings privilege (#202053) (#202987)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Cases] Fix edit cases settings privilege (#202053)](https://github.com/elastic/kibana/pull/202053) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Janki Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-04T15:55:08Z","message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\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":"8e8ba53116c16cc9b9122de27415cf8519cc1863","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-minor","v8.17.0","v8.18.0","v8.16.2"],"number":202053,"url":"https://github.com/elastic/kibana/pull/202053","mergeCommit":{"message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\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":"8e8ba53116c16cc9b9122de27415cf8519cc1863"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202053","number":202053,"mergeCommit":{"message":"[ResponseOps][Cases] Fix edit cases settings privilege (#202053)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/197650\r\n\r\nAlso fixes an issue where user has `cases: all ` and `edit case\r\nsettings: false`, user was able to edit settings.\r\n\r\nUsed `permissions.settings` instead of `permissions.update` and\r\n`permissions.create` for custom fields and templates.\r\n\r\n### How to test\r\n- Verify by creating a user with different combinations of cases and\r\nedit case settings privileges\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":"8e8ba53116c16cc9b9122de27415cf8519cc1863"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202970","number":202970,"state":"OPEN"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202971","number":202971,"state":"OPEN"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Dmitrii Shevchenko
|
e2eaf0c7d2
|
[8.16] [Security Solution] Skip isCustomized calculation when the feature flag is off (#201825) (#202751)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)](https://github.com/elastic/kibana/pull/201825) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T12:11:24Z","message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.17.0","v8.18.0","v8.16.2"],"number":201825,"url":"https://github.com/elastic/kibana/pull/201825","mergeCommit":{"message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201825","number":201825,"mergeCommit":{"message":"[Security Solution] Skip isCustomized calculation when the feature flag is off (#201825)\n\n**Resolves: https://github.com/elastic/kibana/issues/201632**\r\n\r\n## Summary \r\n\r\nWhen the rule customization feature flag is disabled, we should always\r\nreturn `isCustomized: false`, regardless of any changes introduced to a\r\nrule. This ensures that we do not accidentally mark prebuilt rules as\r\ncustomized in 8.16 with the feature flag off. For more details, refer to\r\nthe related issue: https://github.com/elastic/kibana/issues/201632\r\n\r\n### Main Changes \r\n\r\n- The primary change in this PR is encapsulated in the\r\n`calculateIsCustomized` function\r\n- Other changes involve passing the feature flag to this function\r\n- Added integration tests to cover all API CRUD operations that can be\r\nperformed with rules","sha":"22911c1828f40160cf3a2935300aec18c11b56e9"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202696","number":202696,"state":"MERGED","mergeCommit":{"sha":"487149e077e61341f81c871b74f36a9e20df67c0","message":"[8.17] [Security Solution] Skip isCustomized calculation when the feature flag is off (#201825) (#202696)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Security Solution] Skip isCustomized calculation when the feature\nflag is off (#201825)](https://github.com/elastic/kibana/pull/201825)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-03T12:11:24Z\",\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:skip\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is\noff\",\"number\":201825,\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"number\":201825,\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202697","number":202697,"state":"MERGED","mergeCommit":{"sha":"8c9181aa48796a8467e38ad1431238ebaa78de7e","message":"[8.x] [Security Solution] Skip isCustomized calculation when the feature flag is off (#201825) (#202697)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Skip isCustomized calculation when the feature\nflag is off (#201825)](https://github.com/elastic/kibana/pull/201825)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-03T12:11:24Z\",\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:skip\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is\noff\",\"number\":201825,\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201825\",\"number\":201825,\"mergeCommit\":{\"message\":\"[Security\nSolution] Skip isCustomized calculation when the feature flag is off\n(#201825)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/201632**\\r\\n\\r\\n## Summary\n\\r\\n\\r\\nWhen the rule customization feature flag is disabled, we should\nalways\\r\\nreturn `isCustomized: false`, regardless of any changes\nintroduced to a\\r\\nrule. This ensures that we do not accidentally mark\nprebuilt rules as\\r\\ncustomized in 8.16 with the feature flag off. For\nmore details, refer to\\r\\nthe related issue:\nhttps://github.com/elastic/kibana/issues/201632\\r\\n\\r\\n### Main Changes\n\\r\\n\\r\\n- The primary change in this PR is encapsulated in\nthe\\r\\n`calculateIsCustomized` function\\r\\n- Other changes involve\npassing the feature flag to this function\\r\\n- Added integration tests\nto cover all API CRUD operations that can be\\r\\nperformed with\nrules\",\"sha\":\"22911c1828f40160cf3a2935300aec18c11b56e9\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
22c13da776
|
[8.16] [Security Solution] Modify copy of the install rules title and message (#202226) (#202802)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Modify copy of the install rules title and message (#202226)](https://github.com/elastic/kibana/pull/202226) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T19:28:32Z","message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[Security Solution] Modify copy of the install rules title and message","number":202226,"url":"https://github.com/elastic/kibana/pull/202226","mergeCommit":{"message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202226","number":202226,"mergeCommit":{"message":"[Security Solution] Modify copy of the install rules title and message (#202226)\n\n**Resolves: #200521**\n\n## Summary\n\nI am changing the copy of the install rules title and message.\n\n# BEFORE\n\n\n\n<img width=\"873\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5f4b82f1-094e-432f-9d25-c31042b7585b\">\n\n# AFTER\n<img width=\"611\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/bf211743-2edc-4573-8d10-1c156000d875\">\n\n<img width=\"791\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/612b90b1-290d-40e5-96eb-c88182f78673\">\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [X] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"530b4d482c8b293bd7d36aeb698d75df401f349f"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
97ddbc6579
|
[8.16] [Search] a11y make index mappings search results accessible (#201455) (#202797)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search] a11y make index mappings search results accessible (#201455)](https://github.com/elastic/kibana/pull/201455) <!--- 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-12-03T18:37:51Z","message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","v8.16.0","backport:version","v8.17.0","v8.16.1","v8.16.2"],"title":"[Search] a11y make index mappings search results accessible ","number":201455,"url":"https://github.com/elastic/kibana/pull/201455","mergeCommit":{"message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201455","number":201455,"mergeCommit":{"message":"[Search] a11y make index mappings search results accessible (#201455)\n\n## Summary\r\nMake index mappings search results accessible so that it can read by\r\nscreen reader when navigated by keyboard","sha":"5480451f27639ad923fd04c865b56c58666473fd"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com> |
||
Patryk Kopyciński
|
0c0cb2afc3
|
[8.16] [Security KB] Fix setup KB (#201175) (#202392)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security KB] Fix setup KB (#201175)](https://github.com/elastic/kibana/pull/201175) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2024-11-22T16:58:24Z","message":"[Security KB] Fix setup KB (#201175)\n\n## Summary\r\n\r\nFix an issue with auto-recovery of Knowledge Base setup. \r\n\r\nWhen the KB setup was initialized on an undersized cluster, the model\r\nfailed to deploy correctly. This resulted in the KB ending up in a\r\nbroken state, repeatedly displaying the Setup KB button.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cb56d7196cf60b03cb539f32f6a466a17141e02","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","ci:cloud-deploy","Team:Security Generative AI","backport:version","v8.17.0","v8.18.0","v8.16.2"],"number":201175,"url":"https://github.com/elastic/kibana/pull/201175","mergeCommit":{"message":"[Security KB] Fix setup KB (#201175)\n\n## Summary\r\n\r\nFix an issue with auto-recovery of Knowledge Base setup. \r\n\r\nWhen the KB setup was initialized on an undersized cluster, the model\r\nfailed to deploy correctly. This resulted in the KB ending up in a\r\nbroken state, repeatedly displaying the Setup KB button.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cb56d7196cf60b03cb539f32f6a466a17141e02"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201175","number":201175,"mergeCommit":{"message":"[Security KB] Fix setup KB (#201175)\n\n## Summary\r\n\r\nFix an issue with auto-recovery of Knowledge Base setup. \r\n\r\nWhen the KB setup was initialized on an undersized cluster, the model\r\nfailed to deploy correctly. This resulted in the KB ending up in a\r\nbroken state, repeatedly displaying the Setup KB button.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cb56d7196cf60b03cb539f32f6a466a17141e02"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/201436","number":201436,"state":"MERGED","mergeCommit":{"sha":"252fbfd3de5279b450358e8ffa5c87c58a8767c6","message":"[8.17] [Security KB] Fix setup KB (#201175) (#201436)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Security KB] Fix setup KB\n(#201175)](https://github.com/elastic/kibana/pull/201175)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Patryk\nKopyciński\",\"email\":\"contact@patrykkopycinski.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-22T16:58:24Z\",\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"ci:cloud-deploy\",\"Team:Security\nGenerative\nAI\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nKB] Fix setup\nKB\",\"number\":201175,\"url\":\"https://github.com/elastic/kibana/pull/201175\",\"mergeCommit\":{\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201175\",\"number\":201175,\"mergeCommit\":{\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/201437","number":201437,"state":"MERGED","mergeCommit":{"sha":"7d6c034e25e6d9158edd6c5b1ab905265abb2bdb","message":"[8.x] [Security KB] Fix setup KB (#201175) (#201437)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security KB] Fix setup KB\n(#201175)](https://github.com/elastic/kibana/pull/201175)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Patryk\nKopyciński\",\"email\":\"contact@patrykkopycinski.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-22T16:58:24Z\",\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"ci:cloud-deploy\",\"Team:Security\nGenerative\nAI\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v8.16.2\"],\"title\":\"[Security\nKB] Fix setup\nKB\",\"number\":201175,\"url\":\"https://github.com/elastic/kibana/pull/201175\",\"mergeCommit\":{\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\",\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201175\",\"number\":201175,\"mergeCommit\":{\"message\":\"[Security\nKB] Fix setup KB (#201175)\\n\\n## Summary\\r\\n\\r\\nFix an issue with\nauto-recovery of Knowledge Base setup. \\r\\n\\r\\nWhen the KB setup was\ninitialized on an undersized cluster, the model\\r\\nfailed to deploy\ncorrectly. This resulted in the KB ending up in a\\r\\nbroken state,\nrepeatedly displaying the Setup KB\nbutton.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"1cb56d7196cf60b03cb539f32f6a466a17141e02\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.2\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>"}},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
7e0ea54b45
|
[8.16] [ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712) (#202742)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)](https://github.com/elastic/kibana/pull/202712) <!--- 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-12-03T14:29:28Z","message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\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":"ded18eeaac82787ea57d4991bad28b983d43ad0c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models","number":202712,"url":"https://github.com/elastic/kibana/pull/202712","mergeCommit":{"message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\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":"ded18eeaac82787ea57d4991bad28b983d43ad0c"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202712","number":202712,"mergeCommit":{"message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\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":"ded18eeaac82787ea57d4991bad28b983d43ad0c"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
Lisa Cawley
|
e3f3ba382b
|
[8.16] [OpenAPI] Fix Serverless API base URL (#202373) (#202585)
# Backport This will backport the following commits from `main` to `8.16`: - [[OpenAPI] Fix Serverless API base URL (#202373)](https://github.com/elastic/kibana/pull/202373) <!--- Backport version: 8.9.8 --> ### 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-12-02T20:09:03Z","message":"[OpenAPI] Fix Serverless API base URL (#202373)","sha":"54370b209cb8f4fe02186355f69b8d2f4e4bc97e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.17.0","v8.18.0","v8.16.2"],"number":202373,"url":"https://github.com/elastic/kibana/pull/202373","mergeCommit":{"message":"[OpenAPI] Fix Serverless API base URL (#202373)","sha":"54370b209cb8f4fe02186355f69b8d2f4e4bc97e"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202373","number":202373,"mergeCommit":{"message":"[OpenAPI] Fix Serverless API base URL (#202373)","sha":"54370b209cb8f4fe02186355f69b8d2f4e4bc97e"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
1bd20907d9
|
[8.16] [EDR Workflows] Fix wrong endpoint link (#202434) (#202701)
# Backport This will backport the following commits from `main` to `8.16`: - [[EDR Workflows] Fix wrong endpoint link (#202434)](https://github.com/elastic/kibana/pull/202434) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2024-12-03T12:25:30Z","message":"[EDR Workflows] Fix wrong endpoint link (#202434)","sha":"bcd442239f0eaa6ba84579ea19311ad29221c01f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","ci:cloud-deploy","ci:project-deploy-security","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[EDR Workflows] Fix wrong endpoint link","number":202434,"url":"https://github.com/elastic/kibana/pull/202434","mergeCommit":{"message":"[EDR Workflows] Fix wrong endpoint link (#202434)","sha":"bcd442239f0eaa6ba84579ea19311ad29221c01f"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202434","number":202434,"mergeCommit":{"message":"[EDR Workflows] Fix wrong endpoint link (#202434)","sha":"bcd442239f0eaa6ba84579ea19311ad29221c01f"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
a98da9bf50
|
[8.16] Exclude unrecognized tasks from the task manager aggregate API (#202163) (#202681)
# Backport This will backport the following commits from `main` to `8.16`: - [Exclude unrecognized tasks from the task manager aggregate API (#202163)](https://github.com/elastic/kibana/pull/202163) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mike Côté","email":"mikecote@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-03T11:21:49Z","message":"Exclude unrecognized tasks from the task manager aggregate API (#202163)\n\nIn this PR, I'm removing tasks with a status `unrecognized` from\r\nreturning on any `taskStore.aggregate` calls. Without this, we had\r\nunrecognized recurring tasks that were still part of the task manager\r\ncapacity calculation under\r\n`assumedAverageRecurringRequiredThroughputPerMinutePerKibana`.\r\n\r\n## To Verify\r\n1. Create a few ES Query alerting rules running every 1s\r\n2. Capture the task manager health API report via\r\n`/api/task_manager/_health`\r\n3. Apply the following diff to mark es query alerting tasks as\r\nunrecognized\r\n```\r\ndiff --git a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\nindex 1988eebc21a..8d649f4c6a5 100644\r\n--- a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n+++ b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n@@ -10,5 +10,5 @@ import { getRuleType } from './rule_type';\r\n\r\n export function register(params: RegisterRuleTypesParams, isServerless: boolean) {\r\n const { alerting, core } = params;\r\n- alerting.registerType(getRuleType(core, isServerless));\r\n+ // alerting.registerType(getRuleType(core, isServerless));\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\nindex e28d5221e72..dbfc1bbd135 100644\r\n--- a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n+++ b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n@@ -33,6 +33,11 @@ export async function scheduleMarkRemovedTasksAsUnrecognizedDefinition(\r\n state: {},\r\n params: {},\r\n });\r\n+ try {\r\n+ await taskScheduling.runSoon(TASK_ID);\r\n+ } catch (e) {\r\n+ // Ignore\r\n+ }\r\n } catch (e) {\r\n logger.error(`Error scheduling ${TASK_ID} task, received ${e.message}`);\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/task_type_dictionary.ts b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\nindex e0b28eccea3..142c07bb507 100644\r\n--- a/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n+++ b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n@@ -32,6 +32,8 @@ export const REMOVED_TYPES: string[] = [\r\n\r\n 'cleanup_failed_action_executions',\r\n 'reports:monitor',\r\n+\r\n+ 'alerting:.es-query',\r\n ];\r\n\r\n /**\r\n```\r\n5. Capture the task manager health API report again via\r\n`/api/task_manager/_health`\r\n6. Notice the number dropped for\r\n`capacity_estimation.value.observed.avg_recurring_required_throughput_per_minute`","sha":"3b670980431da414535940aeeb0088d2ae7ff89c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Task Manager","Team:ResponseOps","v9.0.0","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"Exclude unrecognized tasks from the task manager aggregate API","number":202163,"url":"https://github.com/elastic/kibana/pull/202163","mergeCommit":{"message":"Exclude unrecognized tasks from the task manager aggregate API (#202163)\n\nIn this PR, I'm removing tasks with a status `unrecognized` from\r\nreturning on any `taskStore.aggregate` calls. Without this, we had\r\nunrecognized recurring tasks that were still part of the task manager\r\ncapacity calculation under\r\n`assumedAverageRecurringRequiredThroughputPerMinutePerKibana`.\r\n\r\n## To Verify\r\n1. Create a few ES Query alerting rules running every 1s\r\n2. Capture the task manager health API report via\r\n`/api/task_manager/_health`\r\n3. Apply the following diff to mark es query alerting tasks as\r\nunrecognized\r\n```\r\ndiff --git a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\nindex 1988eebc21a..8d649f4c6a5 100644\r\n--- a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n+++ b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n@@ -10,5 +10,5 @@ import { getRuleType } from './rule_type';\r\n\r\n export function register(params: RegisterRuleTypesParams, isServerless: boolean) {\r\n const { alerting, core } = params;\r\n- alerting.registerType(getRuleType(core, isServerless));\r\n+ // alerting.registerType(getRuleType(core, isServerless));\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\nindex e28d5221e72..dbfc1bbd135 100644\r\n--- a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n+++ b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n@@ -33,6 +33,11 @@ export async function scheduleMarkRemovedTasksAsUnrecognizedDefinition(\r\n state: {},\r\n params: {},\r\n });\r\n+ try {\r\n+ await taskScheduling.runSoon(TASK_ID);\r\n+ } catch (e) {\r\n+ // Ignore\r\n+ }\r\n } catch (e) {\r\n logger.error(`Error scheduling ${TASK_ID} task, received ${e.message}`);\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/task_type_dictionary.ts b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\nindex e0b28eccea3..142c07bb507 100644\r\n--- a/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n+++ b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n@@ -32,6 +32,8 @@ export const REMOVED_TYPES: string[] = [\r\n\r\n 'cleanup_failed_action_executions',\r\n 'reports:monitor',\r\n+\r\n+ 'alerting:.es-query',\r\n ];\r\n\r\n /**\r\n```\r\n5. Capture the task manager health API report again via\r\n`/api/task_manager/_health`\r\n6. Notice the number dropped for\r\n`capacity_estimation.value.observed.avg_recurring_required_throughput_per_minute`","sha":"3b670980431da414535940aeeb0088d2ae7ff89c"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202163","number":202163,"mergeCommit":{"message":"Exclude unrecognized tasks from the task manager aggregate API (#202163)\n\nIn this PR, I'm removing tasks with a status `unrecognized` from\r\nreturning on any `taskStore.aggregate` calls. Without this, we had\r\nunrecognized recurring tasks that were still part of the task manager\r\ncapacity calculation under\r\n`assumedAverageRecurringRequiredThroughputPerMinutePerKibana`.\r\n\r\n## To Verify\r\n1. Create a few ES Query alerting rules running every 1s\r\n2. Capture the task manager health API report via\r\n`/api/task_manager/_health`\r\n3. Apply the following diff to mark es query alerting tasks as\r\nunrecognized\r\n```\r\ndiff --git a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\nindex 1988eebc21a..8d649f4c6a5 100644\r\n--- a/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n+++ b/x-pack/plugins/stack_alerts/server/rule_types/es_query/index.ts\r\n@@ -10,5 +10,5 @@ import { getRuleType } from './rule_type';\r\n\r\n export function register(params: RegisterRuleTypesParams, isServerless: boolean) {\r\n const { alerting, core } = params;\r\n- alerting.registerType(getRuleType(core, isServerless));\r\n+ // alerting.registerType(getRuleType(core, isServerless));\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\nindex e28d5221e72..dbfc1bbd135 100644\r\n--- a/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n+++ b/x-pack/plugins/task_manager/server/removed_tasks/mark_removed_tasks_as_unrecognized.ts\r\n@@ -33,6 +33,11 @@ export async function scheduleMarkRemovedTasksAsUnrecognizedDefinition(\r\n state: {},\r\n params: {},\r\n });\r\n+ try {\r\n+ await taskScheduling.runSoon(TASK_ID);\r\n+ } catch (e) {\r\n+ // Ignore\r\n+ }\r\n } catch (e) {\r\n logger.error(`Error scheduling ${TASK_ID} task, received ${e.message}`);\r\n }\r\ndiff --git a/x-pack/plugins/task_manager/server/task_type_dictionary.ts b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\nindex e0b28eccea3..142c07bb507 100644\r\n--- a/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n+++ b/x-pack/plugins/task_manager/server/task_type_dictionary.ts\r\n@@ -32,6 +32,8 @@ export const REMOVED_TYPES: string[] = [\r\n\r\n 'cleanup_failed_action_executions',\r\n 'reports:monitor',\r\n+\r\n+ 'alerting:.es-query',\r\n ];\r\n\r\n /**\r\n```\r\n5. Capture the task manager health API report again via\r\n`/api/task_manager/_health`\r\n6. Notice the number dropped for\r\n`capacity_estimation.value.observed.avg_recurring_required_throughput_per_minute`","sha":"3b670980431da414535940aeeb0088d2ae7ff89c"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mike Côté <mikecote@users.noreply.github.com> |
||
|
Kibana Machine
|
eb1381bebd
|
[8.16] Expose values of certain task manager configuration settings in the telemetry (#202511) (#202684)
# Backport This will backport the following commits from `main` to `8.16`: - [Expose values of certain task manager configuration settings in the telemetry (#202511)](https://github.com/elastic/kibana/pull/202511) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mike Côté","email":"mikecote@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-03T11:22:23Z","message":"Expose values of certain task manager configuration settings in the telemetry (#202511)\n\nIn this PR, I'm adding some settings to the `exposeToUsage` variable\r\nwhich allows the values of these settings to be reported via telemetry.\r\nThis way we can see what values, ratios, etc a certain setting has.\r\n\r\nSettings to report values instead of `[redacted]`:\r\n- `xpack.task_manager.claim_strategy`\r\n- `xpack.task_manager.discovery.active_nodes_lookback`\r\n- `xpack.task_manager.unsafe.exclude_task_types`","sha":"bca48508144714b678772541a22a6e5f9210f4a5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Task Manager","Team:ResponseOps","v9.0.0","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"Expose values of certain task manager configuration settings in the telemetry","number":202511,"url":"https://github.com/elastic/kibana/pull/202511","mergeCommit":{"message":"Expose values of certain task manager configuration settings in the telemetry (#202511)\n\nIn this PR, I'm adding some settings to the `exposeToUsage` variable\r\nwhich allows the values of these settings to be reported via telemetry.\r\nThis way we can see what values, ratios, etc a certain setting has.\r\n\r\nSettings to report values instead of `[redacted]`:\r\n- `xpack.task_manager.claim_strategy`\r\n- `xpack.task_manager.discovery.active_nodes_lookback`\r\n- `xpack.task_manager.unsafe.exclude_task_types`","sha":"bca48508144714b678772541a22a6e5f9210f4a5"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202511","number":202511,"mergeCommit":{"message":"Expose values of certain task manager configuration settings in the telemetry (#202511)\n\nIn this PR, I'm adding some settings to the `exposeToUsage` variable\r\nwhich allows the values of these settings to be reported via telemetry.\r\nThis way we can see what values, ratios, etc a certain setting has.\r\n\r\nSettings to report values instead of `[redacted]`:\r\n- `xpack.task_manager.claim_strategy`\r\n- `xpack.task_manager.discovery.active_nodes_lookback`\r\n- `xpack.task_manager.unsafe.exclude_task_types`","sha":"bca48508144714b678772541a22a6e5f9210f4a5"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mike Côté <mikecote@users.noreply.github.com> |
||
Agustina Nahir Ruidiaz
|
048f45474c
|
[8.16] [Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413) (#202643)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413)](https://github.com/elastic/kibana/pull/202413) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-02T14:23:56Z","message":"[Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413)\n\n## Summary\r\n\r\nThis PR temporarily fixes the #201799 issue for Serverless.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/604128cb-49b0-4a93-9a15-2a5a0c511883\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"3daaaa5b8c3e3a47b1e29f75df301b42d89caa87","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0"],"number":202413,"url":"https://github.com/elastic/kibana/pull/202413","mergeCommit":{"message":"[Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413)\n\n## Summary\r\n\r\nThis PR temporarily fixes the #201799 issue for Serverless.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/604128cb-49b0-4a93-9a15-2a5a0c511883\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"3daaaa5b8c3e3a47b1e29f75df301b42d89caa87"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202413","number":202413,"mergeCommit":{"message":"[Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413)\n\n## Summary\r\n\r\nThis PR temporarily fixes the #201799 issue for Serverless.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/604128cb-49b0-4a93-9a15-2a5a0c511883\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"3daaaa5b8c3e3a47b1e29f75df301b42d89caa87"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c521832f00
|
[8.16] [Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792) (#202635)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792)](https://github.com/elastic/kibana/pull/201792) <!--- 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-12-02T11:46:04Z","message":"[Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792)\n\n## Release Note\r\n\r\nRestrict and Reject CEF logs in Automatic Import and redirect to CEF\r\nintegration instead.\r\n\r\n## Summary\r\n\r\nCurrently Automatic Import does not handle CEF logs properly and gives\r\nwierd errors.\r\n\r\nThis PR identifies the CEF logs and sends an error popup to\r\nalternatively go for CEF integration instead.\r\n\r\n<img width=\"1229\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\">\r\n\r\n## Testing\r\n\r\nTested this with different types of CEF logs\r\n\r\n```\r\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024 16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups cs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\Finance fname=Finance act=Folder permissions added dvchost= outcome=Success msg=Read & Execute permissions for This folder, subfolders and files (not inherited) was added to Everyone on E:\\\\Share\\\\Share\\\\Finance cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=Read & Execute cs6Label=ChangedPermissions oldFilePermission=None filePermission=Read & Execute dpriv=Everyone start=\r\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024 16:44:31 cat=Alert cs2=Dani Test - access of credentials cs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\B4\\\\Project mgmt\\\\U3 projects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier act=File opened dvchost= outcome=Success msg= cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions oldFilePermission=None filePermission=None dpriv= start=\r\n```\r\n\r\n```\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511 proto=TCP sourceServiceName=httpd requestContext=https://www.google.com src=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443 request=https://www.example.com/cart\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123 src=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice suser=bob destinationTranslatedAddress=10.10.10.10 fileHash=bc8bbe52f041fd17318f08a0f73762ce oldFileHash=a9796280592f86b74b27e370662d41eb\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user dpriv=root\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This event is padded with whitespace dst=192.168.1.2 src=192.168.3.4\r\n```\r\n\r\n```\r\n<163>Apr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\nApr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\n<164>1 2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ]\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- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f6fa94f4768f8a2623fceaaf242ead24a3667ad6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v8.18.0"],"title":"[Automatic Import] Reject CEF logs in Auto Import until it is supported","number":201792,"url":"https://github.com/elastic/kibana/pull/201792","mergeCommit":{"message":"[Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792)\n\n## Release Note\r\n\r\nRestrict and Reject CEF logs in Automatic Import and redirect to CEF\r\nintegration instead.\r\n\r\n## Summary\r\n\r\nCurrently Automatic Import does not handle CEF logs properly and gives\r\nwierd errors.\r\n\r\nThis PR identifies the CEF logs and sends an error popup to\r\nalternatively go for CEF integration instead.\r\n\r\n<img width=\"1229\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\">\r\n\r\n## Testing\r\n\r\nTested this with different types of CEF logs\r\n\r\n```\r\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024 16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups cs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\Finance fname=Finance act=Folder permissions added dvchost= outcome=Success msg=Read & Execute permissions for This folder, subfolders and files (not inherited) was added to Everyone on E:\\\\Share\\\\Share\\\\Finance cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=Read & Execute cs6Label=ChangedPermissions oldFilePermission=None filePermission=Read & Execute dpriv=Everyone start=\r\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024 16:44:31 cat=Alert cs2=Dani Test - access of credentials cs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\B4\\\\Project mgmt\\\\U3 projects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier act=File opened dvchost= outcome=Success msg= cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions oldFilePermission=None filePermission=None dpriv= start=\r\n```\r\n\r\n```\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511 proto=TCP sourceServiceName=httpd requestContext=https://www.google.com src=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443 request=https://www.example.com/cart\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123 src=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice suser=bob destinationTranslatedAddress=10.10.10.10 fileHash=bc8bbe52f041fd17318f08a0f73762ce oldFileHash=a9796280592f86b74b27e370662d41eb\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user dpriv=root\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This event is padded with whitespace dst=192.168.1.2 src=192.168.3.4\r\n```\r\n\r\n```\r\n<163>Apr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\nApr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\n<164>1 2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ]\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- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f6fa94f4768f8a2623fceaaf242ead24a3667ad6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201792","number":201792,"mergeCommit":{"message":"[Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792)\n\n## Release Note\r\n\r\nRestrict and Reject CEF logs in Automatic Import and redirect to CEF\r\nintegration instead.\r\n\r\n## Summary\r\n\r\nCurrently Automatic Import does not handle CEF logs properly and gives\r\nwierd errors.\r\n\r\nThis PR identifies the CEF logs and sends an error popup to\r\nalternatively go for CEF integration instead.\r\n\r\n<img width=\"1229\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\">\r\n\r\n## Testing\r\n\r\nTested this with different types of CEF logs\r\n\r\n```\r\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024 16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups cs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\Finance fname=Finance act=Folder permissions added dvchost= outcome=Success msg=Read & Execute permissions for This folder, subfolders and files (not inherited) was added to Everyone on E:\\\\Share\\\\Share\\\\Finance cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=Read & Execute cs6Label=ChangedPermissions oldFilePermission=None filePermission=Read & Execute dpriv=Everyone start=\r\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3 CEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024 16:44:31 cat=Alert cs2=Dani Test - access of credentials cs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33 duser=zta.local\\\\Dani Lulli (ADMIN) dhost=10.100.20.12 filePath=E:\\\\Share\\\\Share\\\\B4\\\\Project mgmt\\\\U3 projects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier act=File opened dvchost= outcome=Success msg= cs3= cs3Label=AttachmentName cs4= cs4Label=ClientAccessType deviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5= cs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions oldFilePermission=None filePermission=None dpriv= start=\r\n```\r\n\r\n```\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511 proto=TCP sourceServiceName=httpd requestContext=https://www.google.com src=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443 request=https://www.example.com/cart\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123 src=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice suser=bob destinationTranslatedAddress=10.10.10.10 fileHash=bc8bbe52f041fd17318f08a0f73762ce oldFileHash=a9796280592f86b74b27e370662d41eb\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user dpriv=root\r\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This event is padded with whitespace dst=192.168.1.2 src=192.168.3.4\r\n```\r\n\r\n```\r\n<163>Apr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\nApr 1 05:14:15 192.0.2.1 CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc3164\r\n<164>1 2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003-05:00 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n2021-04-01T05:14:15.000003Z 192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web request|low|msg=rfc5424\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ]\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- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f6fa94f4768f8a2623fceaaf242ead24a3667ad6"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/202444","number":202444,"state":"MERGED","mergeCommit":{"sha":"a1cb4c22e82e107313fa8a9c587a9de47a280689","message":"[8.x] [Automatic Import] Reject CEF logs in Auto Import until it is supported (#201792) (#202444)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Automatic Import] Reject CEF logs in Auto Import until it is\nsupported (#201792)](https://github.com/elastic/kibana/pull/201792)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-12-02T11:46:04Z\",\"message\":\"[Automatic\nImport] Reject CEF logs in Auto Import until it is supported\n(#201792)\\n\\n## Release Note\\r\\n\\r\\nRestrict and Reject CEF logs in\nAutomatic Import and redirect to CEF\\r\\nintegration instead.\\r\\n\\r\\n##\nSummary\\r\\n\\r\\nCurrently Automatic Import does not handle CEF logs\nproperly and gives\\r\\nwierd errors.\\r\\n\\r\\nThis PR identifies the CEF\nlogs and sends an error popup to\\r\\nalternatively go for CEF integration\ninstead.\\r\\n\\r\\n<img width=\\\"1229\\\"\nalt=\\\"image\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\\\">\\r\\n\\r\\n##\nTesting\\r\\n\\r\\nTested this with different types of CEF\nlogs\\r\\n\\r\\n```\\r\\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis\nInc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024\n16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups\ncs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance fname=Finance act=Folder\npermissions added dvchost= outcome=Success msg=Read & Execute\npermissions for This folder, subfolders and files (not inherited) was\nadded to Everyone on E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=Read & Execute\ncs6Label=ChangedPermissions oldFilePermission=None filePermission=Read &\nExecute dpriv=Everyone start=\\r\\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3\nCEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024\n16:44:31 cat=Alert cs2=Dani Test - access of credentials\ncs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\B4\\\\\\\\Project mgmt\\\\\\\\U3\nprojects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier\nact=File opened dvchost= outcome=Success msg= cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions\noldFilePermission=None filePermission=None dpriv=\nstart=\\r\\n```\\r\\n\\r\\n```\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511\nproto=TCP sourceServiceName=httpd requestContext=https://www.google.com\nsrc=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443\nrequest=https://www.example.com/cart\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123\nsrc=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice\nsuser=bob destinationTranslatedAddress=10.10.10.10\nfileHash=bc8bbe52f041fd17318f08a0f73762ce\noldFileHash=a9796280592f86b74b27e370662d41eb\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user\ndpriv=root\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This\nevent is padded with whitespace dst=192.168.1.2\nsrc=192.168.3.4\\r\\n```\\r\\n\\r\\n```\\r\\n<163>Apr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\nApr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\n<164>1 2021-04-01T05:14:15.000003-05:00\n192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003-05:00 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n```\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR\nsatisfies following conditions. \\r\\n\\r\\nReviewers should verify this PR\nsatisfies this list as well.\\r\\n\\r\\n- [x] Any text added follows [EUI's\nwriting\\r\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\r\\nsentence case text and includes\n[i18n\\r\\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\\r\\n-\n[\n]\\r\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\r\\nwas\nadded for features that require explanation or tutorials\\r\\n- [x] [Unit\nor\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [x] The PR\ndescription includes the appropriate Release Notes section,\\r\\nand the\ncorrect `release_note:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"f6fa94f4768f8a2623fceaaf242ead24a3667ad6\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"backport:prev-minor\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\"],\"title\":\"[Automatic\nImport] Reject CEF logs in Auto Import until it is\nsupported\",\"number\":201792,\"url\":\"https://github.com/elastic/kibana/pull/201792\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Reject CEF logs in Auto Import until it is supported\n(#201792)\\n\\n## Release Note\\r\\n\\r\\nRestrict and Reject CEF logs in\nAutomatic Import and redirect to CEF\\r\\nintegration instead.\\r\\n\\r\\n##\nSummary\\r\\n\\r\\nCurrently Automatic Import does not handle CEF logs\nproperly and gives\\r\\nwierd errors.\\r\\n\\r\\nThis PR identifies the CEF\nlogs and sends an error popup to\\r\\nalternatively go for CEF integration\ninstead.\\r\\n\\r\\n<img width=\\\"1229\\\"\nalt=\\\"image\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\\\">\\r\\n\\r\\n##\nTesting\\r\\n\\r\\nTested this with different types of CEF\nlogs\\r\\n\\r\\n```\\r\\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis\nInc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024\n16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups\ncs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance fname=Finance act=Folder\npermissions added dvchost= outcome=Success msg=Read & Execute\npermissions for This folder, subfolders and files (not inherited) was\nadded to Everyone on E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=Read & Execute\ncs6Label=ChangedPermissions oldFilePermission=None filePermission=Read &\nExecute dpriv=Everyone start=\\r\\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3\nCEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024\n16:44:31 cat=Alert cs2=Dani Test - access of credentials\ncs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\B4\\\\\\\\Project mgmt\\\\\\\\U3\nprojects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier\nact=File opened dvchost= outcome=Success msg= cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions\noldFilePermission=None filePermission=None dpriv=\nstart=\\r\\n```\\r\\n\\r\\n```\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511\nproto=TCP sourceServiceName=httpd requestContext=https://www.google.com\nsrc=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443\nrequest=https://www.example.com/cart\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123\nsrc=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice\nsuser=bob destinationTranslatedAddress=10.10.10.10\nfileHash=bc8bbe52f041fd17318f08a0f73762ce\noldFileHash=a9796280592f86b74b27e370662d41eb\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user\ndpriv=root\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This\nevent is padded with whitespace dst=192.168.1.2\nsrc=192.168.3.4\\r\\n```\\r\\n\\r\\n```\\r\\n<163>Apr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\nApr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\n<164>1 2021-04-01T05:14:15.000003-05:00\n192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003-05:00 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n```\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR\nsatisfies following conditions. \\r\\n\\r\\nReviewers should verify this PR\nsatisfies this list as well.\\r\\n\\r\\n- [x] Any text added follows [EUI's\nwriting\\r\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\r\\nsentence case text and includes\n[i18n\\r\\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\\r\\n-\n[\n]\\r\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\r\\nwas\nadded for features that require explanation or tutorials\\r\\n- [x] [Unit\nor\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [x] The PR\ndescription includes the appropriate Release Notes section,\\r\\nand the\ncorrect `release_note:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"f6fa94f4768f8a2623fceaaf242ead24a3667ad6\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201792\",\"number\":201792,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Reject CEF logs in Auto Import until it is supported\n(#201792)\\n\\n## Release Note\\r\\n\\r\\nRestrict and Reject CEF logs in\nAutomatic Import and redirect to CEF\\r\\nintegration instead.\\r\\n\\r\\n##\nSummary\\r\\n\\r\\nCurrently Automatic Import does not handle CEF logs\nproperly and gives\\r\\nwierd errors.\\r\\n\\r\\nThis PR identifies the CEF\nlogs and sends an error popup to\\r\\nalternatively go for CEF integration\ninstead.\\r\\n\\r\\n<img width=\\\"1229\\\"\nalt=\\\"image\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/59037dd4-323a-476a-9747-950fbc6e384d\\\">\\r\\n\\r\\n##\nTesting\\r\\n\\r\\nTested this with different types of CEF\nlogs\\r\\n\\r\\n```\\r\\n<14>Nov 22 16:19:13 ABQ-ZTA-VRNS-3 CEF:0|Varonis\nInc.|DatAdvantage|8.6.51|6000|Folder permissions added|3|rt=Nov 22 2024\n16:19:09 cat=Alert cs2=Permissions granted to Global Access Groups\ncs2Label=RuleName cn1=132 cn1Label=RuleID end=Nov 22 2024 16:19:05\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance fname=Finance act=Folder\npermissions added dvchost= outcome=Success msg=Read & Execute\npermissions for This folder, subfolders and files (not inherited) was\nadded to Everyone on E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\Finance cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=Read & Execute\ncs6Label=ChangedPermissions oldFilePermission=None filePermission=Read &\nExecute dpriv=Everyone start=\\r\\n<14>Nov 22 16:44:31 ABQ-ZTA-VRNS-3\nCEF:0|Varonis Inc.|DatAdvantage|8.6.51|1|File opened|2|rt=Nov 22 2024\n16:44:31 cat=Alert cs2=Dani Test - access of credentials\ncs2Label=RuleName cn1=184 cn1Label=RuleID end=Nov 22 2024 16:34:33\nduser=zta.local\\\\\\\\Dani Lulli (ADMIN) dhost=10.100.20.12\nfilePath=E:\\\\\\\\Share\\\\\\\\Share\\\\\\\\B4\\\\\\\\Project mgmt\\\\\\\\U3\nprojects11.txt:Zone.Identifier fname=U3 projects11.txt:Zone.Identifier\nact=File opened dvchost= outcome=Success msg= cs3=\ncs3Label=AttachmentName cs4= cs4Label=ClientAccessType\ndeviceCustomDate1= fileType= cs1= cs1Label=MailRecipient suser= cs5=\ncs5Label=MailboxAccessType cnt= cs6=None cs6Label=ChangedPermissions\noldFilePermission=None filePermission=None dpriv=\nstart=\\r\\n```\\r\\n\\r\\n```\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|eventId=3457 requestMethod=POST slat=38.915 slong=-77.511\nproto=TCP sourceServiceName=httpd requestContext=https://www.google.com\nsrc=89.160.20.156 spt=33876 dst=192.168.10.1 dpt=443\nrequest=https://www.example.com/cart\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|eventId=123\nsrc=89.160.20.156 spt=33876 dst=89.160.20.156 dpt=443 duser=alice\nsuser=bob destinationTranslatedAddress=10.10.10.10\nfileHash=bc8bbe52f041fd17318f08a0f73762ce\noldFileHash=a9796280592f86b74b27e370662d41eb\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|spriv=user\ndpriv=root\\r\\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Authentication|low|message=This\nevent is padded with whitespace dst=192.168.1.2\nsrc=192.168.3.4\\r\\n```\\r\\n\\r\\n```\\r\\n<163>Apr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\nApr 1 05:14:15 192.0.2.1\nCEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc3164\\r\\n<164>1 2021-04-01T05:14:15.000003-05:00\n192.0.2.1 rfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003-05:00 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n<165>1 2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n2021-04-01T05:14:15.000003Z 192.0.2.1\nrfc5424App 8710 - - CEF:0|Elastic|Vaporware|1.0.0-alpha|18|Web\nrequest|low|msg=rfc5424\\r\\n```\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR\nsatisfies following conditions. \\r\\n\\r\\nReviewers should verify this PR\nsatisfies this list as well.\\r\\n\\r\\n- [x] Any text added follows [EUI's\nwriting\\r\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\r\\nsentence case text and includes\n[i18n\\r\\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\\r\\n-\n[\n]\\r\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\r\\nwas\nadded for features that require explanation or tutorials\\r\\n- [x] [Unit\nor\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [x] The PR\ndescription includes the appropriate Release Notes section,\\r\\nand the\ncorrect `release_note:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"f6fa94f4768f8a2623fceaaf242ead24a3667ad6\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
Kibana Machine
|
2faee8a967
|
[8.16] [Search][Connectors] Disable Elastic managed option when running Kibana locally (#201950) (#202589)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search][Connectors] Disable Elastic managed option when running Kibana locally (#201950)](https://github.com/elastic/kibana/pull/201950) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2024-12-02T21:37:01Z","message":"[Search][Connectors] Disable Elastic managed option when running Kibana locally (#201950)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ option when creating a connector\r\nwhile running Kibana locally. We also inform and encourage users to get\r\na Cloud trial taking them to\r\nhttps://cloud.elastic.co/registration?onboarding_token=connectors If the\r\nuser finish up the registration process he will en up in the\r\n`/app/enterprise_search/content/connectors` in product connectors\r\nsection.\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b5273734317b6278b015851b396d0b4c4edcc571","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[Search][Connectors] Disable Elastic managed option when running Kibana locally","number":201950,"url":"https://github.com/elastic/kibana/pull/201950","mergeCommit":{"message":"[Search][Connectors] Disable Elastic managed option when running Kibana locally (#201950)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ option when creating a connector\r\nwhile running Kibana locally. We also inform and encourage users to get\r\na Cloud trial taking them to\r\nhttps://cloud.elastic.co/registration?onboarding_token=connectors If the\r\nuser finish up the registration process he will en up in the\r\n`/app/enterprise_search/content/connectors` in product connectors\r\nsection.\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b5273734317b6278b015851b396d0b4c4edcc571"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201950","number":201950,"mergeCommit":{"message":"[Search][Connectors] Disable Elastic managed option when running Kibana locally (#201950)\n\n## Summary\r\n\r\nThis PR disables the _Elastic managed_ option when creating a connector\r\nwhile running Kibana locally. We also inform and encourage users to get\r\na Cloud trial taking them to\r\nhttps://cloud.elastic.co/registration?onboarding_token=connectors If the\r\nuser finish up the registration process he will en up in the\r\n`/app/enterprise_search/content/connectors` in product connectors\r\nsection.\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"b5273734317b6278b015851b396d0b4c4edcc571"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: José Luis González <joseluisgj@gmail.com> |
||
|
Kibana Machine
|
3eeb9f17ee
|
[8.16] [Synthetics] Fix to handle ops genie as default connector !! (#201923) (#202571)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fix to handle ops genie as default connector !! (#201923)](https://github.com/elastic/kibana/pull/201923) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-02T19:20:26Z","message":"[Synthetics] Fix to handle ops genie as default connector !! (#201923)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/168681\r\n\r\nFix to handle ops genie as default connector !!\r\n\r\nTested by creating a trail account in ops genie \r\n\r\n<img width=\"1712\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ec768758-0fd3-4e3e-bb16-2bc11f10f6b7\">","sha":"a674b9d043faf58494feda039bb2a563c9f4d661","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[Synthetics] Fix to handle ops genie as default connector !!","number":201923,"url":"https://github.com/elastic/kibana/pull/201923","mergeCommit":{"message":"[Synthetics] Fix to handle ops genie as default connector !! (#201923)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/168681\r\n\r\nFix to handle ops genie as default connector !!\r\n\r\nTested by creating a trail account in ops genie \r\n\r\n<img width=\"1712\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ec768758-0fd3-4e3e-bb16-2bc11f10f6b7\">","sha":"a674b9d043faf58494feda039bb2a563c9f4d661"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201923","number":201923,"mergeCommit":{"message":"[Synthetics] Fix to handle ops genie as default connector !! (#201923)\n\n## Summary\r\n\r\nfixes https://github.com/elastic/kibana/issues/168681\r\n\r\nFix to handle ops genie as default connector !!\r\n\r\nTested by creating a trail account in ops genie \r\n\r\n<img width=\"1712\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ec768758-0fd3-4e3e-bb16-2bc11f10f6b7\">","sha":"a674b9d043faf58494feda039bb2a563c9f4d661"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
515bcb0d57
|
[8.16] [Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515) (#202568)
# Backport This will backport the following commits from `main` to `8.16`: - [[Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515)](https://github.com/elastic/kibana/pull/202515) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-02T19:01:56Z","message":"[Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515)\n\n## Summary\r\n\r\n- Changed Crowdstrike and SentinelOne connectors to no longer validate\r\nAPI responses from the external system","sha":"35fb69e11602173f54b3e61341bb31b8fe8317bc","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:prev-minor","v8.17.0","v8.16.2"],"title":"[Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses","number":202515,"url":"https://github.com/elastic/kibana/pull/202515","mergeCommit":{"message":"[Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515)\n\n## Summary\r\n\r\n- Changed Crowdstrike and SentinelOne connectors to no longer validate\r\nAPI responses from the external system","sha":"35fb69e11602173f54b3e61341bb31b8fe8317bc"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202515","number":202515,"mergeCommit":{"message":"[Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515)\n\n## Summary\r\n\r\n- Changed Crowdstrike and SentinelOne connectors to no longer validate\r\nAPI responses from the external system","sha":"35fb69e11602173f54b3e61341bb31b8fe8317bc"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com> |
||
|
Kibana Machine
|
216722b05c
|
[8.16] [Security solution] Remove legacy ESQL quick prompt (#201276) (#202540)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security solution] Remove legacy ESQL quick prompt (#201276)](https://github.com/elastic/kibana/pull/201276) <!--- 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-12-02T16:47:18Z","message":"[Security solution] Remove legacy ESQL quick prompt (#201276)","sha":"30ceb1a0533364e6915bf544827d59cf441bcbf5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-major","Team:Security Generative AI"],"title":"[Security solution] Remove legacy ESQL quick prompt","number":201276,"url":"https://github.com/elastic/kibana/pull/201276","mergeCommit":{"message":"[Security solution] Remove legacy ESQL quick prompt (#201276)","sha":"30ceb1a0533364e6915bf544827d59cf441bcbf5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201276","number":201276,"mergeCommit":{"message":"[Security solution] Remove legacy ESQL quick prompt (#201276)","sha":"30ceb1a0533364e6915bf544827d59cf441bcbf5"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
264b11d91c
|
[8.16] [Synthetics TLS certificate] Fix error when opening rule flyout (#202386) (#202525)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics TLS certificate] Fix error when opening rule flyout (#202386)](https://github.com/elastic/kibana/pull/202386) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bena Kansara","email":"69037875+benakansara@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-12-02T16:11:12Z","message":"[Synthetics TLS certificate] Fix error when opening rule flyout (#202386)\n\nFixes https://github.com/elastic/kibana/issues/188828","sha":"c4dc230f2ee3da6568d58e4f7caf2daba2ad842f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[Synthetics TLS certificate] Fix error when opening rule flyout","number":202386,"url":"https://github.com/elastic/kibana/pull/202386","mergeCommit":{"message":"[Synthetics TLS certificate] Fix error when opening rule flyout (#202386)\n\nFixes https://github.com/elastic/kibana/issues/188828","sha":"c4dc230f2ee3da6568d58e4f7caf2daba2ad842f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202386","number":202386,"mergeCommit":{"message":"[Synthetics TLS certificate] Fix error when opening rule flyout (#202386)\n\nFixes https://github.com/elastic/kibana/issues/188828","sha":"c4dc230f2ee3da6568d58e4f7caf2daba2ad842f"}}]}] BACKPORT--> Co-authored-by: Bena Kansara <69037875+benakansara@users.noreply.github.com> |
||
Jatin Kathuria
|
06b1474424
|
[8.16] [Security Solution] Adds callback onUpdatePageIndex to get current pageIndex in Unified Data table (#201240) (#202349)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Adds callback `onUpdatePageIndex` to get current `pageIndex` in Unified Data table (#201240)](https://github.com/elastic/kibana/pull/201240) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2024-11-29T15:14:27Z","message":"[Security Solution] Adds callback `onUpdatePageIndex` to get current `pageIndex` in Unified Data table (#201240)\n\n## Summary\n\nHandles resolution for\n- Notes fetching data for all Timeline Records which leads to\nperformance issues.\n- https://github.com/elastic/kibana/issues/201330 \n\n## Issue - Notes fetching data for all Timeline Records \n\nCurrently, there was no way for consumer of `UnifiedDataGrid` to get the\ncurrent `pageIndex`. Security Solution needs to get the current\n`pageIndex` so the items on the current page can be calculated.\n\n@elastic/kibana-data-discovery , please let us know if you have any\nopinion here.\n\nThis results in notes being fetched for all Timeline Records which means\nminimum of 500 records and if user has queries 5000 records ( for\nexample ), a request will be made to query notes for all those 5000\nnotes which leads to performance issue and sometimes error as shown\nbelow:\n\n\n\n\n\n## 👨💻 Changes\n\nThis adds attribute `pageIndex` to timeline state. \n\n```javascript\n{\n \"pageIndex\": number\n}\n```\n`pageIndex` helps with getting the events for that particular page.\n\n## 🟡 Caveat\n\n- Currently this `pageIndex` is shared between Query and EQL tabs which\ncan lead to wonky behavior at time.\n- Additionally, as of now table maintains its own page index and\nconsumer component cannot effect the `pageIndex` of the UnifiedDataGrid.","sha":"de9d5465df5900936991d79306cb2cbbe63f4623","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","v8.16.2"],"number":201240,"url":"https://github.com/elastic/kibana/pull/201240","mergeCommit":{"message":"[Security Solution] Adds callback `onUpdatePageIndex` to get current `pageIndex` in Unified Data table (#201240)\n\n## Summary\n\nHandles resolution for\n- Notes fetching data for all Timeline Records which leads to\nperformance issues.\n- https://github.com/elastic/kibana/issues/201330 \n\n## Issue - Notes fetching data for all Timeline Records \n\nCurrently, there was no way for consumer of `UnifiedDataGrid` to get the\ncurrent `pageIndex`. Security Solution needs to get the current\n`pageIndex` so the items on the current page can be calculated.\n\n@elastic/kibana-data-discovery , please let us know if you have any\nopinion here.\n\nThis results in notes being fetched for all Timeline Records which means\nminimum of 500 records and if user has queries 5000 records ( for\nexample ), a request will be made to query notes for all those 5000\nnotes which leads to performance issue and sometimes error as shown\nbelow:\n\n\n\n\n\n## 👨💻 Changes\n\nThis adds attribute `pageIndex` to timeline state. \n\n```javascript\n{\n \"pageIndex\": number\n}\n```\n`pageIndex` helps with getting the events for that particular page.\n\n## 🟡 Caveat\n\n- Currently this `pageIndex` is shared between Query and EQL tabs which\ncan lead to wonky behavior at time.\n- Additionally, as of now table maintains its own page index and\nconsumer component cannot effect the `pageIndex` of the UnifiedDataGrid.","sha":"de9d5465df5900936991d79306cb2cbbe63f4623"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201240","number":201240,"mergeCommit":{"message":"[Security Solution] Adds callback `onUpdatePageIndex` to get current `pageIndex` in Unified Data table (#201240)\n\n## Summary\n\nHandles resolution for\n- Notes fetching data for all Timeline Records which leads to\nperformance issues.\n- https://github.com/elastic/kibana/issues/201330 \n\n## Issue - Notes fetching data for all Timeline Records \n\nCurrently, there was no way for consumer of `UnifiedDataGrid` to get the\ncurrent `pageIndex`. Security Solution needs to get the current\n`pageIndex` so the items on the current page can be calculated.\n\n@elastic/kibana-data-discovery , please let us know if you have any\nopinion here.\n\nThis results in notes being fetched for all Timeline Records which means\nminimum of 500 records and if user has queries 5000 records ( for\nexample ), a request will be made to query notes for all those 5000\nnotes which leads to performance issue and sometimes error as shown\nbelow:\n\n\n\n\n\n## 👨💻 Changes\n\nThis adds attribute `pageIndex` to timeline state. \n\n```javascript\n{\n \"pageIndex\": number\n}\n```\n`pageIndex` helps with getting the events for that particular page.\n\n## 🟡 Caveat\n\n- Currently this `pageIndex` is shared between Query and EQL tabs which\ncan lead to wonky behavior at time.\n- Additionally, as of now table maintains its own page index and\nconsumer component cannot effect the `pageIndex` of the UnifiedDataGrid.","sha":"de9d5465df5900936991d79306cb2cbbe63f4623"}},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Cauê Marcondes
|
9c1a1025a2
|
[8.16] [Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403) (#202420)
# Backport This will backport the following commits from `main` to `8.16`: - [[Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403)](https://github.com/elastic/kibana/pull/201403) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-25T15:51:23Z","message":"[Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403)\n\ncloses https://github.com/elastic/kibana/issues/180036\r\n\r\nThe logic now, first checks if there are `container.ids` on the selected\r\nservice, if not, it falls back to the `host.name` or `host.hostname`.\r\n\r\n## container.id\r\n<img width=\"1320\" alt=\"Screenshot 2024-11-25 at 10 53 44\"\r\nsrc=\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\">\r\n<img width=\"1300\" alt=\"Screenshot 2024-11-25 at 10 53 55\"\r\nsrc=\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\">\r\n<img width=\"1303\" alt=\"Screenshot 2024-11-25 at 11 06 55\"\r\nsrc=\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\">\r\n\r\n\r\n## host.name\r\n<img width=\"1314\" alt=\"Screenshot 2024-11-25 at 11 02 49\"\r\nsrc=\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\">\r\n<img width=\"1326\" alt=\"Screenshot 2024-11-25 at 11 03 00\"\r\nsrc=\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\">\r\n<img width=\"1342\" alt=\"Screenshot 2024-11-25 at 11 03 08\"\r\nsrc=\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\">\r\n\r\n## host.hostname\r\n<img width=\"1323\" alt=\"Screenshot 2024-11-25 at 11 04 24\"\r\nsrc=\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\">\r\n<img width=\"1321\" alt=\"Screenshot 2024-11-25 at 11 04 34\"\r\nsrc=\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\">\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-25 at 11 04 51\"\r\nsrc=\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\">","sha":"ff97e5234b58599a503c76549f41afb6ce595dc5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.17.0","v8.18.0"],"number":201403,"url":"https://github.com/elastic/kibana/pull/201403","mergeCommit":{"message":"[Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403)\n\ncloses https://github.com/elastic/kibana/issues/180036\r\n\r\nThe logic now, first checks if there are `container.ids` on the selected\r\nservice, if not, it falls back to the `host.name` or `host.hostname`.\r\n\r\n## container.id\r\n<img width=\"1320\" alt=\"Screenshot 2024-11-25 at 10 53 44\"\r\nsrc=\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\">\r\n<img width=\"1300\" alt=\"Screenshot 2024-11-25 at 10 53 55\"\r\nsrc=\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\">\r\n<img width=\"1303\" alt=\"Screenshot 2024-11-25 at 11 06 55\"\r\nsrc=\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\">\r\n\r\n\r\n## host.name\r\n<img width=\"1314\" alt=\"Screenshot 2024-11-25 at 11 02 49\"\r\nsrc=\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\">\r\n<img width=\"1326\" alt=\"Screenshot 2024-11-25 at 11 03 00\"\r\nsrc=\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\">\r\n<img width=\"1342\" alt=\"Screenshot 2024-11-25 at 11 03 08\"\r\nsrc=\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\">\r\n\r\n## host.hostname\r\n<img width=\"1323\" alt=\"Screenshot 2024-11-25 at 11 04 24\"\r\nsrc=\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\">\r\n<img width=\"1321\" alt=\"Screenshot 2024-11-25 at 11 04 34\"\r\nsrc=\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\">\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-25 at 11 04 51\"\r\nsrc=\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\">","sha":"ff97e5234b58599a503c76549f41afb6ce595dc5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201403","number":201403,"mergeCommit":{"message":"[Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403)\n\ncloses https://github.com/elastic/kibana/issues/180036\r\n\r\nThe logic now, first checks if there are `container.ids` on the selected\r\nservice, if not, it falls back to the `host.name` or `host.hostname`.\r\n\r\n## container.id\r\n<img width=\"1320\" alt=\"Screenshot 2024-11-25 at 10 53 44\"\r\nsrc=\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\">\r\n<img width=\"1300\" alt=\"Screenshot 2024-11-25 at 10 53 55\"\r\nsrc=\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\">\r\n<img width=\"1303\" alt=\"Screenshot 2024-11-25 at 11 06 55\"\r\nsrc=\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\">\r\n\r\n\r\n## host.name\r\n<img width=\"1314\" alt=\"Screenshot 2024-11-25 at 11 02 49\"\r\nsrc=\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\">\r\n<img width=\"1326\" alt=\"Screenshot 2024-11-25 at 11 03 00\"\r\nsrc=\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\">\r\n<img width=\"1342\" alt=\"Screenshot 2024-11-25 at 11 03 08\"\r\nsrc=\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\">\r\n\r\n## host.hostname\r\n<img width=\"1323\" alt=\"Screenshot 2024-11-25 at 11 04 24\"\r\nsrc=\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\">\r\n<img width=\"1321\" alt=\"Screenshot 2024-11-25 at 11 04 34\"\r\nsrc=\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\">\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-25 at 11 04 51\"\r\nsrc=\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\">","sha":"ff97e5234b58599a503c76549f41afb6ce595dc5"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/201635","number":201635,"state":"MERGED","mergeCommit":{"sha":"86288e107d47e0e345bea9cfdde839e457712266","message":"[8.17] [Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403) (#201635)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Profiling x APM Integration] Use both host.hostname or host.name and\ncontainer.id to correlate profiling data on APM\n(#201403)](https://github.com/elastic/kibana/pull/201403)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Cauê\nMarcondes\",\"email\":\"55978943+cauemarcondes@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-25T15:51:23Z\",\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"ci:project-deploy-observability\",\"Team:obs-ux-infra_services\",\"v8.17.0\"],\"title\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on\nAPM\",\"number\":201403,\"url\":\"https://github.com/elastic/kibana/pull/201403\",\"mergeCommit\":{\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201403\",\"number\":201403,\"mergeCommit\":{\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/201636","number":201636,"state":"MERGED","mergeCommit":{"sha":"522f57387ba55e7dd66eb7c5b525a110ab0db04c","message":"[8.x] [Profiling x APM Integration] Use both host.hostname or host.name and container.id to correlate profiling data on APM (#201403) (#201636)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Profiling x APM Integration] Use both host.hostname or host.name and\ncontainer.id to correlate profiling data on APM\n(#201403)](https://github.com/elastic/kibana/pull/201403)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Cauê\nMarcondes\",\"email\":\"55978943+cauemarcondes@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-25T15:51:23Z\",\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"ci:project-deploy-observability\",\"Team:obs-ux-infra_services\",\"v8.17.0\"],\"title\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on\nAPM\",\"number\":201403,\"url\":\"https://github.com/elastic/kibana/pull/201403\",\"mergeCommit\":{\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/201403\",\"number\":201403,\"mergeCommit\":{\"message\":\"[Profiling\nx APM Integration] Use both host.hostname or host.name and container.id\nto correlate profiling data on APM (#201403)\\n\\ncloses\nhttps://github.com/elastic/kibana/issues/180036\\r\\n\\r\\nThe logic now,\nfirst checks if there are `container.ids` on the selected\\r\\nservice, if\nnot, it falls back to the `host.name` or `host.hostname`.\\r\\n\\r\\n##\ncontainer.id\\r\\n<img width=\\\"1320\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n44\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/b0515e7a-0319-4d88-bf39-3fbbba3ad957\\\">\\r\\n<img\nwidth=\\\"1300\\\" alt=\\\"Screenshot 2024-11-25 at 10 53\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/66ceacfd-dc36-4f18-bdfa-67f656d41d36\\\">\\r\\n<img\nwidth=\\\"1303\\\" alt=\\\"Screenshot 2024-11-25 at 11 06\n55\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/57516d46-b2ee-41d4-9710-74a8b36124a9\\\">\\r\\n\\r\\n\\r\\n##\nhost.name\\r\\n<img width=\\\"1314\\\" alt=\\\"Screenshot 2024-11-25 at 11 02\n49\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5b7c0cdf-267a-4874-bb29-b9ddba8fb53f\\\">\\r\\n<img\nwidth=\\\"1326\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n00\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/ab8eb946-4513-4b4b-8775-6b8be7fe6957\\\">\\r\\n<img\nwidth=\\\"1342\\\" alt=\\\"Screenshot 2024-11-25 at 11 03\n08\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/80017155-5bcb-4154-91ca-52b154b945b2\\\">\\r\\n\\r\\n##\nhost.hostname\\r\\n<img width=\\\"1323\\\" alt=\\\"Screenshot 2024-11-25 at 11\n04\n24\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/a2a8df63-4049-463e-8bc2-88b7c05c727b\\\">\\r\\n<img\nwidth=\\\"1321\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n34\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/29d6532c-8027-4eb4-88bd-46d32ea56353\\\">\\r\\n<img\nwidth=\\\"1311\\\" alt=\\\"Screenshot 2024-11-25 at 11 04\n51\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/897bd883-014e-4d95-8ed6-d2263eceb490\\\">\",\"sha\":\"ff97e5234b58599a503c76549f41afb6ce595dc5\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>"}}]}] BACKPORT--> |
||
Mike Côté
|
7ed9a663bc
|
[8.16] Set refresh according to stateful vs stateless when indexing alert documents (#201209) (#202222)
# Backport This will backport the following commits from `main` to `8.16`: - [Set refresh according to stateful vs stateless when indexing alert documents (#201209)](https://github.com/elastic/kibana/pull/201209) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mike Côté","email":"mikecote@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-28T17:10:56Z","message":"Set refresh according to stateful vs stateless when indexing alert documents (#201209)\n\nIn this PR, I'm making the change so when Kibana is running with\r\nElasticsearch stateful we set refresh to `wait_for` (instead of `true`)\r\nso we are not putting too much pressure on the Elasticsearch indices\r\nwhen under load.\r\n\r\n## To verify\r\n\r\nVery using the Cloud deployment and Serverless project created from this\r\nPR\r\n\r\n1. Create an always firing ES Query rule\r\n2. Create an always firing security detection rule w/ alert suppression\r\n3. Verify the ECH cluster logs and observe `*** Refresh value when\r\nindexing alerts: wait_for` and `*** Rule registry - refresh value when\r\nindexing alerts: wait_for` messages\r\n4. Verify the serverless project logs on QA overview and observe `***\r\nRefresh value when indexing alerts: true` and `*** Rule registry -\r\nrefresh value when indexing alerts: true` messages\r\n\r\n## To-Do\r\n\r\n- [x] Revert commit\r\n |
||
|
Kibana Machine
|
60efa2c292
|
[8.16] [Fleet] Fix agent policy mappings for space awareness (#201689) (#202239)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] Fix agent policy mappings for space awareness (#201689)](https://github.com/elastic/kibana/pull/201689) <!--- 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-11-28T22:11:10Z","message":"[Fleet] Fix agent policy mappings for space awareness (#201689)","sha":"721b4beb1ae7f12171a34d50ba6068b8c2d7288e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","v8.17.0","v8.16.2"],"title":"[Fleet] Fix agent policy mappings for space awareness","number":201689,"url":"https://github.com/elastic/kibana/pull/201689","mergeCommit":{"message":"[Fleet] Fix agent policy mappings for space awareness (#201689)","sha":"721b4beb1ae7f12171a34d50ba6068b8c2d7288e"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201689","number":201689,"mergeCommit":{"message":"[Fleet] Fix agent policy mappings for space awareness (#201689)","sha":"721b4beb1ae7f12171a34d50ba6068b8c2d7288e"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
2e1ed36c0a
|
[8.16] [ML] Trained Models: Show deployment stats for unallocated deployments (#202005) (#202166)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)](https://github.com/elastic/kibana/pull/202005) <!--- 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-11-28T13:22:31Z","message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","ci:cloud-deploy","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Models: Show deployment stats for unallocated deployments ","number":202005,"url":"https://github.com/elastic/kibana/pull/202005","mergeCommit":{"message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202005","number":202005,"mergeCommit":{"message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
Jean-Louis Leysens
|
1796fcd71c
|
[8.16] [UA] Update wizard copy to callout "x.last" (#201633) (#202112)
# Backport This will backport the following commits from `main` to `8.16`: - [[UA] Update wizard copy to callout "x.last" (#201633)](https://github.com/elastic/kibana/pull/201633) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2024-11-27T14:42:01Z","message":"[UA] Update wizard copy to callout \"x.last\" (#201633)\n\n## Summary\r\n\r\nWe want to make sure users for the upgrade assistant are aware that the\r\nonly way to safely perform a major version upgrade is to upgrade to the\r\nlatest minor of the major they are on.\r\n\r\n\r\n### Current\r\n<img width=\"1258\" alt=\"Screenshot 2024-11-25 at 16 44 37\"\r\nsrc=\"https://github.com/user-attachments/assets/ad114e44-82f4-4afd-98b4-0fe307c8175b\">\r\n\r\n### Next\r\n\r\n<img width=\"1265\" alt=\"Screenshot 2024-11-27 at 13 52 30\"\r\nsrc=\"https://github.com/user-attachments/assets/b02b54a0-cb9e-439e-9218-f1ebe813c1fa\">\r\n\r\n\r\nRelated https://github.com/elastic/kibana/issues/201377\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"e3c532b54a1e79c92e4df0c7006fccec61f40bf1","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Kibana Management","release_note:skip","Feature:Upgrade Assistant","v9.0.0","backport:version","v8.17.0","v7.17.26","v8.18.0","v8.15.5","v8.16.2"],"number":201633,"url":"https://github.com/elastic/kibana/pull/201633","mergeCommit":{"message":"[UA] Update wizard copy to callout \"x.last\" (#201633)\n\n## Summary\r\n\r\nWe want to make sure users for the upgrade assistant are aware that the\r\nonly way to safely perform a major version upgrade is to upgrade to the\r\nlatest minor of the major they are on.\r\n\r\n\r\n### Current\r\n<img width=\"1258\" alt=\"Screenshot 2024-11-25 at 16 44 37\"\r\nsrc=\"https://github.com/user-attachments/assets/ad114e44-82f4-4afd-98b4-0fe307c8175b\">\r\n\r\n### Next\r\n\r\n<img width=\"1265\" alt=\"Screenshot 2024-11-27 at 13 52 30\"\r\nsrc=\"https://github.com/user-attachments/assets/b02b54a0-cb9e-439e-9218-f1ebe813c1fa\">\r\n\r\n\r\nRelated https://github.com/elastic/kibana/issues/201377\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"e3c532b54a1e79c92e4df0c7006fccec61f40bf1"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","7.17","8.x","8.15","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201633","number":201633,"mergeCommit":{"message":"[UA] Update wizard copy to callout \"x.last\" (#201633)\n\n## Summary\r\n\r\nWe want to make sure users for the upgrade assistant are aware that the\r\nonly way to safely perform a major version upgrade is to upgrade to the\r\nlatest minor of the major they are on.\r\n\r\n\r\n### Current\r\n<img width=\"1258\" alt=\"Screenshot 2024-11-25 at 16 44 37\"\r\nsrc=\"https://github.com/user-attachments/assets/ad114e44-82f4-4afd-98b4-0fe307c8175b\">\r\n\r\n### Next\r\n\r\n<img width=\"1265\" alt=\"Screenshot 2024-11-27 at 13 52 30\"\r\nsrc=\"https://github.com/user-attachments/assets/b02b54a0-cb9e-439e-9218-f1ebe813c1fa\">\r\n\r\n\r\nRelated https://github.com/elastic/kibana/issues/201377\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\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- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"e3c532b54a1e79c92e4df0c7006fccec61f40bf1"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.26","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.5","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c3f9d61643
|
[8.16] [Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546) (#202136)
# Backport This will backport the following commits from `main` to `8.16`: - [[Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546)](https://github.com/elastic/kibana/pull/200546) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kerry Gallagher","email":"kerry.gallagher@elastic.co"},"sourceCommit":{"committedDate":"2024-11-28T10:52:38Z","message":"[Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/200256 and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n## Overview of changes\r\n\r\n- The call to `logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views will be deprecated.\r\n- The logs indices that were previously defined via\r\n`defineInternalLogView()` are now exposed via\r\n`externalConfig.logsIndices`\r\n- As part of this change `ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just an index pattern I don't believe there are\r\nany security concerns here.\r\n- `getIndexPatterns()` has been moved to common (this makes it look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer locator is swapped for the Discover locator using an\r\nad-hoc data view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe behaviour here should match exactly what we had before, as the same\r\nindices are constructed from `getIndexPatterns()` and we apply the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes from moving\r\n`getIndexPatterns()` were automated so there shouldn't be any issues,\r\nbut given it's used extensively please check everything works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-logs","backport:version","v8.18.0","v8.16.2"],"title":"[Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring","number":200546,"url":"https://github.com/elastic/kibana/pull/200546","mergeCommit":{"message":"[Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/200256 and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n## Overview of changes\r\n\r\n- The call to `logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views will be deprecated.\r\n- The logs indices that were previously defined via\r\n`defineInternalLogView()` are now exposed via\r\n`externalConfig.logsIndices`\r\n- As part of this change `ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just an index pattern I don't believe there are\r\nany security concerns here.\r\n- `getIndexPatterns()` has been moved to common (this makes it look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer locator is swapped for the Discover locator using an\r\nad-hoc data view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe behaviour here should match exactly what we had before, as the same\r\nindices are constructed from `getIndexPatterns()` and we apply the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes from moving\r\n`getIndexPatterns()` were automated so there shouldn't be any issues,\r\nbut given it's used extensively please check everything works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200546","number":200546,"mergeCommit":{"message":"[Stack Monitoring] Switch Logs Explorer locator for Discover locator in Stack Monitoring (#200546)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/200256 and\r\nhttps://github.com/elastic/kibana/issues/200218.\r\n\r\n## Overview of changes\r\n\r\n- The call to `logsShared.logViews.defineInternalLogView()` is removed\r\nas Log Views will be deprecated.\r\n- The logs indices that were previously defined via\r\n`defineInternalLogView()` are now exposed via\r\n`externalConfig.logsIndices`\r\n- As part of this change `ui.logs` from `config` is now exposed to\r\nbrowser. Given this is just an index pattern I don't believe there are\r\nany security concerns here.\r\n- `getIndexPatterns()` has been moved to common (this makes it look like\r\nthere's a lot of file changes here).\r\n- The Logs Explorer locator is swapped for the Discover locator using an\r\nad-hoc data view.\r\n - This is hidden if Discover isn't available.\r\n\r\nThe behaviour here should match exactly what we had before, as the same\r\nindices are constructed from `getIndexPatterns()` and we apply the same\r\n`query`.\r\n\r\nStack Monitoring reviewer: The path changes from moving\r\n`getIndexPatterns()` were automated so there shouldn't be any issues,\r\nbut given it's used extensively please check everything works as\r\nexpected.\r\n\r\n## Screenshots\r\n\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3e538d67c1378dc438d9f81cb603a7965026ac0c"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kerry Gallagher <kerry.gallagher@elastic.co> |
||
|
Kibana Machine
|
1ce29a7a86
|
[8.16] [Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039) (#202099)
# Backport This will backport the following commits from `main` to `8.16`: - [[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)](https://github.com/elastic/kibana/pull/202039) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2024-11-28T04:05:51Z","message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","v9.0.0","backport:version","v8.17.0","v8.18.0","v8.16.2","v8.15.6"],"title":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines","number":202039,"url":"https://github.com/elastic/kibana/pull/202039","mergeCommit":{"message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202039","number":202039,"mergeCommit":{"message":"[Stack Monitoring] Do not add empty include array when retrieving logstash pipelines (#202039)\n\n## Summary\r\n\r\nThis PR fixes the query that retrieves Logstash pipeline stats and\r\nmetrics to be displayed in Stack Monitoring. The problem with the\r\nexisting query is that a `terms` aggregation contains an empty\r\n`\"include\": []` filtering array, but that has the nasty effect of\r\nexcluding everything and not returning anything, hence the screen is\r\nempty.\r\n\r\nThe fix is to only add the `include` array if it's not empty. The PR\r\nalso fixes a wrong field name used in a cardinality aggregation:\r\n`logstash.node.stats.logstash.uuid` instead of\r\n`logstash_stats.logstash.uuid`\r\n\r\nCloses https://github.com/elastic/kibana/issues/202020\r\n\r\n### Checklist\r\n\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n\r\n---------\r\n\r\nCo-authored-by: Chris Earle <chris.earle@elastic.co>","sha":"b7e46bdae9da7ac6ea7346cd3450597796995eb5"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co> |
||
|
Kibana Machine
|
bb1b99a4b2
|
[8.16] [Security Solution] Fix code scanning alert no. 469: Prototype-polluting function (#201712) (#202080)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Fix code scanning alert no. 469: Prototype-polluting function (#201712)](https://github.com/elastic/kibana/pull/201712) <!--- 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-11-27T21:56:59Z","message":"[Security Solution] Fix code scanning alert no. 469: Prototype-polluting function (#201712)\n\nFixes\r\n[https://github.com/elastic/kibana/security/code-scanning/469](https://github.com/elastic/kibana/security/code-scanning/469)\r\n\r\nWhile I don't think this is actually an issue, as source is only a set\r\nof ecs fields that ultimately are defined in the code and not controlled\r\nby the user\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-alerts-as-data-utils/src/search/security/fields.ts#L47\r\nThis suggested fix doesn't have any negative impact/makes it future\r\nproof if ever used elsewhere.\r\n\r\nTo fix the prototype pollution issue in the `deepMerge` function, we\r\nneed to ensure that the function does not copy the special properties\r\n`__proto__` and `constructor`. Additionally, we should verify that the\r\nproperties being copied are own properties of the `source` object. This\r\ncan be achieved by adding checks within the `deepMerge` function.\r\n\r\n\r\n_Suggested fixes powered by Copilot Autofix. Review carefully before\r\nmerging._\r\n\r\n---------\r\n\r\nCo-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bcbf85a71f0b30e431a9dc94f3a04773e2f43623","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:prev-major"],"title":"[Security Solution] Fix code scanning alert no. 469: Prototype-polluting function","number":201712,"url":"https://github.com/elastic/kibana/pull/201712","mergeCommit":{"message":"[Security Solution] Fix code scanning alert no. 469: Prototype-polluting function (#201712)\n\nFixes\r\n[https://github.com/elastic/kibana/security/code-scanning/469](https://github.com/elastic/kibana/security/code-scanning/469)\r\n\r\nWhile I don't think this is actually an issue, as source is only a set\r\nof ecs fields that ultimately are defined in the code and not controlled\r\nby the user\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-alerts-as-data-utils/src/search/security/fields.ts#L47\r\nThis suggested fix doesn't have any negative impact/makes it future\r\nproof if ever used elsewhere.\r\n\r\nTo fix the prototype pollution issue in the `deepMerge` function, we\r\nneed to ensure that the function does not copy the special properties\r\n`__proto__` and `constructor`. Additionally, we should verify that the\r\nproperties being copied are own properties of the `source` object. This\r\ncan be achieved by adding checks within the `deepMerge` function.\r\n\r\n\r\n_Suggested fixes powered by Copilot Autofix. Review carefully before\r\nmerging._\r\n\r\n---------\r\n\r\nCo-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bcbf85a71f0b30e431a9dc94f3a04773e2f43623"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201712","number":201712,"mergeCommit":{"message":"[Security Solution] Fix code scanning alert no. 469: Prototype-polluting function (#201712)\n\nFixes\r\n[https://github.com/elastic/kibana/security/code-scanning/469](https://github.com/elastic/kibana/security/code-scanning/469)\r\n\r\nWhile I don't think this is actually an issue, as source is only a set\r\nof ecs fields that ultimately are defined in the code and not controlled\r\nby the user\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-alerts-as-data-utils/src/search/security/fields.ts#L47\r\nThis suggested fix doesn't have any negative impact/makes it future\r\nproof if ever used elsewhere.\r\n\r\nTo fix the prototype pollution issue in the `deepMerge` function, we\r\nneed to ensure that the function does not copy the special properties\r\n`__proto__` and `constructor`. Additionally, we should verify that the\r\nproperties being copied are own properties of the `source` object. This\r\ncan be achieved by adding checks within the `deepMerge` function.\r\n\r\n\r\n_Suggested fixes powered by Copilot Autofix. Review carefully before\r\nmerging._\r\n\r\n---------\r\n\r\nCo-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bcbf85a71f0b30e431a9dc94f3a04773e2f43623"}}]}] BACKPORT--> Co-authored-by: Kevin Qualters <56408403+kqualters-elastic@users.noreply.github.com> |