35012 commits

Author	SHA1	Message	Date
jennypavlova	3e296b64e5	[8.17] [APM] Fix: Span Links with OTel data (#212806) (#213886) ... # Backport This will backport the following commits from `main` to `8.17`: - [[APM] Fix: Span Links with OTel data (#212806)](https://github.com/elastic/kibana/pull/212806) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-10T18:47:07Z","message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix: Span Links with OTel data","number":212806,"url":"https://github.com/elastic/kibana/pull/212806","mergeCommit":{"message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212806","number":212806,"mergeCommit":{"message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-11 13:41:09 +01:00
Cauê Marcondes	eee5d76723	[8.17] [APM] Breakdown Top dependencies API (#211441) (#213795) ... # Backport This will backport the following commits from `main` to `8.17`: - [[APM] Breakdown Top dependencies API (#211441)](https://github.com/elastic/kibana/pull/211441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T16:24:37Z","message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Breakdown Top dependencies API","number":211441,"url":"https://github.com/elastic/kibana/pull/211441","mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211441","number":211441,"mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-11 13:29:30 +01:00
Christos Nasikas	f8ff8466dd	[8.17] [ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658) (#213865) ... # Backport This will backport the following commits from `main` to `8.17`: - [[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)](https://github.com/elastic/kibana/pull/213658) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-10T18:53:48Z","message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","Feature:Actions/ConnectorTypes","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector","number":213658,"url":"https://github.com/elastic/kibana/pull/213658","mergeCommit":{"message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213818","number":213818,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213816","number":213816,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213658","number":213658,"mergeCommit":{"message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213817","number":213817,"state":"OPEN"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-11 12:22:51 +01:00
Sergi Massaneda	d62cf5b255	[8.17] [Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563) (#213615) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)](https://github.com/elastic/kibana/pull/212563) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T17:43:24Z","message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Security Solution][Connectors] Torq connector allow EU hooks hostname","number":212563,"url":"https://github.com/elastic/kibana/pull/212563","mergeCommit":{"message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213613","number":213613,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213611","number":213611,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212563","number":212563,"mergeCommit":{"message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213612","number":213612,"state":"OPEN"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2025-03-10 14:06:59 -04:00
Carlos Crespo	7478f4d0c0	[8.17] [Infra] Fix hosts total count query (#212749) (#213691) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Infra] Fix hosts total count query (#212749)](https://github.com/elastic/kibana/pull/212749) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-04T15:46:21Z","message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[Infra] Fix hosts total count query","number":212749,"url":"https://github.com/elastic/kibana/pull/212749","mergeCommit":{"message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212749","number":212749,"mergeCommit":{"message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f"}}]}] BACKPORT-->	2025-03-10 12:02:46 +01:00
Kibana Machine	ab85531373	[8.17] [APM][Errors] Fix: Missing summary data in in error sample (#213430) (#213572) ... # Backport This will backport the following commits from `main` to `8.17`: - [[APM][Errors] Fix: Missing summary data in in error sample (#213430)](https://github.com/elastic/kibana/pull/213430) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T14:08:39Z","message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][Errors] Fix: Missing summary data in in error sample","number":213430,"url":"https://github.com/elastic/kibana/pull/213430","mergeCommit":{"message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213430","number":213430,"mergeCommit":{"message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>	2025-03-07 17:08:07 +01:00
Michael Olorunnisola	2bd9fede4b	[8.17] [Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343) (#213491) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)](https://github.com/elastic/kibana/pull/211343) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T21:09:22Z","message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[Bug][Security Solution] - Reliably persist dataview selections for timeline","number":211343,"url":"https://github.com/elastic/kibana/pull/211343","mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213488","number":213488,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211343","number":211343,"mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-07 08:21:21 +01:00
Kibana Machine	04dc0da349	[8.17] [Fleet] unskip test (#213365) (#213401) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] unskip test (#213365)](https://github.com/elastic/kibana/pull/213365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T14:20:39Z","message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] unskip test","number":213365,"url":"https://github.com/elastic/kibana/pull/213365","mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213365","number":213365,"mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>	2025-03-06 17:22:30 +01:00
Kibana Machine	a5e245337a	[8.17] fix: Product Documentation function not available error (#212676) (#213226) ... # Backport This will backport the following commits from `main` to `8.17`: - [fix: Product Documentation function not available error (#212676)](https://github.com/elastic/kibana/pull/212676) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T11:43:16Z","message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0"],"title":"fix: Product Documentation function not available error","number":212676,"url":"https://github.com/elastic/kibana/pull/212676","mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212676","number":212676,"mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co>	2025-03-05 14:56:11 +01:00
Michael Olorunnisola	543bf80673	[8.17] [Performance][Security Solution][1/4] - Field Browser Performance (#212469) (#213025) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][1/4] - Field Browser Performance (#212469)](https://github.com/elastic/kibana/pull/212469) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T01:22:25Z","message":"[Performance][Security Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart 1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n- Security solution field browser component\n- Flyout table tab.\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was locking of the page and field\nbrowser component when the total number of fields returned were\nsignificantly high.\n\nThis led to cell values not rendering in the alert table, and the field\nbrowser in all the security solution pages causing the page to crash.\nThe relevant images can be seen at the bottom of this description\n\nIn short: The `push(...fields)` is non-performant at scale, and at a\nsignificant enough scale (Testing was done with 500k mapped fields),\nfails to run due to excessive arguments provided to the `push` method.\nIn this PR improvements are made in the `browserFields` transformations\nthat are done for the field browser component, expandable flyout table\ntab, and alert/rule tables via `CellValue` component.\n\nThis work was done to get immediate improvements in the security\nsolution UI, but a longer term consideration will be whether or not the\n`browserFields` is even necessary anymore as a concept based on what is\navailable via the `fields` api. We will revisit once our Sourcerer\nrefactoring work is done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15 29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18 36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19 48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n### After the fix\n(Done on [this branch](https://github.com/elastic/kibana/pull/212173)\nthat has the other changes as well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Performance][Security Solution][1/4] - Field Browser Performance","number":212469,"url":"https://github.com/elastic/kibana/pull/212469","mergeCommit":{"message":"[Performance][Security Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart 1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n- Security solution field browser component\n- Flyout table tab.\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was locking of the page and field\nbrowser component when the total number of fields returned were\nsignificantly high.\n\nThis led to cell values not rendering in the alert table, and the field\nbrowser in all the security solution pages causing the page to crash.\nThe relevant images can be seen at the bottom of this description\n\nIn short: The `push(...fields)` is non-performant at scale, and at a\nsignificant enough scale (Testing was done with 500k mapped fields),\nfails to run due to excessive arguments provided to the `push` method.\nIn this PR improvements are made in the `browserFields` transformations\nthat are done for the field browser component, expandable flyout table\ntab, and alert/rule tables via `CellValue` component.\n\nThis work was done to get immediate improvements in the security\nsolution UI, but a longer term consideration will be whether or not the\n`browserFields` is even necessary anymore as a concept based on what is\navailable via the `fields` api. We will revisit once our Sourcerer\nrefactoring work is done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15 29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18 36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19 48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n### After the fix\n(Done on [this branch](https://github.com/elastic/kibana/pull/212173)\nthat has the other changes as well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212469","number":212469,"mergeCommit":{"message":"[Performance][Security Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart 1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n- Security solution field browser component\n- Flyout table tab.\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was locking of the page and field\nbrowser component when the total number of fields returned were\nsignificantly high.\n\nThis led to cell values not rendering in the alert table, and the field\nbrowser in all the security solution pages causing the page to crash.\nThe relevant images can be seen at the bottom of this description\n\nIn short: The `push(...fields)` is non-performant at scale, and at a\nsignificant enough scale (Testing was done with 500k mapped fields),\nfails to run due to excessive arguments provided to the `push` method.\nIn this PR improvements are made in the `browserFields` transformations\nthat are done for the field browser component, expandable flyout table\ntab, and alert/rule tables via `CellValue` component.\n\nThis work was done to get immediate improvements in the security\nsolution UI, but a longer term consideration will be whether or not the\n`browserFields` is even necessary anymore as a concept based on what is\navailable via the `fields` api. We will revisit once our Sourcerer\nrefactoring work is done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15 29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18 36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19 48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n### After the fix\n(Done on [this branch](https://github.com/elastic/kibana/pull/212173)\nthat has the other changes as well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-04 11:56:13 -06:00
Michael Olorunnisola	72460c6d64	[8.17] [Performance][Security Solution][4/4] - General Performance changes (#212488) (#212992) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][4/4] - General Performance changes (#212488)](https://github.com/elastic/kibana/pull/212488) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T17:59:43Z","message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Performance][Security Solution][4/4] - General Performance changes","number":212488,"url":"https://github.com/elastic/kibana/pull/212488","mergeCommit":{"message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212966","number":212966,"state":"MERGED","mergeCommit":{"sha":"f93acdea1585b265c9a74be93da1c2dfa562631b","message":"[9.0] [Performance][Security Solution][4/4] - General Performance changes (#212488) (#212966)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Performance][Security Solution][4/4] - General Performance changes\n(#212488)](https://github.com/elastic/kibana/pull/212488)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212488","number":212488,"mergeCommit":{"message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-04 11:55:41 -06:00
Sander Philipse	448cc588d8	[8.17] [Search] Don't error out on missing connectors permissions (#212622) (#213091) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Search] Don't error out on missing connectors permissions (#212622)](https://github.com/elastic/kibana/pull/212622) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-28T12:36:37Z","message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Search] Don't error out on missing connectors permissions","number":212622,"url":"https://github.com/elastic/kibana/pull/212622","mergeCommit":{"message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212763","number":212763,"state":"MERGED","mergeCommit":{"sha":"e32f93a3f59c104f0f658ba4d5a7fc6431cb5096","message":"[9.0] [Search] Don't error out on missing connectors permissions (#212622) (#212763)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Search] Don't error out on missing connectors permissions\n(#212622)](https://github.com/elastic/kibana/pull/212622)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212622","number":212622,"mergeCommit":{"message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-04 11:27:23 -05:00
Kibana Machine	a37f1d36af	[8.17] [Elastic Defend] Add windows.ransomware.dump_process for endpoint advanced policy setting (#212439) (#213009) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)](https://github.com/elastic/kibana/pull/212439) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christophe Alladoum","email":"85187342+calladoum-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-04T00:57:20Z","message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:version","v8.18.0","v8.15.6","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting","number":212439,"url":"https://github.com/elastic/kibana/pull/212439","mergeCommit":{"message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.15","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212439","number":212439,"mergeCommit":{"message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Christophe Alladoum <85187342+calladoum-elastic@users.noreply.github.com>	2025-03-04 03:00:16 +00:00
Kibana Machine	298f53986a	[8.17] [Performance][Security Solution][3/4] - Sourcerer performance (#212482) (#212985) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][3/4] - Sourcerer performance (#212482)](https://github.com/elastic/kibana/pull/212482) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T21:06:38Z","message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"[Performance][Security Solution][3/4] - Sourcerer performance","number":212482,"url":"https://github.com/elastic/kibana/pull/212482","mergeCommit":{"message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212482","number":212482,"mergeCommit":{"message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co>	2025-03-03 23:08:17 +00:00
Konrad Szwarc	f6a3d1258e	[8.17] [EDR Workflows] OpenApi Missing Content - Response Actions (#212510) (#212870) ... # Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)](https://github.com/elastic/kibana/pull/212510) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-28T16:44:00Z","message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] OpenApi Missing Content - Response Actions","number":212510,"url":"https://github.com/elastic/kibana/pull/212510","mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212794","number":212794,"state":"MERGED","mergeCommit":{"sha":"3ceba17cbd76f89b72986190b8c77f5079706282","message":"[9.0] [EDR Workflows] OpenApi Missing Content - Response Actions (#212510) (#212794)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[EDR Workflows] OpenApi Missing Content - Response Actions\n(#212510)](https://github.com/elastic/kibana/pull/212510)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>"}},{"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.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212510","number":212510,"mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-03 13:08:55 +00:00
Kibana Machine	229aac1adf	[8.17] [Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786) (#212822) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)](https://github.com/elastic/kibana/pull/212786) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-28T21:21:37Z","message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:all-open","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k","number":212786,"url":"https://github.com/elastic/kibana/pull/212786","mergeCommit":{"message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212786","number":212786,"mergeCommit":{"message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2025-02-28 23:19:31 +00:00
Pablo Machado	faabb4e47a	[SecuritySolution] Fix 8.17.3 branch by reverting bugfix (#212729) ... ## Summary Revert https://github.com/elastic/kibana/pull/212378 The Entity Analytics team backported a broken fix to 8.17.3, preventing users from installing the risk engine on multiple spaces.	2025-02-28 11:18:27 +00:00
Kibana Machine	45321f8b9a	[8.17] Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529) (#212722) ... # Backport This will backport the following commits from `main` to `8.17`: - [Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)](https://github.com/elastic/kibana/pull/212529) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steve Gordon","email":"sgordon@hotmail.co.uk"},"sourceCommit":{"committedDate":"2025-02-28T07:02:41Z","message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.18.0","v9.1.0","v8.17.3","v8.16.5"],"title":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard","number":212529,"url":"https://github.com/elastic/kibana/pull/212529","mergeCommit":{"message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212529","number":212529,"mergeCommit":{"message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steve Gordon <sgordon@hotmail.co.uk>	2025-02-28 09:13:34 +00:00
Kibana Machine	240b79a0ee	[8.17] [Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690) (#212697) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)](https://github.com/elastic/kibana/pull/212690) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T21:25:44Z","message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.18.1"],"title":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline","number":212690,"url":"https://github.com/elastic/kibana/pull/212690","mergeCommit":{"message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212690","number":212690,"mergeCommit":{"message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2025-02-27 23:24:37 +00:00
Kibana Machine	4b88c78903	[8.17] [EDR Workflows][Osquery] OpenApi Missing Content (#212032) (#212640) ... # Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows][Osquery] OpenApi Missing Content (#212032)](https://github.com/elastic/kibana/pull/212032) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T12:29:04Z","message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows][Osquery] OpenApi Missing Content","number":212032,"url":"https://github.com/elastic/kibana/pull/212032","mergeCommit":{"message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212032","number":212032,"mergeCommit":{"message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603"}}]}] BACKPORT--> --------- Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>	2025-02-27 14:51:28 +00:00
Kibana Machine	1d9706caad	[8.17] [Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611) (#212645) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)](https://github.com/elastic/kibana/pull/212611) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-27T12:32:17Z","message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","backport:version","Feature:AutomaticImport","v9.1.0","backport:8.18"],"title":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs","number":212611,"url":"https://github.com/elastic/kibana/pull/212611","mergeCommit":{"message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212611","number":212611,"mergeCommit":{"message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>	2025-02-27 14:37:36 +00:00
Charlotte Alexandra Wilson	f3192d7aed	[8.17] [refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441) (#212561) ... # Backport This will backport the following commits from `main` to `8.17`: - [[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)](https://github.com/elastic/kibana/pull/212441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-26T13:29:21Z","message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["refactoring","release_note:skip","v9.0.0","Theme: entity_analytics","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel ","number":212441,"url":"https://github.com/elastic/kibana/pull/212441","mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212554","number":212554,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212519","number":212519,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212441","number":212441,"mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212556","number":212556,"state":"OPEN"}]}] BACKPORT-->	2025-02-27 10:53:19 +00:00
Philippe Oberti	b86ad4dac3	[8.17] [Security Solution] Fixed Table height row rendering - Event Rendered View (#212130) (#212597) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)](https://github.com/elastic/kibana/pull/212130) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T22:36:50Z","message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fixed Table height row rendering - Event Rendered View","number":212130,"url":"https://github.com/elastic/kibana/pull/212130","mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212596","number":212596,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212130","number":212130,"mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212594","number":212594,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>	2025-02-26 20:33:37 -05:00
Kibana Machine	86fb404db7	[8.17] [Fleet] Fix API key insertion into standalone agent policy (#212440) (#212578) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] Fix API key insertion into standalone agent policy (#212440)](https://github.com/elastic/kibana/pull/212440) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Satvikkaushal","email":"39619179+Satvikkaushal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-26T19:02:11Z","message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","💝community","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] Fix API key insertion into standalone agent policy","number":212440,"url":"https://github.com/elastic/kibana/pull/212440","mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212440","number":212440,"mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}}]}] BACKPORT--> Co-authored-by: Satvikkaushal <39619179+Satvikkaushal@users.noreply.github.com>	2025-02-26 21:03:35 +00:00
Giorgos Bamparopoulos	899a7eb5da	[8.17] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#212388) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)](https://github.com/elastic/kibana/pull/205694) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Giorgos Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T15:41:28Z","message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b","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","backport:version","v8.18.0"],"title":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow","number":205694,"url":"https://github.com/elastic/kibana/pull/205694","mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},"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/205694","number":205694,"mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207866","number":207866,"state":"MERGED","mergeCommit":{"sha":"0d22f08c4bd7da291ab6037980512be9b57ce5d7","message":"[8.x] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#207866)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Observability Onboarding] Update values.yml file URL for the OTel\nK8s flow (#205694)](https://github.com/elastic/kibana/pull/205694)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>"}}]}] BACKPORT-->	2025-02-26 17:35:48 +01:00
Ievgen Sorokopud	f65b7a1d66	[8.17] [Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122) (#212505) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)](https://github.com/elastic/kibana/pull/212122) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T11:03:09Z","message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783)","number":212122,"url":"https://github.com/elastic/kibana/pull/212122","mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212501","number":212501,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212500","number":212500,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212122","number":212122,"mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-26 16:23:15 +00:00
José Luis González	1e06975863	[8.17] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212484) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Search][Connectors] Fixing custom connector icon rendering (#212225)](https://github.com/elastic/kibana/pull/212225) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2025-02-25T14:49:33Z","message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\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- [ ] 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/src/platform/packages/shared/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":"965cbbabc0d59fa3419d0238b4eb460ab930d2db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major","backport:version","v9.1.0"],"title":"[Search][Connectors] Fixing custom connector icon rendering","number":212225,"url":"https://github.com/elastic/kibana/pull/212225","mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\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- [ ] 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/src/platform/packages/shared/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":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212386","number":212386,"state":"MERGED","mergeCommit":{"sha":"e6799ea001e2ef5178294d3e7dc570e7861d19c7","message":"[9.0] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212386)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Search][Connectors] Fixing custom connector icon rendering\n(#212225)](https://github.com/elastic/kibana/pull/212225)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: José Luis González <joseluisgj@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212225","number":212225,"mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\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- [ ] 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/src/platform/packages/shared/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":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}}]}] BACKPORT-->	2025-02-26 14:30:58 +01:00
Abhishek Bhatia	01a430a06c	[8.17] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#212378) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Entity Analytics] API changes for right placement of deleting the old component template (#199734)](https://github.com/elastic/kibana/pull/199734) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-18T15:07:13Z","message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","QA:Validated","Team:Entity Analytics","backport:version","v8.17.0","v8.16.1","v8.18.0"],"title":"[Entity Analytics] API changes for right placement of deleting the old component template","number":199734,"url":"https://github.com/elastic/kibana/pull/199734","mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199734","number":199734,"mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200673","number":200673,"state":"MERGED","mergeCommit":{"sha":"24cbc3ee37cca9610bb8848c7361deeb4dc63ac4","message":"[8.x] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200673)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"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/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/200591\",\"number\":200591,\"state\":\"MERGED\",\"mergeCommit\":{\"sha\":\"06999139d210464c236a3784c58b7e5dcbd64ce3\",\"message\":\"[8.16]\n[Entity Analytics] API changes for right placement of deleting the old\ncomponent template (#199734) (#200591)\\n\\n# Backport\\n\\nThis will\nbackport the following commits from `main` to `8.16`:\\n- [[Entity\nAnalytics] API changes for right placement of deleting the\\nold\ncomponent\ntemplate\\n(#199734)](https://github.com/elastic/kibana/pull/199734)\\n\\n<!---\nBackport version: 8.9.8 -->\\n\\n### Questions ?\\nPlease refer to the\n[Backport\ntool\\ndocumentation](https://github.com/sqren/backport)\\n\\n<!--BACKPORT\n[{\\\"author\\\":{\\\"name\\\":\\\"Abhishek\\nBhatia\\\",\\\"email\\\":\\\"117628830+abhishekbhatia1710@users.noreply.github.com\\\"},\\\"sourceCommit\\\":{\\\"committedDate\\\":\\\"2024-11-18T15:07:13Z\\\",\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\",\\\"branchLabelMapping\\\":{\\\"^v9.0.0$\\\":\\\"main\\\",\\\"^v8.17.0$\\\":\\\"8.x\\\",\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\":\\\"$1.$2\\\"}},\\\"sourcePullRequest\\\":{\\\"labels\\\":[\\\"bug\\\",\\\"release_note:fix\\\",\\\"v9.0.0\\\",\\\"Team:Entity\\nAnalytics\\\",\\\"backport:version\\\",\\\"v8.17.0\\\",\\\"v8.16.1\\\"],\\\"number\\\":199734,\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/199734\\\",\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},\\\"sourceBranch\\\":\\\"main\\\",\\\"suggestedTargetBranches\\\":[\\\"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/199734\\\",\\\"number\\\":199734,\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},{\\\"branch\\\":\\\"8.x\\\",\\\"label\\\":\\\"v8.17.0\\\",\\\"labelRegex\\\":\\\"^v8.17.0$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"},{\\\"branch\\\":\\\"8.16\\\",\\\"label\\\":\\\"v8.16.1\\\",\\\"labelRegex\\\":\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"}]}]\\nBACKPORT-->\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200591","number":200591,"state":"MERGED","mergeCommit":{"sha":"06999139d210464c236a3784c58b7e5dcbd64ce3","message":"[8.16] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200591)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"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/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\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- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-26 12:51:47 +01:00
Konrad Szwarc	83391ca5d9	[8.17] [EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205) (#212387) ... # Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)](https://github.com/elastic/kibana/pull/212205) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-25T13:18:56Z","message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] OpenApi Missing Content - Endpoint Management","number":212205,"url":"https://github.com/elastic/kibana/pull/212205","mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212374","number":212374,"state":"OPEN"},{"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.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212373","number":212373,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212205","number":212205,"mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-26 09:33:07 +01:00
Patryk Kopyciński	0ccc106cac	[8.17] Fix calling Sonnet 3.7 (#212372) (#212411) ... # Backport This will backport the following commits from `main` to `8.17`: - [Fix calling Sonnet 3.7 (#212372)](https://github.com/elastic/kibana/pull/212372) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-02-25T15:41:55Z","message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"Fix calling Sonnet 3.7","number":212372,"url":"https://github.com/elastic/kibana/pull/212372","mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212399","number":212399,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212398","number":212398,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212372","number":212372,"mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-25 13:32:48 -05:00
Kibana Machine	13cfa3ef48	[8.17] Fix Chart Trend by Severity Bug (#212358) ... # Backport This will backport the following commits from `main` to `8.17`: - [Fix Chart Trend by Severity Bug](https://github.com/elastic/kibana/pull/211735) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ido Cohen","email":"90558359+CohenIdo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-25T11:24:50Z","message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"Fix Chart Trend by Severity Bug","number":211735,"url":"https://github.com/elastic/kibana/pull/211735","mergeCommit":{"message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211735","number":211735,"mergeCommit":{"message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992"}}]}] BACKPORT--> Co-authored-by: Ido Cohen <90558359+CohenIdo@users.noreply.github.com>	2025-02-25 13:28:54 +00:00
Charlotte Alexandra Wilson	9e886b57cd	[8.17] [Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078) (#212265) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)](https://github.com/elastic/kibana/pull/212078) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-24T14:35:30Z","message":"[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)\n\n## Summary\n\nEnsure Enable Button Considers Disabled State of Risk Score & Entity\nStore. Previously only used the checked state of the toggle.\n\n### Reproduce the Issue\nSteps, as [per bug\nticket:](https://github.com/elastic/kibana/issues/209242#issue-2826951496)\n\n1. Kibana version 8.16.0 or above should exist\n2. Navigate to the Dashboards tab under Security\n3. Select Entity Analytics dashboard\n4. Click on the enable button and enable risk score\n5. Disable the options for Entity store\n6. Then again select the enable button for Entity store\n7. Disable the enable button\n8. Observe the Enable button is still enabled\n\n### After Issue Solved\n\nSame steps as above, but should show the warning and disable the button.\n\n#### Videos\n\nVideos show when either riskScore or entityStore is enabled, and the\nother is unchecked, the warning should show and the button should be\ndisabled.\n\n\n2971e845-5d46-4eac-997a-79b3b17922c0\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ba9210c2594c5d2d1a4915943e5c73911f1acbf8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","ci:project-deploy-security","ci:project-persist-deployment","Team:Entity Analytics","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal","number":212078,"url":"https://github.com/elastic/kibana/pull/212078","mergeCommit":{"message":"[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)\n\n## Summary\n\nEnsure Enable Button Considers Disabled State of Risk Score & Entity\nStore. Previously only used the checked state of the toggle.\n\n### Reproduce the Issue\nSteps, as [per bug\nticket:](https://github.com/elastic/kibana/issues/209242#issue-2826951496)\n\n1. Kibana version 8.16.0 or above should exist\n2. Navigate to the Dashboards tab under Security\n3. Select Entity Analytics dashboard\n4. Click on the enable button and enable risk score\n5. Disable the options for Entity store\n6. Then again select the enable button for Entity store\n7. Disable the enable button\n8. Observe the Enable button is still enabled\n\n### After Issue Solved\n\nSame steps as above, but should show the warning and disable the button.\n\n#### Videos\n\nVideos show when either riskScore or entityStore is enabled, and the\nother is unchecked, the warning should show and the button should be\ndisabled.\n\n\n2971e845-5d46-4eac-997a-79b3b17922c0\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ba9210c2594c5d2d1a4915943e5c73911f1acbf8"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"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.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212250","number":212250,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212078","number":212078,"mergeCommit":{"message":"[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)\n\n## Summary\n\nEnsure Enable Button Considers Disabled State of Risk Score & Entity\nStore. Previously only used the checked state of the toggle.\n\n### Reproduce the Issue\nSteps, as [per bug\nticket:](https://github.com/elastic/kibana/issues/209242#issue-2826951496)\n\n1. Kibana version 8.16.0 or above should exist\n2. Navigate to the Dashboards tab under Security\n3. Select Entity Analytics dashboard\n4. Click on the enable button and enable risk score\n5. Disable the options for Entity store\n6. Then again select the enable button for Entity store\n7. Disable the enable button\n8. Observe the Enable button is still enabled\n\n### After Issue Solved\n\nSame steps as above, but should show the warning and disable the button.\n\n#### Videos\n\nVideos show when either riskScore or entityStore is enabled, and the\nother is unchecked, the warning should show and the button should be\ndisabled.\n\n\n2971e845-5d46-4eac-997a-79b3b17922c0\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ba9210c2594c5d2d1a4915943e5c73911f1acbf8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212251","number":212251,"state":"OPEN"}]}] BACKPORT-->	2025-02-24 17:32:00 +00:00
Felix Stürmer	43587d848f	[8.17] [Logs UI] Fix log view loading states (#212124) (#212140) ... # Backport This will backport the following commits from `8.x` to `8.17`: - [[Logs UI] Fix log view loading states (#212124)](https://github.com/elastic/kibana/pull/212124) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-21T18:49:34Z","message":"[Logs UI] Fix log view loading states (#212124)\n\nThis fixes a problem with the log view resolution when entering the log\nsettings page under certain conditions.","sha":"aa26fe3c0b921c3696dba7023a4fced72c4a2043","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","backport:version","v8.18.0","v8.19.0","v8.17.3"],"title":"[Logs UI] Fix log view loading states","number":212124,"url":"https://github.com/elastic/kibana/pull/212124","mergeCommit":{"message":"[Logs UI] Fix log view loading states (#212124)\n\nThis fixes a problem with the log view resolution when entering the log\nsettings page under certain conditions.","sha":"aa26fe3c0b921c3696dba7023a4fced72c4a2043"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2025-02-24 16:01:59 +00:00
Kibana Machine	3bd3eecdb4	[8.17] Log request ID in SAML provider (#211877) (#212218) ... # Backport This will backport the following commits from `main` to `8.17`: - [Log request ID in SAML provider (#211877)](https://github.com/elastic/kibana/pull/211877) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T11:00:06Z","message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:prev-major","v9.1.0"],"title":"Log request ID in SAML provider","number":211877,"url":"https://github.com/elastic/kibana/pull/211877","mergeCommit":{"message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211877","number":211877,"mergeCommit":{"message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6"}}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>	2025-02-24 12:57:19 +00:00
Jen Huang	beb0f5945b	[8.17] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212151) ... # Backport This will backport the following commits from `main` to `8.17`: - [[UII] Drop ssl field from output if it's in an invalid format (#211848)](https://github.com/elastic/kibana/pull/211848) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2025-02-21T08:52:17Z","message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-major","v8.18.0","v9.1.0","v8.19.0"],"title":"[UII] Drop ssl field from output if it's in an invalid format","number":211848,"url":"https://github.com/elastic/kibana/pull/211848","mergeCommit":{"message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212015","number":212015,"state":"MERGED","mergeCommit":{"sha":"fc82a79ec2f0f6ad1d91c7a32f06822ebd7bf535","message":"[8.18] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212015)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[UII] Drop ssl field from output if it's in an invalid format\n(#211848)](https://github.com/elastic/kibana/pull/211848)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jen Huang <its.jenetic@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211848","number":211848,"mergeCommit":{"message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212016","number":212016,"state":"MERGED","mergeCommit":{"sha":"26fe14935bc6c1be610057662c55f3b6bc0c2fde","message":"[8.x] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212016)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[UII] Drop ssl field from output if it's in an invalid format\n(#211848)](https://github.com/elastic/kibana/pull/211848)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jen Huang <its.jenetic@gmail.com>"}}]}] BACKPORT-->	2025-02-21 19:48:09 -05:00
Kibana Machine	cf07b4882d	[8.17] [Fleet] fix prerelease:boolean in package_service (#212054) (#212083) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] fix `prerelease:boolean` in package_service (#212054)](https://github.com/elastic/kibana/pull/212054) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-21T13:51:21Z","message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-major","v9.1.0"],"title":"[Fleet] fix `prerelease:boolean` in package_service","number":212054,"url":"https://github.com/elastic/kibana/pull/212054","mergeCommit":{"message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212054","number":212054,"mergeCommit":{"message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>	2025-02-21 16:00:07 +00:00
Bryce Buchanan	c1220342a6	[8.17] Added versioning to inventory_view_saved_object (#207007) (#211634) ... # Backport This will backport the following commits from `main` to `8.17`: - [Added versioning to inventory_view_saved_object (#207007)](https://github.com/elastic/kibana/pull/207007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T18:09:32Z","message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:fix","backport missing","v9.0.0","Team:obs-ux-infra_services"],"title":"Added versioning to inventory_view_saved_object","number":207007,"url":"https://github.com/elastic/kibana/pull/207007","mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}},"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/207007","number":207007,"mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}}]}] BACKPORT-->	2025-02-21 10:06:22 +01:00
Quynh Nguyen (Quinn)	6836e6c67d	[8.17] [Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217) (#211809) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)](https://github.com/elastic/kibana/pull/210217) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T05:49:58Z","message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:Fleet","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing","number":210217,"url":"https://github.com/elastic/kibana/pull/210217","mergeCommit":{"message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210950","number":210950,"state":"MERGED","mergeCommit":{"sha":"a8d9319cdd70a1ead8228d0da858c71bd709efe6","message":"[9.0] [Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217) (#210950)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Fix unattended Transforms in integration packages not\nautomatically restarting after reauthorizing\n(#210217)](https://github.com/elastic/kibana/pull/210217)\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\":\"Quynh Nguyen\n(Quinn)\",\"email\":\"43350163+qn895@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T05:49:58Z\",\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\":ml\",\"Team:Fleet\",\"v9.0.0\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\",\"v8.17.3\",\"v8.16.5\"],\"title\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after\nreauthorizing\",\"number\":210217,\"url\":\"https://github.com/elastic/kibana/pull/210217\",\"mergeCommit\":{\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"8.x\",\"8.17\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.18\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/210217\",\"number\":210217,\"mergeCommit\":{\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.3\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.5\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210217","number":210217,"mergeCommit":{"message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-19 11:33:48 -07:00
Kibana Machine	5e5f56de9e	[8.17] [SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845) (#211754) ... # Backport This will backport the following commits from `main` to `8.17`: - [[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)](https://github.com/elastic/kibana/pull/210845) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-19T12:52:30Z","message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[SecuritySolution][Endpoint] Re enable scan response action e2e test","number":210845,"url":"https://github.com/elastic/kibana/pull/210845","mergeCommit":{"message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210845","number":210845,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>	2025-02-19 15:56:11 +01:00
Charlotte Alexandra Wilson	a35f5057e2	[8.17] Entity Flyout flickers when loading risk score panel (#211568) (#211697) ... # Backport This will backport the following commits from `8.x` to `8.17`: - [Entity Flyout flickers when loading risk score panel (#211568)](https://github.com/elastic/kibana/pull/211568) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-18T15:09:12Z","message":"Entity Flyout flickers when loading risk score panel (#211568)\n\n## Summary\r\nThis PR fixes the issue where the Risk Score Panel flickers into view\r\nwhen no risk score is available yet. This occurs in two cases:\r\n1. Opening the flyout for a user or host.\r\n2. Updating Asset Criticality from the flyout.\r\n\r\n### Steps to Reproduce (Before Fix)\r\n[@abhishekbhatia1710](https://github.com/abhishekbhatia1710) [provided\r\nsteps as below in original\r\nticket](https://github.com/elastic/security-team/issues/11590#issuecomment-2643056694):\r\n\r\n1. Ensure you are using version 8.18\r\n2. Enable the Risk Engine.\r\n3. Enable the Entity Store.\r\n4. Upload the asset criticality file.\r\n5. Do not run the risk score on the newly added entities yet.\r\n6. Navigate to the EA Dashboard.\r\n7. Scroll down to the Entities section.\r\n8. Search for the user/host uploaded in the asset criticality file.\r\n9. Click on the entity to open the flyout.\r\n10. Assign asset criticality within the flyout.\r\n11. Before fix: Risk Score panel briefly appears (flickers) despite no\r\nrisk score being available.\r\n\r\n### Expected Behaviour (After Fix)\r\nFollowing the same steps, the Risk Score Panel no longer flickers when\r\nopening the flyout or updating asset criticality - for both user and\r\nhost entity types.\r\n\r\n### Video (After Fix)\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7ef28ee1-7e5d-43ae-b6d3-7075b63229be","sha":"f486939e0aa00163f4c41cdfaae96110ca508dc4","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","fixed","Team: SecuritySolution","ci:project-deploy-security","ci:project-persist-deployment","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0"],"title":"Entity Flyout flickers when loading risk score panel","number":211568,"url":"https://github.com/elastic/kibana/pull/211568","mergeCommit":{"message":"Entity Flyout flickers when loading risk score panel (#211568)\n\n## Summary\r\nThis PR fixes the issue where the Risk Score Panel flickers into view\r\nwhen no risk score is available yet. This occurs in two cases:\r\n1. Opening the flyout for a user or host.\r\n2. Updating Asset Criticality from the flyout.\r\n\r\n### Steps to Reproduce (Before Fix)\r\n[@abhishekbhatia1710](https://github.com/abhishekbhatia1710) [provided\r\nsteps as below in original\r\nticket](https://github.com/elastic/security-team/issues/11590#issuecomment-2643056694):\r\n\r\n1. Ensure you are using version 8.18\r\n2. Enable the Risk Engine.\r\n3. Enable the Entity Store.\r\n4. Upload the asset criticality file.\r\n5. Do not run the risk score on the newly added entities yet.\r\n6. Navigate to the EA Dashboard.\r\n7. Scroll down to the Entities section.\r\n8. Search for the user/host uploaded in the asset criticality file.\r\n9. Click on the entity to open the flyout.\r\n10. Assign asset criticality within the flyout.\r\n11. Before fix: Risk Score panel briefly appears (flickers) despite no\r\nrisk score being available.\r\n\r\n### Expected Behaviour (After Fix)\r\nFollowing the same steps, the Risk Score Panel no longer flickers when\r\nopening the flyout or updating asset criticality - for both user and\r\nhost entity types.\r\n\r\n### Video (After Fix)\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7ef28ee1-7e5d-43ae-b6d3-7075b63229be","sha":"f486939e0aa00163f4c41cdfaae96110ca508dc4"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.17","8.18"],"targetPullRequestStates":[{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-19 14:21:24 +00:00
Tiago Costa	42f6645391	[8.17] chore(NA): upgrade to webpack 5 (#191106) (#211148) ... # Backport This will backport the following commits from `main` to `8.17`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},{"url":"https://github.com/elastic/kibana/pull/211146","number":211146,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/211147","number":211147,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-19 03:48:08 +00:00
Bharat Pasupula	6b2ed55f13	[8.17] [Automatic Import] Remove pipeline tests from the package (#211223) (#211405) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Remove pipeline tests from the package (#211223)](https://github.com/elastic/kibana/pull/211223) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-17T09:28:57Z","message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","ci:build-cloud-image","ci:cloud-deploy","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Remove pipeline tests from the package","number":211223,"url":"https://github.com/elastic/kibana/pull/211223","mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211223","number":211223,"mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}}]}] BACKPORT-->	2025-02-17 15:57:08 +01:00
Felix Stürmer	4de5655725	[8.17] [Logs UI] Allow editing of non-resolving log views (#210633) (#211242) ... # Backport This will backport the following commits from `8.x` to `8.17`: - [[Logs UI] Allow editing of non-resolving log views (#210633)](https://github.com/elastic/kibana/pull/210633) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T14:55:17Z","message":"[Logs UI] Allow editing of non-resolving log views (#210633)\n\nThis changes the settings page of the Logs UI such that it allows editing of log view settings even if the resolution or status check failed. This allows recovery from various situations that were previously only recoverable by resetting the log view completely.","sha":"41cd657811bd1c00ac15860268c018d4d80085ac","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Logs UI","backport:skip","Team:obs-ux-logs","v8.18.0","v8.17.3"],"title":"[Logs UI] Allow editing of non-resolving log views","number":210633,"url":"https://github.com/elastic/kibana/pull/210633","mergeCommit":{"message":"[Logs UI] Allow editing of non-resolving log views (#210633)\n\nThis changes the settings page of the Logs UI such that it allows editing of log view settings even if the resolution or status check failed. This allows recovery from various situations that were previously only recoverable by resetting the log view completely.","sha":"41cd657811bd1c00ac15860268c018d4d80085ac"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-15 07:18:18 +01:00
Kibana Machine	b7cd76ef91	[8.17] Update Logs Explorer deprecation messages (#201307) (#210681) ... # Backport This will backport the following commits from `main` to `8.17`: - [Update Logs Explorer deprecation messages (#201307)](https://github.com/elastic/kibana/pull/201307) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T18:26:33Z","message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\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)","sha":"056eba293728e2f67413a70f5021dff344054126","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","ci:project-deploy-observability","Team:obs-ux-logs","Project:OneDiscover","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"Update Logs Explorer deprecation messages","number":201307,"url":"https://github.com/elastic/kibana/pull/201307","mergeCommit":{"message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\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)","sha":"056eba293728e2f67413a70f5021dff344054126"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201307","number":201307,"mergeCommit":{"message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\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)","sha":"056eba293728e2f67413a70f5021dff344054126"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>	2025-02-14 22:28:35 +01:00
Kibana Machine	3ac78a46ea	[8.17] Fix notify_badge.tsx toggle not working (#208996) (#211184) ... # Backport This will backport the following commits from `main` to `8.17`: - [Fix notify_badge.tsx toggle not working (#208996)](https://github.com/elastic/kibana/pull/208996) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eamonn-OL","email":"119305140+Eamonn-OL@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T09:56:43Z","message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nd1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:prev-major","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"Fix notify_badge.tsx toggle not working","number":208996,"url":"https://github.com/elastic/kibana/pull/208996","mergeCommit":{"message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nd1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208996","number":208996,"mergeCommit":{"message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\nd1ef9abc-e0ee-44cb-ae75-0219047c4a67\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"995b851148fab19b0922f298a7c8b3607f00de9e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Eamonn-OL <119305140+Eamonn-OL@users.noreply.github.com>	2025-02-14 12:53:02 +01:00
Bharat Pasupula	3367949254	[8.17] [Automatic Import] Fix generated name for integration title (#210916) (#211151) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix generated name for integration title (#210916)](https://github.com/elastic/kibana/pull/210916) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T16:02:03Z","message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix generated name for integration title","number":210916,"url":"https://github.com/elastic/kibana/pull/210916","mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211037","number":211037,"state":"MERGED","mergeCommit":{"sha":"badb523efc6e567dc33136f84bae6c240de7ab4c","message":"[9.0] [Automatic Import] Fix generated name for integration title (#210916) (#211037)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Automatic Import] Fix generated name for integration title\n(#210916)](https://github.com/elastic/kibana/pull/210916)\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\":\"2025-02-13T16:02:03Z\",\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"backport:prev-minor\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Fix generated name for integration\ntitle\",\"number\":210916,\"url\":\"https://github.com/elastic/kibana/pull/210916\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/210916\",\"number\":210916,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210916","number":210916,"mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-14 11:25:51 +01:00
Bharat Pasupula	276752e8b1	[8.17] [Automatic Import] Fix package name validation (#210770) (#210816) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix package name validation (#210770)](https://github.com/elastic/kibana/pull/210770) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T11:48:20Z","message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix package name validation","number":210770,"url":"https://github.com/elastic/kibana/pull/210770","mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210770","number":210770,"mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},{"url":"https://github.com/elastic/kibana/pull/210801","number":210801,"branch":"9.0","state":"OPEN"}]}] BACKPORT-->	2025-02-13 11:03:52 -06:00
Kibana Machine	c7cd1bb8c3	[8.17] [Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922) (#211007) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)](https://github.com/elastic/kibana/pull/210922) <!--- Backport version: 9.4.3 --> ### 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":"2025-02-13T13:37:37Z","message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:fix","v9.0.0","sdh-linked","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal","number":210922,"url":"https://github.com/elastic/kibana/pull/210922","mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210922","number":210922,"mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co>	2025-02-13 16:38:33 +01:00
Nick Partridge	6a61db01b9	[8.17] [Lens] Restore dynamic colouring by value for Last value agg (#209110) (#210878) ... # Backport This will backport the following commits from `main` to `8.17`: - [[Lens] Restore dynamic colouring by value for Last value agg (#209110)](https://github.com/elastic/kibana/pull/209110) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T14:55:35Z","message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport missing","backport:prev-major","v9.1.0"],"title":"[Lens] Restore dynamic colouring by value for Last value agg","number":209110,"url":"https://github.com/elastic/kibana/pull/209110","mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209110","number":209110,"mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>	2025-02-12 19:12:27 +01:00
Konrad Szwarc	244d3a654c	[8.17] [EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348) (#210833) ... # Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)](https://github.com/elastic/kibana/pull/210348) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T13:02:00Z","message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts","number":210348,"url":"https://github.com/elastic/kibana/pull/210348","mergeCommit":{"message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210822","number":210822,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210830","number":210830,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210348","number":210348,"mergeCommit":{"message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06"}}]}] BACKPORT-->	2025-02-12 17:34:43 +01:00