mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
84935 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
3b8379b249
|
[9.0] [APM][Metrics] Allow text panels in the metric dashboards (#224426) (#224473)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM][Metrics] Allow text panels in the metric dashboards (#224426)](https://github.com/elastic/kibana/pull/224426) <!--- 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-06-18T16:16:12Z","message":"[APM][Metrics] Allow text panels in the metric dashboards (#224426)\n\nCloses #224425 \n\n## Summary\n\nThis PR adds support for the text panel in the APM dashboards inside the\nmetrics tab\n\n## Testing \n\n⚠️ UPDATE: The dashboard won't be part of the PR so ⬇️ won't work now\n\n - with connection to edge oblt cluster: \n- Open Applications > Service Inventory and click on the `cart` (or any\nEDOT .NET service) service\n - Go to the metrics tab\n - The dashboard should be visible \n \n\n","sha":"2c526fc4906cee7b5018756da15718a71e8286cd","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","apm:opentelemetry","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[APM][Metrics] Allow text panels in the metric dashboards","number":224426,"url":"https://github.com/elastic/kibana/pull/224426","mergeCommit":{"message":"[APM][Metrics] Allow text panels in the metric dashboards (#224426)\n\nCloses #224425 \n\n## Summary\n\nThis PR adds support for the text panel in the APM dashboards inside the\nmetrics tab\n\n## Testing \n\n⚠️ UPDATE: The dashboard won't be part of the PR so ⬇️ won't work now\n\n - with connection to edge oblt cluster: \n- Open Applications > Service Inventory and click on the `cart` (or any\nEDOT .NET service) service\n - Go to the metrics tab\n - The dashboard should be visible \n \n\n","sha":"2c526fc4906cee7b5018756da15718a71e8286cd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224426","number":224426,"mergeCommit":{"message":"[APM][Metrics] Allow text panels in the metric dashboards (#224426)\n\nCloses #224425 \n\n## Summary\n\nThis PR adds support for the text panel in the APM dashboards inside the\nmetrics tab\n\n## Testing \n\n⚠️ UPDATE: The dashboard won't be part of the PR so ⬇️ won't work now\n\n - with connection to edge oblt cluster: \n- Open Applications > Service Inventory and click on the `cart` (or any\nEDOT .NET service) service\n - Go to the metrics tab\n - The dashboard should be visible \n \n\n","sha":"2c526fc4906cee7b5018756da15718a71e8286cd"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
aa5b12683f
|
[9.0] [Cases] - Add missing codeowners (#224163) (#224469)
# Backport This will backport the following commits from `main` to `9.0`: - [[Cases] - Add missing codeowners (#224163)](https://github.com/elastic/kibana/pull/224163) <!--- 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-06-18T16:05:26Z","message":"[Cases] - Add missing codeowners (#224163)\n\n## Summary\n\nadd missing codeowners for file path","sha":"6c0d67ea8834fa68d19f232a655ed516a2092997","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Cases","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3","v8.17.8"],"title":"[Cases] - Add missing codeowners","number":224163,"url":"https://github.com/elastic/kibana/pull/224163","mergeCommit":{"message":"[Cases] - Add missing codeowners (#224163)\n\n## Summary\n\nadd missing codeowners for file path","sha":"6c0d67ea8834fa68d19f232a655ed516a2092997"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224163","number":224163,"mergeCommit":{"message":"[Cases] - Add missing codeowners (#224163)\n\n## Summary\n\nadd missing codeowners for file path","sha":"6c0d67ea8834fa68d19f232a655ed516a2092997"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> |
||
|
Kibana Machine
|
c1c70ea65d
|
[9.0] [Synthetics] Error details - Improved network error handling (#224296) (#224447)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Error details - Improved network error handling (#224296)](https://github.com/elastic/kibana/pull/224296) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-06-18T14:58:17Z","message":"[Synthetics] Error details - Improved network error handling (#224296)\n\nThis PR improves how we handle network errors in the Error details page\nin Synthetics.\n\n**Before**\n\n\n |
||
Nikita Indik
|
5e02f5e972
|
[9.0] [Security Solution] Fix "too many clauses" error on prebuilt rules installation page (#223240) (#224282)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix "too many clauses" error on prebuilt rules installation page (#223240)](https://github.com/elastic/kibana/pull/223240) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T14:14:56Z","message":"[Security Solution] Fix \"too many clauses\" error on prebuilt rules installation page (#223240)\n\n**Resolves: https://github.com/elastic/kibana/issues/223399**\n\n## Summary\nThis PR fixes an error on the \"Add Elastic rules\" page. The error is\nshown when running a local dev environment from `main` branch and going\nto the \"Add Elastic rules\" page.\n\n<img width=\"1741\" alt=\"Screenshot 2025-06-10 at 11 28 19\"\nsrc=\"https://github.com/user-attachments/assets/f8f81f88-3749-491f-bcdb-cd51f465bda6\"\n/>\n\n## Changes\nPR updates methods of `PrebuiltRuleAssetsClient` to split requests to ES\ninto smaller chunks to avoid the error.\n\n## Cause\nKibana makes a search request to ES with a filter that has too many\nclauses, so ES rejects with an error.\n\nMore specifically, `/prebuilt_rules/installation/_review` route handler\ncalls `PrebuiltRuleAssetsClient.fetchAssetsByVersion` to fetch all\ninstallable rules. To do this, we construct a request with thousands of\nclauses in a filter. ES counts the number of clauses in a filter and\nrejects because it's bigger than `maxClauseCount`. `maxClauseCount`\nvalue is computed dynamically by ES and its size depends on hardware and\navailable resources\n([docs](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/search-settings.html),\n[code](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/search/SearchUtils.java)).\nThe minimum value for `maxClauseCount` is 1024.\n\n## Why it didn't fail before\nTwo reasons:\n1. ES changed how `maxClauseCount` is computed. They've recently merged\na [PR](https://github.com/elastic/elasticsearch/pull/128293) that made\nqueries against numeric types count three times towards the\n`maxClauseCount` limit. They plan to revert the change in [this\nPR](https://github.com/elastic/elasticsearch/pull/129206).\n2. Prebuilt rule packages are growing bigger with each version,\nresulting in a bigger number of clauses. I've tested behaviour with ES\nchange in place on different package versions:\n- 8.17.1 (contains 1262 rule versions) - no \"too many clauses\" error\n- 8.18.1 (contains 1356 rule versions) - causes \"too many clauses\" error\n- 9.0.1 (also contains 1356 rule versions) - causes \"too many clauses\"\nerror\nThe precise number of versions that start to cause errors is 1293 on my\nlaptop.\n\nSo even if ES team rolls back their change, we still need to make sure\nwe don't go over the limit with ever-growing prebuilt rule package\nsizes.","sha":"482953ddc5a9e1494a3182c9cedfa4214179a297","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Security Solution] Fix \"too many clauses\" error on prebuilt rules installation page","number":223240,"url":"https://github.com/elastic/kibana/pull/223240","mergeCommit":{"message":"[Security Solution] Fix \"too many clauses\" error on prebuilt rules installation page (#223240)\n\n**Resolves: https://github.com/elastic/kibana/issues/223399**\n\n## Summary\nThis PR fixes an error on the \"Add Elastic rules\" page. The error is\nshown when running a local dev environment from `main` branch and going\nto the \"Add Elastic rules\" page.\n\n<img width=\"1741\" alt=\"Screenshot 2025-06-10 at 11 28 19\"\nsrc=\"https://github.com/user-attachments/assets/f8f81f88-3749-491f-bcdb-cd51f465bda6\"\n/>\n\n## Changes\nPR updates methods of `PrebuiltRuleAssetsClient` to split requests to ES\ninto smaller chunks to avoid the error.\n\n## Cause\nKibana makes a search request to ES with a filter that has too many\nclauses, so ES rejects with an error.\n\nMore specifically, `/prebuilt_rules/installation/_review` route handler\ncalls `PrebuiltRuleAssetsClient.fetchAssetsByVersion` to fetch all\ninstallable rules. To do this, we construct a request with thousands of\nclauses in a filter. ES counts the number of clauses in a filter and\nrejects because it's bigger than `maxClauseCount`. `maxClauseCount`\nvalue is computed dynamically by ES and its size depends on hardware and\navailable resources\n([docs](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/search-settings.html),\n[code](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/search/SearchUtils.java)).\nThe minimum value for `maxClauseCount` is 1024.\n\n## Why it didn't fail before\nTwo reasons:\n1. ES changed how `maxClauseCount` is computed. They've recently merged\na [PR](https://github.com/elastic/elasticsearch/pull/128293) that made\nqueries against numeric types count three times towards the\n`maxClauseCount` limit. They plan to revert the change in [this\nPR](https://github.com/elastic/elasticsearch/pull/129206).\n2. Prebuilt rule packages are growing bigger with each version,\nresulting in a bigger number of clauses. I've tested behaviour with ES\nchange in place on different package versions:\n- 8.17.1 (contains 1262 rule versions) - no \"too many clauses\" error\n- 8.18.1 (contains 1356 rule versions) - causes \"too many clauses\" error\n- 9.0.1 (also contains 1356 rule versions) - causes \"too many clauses\"\nerror\nThe precise number of versions that start to cause errors is 1293 on my\nlaptop.\n\nSo even if ES team rolls back their change, we still need to make sure\nwe don't go over the limit with ever-growing prebuilt rule package\nsizes.","sha":"482953ddc5a9e1494a3182c9cedfa4214179a297"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223240","number":223240,"mergeCommit":{"message":"[Security Solution] Fix \"too many clauses\" error on prebuilt rules installation page (#223240)\n\n**Resolves: https://github.com/elastic/kibana/issues/223399**\n\n## Summary\nThis PR fixes an error on the \"Add Elastic rules\" page. The error is\nshown when running a local dev environment from `main` branch and going\nto the \"Add Elastic rules\" page.\n\n<img width=\"1741\" alt=\"Screenshot 2025-06-10 at 11 28 19\"\nsrc=\"https://github.com/user-attachments/assets/f8f81f88-3749-491f-bcdb-cd51f465bda6\"\n/>\n\n## Changes\nPR updates methods of `PrebuiltRuleAssetsClient` to split requests to ES\ninto smaller chunks to avoid the error.\n\n## Cause\nKibana makes a search request to ES with a filter that has too many\nclauses, so ES rejects with an error.\n\nMore specifically, `/prebuilt_rules/installation/_review` route handler\ncalls `PrebuiltRuleAssetsClient.fetchAssetsByVersion` to fetch all\ninstallable rules. To do this, we construct a request with thousands of\nclauses in a filter. ES counts the number of clauses in a filter and\nrejects because it's bigger than `maxClauseCount`. `maxClauseCount`\nvalue is computed dynamically by ES and its size depends on hardware and\navailable resources\n([docs](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/search-settings.html),\n[code](https://github.com/elastic/elasticsearch/blob/main/server/src/main/java/org/elasticsearch/search/SearchUtils.java)).\nThe minimum value for `maxClauseCount` is 1024.\n\n## Why it didn't fail before\nTwo reasons:\n1. ES changed how `maxClauseCount` is computed. They've recently merged\na [PR](https://github.com/elastic/elasticsearch/pull/128293) that made\nqueries against numeric types count three times towards the\n`maxClauseCount` limit. They plan to revert the change in [this\nPR](https://github.com/elastic/elasticsearch/pull/129206).\n2. Prebuilt rule packages are growing bigger with each version,\nresulting in a bigger number of clauses. I've tested behaviour with ES\nchange in place on different package versions:\n- 8.17.1 (contains 1262 rule versions) - no \"too many clauses\" error\n- 8.18.1 (contains 1356 rule versions) - causes \"too many clauses\" error\n- 9.0.1 (also contains 1356 rule versions) - causes \"too many clauses\"\nerror\nThe precise number of versions that start to cause errors is 1293 on my\nlaptop.\n\nSo even if ES team rolls back their change, we still need to make sure\nwe don't go over the limit with ever-growing prebuilt rule package\nsizes.","sha":"482953ddc5a9e1494a3182c9cedfa4214179a297"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/224269","number":224269,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Tim Sullivan
|
c5a46f4487
|
[9.0] [Canvas/PDF report] Allow canvas to generate PDF report (#224309) (#224338)
# Backport This will backport the following commits from `main` to `9.0`: - [[Canvas/PDF report] Allow canvas to generate PDF report (#224309)](https://github.com/elastic/kibana/pull/224309) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-17T22:47:22Z","message":"[Canvas/PDF report] Allow canvas to generate PDF report (#224309)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/224275\n\n**Context:** In https://github.com/elastic/kibana/pull/222273, we added\nrestrictions to the \"Reporting redirect app\" to make sure it could not\nbe abused by using unexpected locator types (such as the short URL\nlocator or the \"legacy\" locator type) when triggering redirects in the\nReporting headless browser. The restrictions are on the basis of a list\nof allowed locator types, which should be a list of every analytical app\nthat supports Reporting.\n\n**Problem:** Unfortunately that added a regression to Canvas PDF\nreporting, because the allow-list for locator types neglected to include\nthe Canvas locator type.\n\nThis PR solves the problem by adding the Canvas locator type to the set\nof allowed locator types.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f5dee1347f019d4e98a45070eeb80356453a9827","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v8.15.6","v9.1.0","v8.19.0","v7.17.29","v9.0.3","v8.18.3","v8.17.8"],"title":"[Canvas/PDF report] Allow canvas to generate PDF report","number":224309,"url":"https://github.com/elastic/kibana/pull/224309","mergeCommit":{"message":"[Canvas/PDF report] Allow canvas to generate PDF report (#224309)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/224275\n\n**Context:** In https://github.com/elastic/kibana/pull/222273, we added\nrestrictions to the \"Reporting redirect app\" to make sure it could not\nbe abused by using unexpected locator types (such as the short URL\nlocator or the \"legacy\" locator type) when triggering redirects in the\nReporting headless browser. The restrictions are on the basis of a list\nof allowed locator types, which should be a list of every analytical app\nthat supports Reporting.\n\n**Problem:** Unfortunately that added a regression to Canvas PDF\nreporting, because the allow-list for locator types neglected to include\nthe Canvas locator type.\n\nThis PR solves the problem by adding the Canvas locator type to the set\nof allowed locator types.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f5dee1347f019d4e98a45070eeb80356453a9827"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","7.17","9.0","8.18","8.17"],"targetPullRequestStates":[{"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/224309","number":224309,"mergeCommit":{"message":"[Canvas/PDF report] Allow canvas to generate PDF report (#224309)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/224275\n\n**Context:** In https://github.com/elastic/kibana/pull/222273, we added\nrestrictions to the \"Reporting redirect app\" to make sure it could not\nbe abused by using unexpected locator types (such as the short URL\nlocator or the \"legacy\" locator type) when triggering redirects in the\nReporting headless browser. The restrictions are on the basis of a list\nof allowed locator types, which should be a list of every analytical app\nthat supports Reporting.\n\n**Problem:** Unfortunately that added a regression to Canvas PDF\nreporting, because the allow-list for locator types neglected to include\nthe Canvas locator type.\n\nThis PR solves the problem by adding the Canvas locator type to the set\nof allowed locator types.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f5dee1347f019d4e98a45070eeb80356453a9827"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/224335","number":224335,"state":"OPEN"},{"branch":"7.17","label":"v7.17.29","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Patrick Mueller
|
f01c346bfa
|
[9.0] [ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409) (#224345)
# Backport This will backport the following commits from `main` to `9.0`: - [[ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409)](https://github.com/elastic/kibana/pull/223409) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T16:47:31Z","message":"[ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409)\n\nresolves https://github.com/elastic/kibana/issues/221252\n\nEnsure alert field values added from grouping information are the right\ncardinality. Previously, array typed fields were assigned strings and\nthe string characters were split into an array by down-stream\nprocessing.","sha":"ac5c313c1d25ebb28bbd6a88915b789a5c4183c1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesFramework","Feature:Alerting/Alerts-as-Data","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[ResponseOps][Alerting] assure grouping fields in alert match expected cardinality","number":223409,"url":"https://github.com/elastic/kibana/pull/223409","mergeCommit":{"message":"[ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409)\n\nresolves https://github.com/elastic/kibana/issues/221252\n\nEnsure alert field values added from grouping information are the right\ncardinality. Previously, array typed fields were assigned strings and\nthe string characters were split into an array by down-stream\nprocessing.","sha":"ac5c313c1d25ebb28bbd6a88915b789a5c4183c1"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223409","number":223409,"mergeCommit":{"message":"[ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409)\n\nresolves https://github.com/elastic/kibana/issues/221252\n\nEnsure alert field values added from grouping information are the right\ncardinality. Previously, array typed fields were assigned strings and\nthe string characters were split into an array by down-stream\nprocessing.","sha":"ac5c313c1d25ebb28bbd6a88915b789a5c4183c1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Anton Dosov
|
845194741c
|
[9.0] Update classnames dependencies (main) (#219587) (#224378)
# Backport This will backport the following commits from `main` to `9.0`: - [Update classnames dependencies (main) (#219587)](https://github.com/elastic/kibana/pull/219587) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-17T15:27:28Z","message":"Update classnames dependencies (main) (#219587)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/classnames | devDependencies | minor | [`^2.2.9` ->\n`^2.3.4`](https://renovatebot.com/diffs/npm/@types%2fclassnames/2.2.9/2.3.4)\n|\n| [classnames](https://redirect.github.com/JedWatson/classnames) |\ndependencies | minor | [`2.2.6` ->\n`2.5.1`](https://renovatebot.com/diffs/npm/classnames/2.2.6/2.5.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>JedWatson/classnames (classnames)</summary>\n\n###\n[`v2.5.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v251--2023-12-29)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.5.0...v2.5.1)\n\n- Remove `workspaces` field from package\n([#​350](https://redirect.github.com/JedWatson/classnames/pull/350))\n\n###\n[`v2.5.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v250--2023-12-27)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.4.0...v2.5.0)\n\n- Restore ability to pass a TypeScript `interface`\n([#​341](https://redirect.github.com/JedWatson/classnames/pull/341))\n- Add `exports` field to package\n([#​342](https://redirect.github.com/JedWatson/classnames/pull/342))\n\n###\n[`v2.4.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v240--2023-12-26)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.3...v2.4.0)\n\n- Use string concatenation to increase performance thanks [Jon\nKoops](https://redirect.github.com/jonkoops)\n([#​336](https://redirect.github.com/JedWatson/classnames/pull/336))\n\n###\n[`v2.3.3`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v233--2023-12-21)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.2...v2.3.3)\n\n- Fix default export, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​301](https://redirect.github.com/JedWatson/classnames/pull/301))\n- Fix types for read-only arrays, thanks [Ben\nThompson](https://redirect.github.com/BenGearset)\n([#​307](https://redirect.github.com/JedWatson/classnames/pull/307))\n- Replace README examples with functional-style components, thanks\n[JoeDGit](https://redirect.github.com/JoeDGit)\n([#​303](https://redirect.github.com/JedWatson/classnames/pull/303))\n\n###\n[`v2.3.2`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v232--2022-09-13)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.1...v2.3.2)\n\n- Fix TypeScript types when using require, thanks [Mark\nDalgleish](https://redirect.github.com/markdalgleish)\n([#​276](https://redirect.github.com/JedWatson/classnames/pull/276))\n- Fix toString as `[Object object]` in a vm, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​281](https://redirect.github.com/JedWatson/classnames/pull/281))\n\n###\n[`v2.3.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v231--2021-04-03)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.0...v2.3.1)\n\n- Fix bind/dedupe TypeScript types exports\n- Fix mapping Value types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n- Removed non-existent named exports from types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n\n###\n[`v2.3.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v230--2021-04-01)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.2.6...v2.3.0)\n\n- Added TypeScript types\n- Added consistent support for custom `.toString()` methods on\narguments, thanks [Stanislav\nTitenko](https://redirect.github.com/resetko)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3b4bd5895e53c371a6f281d16c8d982e258ffbf1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update classnames dependencies (main)","number":219587,"url":"https://github.com/elastic/kibana/pull/219587","mergeCommit":{"message":"Update classnames dependencies (main) (#219587)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/classnames | devDependencies | minor | [`^2.2.9` ->\n`^2.3.4`](https://renovatebot.com/diffs/npm/@types%2fclassnames/2.2.9/2.3.4)\n|\n| [classnames](https://redirect.github.com/JedWatson/classnames) |\ndependencies | minor | [`2.2.6` ->\n`2.5.1`](https://renovatebot.com/diffs/npm/classnames/2.2.6/2.5.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>JedWatson/classnames (classnames)</summary>\n\n###\n[`v2.5.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v251--2023-12-29)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.5.0...v2.5.1)\n\n- Remove `workspaces` field from package\n([#​350](https://redirect.github.com/JedWatson/classnames/pull/350))\n\n###\n[`v2.5.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v250--2023-12-27)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.4.0...v2.5.0)\n\n- Restore ability to pass a TypeScript `interface`\n([#​341](https://redirect.github.com/JedWatson/classnames/pull/341))\n- Add `exports` field to package\n([#​342](https://redirect.github.com/JedWatson/classnames/pull/342))\n\n###\n[`v2.4.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v240--2023-12-26)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.3...v2.4.0)\n\n- Use string concatenation to increase performance thanks [Jon\nKoops](https://redirect.github.com/jonkoops)\n([#​336](https://redirect.github.com/JedWatson/classnames/pull/336))\n\n###\n[`v2.3.3`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v233--2023-12-21)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.2...v2.3.3)\n\n- Fix default export, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​301](https://redirect.github.com/JedWatson/classnames/pull/301))\n- Fix types for read-only arrays, thanks [Ben\nThompson](https://redirect.github.com/BenGearset)\n([#​307](https://redirect.github.com/JedWatson/classnames/pull/307))\n- Replace README examples with functional-style components, thanks\n[JoeDGit](https://redirect.github.com/JoeDGit)\n([#​303](https://redirect.github.com/JedWatson/classnames/pull/303))\n\n###\n[`v2.3.2`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v232--2022-09-13)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.1...v2.3.2)\n\n- Fix TypeScript types when using require, thanks [Mark\nDalgleish](https://redirect.github.com/markdalgleish)\n([#​276](https://redirect.github.com/JedWatson/classnames/pull/276))\n- Fix toString as `[Object object]` in a vm, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​281](https://redirect.github.com/JedWatson/classnames/pull/281))\n\n###\n[`v2.3.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v231--2021-04-03)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.0...v2.3.1)\n\n- Fix bind/dedupe TypeScript types exports\n- Fix mapping Value types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n- Removed non-existent named exports from types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n\n###\n[`v2.3.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v230--2021-04-01)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.2.6...v2.3.0)\n\n- Added TypeScript types\n- Added consistent support for custom `.toString()` methods on\narguments, thanks [Stanislav\nTitenko](https://redirect.github.com/resetko)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3b4bd5895e53c371a6f281d16c8d982e258ffbf1"}},"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/219587","number":219587,"mergeCommit":{"message":"Update classnames dependencies (main) (#219587)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/classnames | devDependencies | minor | [`^2.2.9` ->\n`^2.3.4`](https://renovatebot.com/diffs/npm/@types%2fclassnames/2.2.9/2.3.4)\n|\n| [classnames](https://redirect.github.com/JedWatson/classnames) |\ndependencies | minor | [`2.2.6` ->\n`2.5.1`](https://renovatebot.com/diffs/npm/classnames/2.2.6/2.5.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>JedWatson/classnames (classnames)</summary>\n\n###\n[`v2.5.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v251--2023-12-29)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.5.0...v2.5.1)\n\n- Remove `workspaces` field from package\n([#​350](https://redirect.github.com/JedWatson/classnames/pull/350))\n\n###\n[`v2.5.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v250--2023-12-27)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.4.0...v2.5.0)\n\n- Restore ability to pass a TypeScript `interface`\n([#​341](https://redirect.github.com/JedWatson/classnames/pull/341))\n- Add `exports` field to package\n([#​342](https://redirect.github.com/JedWatson/classnames/pull/342))\n\n###\n[`v2.4.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v240--2023-12-26)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.3...v2.4.0)\n\n- Use string concatenation to increase performance thanks [Jon\nKoops](https://redirect.github.com/jonkoops)\n([#​336](https://redirect.github.com/JedWatson/classnames/pull/336))\n\n###\n[`v2.3.3`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v233--2023-12-21)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.2...v2.3.3)\n\n- Fix default export, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​301](https://redirect.github.com/JedWatson/classnames/pull/301))\n- Fix types for read-only arrays, thanks [Ben\nThompson](https://redirect.github.com/BenGearset)\n([#​307](https://redirect.github.com/JedWatson/classnames/pull/307))\n- Replace README examples with functional-style components, thanks\n[JoeDGit](https://redirect.github.com/JoeDGit)\n([#​303](https://redirect.github.com/JedWatson/classnames/pull/303))\n\n###\n[`v2.3.2`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v232--2022-09-13)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.1...v2.3.2)\n\n- Fix TypeScript types when using require, thanks [Mark\nDalgleish](https://redirect.github.com/markdalgleish)\n([#​276](https://redirect.github.com/JedWatson/classnames/pull/276))\n- Fix toString as `[Object object]` in a vm, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n([#​281](https://redirect.github.com/JedWatson/classnames/pull/281))\n\n###\n[`v2.3.1`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v231--2021-04-03)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.3.0...v2.3.1)\n\n- Fix bind/dedupe TypeScript types exports\n- Fix mapping Value types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n- Removed non-existent named exports from types, thanks [Remco\nHaszing](https://redirect.github.com/remcohaszing)\n\n###\n[`v2.3.0`](https://redirect.github.com/JedWatson/classnames/blob/HEAD/HISTORY.md#v230--2021-04-01)\n\n[Compare\nSource](https://redirect.github.com/JedWatson/classnames/compare/v2.2.6...v2.3.0)\n\n- Added TypeScript types\n- Added consistent support for custom `.toString()` methods on\narguments, thanks [Stanislav\nTitenko](https://redirect.github.com/resetko)\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3b4bd5895e53c371a6f281d16c8d982e258ffbf1"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Anton Dosov
|
5737e8cae6
|
[9.0] Update dependency react-use to v17 (main) (#219595) (#224281)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency react-use to v17 (main) (#219595)](https://github.com/elastic/kibana/pull/219595) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-17T14:53:42Z","message":"Update dependency react-use to v17 (main) (#219595)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [react-use](https://redirect.github.com/streamich/react-use) |\ndependencies | major | [`^15.3.8` ->\n`^17.6.0`](https://renovatebot.com/diffs/npm/react-use/15.3.8/17.6.0) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>streamich/react-use (react-use)</summary>\n\n###\n[`v17.6.0`](https://redirect.github.com/streamich/react-use/blob/HEAD/CHANGELOG.md#1760-2024-12-09)\n\n[Compare\nSource](https://redirect.github.com/streamich/react-use/compare/v17.5.1...v17.6.0)\n\n##### Features\n\n- add onChange callback to useWindowSize\n([ea656f7]( |
||
|
Kibana Machine
|
ec75ce80be
|
[9.0] Update elastic-managed-llm.md (#224337) (#224358)
# Backport This will backport the following commits from `main` to `9.0`: - [Update elastic-managed-llm.md (#224337)](https://github.com/elastic/kibana/pull/224337) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shubha Anjur Tupil","email":"at.shubha@gmail.com"},"sourceCommit":{"committedDate":"2025-06-18T08:05:55Z","message":"Update elastic-managed-llm.md (#224337)\n\nAdded a detail to make it clear we are not hosting the LLM but proxying\nto AWS Bedrock in us-east-1\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: István Zoltán Szabó <szabosteve@gmail.com>","sha":"1a26254fb6cdde38f1efe84b3ddf21d96f11dacb","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v9.0.3"],"title":"Update elastic-managed-llm.md","number":224337,"url":"https://github.com/elastic/kibana/pull/224337","mergeCommit":{"message":"Update elastic-managed-llm.md (#224337)\n\nAdded a detail to make it clear we are not hosting the LLM but proxying\nto AWS Bedrock in us-east-1\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: István Zoltán Szabó <szabosteve@gmail.com>","sha":"1a26254fb6cdde38f1efe84b3ddf21d96f11dacb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224337","number":224337,"mergeCommit":{"message":"Update elastic-managed-llm.md (#224337)\n\nAdded a detail to make it clear we are not hosting the LLM but proxying\nto AWS Bedrock in us-east-1\n\n## Summary\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: István Zoltán Szabó <szabosteve@gmail.com>","sha":"1a26254fb6cdde38f1efe84b3ddf21d96f11dacb"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shubha Anjur Tupil <at.shubha@gmail.com> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com> |
||
Steph Milovic
|
d4e987247a
|
[9.0] [Security Assistant] Fix telemetry tool reporting (#223832) (#224343)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Assistant] Fix telemetry tool reporting (#223832)](https://github.com/elastic/kibana/pull/223832) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-06-12T22:52:33Z","message":"[Security Assistant] Fix telemetry tool reporting (#223832)","sha":"602f96d46a3332471437e5e79faa5454293cbe14","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Security Assistant] Fix telemetry tool reporting","number":223832,"url":"https://github.com/elastic/kibana/pull/223832","mergeCommit":{"message":"[Security Assistant] Fix telemetry tool reporting (#223832)","sha":"602f96d46a3332471437e5e79faa5454293cbe14"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223832","number":223832,"mergeCommit":{"message":"[Security Assistant] Fix telemetry tool reporting (#223832)","sha":"602f96d46a3332471437e5e79faa5454293cbe14"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223845","number":223845,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Garrett Spong
|
ab991ed140
|
[9.0] [Connectors] Fix Bedrock connector not using the action proxy configuration (#224130) (#224326)
# Backport This will backport the following commits from `main` to `9.0`: - [[Connectors] Fix Bedrock connector not using the action proxy configuration (#224130)](https://github.com/elastic/kibana/pull/224130) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Garrett Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-17T20:07:24Z","message":"[Connectors] Fix Bedrock connector not using the action proxy configuration (#224130)\n\n## Summary\n\nSimilar to https://github.com/elastic/kibana/pull/219617, this PR fixes\nan issue with the `BedrockConnector` not using the configured\n`xpack.actions.proxyUrl`.\n\nTo test, add the following\n[`xpack.actions.proxyUrl`](https://p.elstc.co/paste/DaM71BUP#iHki8gmY4-LZcfQD0ja6HeMHknuvpEvQtSbapcAEOXb)\nto your `kibana.dev.yml`, then create a Bedrock connector and confirm in\nthe Kibana server logs that the configured proxy is being used and a\nsuccessful response is returned. Sample `debug` logs look something\nalong the lines of:\n\n\n```\n[2025-06-16T11:59:36.282-06:00][DEBUG][plugins.actions.bedrock] executing action .bedrock:sonnet-3-7: Sonnet 3.7 (Bedrock)\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Request to external service. Connector Id: sonnet-3-7. Connector type: .bedrock Method: post. URL: https://bedrock-runtime.us-east-1.amazonaws.com/model/us.anthropic.claude-3-7-sonnet-20250219-v1%3A0/invoke\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Creating proxy agents for proxy: https://PROXY_URL/\n```\n\n\nBe sure to enable debug logging for the actions plugin ala:\n\n```\nlogging:\n loggers:\n - name: plugins.actions\n level: debug\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\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"321f9a18d4d93bf87ef2b1612edbd571bf0fcb48","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","backport:version","Team:AI Infra","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Connectors] Fix Bedrock connector not using the action proxy configuration","number":224130,"url":"https://github.com/elastic/kibana/pull/224130","mergeCommit":{"message":"[Connectors] Fix Bedrock connector not using the action proxy configuration (#224130)\n\n## Summary\n\nSimilar to https://github.com/elastic/kibana/pull/219617, this PR fixes\nan issue with the `BedrockConnector` not using the configured\n`xpack.actions.proxyUrl`.\n\nTo test, add the following\n[`xpack.actions.proxyUrl`](https://p.elstc.co/paste/DaM71BUP#iHki8gmY4-LZcfQD0ja6HeMHknuvpEvQtSbapcAEOXb)\nto your `kibana.dev.yml`, then create a Bedrock connector and confirm in\nthe Kibana server logs that the configured proxy is being used and a\nsuccessful response is returned. Sample `debug` logs look something\nalong the lines of:\n\n\n```\n[2025-06-16T11:59:36.282-06:00][DEBUG][plugins.actions.bedrock] executing action .bedrock:sonnet-3-7: Sonnet 3.7 (Bedrock)\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Request to external service. Connector Id: sonnet-3-7. Connector type: .bedrock Method: post. URL: https://bedrock-runtime.us-east-1.amazonaws.com/model/us.anthropic.claude-3-7-sonnet-20250219-v1%3A0/invoke\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Creating proxy agents for proxy: https://PROXY_URL/\n```\n\n\nBe sure to enable debug logging for the actions plugin ala:\n\n```\nlogging:\n loggers:\n - name: plugins.actions\n level: debug\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\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"321f9a18d4d93bf87ef2b1612edbd571bf0fcb48"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224130","number":224130,"mergeCommit":{"message":"[Connectors] Fix Bedrock connector not using the action proxy configuration (#224130)\n\n## Summary\n\nSimilar to https://github.com/elastic/kibana/pull/219617, this PR fixes\nan issue with the `BedrockConnector` not using the configured\n`xpack.actions.proxyUrl`.\n\nTo test, add the following\n[`xpack.actions.proxyUrl`](https://p.elstc.co/paste/DaM71BUP#iHki8gmY4-LZcfQD0ja6HeMHknuvpEvQtSbapcAEOXb)\nto your `kibana.dev.yml`, then create a Bedrock connector and confirm in\nthe Kibana server logs that the configured proxy is being used and a\nsuccessful response is returned. Sample `debug` logs look something\nalong the lines of:\n\n\n```\n[2025-06-16T11:59:36.282-06:00][DEBUG][plugins.actions.bedrock] executing action .bedrock:sonnet-3-7: Sonnet 3.7 (Bedrock)\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Request to external service. Connector Id: sonnet-3-7. Connector type: .bedrock Method: post. URL: https://bedrock-runtime.us-east-1.amazonaws.com/model/us.anthropic.claude-3-7-sonnet-20250219-v1%3A0/invoke\n[2025-06-16T11:59:36.286-06:00][DEBUG][plugins.actions] Creating proxy agents for proxy: https://PROXY_URL/\n```\n\n\nBe sure to enable debug logging for the actions plugin ala:\n\n```\nlogging:\n loggers:\n - name: plugins.actions\n level: debug\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\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"321f9a18d4d93bf87ef2b1612edbd571bf0fcb48"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
eaa52d69fe
|
[9.0] [Infra] Add retry to url assert (#224126) (#224313)
# Backport This will backport the following commits from `main` to `9.0`: - [[Infra] Add retry to url assert (#224126)](https://github.com/elastic/kibana/pull/224126) <!--- 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-06-17T17:21:17Z","message":"[Infra] Add retry to url assert (#224126)\n\nfixes [#192882](https://github.com/elastic/kibana/issues/192882)","sha":"012761e80c1e863ee93115c129de1c0959d4007f","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Infra] Add retry to url assert","number":224126,"url":"https://github.com/elastic/kibana/pull/224126","mergeCommit":{"message":"[Infra] Add retry to url assert (#224126)\n\nfixes [#192882](https://github.com/elastic/kibana/issues/192882)","sha":"012761e80c1e863ee93115c129de1c0959d4007f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.19"],"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/224126","number":224126,"mergeCommit":{"message":"[Infra] Add retry to url assert (#224126)\n\nfixes [#192882](https://github.com/elastic/kibana/issues/192882)","sha":"012761e80c1e863ee93115c129de1c0959d4007f"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
|
Kibana Machine
|
5fd06dc37b
|
[9.0] [Security Solution] Fix rule filters display issues (#222963) (#224303)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix rule filters display issues (#222963)](https://github.com/elastic/kibana/pull/222963) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T16:14:44Z","message":"[Security Solution] Fix rule filters display issues (#222963)\n\n**Resolves: https://github.com/elastic/kibana/issues/203615**\n**Resolves: https://github.com/elastic/kibana/issues/203600**\n\n## Summary\nThis PR resolves a few bugs related to how query filters are displayed:\n- fixes display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout (bug introduced in PR #210191)\n - fixes warnings shown in edit mode of rule upgrade flyout\n- fixes warning flashes on rule edit page when updating the index\npattern\n\n## Changes\n\n### Display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout\nCaused by change in recent [PR](#210191) where we stopped responding\nwith a full filter object.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"951\" alt=\"broken_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/3b06feb6-595f-4140-a795-3ac7a3d81fed\"\n/>\n\n **After**\n<img width=\"948\" alt=\"fixed_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/6a59c2a5-7165-4e4e-9a2f-8cb4250125a0\"\n/>\n</details>\n\n### Warnings shown in edit mode of rule upgrade flyout\nCaused by a mismatch between index patterns in filters and data view\nobjects. We path both filters and a data view into a unified search\ncomponent. If it detects a mismatch, it shows a confusing warning.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"1265\" alt=\"broken_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/947be729-a247-4eee-8046-155c2599e0bd\"\n/>\n\n **After**\n<img width=\"1265\" alt=\"fixed_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/7bec19bc-5180-47f1-876e-850677d1503d\"\n/>\n</details>\n\n### Warning flashes on rule edit page when updating the index pattern\nCaused by a re-render with an incomplete DataView object.\n\n<details>\n <summary>Click to see screen recordings</summary>\n **Before**\n\n\nhttps://github.com/user-attachments/assets/0140cfa5-4a87-4ed2-8c81-80e3b94e1166\n\n **After**\n\n\nhttps://github.com/user-attachments/assets/0b539d11-bed2-4e4b-9399-ea95f7f5baa4\n\n</details>\n\nAlso removed\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/threatmatch_input/index.tsx`\nbecause it was not used anywhere.","sha":"f0829b7c1179ef998380153ad7dd5b6a3bee6ea2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","Feature:Rule Creation","Feature:Rule Edit","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3","v8.17.8"],"title":"[Security Solution] Fix rule filters display issues","number":222963,"url":"https://github.com/elastic/kibana/pull/222963","mergeCommit":{"message":"[Security Solution] Fix rule filters display issues (#222963)\n\n**Resolves: https://github.com/elastic/kibana/issues/203615**\n**Resolves: https://github.com/elastic/kibana/issues/203600**\n\n## Summary\nThis PR resolves a few bugs related to how query filters are displayed:\n- fixes display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout (bug introduced in PR #210191)\n - fixes warnings shown in edit mode of rule upgrade flyout\n- fixes warning flashes on rule edit page when updating the index\npattern\n\n## Changes\n\n### Display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout\nCaused by change in recent [PR](#210191) where we stopped responding\nwith a full filter object.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"951\" alt=\"broken_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/3b06feb6-595f-4140-a795-3ac7a3d81fed\"\n/>\n\n **After**\n<img width=\"948\" alt=\"fixed_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/6a59c2a5-7165-4e4e-9a2f-8cb4250125a0\"\n/>\n</details>\n\n### Warnings shown in edit mode of rule upgrade flyout\nCaused by a mismatch between index patterns in filters and data view\nobjects. We path both filters and a data view into a unified search\ncomponent. If it detects a mismatch, it shows a confusing warning.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"1265\" alt=\"broken_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/947be729-a247-4eee-8046-155c2599e0bd\"\n/>\n\n **After**\n<img width=\"1265\" alt=\"fixed_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/7bec19bc-5180-47f1-876e-850677d1503d\"\n/>\n</details>\n\n### Warning flashes on rule edit page when updating the index pattern\nCaused by a re-render with an incomplete DataView object.\n\n<details>\n <summary>Click to see screen recordings</summary>\n **Before**\n\n\nhttps://github.com/user-attachments/assets/0140cfa5-4a87-4ed2-8c81-80e3b94e1166\n\n **After**\n\n\nhttps://github.com/user-attachments/assets/0b539d11-bed2-4e4b-9399-ea95f7f5baa4\n\n</details>\n\nAlso removed\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/threatmatch_input/index.tsx`\nbecause it was not used anywhere.","sha":"f0829b7c1179ef998380153ad7dd5b6a3bee6ea2"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222963","number":222963,"mergeCommit":{"message":"[Security Solution] Fix rule filters display issues (#222963)\n\n**Resolves: https://github.com/elastic/kibana/issues/203615**\n**Resolves: https://github.com/elastic/kibana/issues/203600**\n\n## Summary\nThis PR resolves a few bugs related to how query filters are displayed:\n- fixes display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout (bug introduced in PR #210191)\n - fixes warnings shown in edit mode of rule upgrade flyout\n- fixes warning flashes on rule edit page when updating the index\npattern\n\n## Changes\n\n### Display of filters with \"AND\"/\"OR\" logic in view mode of rule\nupgrade flyout\nCaused by change in recent [PR](#210191) where we stopped responding\nwith a full filter object.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"951\" alt=\"broken_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/3b06feb6-595f-4140-a795-3ac7a3d81fed\"\n/>\n\n **After**\n<img width=\"948\" alt=\"fixed_filters_flyout_view\"\nsrc=\"https://github.com/user-attachments/assets/6a59c2a5-7165-4e4e-9a2f-8cb4250125a0\"\n/>\n</details>\n\n### Warnings shown in edit mode of rule upgrade flyout\nCaused by a mismatch between index patterns in filters and data view\nobjects. We path both filters and a data view into a unified search\ncomponent. If it detects a mismatch, it shows a confusing warning.\n\n<details>\n <summary>Click to see screenshots</summary>\n **Before**\n<img width=\"1265\" alt=\"broken_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/947be729-a247-4eee-8046-155c2599e0bd\"\n/>\n\n **After**\n<img width=\"1265\" alt=\"fixed_filters_flyout_edit\"\nsrc=\"https://github.com/user-attachments/assets/7bec19bc-5180-47f1-876e-850677d1503d\"\n/>\n</details>\n\n### Warning flashes on rule edit page when updating the index pattern\nCaused by a re-render with an incomplete DataView object.\n\n<details>\n <summary>Click to see screen recordings</summary>\n **Before**\n\n\nhttps://github.com/user-attachments/assets/0140cfa5-4a87-4ed2-8c81-80e3b94e1166\n\n **After**\n\n\nhttps://github.com/user-attachments/assets/0b539d11-bed2-4e4b-9399-ea95f7f5baa4\n\n</details>\n\nAlso removed\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/threatmatch_input/index.tsx`\nbecause it was not used anywhere.","sha":"f0829b7c1179ef998380153ad7dd5b6a3bee6ea2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
Konrad Szwarc
|
58e519350f
|
[9.0] [EDR Workflows]Automatic troubleshooting usage callout (#224030) (#224267)
# Backport This will backport the following commits from `main` to `9.0`: - [[EDR Workflows]Automatic troubleshooting usage callout (#224030)](https://github.com/elastic/kibana/pull/224030) <!--- Backport version: 10.0.1 --> ### 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-06-17T08:48:15Z","message":"[EDR Workflows]Automatic troubleshooting usage callout (#224030)\n\nTracks https://github.com/elastic/kibana/pull/221566\nCloses https://github.com/elastic/security-team/issues/12824\n\nWith this change, whenever a user selects the Elastic LLM connector\nwithin the Automatic Troubleshooting feature, they'll see a callout\ninforming them about the potential costs of using it. Once the callout\nis acknowledged, it will be dismissed and the closed state will be\nstored in local storage, so it won’t appear again on future visits.\n\nTo enable EIS locally:\n```\nexport VAULT_ADDR=https://secrets.elastic.co:8200/\nvault login --method=oidc\nnode scripts/eis.js\n```\nand run ES server with provided env + start kibana with .dev.yaml entry\nfrom the output of the command above.\n\n\nhttps://github.com/user-attachments/assets/51a2ce77-ed25-4611-9d62-72e9d09bb789\n\n---------\n\nCo-authored-by: Angela Chuang <yi-chun.chuang@elastic.co>\nCo-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"dfe6f541c163235677a6a27498c3cd85594c174f","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v9.1.0"],"title":"[EDR Workflows]Automatic troubleshooting usage callout","number":224030,"url":"https://github.com/elastic/kibana/pull/224030","mergeCommit":{"message":"[EDR Workflows]Automatic troubleshooting usage callout (#224030)\n\nTracks https://github.com/elastic/kibana/pull/221566\nCloses https://github.com/elastic/security-team/issues/12824\n\nWith this change, whenever a user selects the Elastic LLM connector\nwithin the Automatic Troubleshooting feature, they'll see a callout\ninforming them about the potential costs of using it. Once the callout\nis acknowledged, it will be dismissed and the closed state will be\nstored in local storage, so it won’t appear again on future visits.\n\nTo enable EIS locally:\n```\nexport VAULT_ADDR=https://secrets.elastic.co:8200/\nvault login --method=oidc\nnode scripts/eis.js\n```\nand run ES server with provided env + start kibana with .dev.yaml entry\nfrom the output of the command above.\n\n\nhttps://github.com/user-attachments/assets/51a2ce77-ed25-4611-9d62-72e9d09bb789\n\n---------\n\nCo-authored-by: Angela Chuang <yi-chun.chuang@elastic.co>\nCo-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"dfe6f541c163235677a6a27498c3cd85594c174f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224030","number":224030,"mergeCommit":{"message":"[EDR Workflows]Automatic troubleshooting usage callout (#224030)\n\nTracks https://github.com/elastic/kibana/pull/221566\nCloses https://github.com/elastic/security-team/issues/12824\n\nWith this change, whenever a user selects the Elastic LLM connector\nwithin the Automatic Troubleshooting feature, they'll see a callout\ninforming them about the potential costs of using it. Once the callout\nis acknowledged, it will be dismissed and the closed state will be\nstored in local storage, so it won’t appear again on future visits.\n\nTo enable EIS locally:\n```\nexport VAULT_ADDR=https://secrets.elastic.co:8200/\nvault login --method=oidc\nnode scripts/eis.js\n```\nand run ES server with provided env + start kibana with .dev.yaml entry\nfrom the output of the command above.\n\n\nhttps://github.com/user-attachments/assets/51a2ce77-ed25-4611-9d62-72e9d09bb789\n\n---------\n\nCo-authored-by: Angela Chuang <yi-chun.chuang@elastic.co>\nCo-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"dfe6f541c163235677a6a27498c3cd85594c174f"}}]}] BACKPORT--> Co-authored-by: Angela Chuang <yi-chun.chuang@elastic.co> Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> Co-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com> |
||
|
Kibana Machine
|
bac57fa68f
|
[9.0] [Synthetics] Last Successful screenshots match the step (#224220) (#224252)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Last Successful screenshots match the step (#224220)](https://github.com/elastic/kibana/pull/224220) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-06-17T12:57:44Z","message":"[Synthetics] Last Successful screenshots match the step (#224220)\n\nThis PR closes #209844 . It also fixes a bug introduces in [this\nPR](https://github.com/elastic/kibana/pull/208776) that was preventing\nthe Error details page from loading.\n\n**Before**\n\n\n**After**\n","sha":"a584b044cf9c76c847897eb03b4de7d3426ca0eb","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","author:obs-ux-management","v9.0.3","v8.18.3","v8.17.8"],"title":"[Synthetics] Last Successful screenshots match the step","number":224220,"url":"https://github.com/elastic/kibana/pull/224220","mergeCommit":{"message":"[Synthetics] Last Successful screenshots match the step (#224220)\n\nThis PR closes #209844 . It also fixes a bug introduces in [this\nPR](https://github.com/elastic/kibana/pull/208776) that was preventing\nthe Error details page from loading.\n\n**Before**\n\n\n**After**\n","sha":"a584b044cf9c76c847897eb03b4de7d3426ca0eb"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224220","number":224220,"mergeCommit":{"message":"[Synthetics] Last Successful screenshots match the step (#224220)\n\nThis PR closes #209844 . It also fixes a bug introduces in [this\nPR](https://github.com/elastic/kibana/pull/208776) that was preventing\nthe Error details page from loading.\n\n**Before**\n\n\n**After**\n","sha":"a584b044cf9c76c847897eb03b4de7d3426ca0eb"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com> |
||
|
Kibana Machine
|
46d738849c
|
[9.0] [a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047) (#224240)
# Backport This will backport the following commits from `main` to `9.0`: - [[a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047)](https://github.com/elastic/kibana/pull/224047) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paulina Shakirova","email":"paulina.shakirova@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T11:52:24Z","message":"[a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047)\n\nThis PR resolves [[ML] ES|QL Data Visualizer: The button to access es|ql\nquick reference is missing discernible\ntext](https://github.com/elastic/kibana/issues/217094) issue.\n\n\nhttps://github.com/user-attachments/assets/09e18f9f-eb06-4468-bc72-c0c4e46a642e","sha":"f03c565daf7796fc79b70fc9f540f86d44d224f2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","a11y","v9.1.0"],"title":"[a11y][ml] Add visually hidden label for screenreader for open documentation button","number":224047,"url":"https://github.com/elastic/kibana/pull/224047","mergeCommit":{"message":"[a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047)\n\nThis PR resolves [[ML] ES|QL Data Visualizer: The button to access es|ql\nquick reference is missing discernible\ntext](https://github.com/elastic/kibana/issues/217094) issue.\n\n\nhttps://github.com/user-attachments/assets/09e18f9f-eb06-4468-bc72-c0c4e46a642e","sha":"f03c565daf7796fc79b70fc9f540f86d44d224f2"}},"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/224047","number":224047,"mergeCommit":{"message":"[a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047)\n\nThis PR resolves [[ML] ES|QL Data Visualizer: The button to access es|ql\nquick reference is missing discernible\ntext](https://github.com/elastic/kibana/issues/217094) issue.\n\n\nhttps://github.com/user-attachments/assets/09e18f9f-eb06-4468-bc72-c0c4e46a642e","sha":"f03c565daf7796fc79b70fc9f540f86d44d224f2"}}]}] BACKPORT--> Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co> |
||
Angela Chuang
|
0a64122d36
|
[9.0][Security Assistant] EIS usage callout (#221566) (#224127)
# Backport This will backport the following commits from `main` to `8.18`: - [Security Assistant] EIS usage callout #221566(https://github.com/elastic/kibana/pull/221566) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> Co-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com> |
||
|
Kibana Machine
|
9c13b60e1f
|
[9.0] Fix that gap can be stuck "in-progress" (#221473) (#224178)
# Backport
This will backport the following commits from `main` to `9.0`:
- Fix that gap can be stuck "in-progress" (#221473) (
|
||
|
Kibana Machine
|
defcb9e596
|
[9.0] [Inspector]: fix pagination not working (#223537) (#224217)
# Backport This will backport the following commits from `main` to `9.0`: - [[Inspector]: fix pagination not working (#223537)](https://github.com/elastic/kibana/pull/223537) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T10:33:38Z","message":"[Inspector]: fix pagination not working (#223537)\n\n## Summary\n\nfix https://github.com/elastic/kibana/issues/223536\n\nIt wasn't possible to change the page index in the Inspector Data View.\nThe table was using the `onTableChange` callback, coming from the\n`useEuiTablePersist` hook in the wrapping function, in the `onChange`\nprop of the `EuiTable` instead of being attached to the `onTableChange`\nprop.\n\nWhen using the `onChange` the EuiTable leave all the pagination/size etc\nhandling to the consumer, where the `onTableChange` is just a callback\nrelated to the changes, used within the `useEuiTablePersist` to store\nsome configuration across tabels.\n\nThe PR fixes the `onTableChange` callback to the correct prop.\n\nA functional test was also added to check the pagination works within\nLens. I haven't used the existing `inspector.ts` functional tests\nbecause they where within the Legacy Visualize.\n\nI've checked the usage of `useEuiTablePersist` and the returned\n`onTableChange` and is correctly used everywhere except for ESQL query\nhistory that doesn't seems to have enabled pagination cc @stratoula\n\n |
||
Georgiana-Andreea Onoleață
|
5b3d9e718d
|
[9.0] [ResponseOps][Cases]Allow dashes in host names in Observables (#219038) (#224203)
# Backport This will backport the following commits from `main` to `9.0`: - [[ResponseOps][Cases]Allow dashes in host names in Observables (#219038)](https://github.com/elastic/kibana/pull/219038) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-04-29T07:27:18Z","message":"[ResponseOps][Cases]Allow dashes in host names in Observables (#219038)\n\nCloses https://github.com/elastic/kibana/issues/218946\n\n## Summary\n\n- changed the GENERIC_REGEX to allow `-` \n\n<img width=\"488\" alt=\"Screenshot 2025-04-24 at 10 31 00\"\nsrc=\"https://github.com/user-attachments/assets/57841c74-9e6c-4600-81f4-8b454d1ddec1\"\n/>","sha":"d0d08b0bdb8f178e88063e0a05467f78d4d8b99f","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[ResponseOps][Cases]Allow dashes in host names in Observables","number":219038,"url":"https://github.com/elastic/kibana/pull/219038","mergeCommit":{"message":"[ResponseOps][Cases]Allow dashes in host names in Observables (#219038)\n\nCloses https://github.com/elastic/kibana/issues/218946\n\n## Summary\n\n- changed the GENERIC_REGEX to allow `-` \n\n<img width=\"488\" alt=\"Screenshot 2025-04-24 at 10 31 00\"\nsrc=\"https://github.com/user-attachments/assets/57841c74-9e6c-4600-81f4-8b454d1ddec1\"\n/>","sha":"d0d08b0bdb8f178e88063e0a05467f78d4d8b99f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219038","number":219038,"mergeCommit":{"message":"[ResponseOps][Cases]Allow dashes in host names in Observables (#219038)\n\nCloses https://github.com/elastic/kibana/issues/218946\n\n## Summary\n\n- changed the GENERIC_REGEX to allow `-` \n\n<img width=\"488\" alt=\"Screenshot 2025-04-24 at 10 31 00\"\nsrc=\"https://github.com/user-attachments/assets/57841c74-9e6c-4600-81f4-8b454d1ddec1\"\n/>","sha":"d0d08b0bdb8f178e88063e0a05467f78d4d8b99f"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/219489","number":219489,"state":"MERGED","mergeCommit":{"sha":"078e45f32cc56d76fbeb5ecffbf46d8262cc23bb","message":"[8.19] [ResponseOps][Cases]Allow dashes in host names in Observables (#219038) (#219489)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[ResponseOps][Cases]Allow dashes in host names in Observables\n(#219038)](https://github.com/elastic/kibana/pull/219038)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
elastic-vault-github-plugin-prod[bot]
|
13767197c2
|
[9.0] Sync bundled packages with Package Storage (#224018)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2927 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
ff543226e8
|
[9.0] [UI Counters] fix flaky test retry logic (#224151) (#224167)
# Backport This will backport the following commits from `main` to `9.0`: - [[UI Counters] fix flaky test retry logic (#224151)](https://github.com/elastic/kibana/pull/224151) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2025-06-17T01:37:37Z","message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0","v9.0.3"],"title":"[UI Counters] fix flaky test retry logic","number":224151,"url":"https://github.com/elastic/kibana/pull/224151","mergeCommit":{"message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224151","number":224151,"mergeCommit":{"message":"[UI Counters] fix flaky test retry logic (#224151)\n\nRevisit `waitForWithTimeout` to use 5 retries and an initial waiting\ntime\ncloses https://github.com/elastic/kibana/issues/98240\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"699212fa7eb7a5440759c8a01f095e0bf2ca9479"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co> |
||
Ievgen Sorokopud
|
4701947f91
|
[9.0] [Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129) (#224145)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129)](https://github.com/elastic/kibana/pull/224129) <!--- Backport version: 10.0.1 --> ### 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-06-16T20:50:27Z","message":"[Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129)\n\n## Summary\n\nMain ticket: https://github.com/elastic/security-team/issues/12827\n\nThese changes fix the issue with the locally running models over the\n`HTTP` server. We do always use `HTTPS` agent even when URL uses HTTP\nprotocol. This leads to an error:\n\n```\nTypeError: Protocol \"http:\" not supported. Expected \"https:\"\n at new ClientRequest (node:_http_client:187:11)\n at request (node:http:101:10)\n at AsyncLocalStorage.run (node:async_hooks:346:14)\n at AsyncLocalStorageRunContextManager.with (/kibana/node_modules/elastic-apm-node/lib/instrumentation/run-context/AsyncLocalStorageRunContextManager.js:57:36)\n at Instrumentation.withRunContext (/kibana/node_modules/elastic-apm-node/lib/instrumentation/index.js:1126:30)\n at wrappedHttpRequest (/kibana/node_modules/elastic-apm-node/lib/instrumentation/http-shared.js:292:21)\n at /kibana/node_modules/node-fetch/lib/index.js:1478:15\n at new Promise (<anonymous>)\n at fetch (/kibana/node_modules/node-fetch/lib/index.js:1447:9)\n at OpenAI.fetchWithTimeout (/kibana/node_modules/openai/src/core.ts:580:18)\n at OpenAI.makeRequest (/kibana/node_modules/openai/src/core.ts:476:33)\n at OpenAIConnector.invokeAsyncIterator (openai.ts:418:22)\n at Object.executor (executor.ts:99:18)\n at action_executor.ts:504:23\n at ActionExecutor.execute (action_executor.ts:153:12)\n at chat_openai.ts:162:28\n at RetryOperation._fn (/kibana/node_modules/p-retry/index.js:50:12)\n```\n\n### To test\n\nSteps to reproduce the behavior:\n\n1. Run locally hosted model and make sure that the chat completion url\nuses the HTTP protocol\n2. Add OSS model via Other (OpenAI Compatible Service) provider\n3. Turn streaming ON\n4. Try to chat via AI Assistant\n\nThanks @stephmilovic helping to solve the issue!","sha":"4c62313e1bb5a02beeb33e24ef6d5d9f758ab082","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Security GenAI][Bug] OSS models do not work when streaming is ON (#12827)","number":224129,"url":"https://github.com/elastic/kibana/pull/224129","mergeCommit":{"message":"[Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129)\n\n## Summary\n\nMain ticket: https://github.com/elastic/security-team/issues/12827\n\nThese changes fix the issue with the locally running models over the\n`HTTP` server. We do always use `HTTPS` agent even when URL uses HTTP\nprotocol. This leads to an error:\n\n```\nTypeError: Protocol \"http:\" not supported. Expected \"https:\"\n at new ClientRequest (node:_http_client:187:11)\n at request (node:http:101:10)\n at AsyncLocalStorage.run (node:async_hooks:346:14)\n at AsyncLocalStorageRunContextManager.with (/kibana/node_modules/elastic-apm-node/lib/instrumentation/run-context/AsyncLocalStorageRunContextManager.js:57:36)\n at Instrumentation.withRunContext (/kibana/node_modules/elastic-apm-node/lib/instrumentation/index.js:1126:30)\n at wrappedHttpRequest (/kibana/node_modules/elastic-apm-node/lib/instrumentation/http-shared.js:292:21)\n at /kibana/node_modules/node-fetch/lib/index.js:1478:15\n at new Promise (<anonymous>)\n at fetch (/kibana/node_modules/node-fetch/lib/index.js:1447:9)\n at OpenAI.fetchWithTimeout (/kibana/node_modules/openai/src/core.ts:580:18)\n at OpenAI.makeRequest (/kibana/node_modules/openai/src/core.ts:476:33)\n at OpenAIConnector.invokeAsyncIterator (openai.ts:418:22)\n at Object.executor (executor.ts:99:18)\n at action_executor.ts:504:23\n at ActionExecutor.execute (action_executor.ts:153:12)\n at chat_openai.ts:162:28\n at RetryOperation._fn (/kibana/node_modules/p-retry/index.js:50:12)\n```\n\n### To test\n\nSteps to reproduce the behavior:\n\n1. Run locally hosted model and make sure that the chat completion url\nuses the HTTP protocol\n2. Add OSS model via Other (OpenAI Compatible Service) provider\n3. Turn streaming ON\n4. Try to chat via AI Assistant\n\nThanks @stephmilovic helping to solve the issue!","sha":"4c62313e1bb5a02beeb33e24ef6d5d9f758ab082"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224129","number":224129,"mergeCommit":{"message":"[Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129)\n\n## Summary\n\nMain ticket: https://github.com/elastic/security-team/issues/12827\n\nThese changes fix the issue with the locally running models over the\n`HTTP` server. We do always use `HTTPS` agent even when URL uses HTTP\nprotocol. This leads to an error:\n\n```\nTypeError: Protocol \"http:\" not supported. Expected \"https:\"\n at new ClientRequest (node:_http_client:187:11)\n at request (node:http:101:10)\n at AsyncLocalStorage.run (node:async_hooks:346:14)\n at AsyncLocalStorageRunContextManager.with (/kibana/node_modules/elastic-apm-node/lib/instrumentation/run-context/AsyncLocalStorageRunContextManager.js:57:36)\n at Instrumentation.withRunContext (/kibana/node_modules/elastic-apm-node/lib/instrumentation/index.js:1126:30)\n at wrappedHttpRequest (/kibana/node_modules/elastic-apm-node/lib/instrumentation/http-shared.js:292:21)\n at /kibana/node_modules/node-fetch/lib/index.js:1478:15\n at new Promise (<anonymous>)\n at fetch (/kibana/node_modules/node-fetch/lib/index.js:1447:9)\n at OpenAI.fetchWithTimeout (/kibana/node_modules/openai/src/core.ts:580:18)\n at OpenAI.makeRequest (/kibana/node_modules/openai/src/core.ts:476:33)\n at OpenAIConnector.invokeAsyncIterator (openai.ts:418:22)\n at Object.executor (executor.ts:99:18)\n at action_executor.ts:504:23\n at ActionExecutor.execute (action_executor.ts:153:12)\n at chat_openai.ts:162:28\n at RetryOperation._fn (/kibana/node_modules/p-retry/index.js:50:12)\n```\n\n### To test\n\nSteps to reproduce the behavior:\n\n1. Run locally hosted model and make sure that the chat completion url\nuses the HTTP protocol\n2. Add OSS model via Other (OpenAI Compatible Service) provider\n3. Turn streaming ON\n4. Try to chat via AI Assistant\n\nThanks @stephmilovic helping to solve the issue!","sha":"4c62313e1bb5a02beeb33e24ef6d5d9f758ab082"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Quynh Nguyen (Quinn)
|
db0497a12c
|
[9.0] [ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617) (#224124)
# Backport This will backport the following commits from `main` to `9.0`: - [[ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617)](https://github.com/elastic/kibana/pull/219617) <!--- Backport version: 10.0.0 --> ### 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-06-05T17:34:27Z","message":"[ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617)\n\n## Summary\n\nThis PR fixes https://github.com/elastic/kibana/issues/214057 by adding\nthe httpsAgent/httpAgent to the OpenAI client.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2564d6de38855a32be94ececd062cf1820dc52bb","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","backport:version","Team:AI Infra","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[ML] Fix OpenAI connector does not use the action proxy configuration for all subactions","number":219617,"url":"https://github.com/elastic/kibana/pull/219617","mergeCommit":{"message":"[ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617)\n\n## Summary\n\nThis PR fixes https://github.com/elastic/kibana/issues/214057 by adding\nthe httpsAgent/httpAgent to the OpenAI client.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2564d6de38855a32be94ececd062cf1820dc52bb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219617","number":219617,"mergeCommit":{"message":"[ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617)\n\n## Summary\n\nThis PR fixes https://github.com/elastic/kibana/issues/214057 by adding\nthe httpsAgent/httpAgent to the OpenAI client.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2564d6de38855a32be94ececd062cf1820dc52bb"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/222869","number":222869,"state":"MERGED","mergeCommit":{"sha":"b48ff971cada9153ab220a78d012204a53681efe","message":"[8.19] [ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617) (#222869)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [[ML] Fix OpenAI connector does not use the action proxy configuration\nfor all subactions\n(#219617)](https://github.com/elastic/kibana/pull/219617)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d322792ae5
|
[9.0] Upgrade Puppeteer to v24.10.1 (#223985) (#224116)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade Puppeteer to v24.10.1 (#223985)](https://github.com/elastic/kibana/pull/223985) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ersin Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T17:56:05Z","message":"Upgrade Puppeteer to v24.10.1 (#223985)\n\nThis PR upgrades Puppeteer version to v24.10.1.\n\nTested locally, works as expected:\n\n<img width=\"968\" alt=\"Screenshot 2025-06-14 at 02 28 49\"\nsrc=\"https://github.com/user-attachments/assets/52ede4a6-d342-45f6-9fdf-5a01ce77fb47\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>\nCo-authored-by: Alexandra Doak <alexandra.doak@elastic.co>","sha":"1a8b6694b28674a3826ee57c1cb7440a9a64601b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","ci:cloud-deploy","backport:version","v7.17.28","v9.1.0","v8.19.0","v7.17.29","v8.17.7","v8.18.2","v9.0.2","v9.0.3","v8.18.3","v8.17.8"],"title":"Upgrade Puppeteer to v24.10.1","number":223985,"url":"https://github.com/elastic/kibana/pull/223985","mergeCommit":{"message":"Upgrade Puppeteer to v24.10.1 (#223985)\n\nThis PR upgrades Puppeteer version to v24.10.1.\n\nTested locally, works as expected:\n\n<img width=\"968\" alt=\"Screenshot 2025-06-14 at 02 28 49\"\nsrc=\"https://github.com/user-attachments/assets/52ede4a6-d342-45f6-9fdf-5a01ce77fb47\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>\nCo-authored-by: Alexandra Doak <alexandra.doak@elastic.co>","sha":"1a8b6694b28674a3826ee57c1cb7440a9a64601b"}},"sourceBranch":"main","suggestedTargetBranches":["7.17","8.19","8.17","8.18","9.0"],"targetPullRequestStates":[{"branch":"7.17","label":"v7.17.28","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/223985","number":223985,"mergeCommit":{"message":"Upgrade Puppeteer to v24.10.1 (#223985)\n\nThis PR upgrades Puppeteer version to v24.10.1.\n\nTested locally, works as expected:\n\n<img width=\"968\" alt=\"Screenshot 2025-06-14 at 02 28 49\"\nsrc=\"https://github.com/user-attachments/assets/52ede4a6-d342-45f6-9fdf-5a01ce77fb47\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>\nCo-authored-by: Alexandra Doak <alexandra.doak@elastic.co>","sha":"1a8b6694b28674a3826ee57c1cb7440a9a64601b"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com> Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com> Co-authored-by: Alexandra Doak <alexandra.doak@elastic.co> |
||
|
Kibana Machine
|
bc6d2258f2
|
[9.0] [a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025) (#224123)
# Backport This will backport the following commits from `main` to `9.0`: - [[a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025)](https://github.com/elastic/kibana/pull/224025) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paulina Shakirova","email":"paulina.shakirova@elastic.co"},"sourceCommit":{"committedDate":"2025-06-16T18:05:18Z","message":"[a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025)\n\n## Summary\n\nThis PR resolves [[ML] Anomaly Detection: Job selector flyout checkboxes\nin the first column missing title from\nannouncement](https://github.com/elastic/kibana/issues/216802).\n\n#### This is a follow up from\nhttps://github.com/elastic/kibana/pull/221865 pr. (Closed because of\nmerge issues.)\n\n\nhttps://github.com/user-attachments/assets/a6796576-cc46-4769-ab3d-c8f5dc37409e\n\nFixes https://github.com/elastic/kibana/issues/216802","sha":"3f5e970d3bbaa9d73412b67937a5e1c82f94de06","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","backport:all-open","a11y","v9.1.0"],"title":"[a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout","number":224025,"url":"https://github.com/elastic/kibana/pull/224025","mergeCommit":{"message":"[a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025)\n\n## Summary\n\nThis PR resolves [[ML] Anomaly Detection: Job selector flyout checkboxes\nin the first column missing title from\nannouncement](https://github.com/elastic/kibana/issues/216802).\n\n#### This is a follow up from\nhttps://github.com/elastic/kibana/pull/221865 pr. (Closed because of\nmerge issues.)\n\n\nhttps://github.com/user-attachments/assets/a6796576-cc46-4769-ab3d-c8f5dc37409e\n\nFixes https://github.com/elastic/kibana/issues/216802","sha":"3f5e970d3bbaa9d73412b67937a5e1c82f94de06"}},"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/224025","number":224025,"mergeCommit":{"message":"[a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025)\n\n## Summary\n\nThis PR resolves [[ML] Anomaly Detection: Job selector flyout checkboxes\nin the first column missing title from\nannouncement](https://github.com/elastic/kibana/issues/216802).\n\n#### This is a follow up from\nhttps://github.com/elastic/kibana/pull/221865 pr. (Closed because of\nmerge issues.)\n\n\nhttps://github.com/user-attachments/assets/a6796576-cc46-4769-ab3d-c8f5dc37409e\n\nFixes https://github.com/elastic/kibana/issues/216802","sha":"3f5e970d3bbaa9d73412b67937a5e1c82f94de06"}}]}] BACKPORT--> Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co> |
||
|
Kibana Machine
|
082ddab160
|
[9.0] add es-cache to cleaned folders (#223373) (#223511)
# Backport This will backport the following commits from `main` to `9.0`: - [add es-cache to cleaned folders (#223373)](https://github.com/elastic/kibana/pull/223373) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-06-12T08:58:05Z","message":"add es-cache to cleaned folders (#223373)\n\n## Summary\nCurrently, `yarn kbn clean` nor `yarn kbn reset` won't remove cached ES\nsnapshot builds. This might cause issues for developers when switching\nbetween branches with major changes. (see:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1749628993034289)\n\nThis PR adds a softer and a harder clean to `clean` and `reset`\nrespectively.","sha":"20764b6914e6775c4b6fb0db75361841eb9f41f4","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","skip-ci","backport:all-open","v9.1.0"],"title":"add es-cache to cleaned folders","number":223373,"url":"https://github.com/elastic/kibana/pull/223373","mergeCommit":{"message":"add es-cache to cleaned folders (#223373)\n\n## Summary\nCurrently, `yarn kbn clean` nor `yarn kbn reset` won't remove cached ES\nsnapshot builds. This might cause issues for developers when switching\nbetween branches with major changes. (see:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1749628993034289)\n\nThis PR adds a softer and a harder clean to `clean` and `reset`\nrespectively.","sha":"20764b6914e6775c4b6fb0db75361841eb9f41f4"}},"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/223373","number":223373,"mergeCommit":{"message":"add es-cache to cleaned folders (#223373)\n\n## Summary\nCurrently, `yarn kbn clean` nor `yarn kbn reset` won't remove cached ES\nsnapshot builds. This might cause issues for developers when switching\nbetween branches with major changes. (see:\nhttps://elastic.slack.com/archives/C5UDAFZQU/p1749628993034289)\n\nThis PR adds a softer and a harder clean to `clean` and `reset`\nrespectively.","sha":"20764b6914e6775c4b6fb0db75361841eb9f41f4"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
5277622918
|
[9.0] [EDR Workflows] Add dns event collection for macOS for Elastic Defend (#223566) (#224067)
# Backport This will backport the following commits from `main` to `9.0`: - [[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend (#223566)](https://github.com/elastic/kibana/pull/223566) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-06-16T13:25:47Z","message":"[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend (#223566)\n\n## Summary\n\nAdds `DNS` to Defend policy config:\n<img width=\"952\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/de5aabe2-544a-49ae-82c2-59f9ffbca8c4\"\n/>\n\nThere is no migration for existing policies.\n\nFor new policies, it is enabled by default for\n- Complete EDR\n- Data Collection\n\nand disabled for other configs.\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"28c230d587cb4a418d8fa16f67abb9295d1f6590","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Defend Workflows","ci:cloud-deploy","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend","number":223566,"url":"https://github.com/elastic/kibana/pull/223566","mergeCommit":{"message":"[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend (#223566)\n\n## Summary\n\nAdds `DNS` to Defend policy config:\n<img width=\"952\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/de5aabe2-544a-49ae-82c2-59f9ffbca8c4\"\n/>\n\nThere is no migration for existing policies.\n\nFor new policies, it is enabled by default for\n- Complete EDR\n- Data Collection\n\nand disabled for other configs.\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"28c230d587cb4a418d8fa16f67abb9295d1f6590"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223566","number":223566,"mergeCommit":{"message":"[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend (#223566)\n\n## Summary\n\nAdds `DNS` to Defend policy config:\n<img width=\"952\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/de5aabe2-544a-49ae-82c2-59f9ffbca8c4\"\n/>\n\nThere is no migration for existing policies.\n\nFor new policies, it is enabled by default for\n- Complete EDR\n- Data Collection\n\nand disabled for other configs.\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[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"28c230d587cb4a418d8fa16f67abb9295d1f6590"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
257df7e551
|
[9.0] [Watcher] Revert back to using .watches system index (#223898) (#224080)
# Backport This will backport the following commits from `main` to `9.0`: - [[Watcher] Revert back to using .watches system index (#223898)](https://github.com/elastic/kibana/pull/223898) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T14:26:24Z","message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts https://github.com/elastic/kibana/pull/204296 and\nhttps://github.com/elastic/kibana/pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Watcher","Team:Kibana Management","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Watcher] Revert back to using .watches system index","number":223898,"url":"https://github.com/elastic/kibana/pull/223898","mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts https://github.com/elastic/kibana/pull/204296 and\nhttps://github.com/elastic/kibana/pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223898","number":223898,"mergeCommit":{"message":"[Watcher] Revert back to using .watches system index (#223898)\n\nFixes https://github.com/elastic/kibana/issues/221820\nFixes https://github.com/elastic/kibana/issues/220879\n\n## Summary\n\nThis PR reverts https://github.com/elastic/kibana/pull/204296 and\nhttps://github.com/elastic/kibana/pull/218853 as these PRs caused issues\nin the UI due to limitations in the Query Watches API. Therefore, we are\ntemporarily reverting back to fetching watches through the `.watches`\nsystem index until we have better support from the Query Watches API.\n\n**How to test:**\n1. Start Es with `yarn es snapshot --license=trial` and Kibana with\n`yarn start` (no need to test in serverless as Watcher is not available\nthere.\n2. Navigate to Stack Management -> Watcher and create multiple watches\n(the more, the better). Make sure you create watches of different types\n(advanced/json or threshold), watches with or without names, etc. There\nare different watches and use cases described in the\n[documentation](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher).\nAlso, adding sample data sets is helpful so that you can get watches to\nexecute and have values under the \"Condition last met\" and \"Last\nchecked\" columns.\n3. After creating various watches, open the table with watches and make\nsure that all functionalities work correctly. For example:\n- All watches are displayed, check with >10 watches and different page\nsizes.\n- Sorting works for all columns.\n- Search bar works as expected and searching by partial id is supported.\n- Deleting watches updates the table correctly.\n\n\nhttps://github.com/user-attachments/assets/d0da9c24-7389-481d-8a16-a0d01bda0e80\n\n## Release notes:\nThis update resolves multiple issues in Watcher UI that were introduced\nin 8.18.0, 8.18.1, 9.0.0, and 9.1.0, including the table not displaying\nmore than 10 watches, an error banner appearing unexpectedly in certain\nscenarios, and the search bar functionality not working as expected.","sha":"5c0b6b0fe7c08b20a6cc540b0e90b8106147b54a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
efb58162ef
|
[9.0] [ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page (#223563) (#224065)
# Backport This will backport the following commits from `main` to `9.0`: - [[ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page (#223563)](https://github.com/elastic/kibana/pull/223563) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Damian Polewski","email":"125268832+damian-polewski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-16T13:24:44Z","message":"[ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page (#223563)\n\nCloses #217963\n\nThis PR fixes an issue where API Request flyout in Ingest Pipelines >\nNew pipeline page is missing title.","sha":"77038d35c361031214eac5637ae5d391bf749c09","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","Feature:Ingest Node Pipelines","backport:version","v9.1.0","v8.19.0","v9.0.3"],"title":"[ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page","number":223563,"url":"https://github.com/elastic/kibana/pull/223563","mergeCommit":{"message":"[ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page (#223563)\n\nCloses #217963\n\nThis PR fixes an issue where API Request flyout in Ingest Pipelines >\nNew pipeline page is missing title.","sha":"77038d35c361031214eac5637ae5d391bf749c09"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223563","number":223563,"mergeCommit":{"message":"[ES UI Shared][Ingest Pipelines] Fix missing title for API Request flyout in Ingest Pipelines > Edit pipeline page (#223563)\n\nCloses #217963\n\nThis PR fixes an issue where API Request flyout in Ingest Pipelines >\nNew pipeline page is missing title.","sha":"77038d35c361031214eac5637ae5d391bf749c09"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Damian Polewski <125268832+damian-polewski@users.noreply.github.com> |
||
Ahmad Bamieh
|
26c35c6da1
|
[9.0] Remove unnecessary try catch in the APM user filters (#224014) (#224056)
# Backport This will backport the following commits from `main` to `9.0`: - [Remove unnecessary try catch in the APM user filters (#224014)](https://github.com/elastic/kibana/pull/224014) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2025-06-16T10:28:40Z","message":"Remove unnecessary try catch in the APM user filters (#224014)\n\n## Summary\n\nImproves the IF statement to ensure that we are dealing with an object\nwith loopable keys and remove the try-catch. If not loopable, we might\nwant to remove the user context entirely (or replace it with a known\nobject { id: '[INVALID]' }) since it might lead to APM traces being\ndiscarded due to invalid user context.\n\ncloses https://github.com/elastic/kibana/issues/219095","sha":"a77f6f0cc93d147675113261354d445c7f85860e","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v9.1.0","v9.0.3"],"title":"Remove unnecessary try catch in the APM user filters","number":224014,"url":"https://github.com/elastic/kibana/pull/224014","mergeCommit":{"message":"Remove unnecessary try catch in the APM user filters (#224014)\n\n## Summary\n\nImproves the IF statement to ensure that we are dealing with an object\nwith loopable keys and remove the try-catch. If not loopable, we might\nwant to remove the user context entirely (or replace it with a known\nobject { id: '[INVALID]' }) since it might lead to APM traces being\ndiscarded due to invalid user context.\n\ncloses https://github.com/elastic/kibana/issues/219095","sha":"a77f6f0cc93d147675113261354d445c7f85860e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224014","number":224014,"mergeCommit":{"message":"Remove unnecessary try catch in the APM user filters (#224014)\n\n## Summary\n\nImproves the IF statement to ensure that we are dealing with an object\nwith loopable keys and remove the try-catch. If not loopable, we might\nwant to remove the user context entirely (or replace it with a known\nobject { id: '[INVALID]' }) since it might lead to APM traces being\ndiscarded due to invalid user context.\n\ncloses https://github.com/elastic/kibana/issues/219095","sha":"a77f6f0cc93d147675113261354d445c7f85860e"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Mark Hopkin
|
3194a1b1db
|
[9.0] Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices (#221937) (#223905)
# Backport This will backport the following commits from `main` to `9.0`: - [Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices (#221937)](https://github.com/elastic/kibana/pull/221937) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"mark.hopkin@elastic.co"},"sourceCommit":{"committedDate":"2025-06-13T09:41:40Z","message":"Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices (#221937)\n\nCustomers who enabled risk scoring in a version below 8.18 and then\nupgraded to 8.18 or 9.0, will find risk scoring stops working in 0-30\ndays, this is because the ingest pipeline to set event ingested is not\ninstalled, but is specified on the risk scoring index, causing all\nwrites to fail.\n\nThis PR fixes this by installing the ingest pipeline in all spaces where\neither:\n- risk scoring is set up (the risk-engine-configuration saved object is\npresent)\n- the asset criticality index exists\n\nThis PR also increases the internal versioning of the asset criticality\nand risk scoring indices, to trigger the migration which will:\n- add the pipeline to the asset criticality index\n- add the pipeline to a risk scoring index which hasnt been rolled over\n- remove the pipeline from the risk scoring latest index if it is set\n(if risk scoring was set up in 9.0 or 8.18 for the first time) we remove\nthis because the latest index should not modify the risk scoring\ndocuments.\n\nThe result is that asset criticality and risk scoring should work and\nevent.ingested should correctly be set.\n\n## Other important technical changes\n\n- whenevr we increase the risk scoring internal index version, this will\nnow trigger a rollover on the data stream\n- asset criticality and risk scoring index migrations now support\nsettings changes\n\n## test steps\n\n- on 8.17 initialise risk engine and generate some risk scores\n- upgrade to 8.18.0 or 9.0.0\n- rollover the risk score latest datastream dev tool `POST\n/risk-score.risk-score-default/_rollover`\n- verify risk scoring has broken, easy way is by assigning asset\ncriticality in the entity flyout\n- upgrade to 9.0.3 or 8.18.3\n- verify risk scoring and asset criticality work\n\n## Test steps for local env:\n\n- start kibana\n- checkout SDG branch\nhttps://github.com/elastic/security-documents-generator/pull/153\n- run `yarn start risk-score-ingest-bug` AS SUPERUSER\n- observe asset criticality assignment results in an error / is not\nperformed\n- restart kibana\n- observe the ingest pipeline has been created and it works again\n\ndev tools verification:\n```\n# the pipeline should have been created\nGET /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipeline-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /.asset-criticality.asset-criticality-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /risk-score.risk-score-default\n\n# the default pipeline should be set\nGET /_index_template/.risk-score.risk-score-default-index-template\n\n# the default pipeline should NOT be set\nGET /risk-score.risk-score-latest-default\n```\n\nOther verifications:\n- risk scoring should work\n- asset criticality assignment should work\n- ???\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d5d37c7b2ab9b84d4aafe80b6fdc572b8f95035b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","Team:Entity Analytics","v9.1.0","backport:8.18","v9.0.3"],"title":"Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices","number":221937,"url":"https://github.com/elastic/kibana/pull/221937","mergeCommit":{"message":"Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices (#221937)\n\nCustomers who enabled risk scoring in a version below 8.18 and then\nupgraded to 8.18 or 9.0, will find risk scoring stops working in 0-30\ndays, this is because the ingest pipeline to set event ingested is not\ninstalled, but is specified on the risk scoring index, causing all\nwrites to fail.\n\nThis PR fixes this by installing the ingest pipeline in all spaces where\neither:\n- risk scoring is set up (the risk-engine-configuration saved object is\npresent)\n- the asset criticality index exists\n\nThis PR also increases the internal versioning of the asset criticality\nand risk scoring indices, to trigger the migration which will:\n- add the pipeline to the asset criticality index\n- add the pipeline to a risk scoring index which hasnt been rolled over\n- remove the pipeline from the risk scoring latest index if it is set\n(if risk scoring was set up in 9.0 or 8.18 for the first time) we remove\nthis because the latest index should not modify the risk scoring\ndocuments.\n\nThe result is that asset criticality and risk scoring should work and\nevent.ingested should correctly be set.\n\n## Other important technical changes\n\n- whenevr we increase the risk scoring internal index version, this will\nnow trigger a rollover on the data stream\n- asset criticality and risk scoring index migrations now support\nsettings changes\n\n## test steps\n\n- on 8.17 initialise risk engine and generate some risk scores\n- upgrade to 8.18.0 or 9.0.0\n- rollover the risk score latest datastream dev tool `POST\n/risk-score.risk-score-default/_rollover`\n- verify risk scoring has broken, easy way is by assigning asset\ncriticality in the entity flyout\n- upgrade to 9.0.3 or 8.18.3\n- verify risk scoring and asset criticality work\n\n## Test steps for local env:\n\n- start kibana\n- checkout SDG branch\nhttps://github.com/elastic/security-documents-generator/pull/153\n- run `yarn start risk-score-ingest-bug` AS SUPERUSER\n- observe asset criticality assignment results in an error / is not\nperformed\n- restart kibana\n- observe the ingest pipeline has been created and it works again\n\ndev tools verification:\n```\n# the pipeline should have been created\nGET /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipeline-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /.asset-criticality.asset-criticality-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /risk-score.risk-score-default\n\n# the default pipeline should be set\nGET /_index_template/.risk-score.risk-score-default-index-template\n\n# the default pipeline should NOT be set\nGET /risk-score.risk-score-latest-default\n```\n\nOther verifications:\n- risk scoring should work\n- asset criticality assignment should work\n- ???\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d5d37c7b2ab9b84d4aafe80b6fdc572b8f95035b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221937","number":221937,"mergeCommit":{"message":"Install event.ingested ingest pipeline in all spaces that the risk engine or asset criticality is installed, and add the pipeline to their indices (#221937)\n\nCustomers who enabled risk scoring in a version below 8.18 and then\nupgraded to 8.18 or 9.0, will find risk scoring stops working in 0-30\ndays, this is because the ingest pipeline to set event ingested is not\ninstalled, but is specified on the risk scoring index, causing all\nwrites to fail.\n\nThis PR fixes this by installing the ingest pipeline in all spaces where\neither:\n- risk scoring is set up (the risk-engine-configuration saved object is\npresent)\n- the asset criticality index exists\n\nThis PR also increases the internal versioning of the asset criticality\nand risk scoring indices, to trigger the migration which will:\n- add the pipeline to the asset criticality index\n- add the pipeline to a risk scoring index which hasnt been rolled over\n- remove the pipeline from the risk scoring latest index if it is set\n(if risk scoring was set up in 9.0 or 8.18 for the first time) we remove\nthis because the latest index should not modify the risk scoring\ndocuments.\n\nThe result is that asset criticality and risk scoring should work and\nevent.ingested should correctly be set.\n\n## Other important technical changes\n\n- whenevr we increase the risk scoring internal index version, this will\nnow trigger a rollover on the data stream\n- asset criticality and risk scoring index migrations now support\nsettings changes\n\n## test steps\n\n- on 8.17 initialise risk engine and generate some risk scores\n- upgrade to 8.18.0 or 9.0.0\n- rollover the risk score latest datastream dev tool `POST\n/risk-score.risk-score-default/_rollover`\n- verify risk scoring has broken, easy way is by assigning asset\ncriticality in the entity flyout\n- upgrade to 9.0.3 or 8.18.3\n- verify risk scoring and asset criticality work\n\n## Test steps for local env:\n\n- start kibana\n- checkout SDG branch\nhttps://github.com/elastic/security-documents-generator/pull/153\n- run `yarn start risk-score-ingest-bug` AS SUPERUSER\n- observe asset criticality assignment results in an error / is not\nperformed\n- restart kibana\n- observe the ingest pipeline has been created and it works again\n\ndev tools verification:\n```\n# the pipeline should have been created\nGET /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipeline-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /.asset-criticality.asset-criticality-default\n\n# the mapping version should be 4 and the default pipeline should be set\nGET /risk-score.risk-score-default\n\n# the default pipeline should be set\nGET /_index_template/.risk-score.risk-score-default-index-template\n\n# the default pipeline should NOT be set\nGET /risk-score.risk-score-latest-default\n```\n\nOther verifications:\n- risk scoring should work\n- asset criticality assignment should work\n- ???\n\n---------\n\nCo-authored-by: machadoum <pablo.nevesmachado@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d5d37c7b2ab9b84d4aafe80b6fdc572b8f95035b"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3ea294bbad
|
[9.0] fix(): inconsistent page_url between refresh and navigations (#224006) (#224042)
# Backport This will backport the following commits from `main` to `9.0`: - [fix(): inconsistent page_url between refresh and navigations (#224006)](https://github.com/elastic/kibana/pull/224006) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-06-16T09:43:10Z","message":"fix(): inconsistent page_url between refresh and navigations (#224006)","sha":"0f3726bc547b7d27aec1b7ce6f410f5ab151b9e3","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"fix(): inconsistent page_url between refresh and navigations","number":224006,"url":"https://github.com/elastic/kibana/pull/224006","mergeCommit":{"message":"fix(): inconsistent page_url between refresh and navigations (#224006)","sha":"0f3726bc547b7d27aec1b7ce6f410f5ab151b9e3"}},"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/224006","number":224006,"mergeCommit":{"message":"fix(): inconsistent page_url between refresh and navigations (#224006)","sha":"0f3726bc547b7d27aec1b7ce6f410f5ab151b9e3"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
501b8efc2c
|
[9.0] fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers (#223105) (#223941)
# Backport This will backport the following commits from `main` to `9.0`: - [fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers (#223105)](https://github.com/elastic/kibana/pull/223105) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-06-13T15:05:33Z","message":"fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers (#223105)\n\nCloses: #151493\n\n**Description**\nEnsure consistent screen reader announcements for errors when saving a\nDashboard with the \"Create Tag\" workflow.\n\n**Changes Made**\nAdded the required` aria-invalid` attribute at the appropriate location\nto support screen reader error announcements.\n\n**Notes**\nThe original issue suggested setting `aria-live=\"assertive\"`, but this\nmay not be necessary. Based on our current accessibility guidelines,\nusing `aria-invalid` is sufficient and aligns with best practices.\n\n**Screen**\n\n<img width=\"1434\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/afe1416b-34d2-46b5-88c4-fcac6a1f4c86\"\n/>","sha":"d44e332bce529e75236401bf21c39685c4dbae88","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","backport:prev-minor","v9.1.0"],"title":"fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers","number":223105,"url":"https://github.com/elastic/kibana/pull/223105","mergeCommit":{"message":"fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers (#223105)\n\nCloses: #151493\n\n**Description**\nEnsure consistent screen reader announcements for errors when saving a\nDashboard with the \"Create Tag\" workflow.\n\n**Changes Made**\nAdded the required` aria-invalid` attribute at the appropriate location\nto support screen reader error announcements.\n\n**Notes**\nThe original issue suggested setting `aria-live=\"assertive\"`, but this\nmay not be necessary. Based on our current accessibility guidelines,\nusing `aria-invalid` is sufficient and aligns with best practices.\n\n**Screen**\n\n<img width=\"1434\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/afe1416b-34d2-46b5-88c4-fcac6a1f4c86\"\n/>","sha":"d44e332bce529e75236401bf21c39685c4dbae88"}},"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/223105","number":223105,"mergeCommit":{"message":"fix: [Platform:Dashboards:DashboardEdit] Create tag workflow when saving Dashboard should announce error consistently to screen readers (#223105)\n\nCloses: #151493\n\n**Description**\nEnsure consistent screen reader announcements for errors when saving a\nDashboard with the \"Create Tag\" workflow.\n\n**Changes Made**\nAdded the required` aria-invalid` attribute at the appropriate location\nto support screen reader error announcements.\n\n**Notes**\nThe original issue suggested setting `aria-live=\"assertive\"`, but this\nmay not be necessary. Based on our current accessibility guidelines,\nusing `aria-invalid` is sufficient and aligns with best practices.\n\n**Screen**\n\n<img width=\"1434\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/afe1416b-34d2-46b5-88c4-fcac6a1f4c86\"\n/>","sha":"d44e332bce529e75236401bf21c39685c4dbae88"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
29270b170d
|
[9.0] [Connectors] Apply autoFocus prop to cc and bcc elements on email connector form (#223828) (#223940)
# Backport This will backport the following commits from `main` to `9.0`: - [[Connectors] Apply `autoFocus` prop to `cc` and `bcc` elements on email connector form (#223828)](https://github.com/elastic/kibana/pull/223828) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-06-13T15:00:59Z","message":"[Connectors] Apply `autoFocus` prop to `cc` and `bcc` elements on email connector form (#223828)\n\n## Summary\n\nResolves #212419.\n\nIn the Synthetics plugin, we are referencing the action connector form\nprovided for Email. The a11y audit noted that the `Cc` and `Bcc`\nfeatures on this form break the focus flow and make the page\ninaccessible. This patch will apply `autoFocus` to the combo box\nelements that get rendered when these buttons are clicked, thus allowing\nscreen reader and keyboard-only users to navigate the UI properly.\n\n**NOTE:** you may see an example of the failure on the linked issue. I\nhave re-created the flow using VoiceOver and keyboard navigation and\nincluded a GIF of it below.\n\n## Example\n\n\n","sha":"449c62f972b54f6659a0c1772ced5a5242d3d20c","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3","v8.17.8"],"title":"[Connectors] Apply `autoFocus` prop to `cc` and `bcc` elements on email connector form","number":223828,"url":"https://github.com/elastic/kibana/pull/223828","mergeCommit":{"message":"[Connectors] Apply `autoFocus` prop to `cc` and `bcc` elements on email connector form (#223828)\n\n## Summary\n\nResolves #212419.\n\nIn the Synthetics plugin, we are referencing the action connector form\nprovided for Email. The a11y audit noted that the `Cc` and `Bcc`\nfeatures on this form break the focus flow and make the page\ninaccessible. This patch will apply `autoFocus` to the combo box\nelements that get rendered when these buttons are clicked, thus allowing\nscreen reader and keyboard-only users to navigate the UI properly.\n\n**NOTE:** you may see an example of the failure on the linked issue. I\nhave re-created the flow using VoiceOver and keyboard navigation and\nincluded a GIF of it below.\n\n## Example\n\n\n","sha":"449c62f972b54f6659a0c1772ced5a5242d3d20c"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223828","number":223828,"mergeCommit":{"message":"[Connectors] Apply `autoFocus` prop to `cc` and `bcc` elements on email connector form (#223828)\n\n## Summary\n\nResolves #212419.\n\nIn the Synthetics plugin, we are referencing the action connector form\nprovided for Email. The a11y audit noted that the `Cc` and `Bcc`\nfeatures on this form break the focus flow and make the page\ninaccessible. This patch will apply `autoFocus` to the combo box\nelements that get rendered when these buttons are clicked, thus allowing\nscreen reader and keyboard-only users to navigate the UI properly.\n\n**NOTE:** you may see an example of the failure on the linked issue. I\nhave re-created the flow using VoiceOver and keyboard navigation and\nincluded a GIF of it below.\n\n## Example\n\n\n","sha":"449c62f972b54f6659a0c1772ced5a5242d3d20c"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.8","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
Marco Vettorello
|
699bc6b3da
|
[9.0] [Charts] Use chartTheme hook everywhere (#217370) (#223922)
# Backport This will backport the following commits from `main` to `9.0`: - [[Charts] Use chartTheme hook everywhere (#217370)](https://github.com/elastic/kibana/pull/217370) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Vettorello","email":"marco.vettorello@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T16:09:15Z","message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ElasticCharts","Team:Visualizations","release_note:skip","Team:obs-ux-infra_services","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[Charts] Use chartTheme hook everywhere","number":217370,"url":"https://github.com/elastic/kibana/pull/217370","mergeCommit":{"message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b"}},"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/217370","number":217370,"mergeCommit":{"message":"[Charts] Use chartTheme hook everywhere (#217370)\n\n## Summary\n\nThis PR fixes the existing usage of the chart themes by using the\nprovided `useElasticChartsTheme` hook that is color mode aware and theme\nadaptive (borealis/amsterdam)\n\nSome charts where using just the Light theme version or the legacy (aka\namsterdam theme), and I've applied the hook to pick up the correct\ntheme.\n\nTO REVIEWERS: Please pull down the PR and check if the actual changed\ncharts looks correct with the new theme configuration.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"a9c9354382d0e52d7790fecf653f4c7758e3703b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/218147","number":218147,"state":"MERGED","mergeCommit":{"sha":"13af80f2d4aaf30a0a1ffa76fbc24cf2d0d995a0","message":"[8.x] [Charts] Use chartTheme hook everywhere (#217370) (#218147)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Charts] Use chartTheme hook everywhere\n(#217370)](https://github.com/elastic/kibana/pull/217370)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
dcb6d636f9
|
[9.0] [DOCS] Adds Experience Docs to codeowners for setting docs (#223615) (#223842)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Adds Experience Docs to codeowners for setting docs (#223615)](https://github.com/elastic/kibana/pull/223615) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nastasha Solomon","email":"79124755+nastasha-solomon@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-12T22:14:45Z","message":"[DOCS] Adds Experience Docs to codeowners for setting docs (#223615)\n\nAdds the Experience Docs group as codeowners for the setting docs.","sha":"70449f78b56045130456c294e126d478197525c9","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:all-open","v9.1.0"],"title":"[DOCS] Adds Experience Docs to codeowners for setting docs","number":223615,"url":"https://github.com/elastic/kibana/pull/223615","mergeCommit":{"message":"[DOCS] Adds Experience Docs to codeowners for setting docs (#223615)\n\nAdds the Experience Docs group as codeowners for the setting docs.","sha":"70449f78b56045130456c294e126d478197525c9"}},"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/223615","number":223615,"mergeCommit":{"message":"[DOCS] Adds Experience Docs to codeowners for setting docs (#223615)\n\nAdds the Experience Docs group as codeowners for the setting docs.","sha":"70449f78b56045130456c294e126d478197525c9"}}]}] BACKPORT--> Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> |
||
Viduni Wickramarachchi
|
c453d5a03f
|
[9.0] [Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278) (#223581)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278)](https://github.com/elastic/kibana/pull/223278) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-12T14:56:43Z","message":"[Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278)\n\nCloses https://github.com/elastic/kibana/issues/223273\n\n## Summary\n\n### Problem\nTools are disabled for contextual insights by default. However, tools\nare not conditionally registered based on whether tools are disabled or\nnot. Therefore, the system message includes instructions for tools even\nthough tools are disabled for contextual insights. LLMs such as Claude,\ntries to call these tools and results in an error because we don't pass\nany tools to the LLM when `disableFunctions: true`\n\n\n\n\n### Solution\nAvoid passing tool instructions in the system message when tools are\ndisabled.\n\n\nhttps://github.com/user-attachments/assets/ba1a0016-4851-4ce7-9b40-efadbb96bd34\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\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":"2ae790506fcf21aff490d06ea56725d3ce76fbcb","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Obs AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled","number":223278,"url":"https://github.com/elastic/kibana/pull/223278","mergeCommit":{"message":"[Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278)\n\nCloses https://github.com/elastic/kibana/issues/223273\n\n## Summary\n\n### Problem\nTools are disabled for contextual insights by default. However, tools\nare not conditionally registered based on whether tools are disabled or\nnot. Therefore, the system message includes instructions for tools even\nthough tools are disabled for contextual insights. LLMs such as Claude,\ntries to call these tools and results in an error because we don't pass\nany tools to the LLM when `disableFunctions: true`\n\n\n\n\n### Solution\nAvoid passing tool instructions in the system message when tools are\ndisabled.\n\n\nhttps://github.com/user-attachments/assets/ba1a0016-4851-4ce7-9b40-efadbb96bd34\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\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":"2ae790506fcf21aff490d06ea56725d3ce76fbcb"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223278","number":223278,"mergeCommit":{"message":"[Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278)\n\nCloses https://github.com/elastic/kibana/issues/223273\n\n## Summary\n\n### Problem\nTools are disabled for contextual insights by default. However, tools\nare not conditionally registered based on whether tools are disabled or\nnot. Therefore, the system message includes instructions for tools even\nthough tools are disabled for contextual insights. LLMs such as Claude,\ntries to call these tools and results in an error because we don't pass\nany tools to the LLM when `disableFunctions: true`\n\n\n\n\n### Solution\nAvoid passing tool instructions in the system message when tools are\ndisabled.\n\n\nhttps://github.com/user-attachments/assets/ba1a0016-4851-4ce7-9b40-efadbb96bd34\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\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":"2ae790506fcf21aff490d06ea56725d3ce76fbcb"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
205638746b
|
[9.0] chore(dep): bump brace-expansion from 1.1.11 to 1.11.12 and 2.0.1 to 2.0.2 (#223589) (#223625)
# Backport This will backport the following commits from `main` to `9.0`: - [chore(dep): bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2` (#223589)](https://github.com/elastic/kibana/pull/223589) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-06-12T17:58:30Z","message":"chore(dep): bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2` (#223589)\n\n## Summary\n\nBump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2`.","sha":"ac9cec3d6134c8ded3adca4c79f76a9a590fa791","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","dependencies","backport:all-open","v9.1.0"],"title":"chore(dep): bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2`","number":223589,"url":"https://github.com/elastic/kibana/pull/223589","mergeCommit":{"message":"chore(dep): bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2` (#223589)\n\n## Summary\n\nBump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2`.","sha":"ac9cec3d6134c8ded3adca4c79f76a9a590fa791"}},"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/223589","number":223589,"mergeCommit":{"message":"chore(dep): bump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2` (#223589)\n\n## Summary\n\nBump `brace-expansion` from `1.1.11` to `1.11.12` and `2.0.1` to `2.0.2`.","sha":"ac9cec3d6134c8ded3adca4c79f76a9a590fa791"}}]}] BACKPORT--> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> |
||
|
Kibana Machine
|
744ba61a85
|
[9.0] [APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539) (#223608)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539)](https://github.com/elastic/kibana/pull/223539) <!--- 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-06-12T16:28:51Z","message":"[APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539)\n\nCloses #223533 \n\n## Summary\n\nTo fix the issue I replaced the `metrics-*` with `*:metrics-*,metrics-*`\nin the ES|QL queries\n\n## Testing\n- With local connection to a new edge edot cluster (created with the\noblt-cli tool)\n- Go to APM > Services and click on the `ad` service\n- Open the Metrics tab\n- The charts should load \n\n\n","sha":"2a86612d9f2fcc8041a50cec709d71652807c82e","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[APM][OTel] Java EDOT Dashboard: Extend the metrics pattern","number":223539,"url":"https://github.com/elastic/kibana/pull/223539","mergeCommit":{"message":"[APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539)\n\nCloses #223533 \n\n## Summary\n\nTo fix the issue I replaced the `metrics-*` with `*:metrics-*,metrics-*`\nin the ES|QL queries\n\n## Testing\n- With local connection to a new edge edot cluster (created with the\noblt-cli tool)\n- Go to APM > Services and click on the `ad` service\n- Open the Metrics tab\n- The charts should load \n\n\n","sha":"2a86612d9f2fcc8041a50cec709d71652807c82e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.19"],"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/223539","number":223539,"mergeCommit":{"message":"[APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539)\n\nCloses #223533 \n\n## Summary\n\nTo fix the issue I replaced the `metrics-*` with `*:metrics-*,metrics-*`\nin the ES|QL queries\n\n## Testing\n- With local connection to a new edge edot cluster (created with the\noblt-cli tool)\n- Go to APM > Services and click on the `ad` service\n- Open the Metrics tab\n- The charts should load \n\n\n","sha":"2a86612d9f2fcc8041a50cec709d71652807c82e"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
a60e053089
|
[9.0] [Observability] [Alert details page] View in discover link is partial broken (#217993) (#223584)
# Backport This will backport the following commits from `main` to `9.0`: - [[Observability] [Alert details page] View in discover link is partial broken (#217993)](https://github.com/elastic/kibana/pull/217993) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Faisal Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2025-06-12T15:33:47Z","message":"[Observability] [Alert details page] View in discover link is partial broken (#217993)\n\n## Summary\nIt closes #212133 by fixing the URL that contains the DataViewSpec.\nThe URL was passing the DataViewSpec as a string (DataView ID) instead\nof the Spec of the DataView, which caused the DataView ID to change in\nthe URL in the Discover page, and the page could not load the fields.\n\n#### Before\n\n<img width=\"1449\" alt=\"Screenshot 2025-04-10 at 14 51 04\"\nsrc=\"https://github.com/user-attachments/assets/50f8dcab-1964-4f33-8e21-694014273a72\"\n/>\n\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/689253d3-9b97-4fa7-ba60-e953e979953e","sha":"52e3d1f228660646500ac66a0e1a9d8ace2fe431","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"[Observability] [Alert details page] View in discover link is partial broken","number":217993,"url":"https://github.com/elastic/kibana/pull/217993","mergeCommit":{"message":"[Observability] [Alert details page] View in discover link is partial broken (#217993)\n\n## Summary\nIt closes #212133 by fixing the URL that contains the DataViewSpec.\nThe URL was passing the DataViewSpec as a string (DataView ID) instead\nof the Spec of the DataView, which caused the DataView ID to change in\nthe URL in the Discover page, and the page could not load the fields.\n\n#### Before\n\n<img width=\"1449\" alt=\"Screenshot 2025-04-10 at 14 51 04\"\nsrc=\"https://github.com/user-attachments/assets/50f8dcab-1964-4f33-8e21-694014273a72\"\n/>\n\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/689253d3-9b97-4fa7-ba60-e953e979953e","sha":"52e3d1f228660646500ac66a0e1a9d8ace2fe431"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217993","number":217993,"mergeCommit":{"message":"[Observability] [Alert details page] View in discover link is partial broken (#217993)\n\n## Summary\nIt closes #212133 by fixing the URL that contains the DataViewSpec.\nThe URL was passing the DataViewSpec as a string (DataView ID) instead\nof the Spec of the DataView, which caused the DataView ID to change in\nthe URL in the Discover page, and the page could not load the fields.\n\n#### Before\n\n<img width=\"1449\" alt=\"Screenshot 2025-04-10 at 14 51 04\"\nsrc=\"https://github.com/user-attachments/assets/50f8dcab-1964-4f33-8e21-694014273a72\"\n/>\n\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/689253d3-9b97-4fa7-ba60-e953e979953e","sha":"52e3d1f228660646500ac66a0e1a9d8ace2fe431"}}]}] BACKPORT--> Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co> |
||
|
Kibana Machine
|
7b54ebd7af
|
[9.0] Add codeowner for prebuilt Security ML jobs (#223449) (#223543)
# Backport This will backport the following commits from `main` to `9.0`: - [Add codeowner for prebuilt Security ML jobs (#223449)](https://github.com/elastic/kibana/pull/223449) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Susan","email":"23287722+susan-shu-c@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-12T12:47:32Z","message":"Add codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd the Security ML team to codeowners of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis is in order for Security ML to be notified of changes to the\n[Prebuilt ML detections for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich they are responsible for. The security jobs' folders are prefixed\nwith `security_`, such as `security_windows`.\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Add codeowner for prebuilt Security ML jobs","number":223449,"url":"https://github.com/elastic/kibana/pull/223449","mergeCommit":{"message":"Add codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd the Security ML team to codeowners of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis is in order for Security ML to be notified of changes to the\n[Prebuilt ML detections for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich they are responsible for. The security jobs' folders are prefixed\nwith `security_`, such as `security_windows`.\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b"}},"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/223449","number":223449,"mergeCommit":{"message":"Add codeowner for prebuilt Security ML jobs (#223449)\n\n## Summary\n\nAdd the Security ML team to codeowners of\n`x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_*`\n-\n[link](https://github.com/elastic/kibana/tree/main/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules)\n\nThis is in order for Security ML to be notified of changes to the\n[Prebuilt ML detections for\nSecurity](https://www.elastic.co/docs/reference/data-analysis/machine-learning/ootb-ml-jobs-siem)\nwhich they are responsible for. The security jobs' folders are prefixed\nwith `security_`, such as `security_windows`.\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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>","sha":"c7d274052973c2e5e3089b6b44e6df51a773579b"}}]}] BACKPORT--> Co-authored-by: Susan <23287722+susan-shu-c@users.noreply.github.com> Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co> |
||
|
Kibana Machine
|
e835dff82e
|
[9.0] Chunk saved object creation by 10 (#221479) (#223194)
# Backport This will backport the following commits from `main` to `9.0`: - [Chunk saved object creation by 10 (#221479)](https://github.com/elastic/kibana/pull/221479) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2025-06-10T09:26:30Z","message":"Chunk saved object creation by 10 (#221479)\n\n## Summary\n\nBulk create saved object for manual rule run in chunks\n\nIssue [here](https://github.com/elastic/security-team/issues/12678)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29b11809b7b2973161932e46d7d1f84a80aafeaf","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"Chunk saved object creation by 10","number":221479,"url":"https://github.com/elastic/kibana/pull/221479","mergeCommit":{"message":"Chunk saved object creation by 10 (#221479)\n\n## Summary\n\nBulk create saved object for manual rule run in chunks\n\nIssue [here](https://github.com/elastic/security-team/issues/12678)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29b11809b7b2973161932e46d7d1f84a80aafeaf"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221479","number":221479,"mergeCommit":{"message":"Chunk saved object creation by 10 (#221479)\n\n## Summary\n\nBulk create saved object for manual rule run in chunks\n\nIssue [here](https://github.com/elastic/security-team/issues/12678)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29b11809b7b2973161932e46d7d1f84a80aafeaf"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
5419984424
|
[9.0] Add trace.id to EBT events (#222366) (#223517)
# Backport This will backport the following commits from `main` to `9.0`: - [Add trace.id to EBT events (#222366)](https://github.com/elastic/kibana/pull/222366) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T20:11:41Z","message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.1.0","v8.19.0","author:obs-ux-management","v9.0.3"],"title":"Add trace.id to EBT events","number":222366,"url":"https://github.com/elastic/kibana/pull/222366","mergeCommit":{"message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222366","number":222366,"mergeCommit":{"message":"Add trace.id to EBT events (#222366)\n\nCloses https://github.com/elastic/observability-dev/issues/4445\n\nEBT implementation: https://github.com/elastic/ebt/pull/57\n\n## Summary\n\nIn this PR, we are adding `getTraceContext` to the `createAnalytics` in\norder to include `trace.id` in the EBT events.\n\n\n\n\n### ⚠️ Note\n\nSome events might not have a `trace.id` due to not having an active\ntransaction at the moment of reporting the event. For those, we can\nimplement more sophisticated logic to keep track of transactions and use\nthe `trace.id` of the last one for the event (in a follow-up ticket, if\nnecessary).\n\n### How to test\n- Add `telemetry.localShipper: true` to the kibana config and create a\ndata view for `ebt-kibana-browser` index\n- Check the `trace.id` in the events that are passed\n\n---------\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>","sha":"cfc7f0ed0e84e486b9757756334f61153bae2037"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223464","number":223464,"state":"MERGED","mergeCommit":{"sha":"71b79af9b7c44566118e65b2e6d9341c5c39898d","message":"[8.19] Add trace.id to EBT events (#222366) (#223464)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Add trace.id to EBT events\n(#222366)](https://github.com/elastic/kibana/pull/222366)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Viduni Wickramarachchi
|
01bb8fc018
|
[9.0] [Obs AI Assistant] Improve conversation callout (#223442) (#223460)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Improve conversation callout (#223442)](https://github.com/elastic/kibana/pull/223442) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T18:06:19Z","message":"[Obs AI Assistant] Improve conversation callout (#223442)\n\n## Summary\n\nImprove conversation callout rendering when the callout should not be\ndisplayed.\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)","sha":"4a9b69fb22ca58a8058df9e851d117501066a658","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"[Obs AI Assistant] Improve conversation callout","number":223442,"url":"https://github.com/elastic/kibana/pull/223442","mergeCommit":{"message":"[Obs AI Assistant] Improve conversation callout (#223442)\n\n## Summary\n\nImprove conversation callout rendering when the callout should not be\ndisplayed.\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)","sha":"4a9b69fb22ca58a8058df9e851d117501066a658"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.0","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223442","number":223442,"mergeCommit":{"message":"[Obs AI Assistant] Improve conversation callout (#223442)\n\n## Summary\n\nImprove conversation callout rendering when the callout should not be\ndisplayed.\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)","sha":"4a9b69fb22ca58a8058df9e851d117501066a658"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Garrett Spong
|
652e3eba69
|
[9.0] [Security Solution] [Security Assistant] Poll for evaluation completion in FTR tests (#222487) (#223474)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] [Security Assistant] Poll for evaluation completion in FTR tests (#222487)](https://github.com/elastic/kibana/pull/222487) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Garrett Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T21:47:07Z","message":"[Security Solution] [Security Assistant] Poll for evaluation completion in FTR tests (#222487)\n\n## Summary\n\nThis PR fixes an issue with running our Security Assistant evals on CI\nwhere the tests would finish and cleanup before the evaluations would\nactually complete. There was no issue with actually running the\nevaluations, they would finish without error, however since the tests\nwould complete beforehand, the required resources (alerts, kb docs,\nelser, etc) would be cleaned up and the evaluations wouldn't pass.\n\nThe issue has been fixed by polling for evaluation completion before\nletting the tests complete. This was accomplished by writing evaluation\nresults (`id`/`status`) to a new ephemeral index\n`.kibana-elastic-ai-assistant-evaluations-default` with an ILM policy of\n`1d`, and then updating the GET evaluation route to include a `results`\narray that can be used to confirm the status of the evaluation.\n\n\nNote: There is no impact to production deployments with these changes as\nall evaluation routes are gated behind the evaluation feature flag,\nwhich can be enabled by adding the below configuration to your\n`kibana.dev.yml`:\n\n\n```\nxpack.securitySolution.enableExperimental:\n - \"assistantModelEvaluation\"\n```\n---\n\n## Results\n\n[Successful\nBuild](https://buildkite.com/elastic/kibana-pull-request/builds/306787/summary/annotations?jid=019756d8-e32f-4366-be5c-0f766a7c2934)\nwith `33m16s` runtime\n\n[ES|QL Generation\nRegression]( |
||
|
Kibana Machine
|
b1f63fb45c
|
[9.0] [Build] Fix parallel stderr (#223177) (#223481)
# Backport This will backport the following commits from `main` to `9.0`: - [[Build] Fix parallel stderr (#223177)](https://github.com/elastic/kibana/pull/223177) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T22:49:30Z","message":"[Build] Fix parallel stderr (#223177)\n\n## Summary\n- Caused by #217929\n- Fixes errors not being correctly surfaced when running tasks in\nparallel, see:\n[logs](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6363#0197545d-e878-4dfb-97a5-0ab7d11af95c/7318-7837)\n- Added tests for `bufferLogs: true`\n\n### Testing\n- [Error\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6391)\n- Future errors will be under the \"Finalizing Kibana Artifacts\" header\ninstead of the last artifact's logs. See\n2aa4e6523add9b77ba4e79f5863c5cbd5bc396aa\n- [Good\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6392)","sha":"fe9c921b3ed8614d2c7b9ae193fe1f83ef7c0d42","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Build] Fix parallel stderr","number":223177,"url":"https://github.com/elastic/kibana/pull/223177","mergeCommit":{"message":"[Build] Fix parallel stderr (#223177)\n\n## Summary\n- Caused by #217929\n- Fixes errors not being correctly surfaced when running tasks in\nparallel, see:\n[logs](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6363#0197545d-e878-4dfb-97a5-0ab7d11af95c/7318-7837)\n- Added tests for `bufferLogs: true`\n\n### Testing\n- [Error\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6391)\n- Future errors will be under the \"Finalizing Kibana Artifacts\" header\ninstead of the last artifact's logs. See\n2aa4e6523add9b77ba4e79f5863c5cbd5bc396aa\n- [Good\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6392)","sha":"fe9c921b3ed8614d2c7b9ae193fe1f83ef7c0d42"}},"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/223177","number":223177,"mergeCommit":{"message":"[Build] Fix parallel stderr (#223177)\n\n## Summary\n- Caused by #217929\n- Fixes errors not being correctly surfaced when running tasks in\nparallel, see:\n[logs](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6363#0197545d-e878-4dfb-97a5-0ab7d11af95c/7318-7837)\n- Added tests for `bufferLogs: true`\n\n### Testing\n- [Error\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6391)\n- Future errors will be under the \"Finalizing Kibana Artifacts\" header\ninstead of the last artifact's logs. See\n2aa4e6523add9b77ba4e79f5863c5cbd5bc396aa\n- [Good\nbuild](https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6392)","sha":"fe9c921b3ed8614d2c7b9ae193fe1f83ef7c0d42"}}]}] BACKPORT--> Co-authored-by: Brad White <Ikuni17@users.noreply.github.com> |
||
Philippe Oberti
|
a441fd60e7
|
[9.0][Security Solution] fix cell actions not working when opening a timeline from specific rules (#223306)
## Summary This PR fixes an issue raised in a recent SDH. The problem is the cell actions in the Timeline flyout are not being shown in the UI for Timelines created off of alerts generated by the some rule types (for example threshold or new terms). All Timelines are created with a `dataViewId` set to undefined at first. For the Timelines listed above, at the time of creation, we pass an array of `indexNames` (see [here](https://github.com/elastic/kibana/blob/9.0/x-pack/solutions/security/plugins/security_solution/public/detections/components/alerts_table/actions.tsx#L484) for Threshold rule for example). We then have [a check in this hook](https://github.com/elastic/kibana/blob/9.0/x-pack/solutions/security/plugins/security_solution/public/timelines/components/open_timeline/use_update_timeline.tsx#L60) that sets the selected dataView in Redux if the `indexNames` is not empty. This is the source of the issue here. For all other rule types, we do not pass anything for `indexNames` and therefore do not have any problems... Instead of making changes to [this actions.tsx](https://github.com/elastic/kibana/blob/9.0/x-pack/solutions/security/plugins/security_solution/public/detections/components/alerts_table/actions.tsx) file, which is very risky, the approach here was to have a fallback when the `dataView` is undefined, and ONLY in case we are trying to display cell actions in a Timeline. This way, the risk to impact any other scenarios are extremely limited. #### Before https://github.com/user-attachments/assets/04c1c64b-2baa-4d93-8476-f2c5bcb5157f #### After https://github.com/user-attachments/assets/dc15c9b8-00b4-49bf-b5da-a01ac6a257e8 ### Notes **_We do not want to fix this is `main`, as this code is being modified extensively with the current sourcerer refactor/improvement the @elastic/security-threat-hunting-investigations team is doing. This is why I am created 4 identical PRs, targeting `8.17`, `8.18`, `8.19` and `9.0`, instead of using automated backports._** |
||
Alejandro Fernández Haro
|
92f5fc1f07
|
[9.0] Update dependency @elastic/ebt to ^1.2.1 (main) (#223269) (#223458)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @elastic/ebt to ^1.2.1 (main) (#223269)](https://github.com/elastic/kibana/pull/223269) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T18:02:31Z","message":"Update dependency @elastic/ebt to ^1.2.1 (main) (#223269)","sha":"f6834ce0f2e699e6fb245ff76c5452640c456593","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v9.1.0","v8.19.0","v9.0.3"],"title":"Update dependency @elastic/ebt to ^1.2.1 (main)","number":223269,"url":"https://github.com/elastic/kibana/pull/223269","mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.1 (main) (#223269)","sha":"f6834ce0f2e699e6fb245ff76c5452640c456593"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223269","number":223269,"mergeCommit":{"message":"Update dependency @elastic/ebt to ^1.2.1 (main) (#223269)","sha":"f6834ce0f2e699e6fb245ff76c5452640c456593"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/223457","number":223457,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
7d19895877
|
[9.0] Update base64-js dependencies (main) (#219586) (#223441)
# Backport This will backport the following commits from `main` to `9.0`: - [Update base64-js dependencies (main) (#219586)](https://github.com/elastic/kibana/pull/219586) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-11T16:17:40Z","message":"Update base64-js dependencies (main) (#219586)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/base64-js | devDependencies | minor | [`^1.2.5` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2fbase64-js/1.2.5/1.5.0)\n|\n| [base64-js](https://redirect.github.com/beatgammit/base64-js) |\ndependencies | patch | [`^1.3.1` ->\n`^1.5.1`](https://renovatebot.com/diffs/npm/base64-js/1.5.1/1.5.1) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"bdf403582eca5c10effcbe8437976368b71ea1d9","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update base64-js dependencies (main)","number":219586,"url":"https://github.com/elastic/kibana/pull/219586","mergeCommit":{"message":"Update base64-js dependencies (main) (#219586)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/base64-js | devDependencies | minor | [`^1.2.5` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2fbase64-js/1.2.5/1.5.0)\n|\n| [base64-js](https://redirect.github.com/beatgammit/base64-js) |\ndependencies | patch | [`^1.3.1` ->\n`^1.5.1`](https://renovatebot.com/diffs/npm/base64-js/1.5.1/1.5.1) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"bdf403582eca5c10effcbe8437976368b71ea1d9"}},"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/219586","number":219586,"mergeCommit":{"message":"Update base64-js dependencies (main) (#219586)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​types/base64-js | devDependencies | minor | [`^1.2.5` ->\n`^1.5.0`](https://renovatebot.com/diffs/npm/@types%2fbase64-js/1.2.5/1.5.0)\n|\n| [base64-js](https://redirect.github.com/beatgammit/base64-js) |\ndependencies | patch | [`^1.3.1` ->\n`^1.5.1`](https://renovatebot.com/diffs/npm/base64-js/1.5.1/1.5.1) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get\n[config\nhelp](https://redirect.github.com/renovatebot/renovate/discussions) if\nthat's undesired.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"bdf403582eca5c10effcbe8437976368b71ea1d9"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com> |