mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
83335 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
70e0ee45ae
|
[8.18] [Synthetics] Error details - Improved network error handling (#224296) (#224445)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
1d5547d90e
|
[8.18] [Security Solution] Fix "too many clauses" error on prebuilt rules installation page (#223240) (#224283)
# Backport This will backport the following commits from `main` to `8.18`: - [[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":["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,"url":"https://github.com/elastic/kibana/pull/224282","number":224282,"state":"OPEN"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Tim Sullivan
|
bf1ef87b35
|
[8.18] [Canvas/PDF report] Allow canvas to generate PDF report (#224309) (#224339)
# Backport This will backport the following commits from `main` to `8.18`: - [[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--> |
||
|
Kibana Machine
|
be28e8ee47
|
[8.18] [Fleet] Add install retry to ensureInstalledPackage (#224265) (#224418)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Add install retry to ensureInstalledPackage (#224265)](https://github.com/elastic/kibana/pull/224265) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2025-06-18T12:23:47Z","message":"[Fleet] Add install retry to ensureInstalledPackage (#224265)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/213337\n\nWhen requests to install a package as part of the logic ensuring that a\npackage is installed are fired concurrently, the second request fails\nwith a 409 `version_conflict_engine_exception`, which causes flakiness\nin tests. Ignoring these errors in transform installs was already\nattempted in https://github.com/elastic/kibana/pull/177380. This PR adds\na retry mechanism directly into the package install to consolidate the\nflow.\n\n### Identify risks\n\nLow probability risk of slower package policy creation.","sha":"62f56c884b87e953ef9d6c09e693a70691c28c09","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] Add install retry to ensureInstalledPackage","number":224265,"url":"https://github.com/elastic/kibana/pull/224265","mergeCommit":{"message":"[Fleet] Add install retry to ensureInstalledPackage (#224265)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/213337\n\nWhen requests to install a package as part of the logic ensuring that a\npackage is installed are fired concurrently, the second request fails\nwith a 409 `version_conflict_engine_exception`, which causes flakiness\nin tests. Ignoring these errors in transform installs was already\nattempted in https://github.com/elastic/kibana/pull/177380. This PR adds\na retry mechanism directly into the package install to consolidate the\nflow.\n\n### Identify risks\n\nLow probability risk of slower package policy creation.","sha":"62f56c884b87e953ef9d6c09e693a70691c28c09"}},"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/224265","number":224265,"mergeCommit":{"message":"[Fleet] Add install retry to ensureInstalledPackage (#224265)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/213337\n\nWhen requests to install a package as part of the logic ensuring that a\npackage is installed are fired concurrently, the second request fails\nwith a 409 `version_conflict_engine_exception`, which causes flakiness\nin tests. Ignoring these errors in transform installs was already\nattempted in https://github.com/elastic/kibana/pull/177380. This PR adds\na retry mechanism directly into the package install to consolidate the\nflow.\n\n### Identify risks\n\nLow probability risk of slower package policy creation.","sha":"62f56c884b87e953ef9d6c09e693a70691c28c09"}}]}] BACKPORT--> Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co> |
||
Patrick Mueller
|
0ca1e4ded2
|
[8.18] [ResponseOps][Alerting] assure grouping fields in alert match expected cardinality (#223409) (#224347)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
07071464e1
|
[8.18] Update dependency react-use to v17 (main) (#219595) (#224386)
# Backport This will backport the following commits from `main` to `8.18`: - [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]( |
||
|
Anton Dosov
|
4bdab15e45
|
[8.18] Update classnames dependencies (main) (#219587) (#224383)
# Backport This will backport the following commits from `main` to `8.18`: - [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> |
||
Steph Milovic
|
7c47b7ef45
|
[8.18] [Security Assistant] Fix telemetry tool reporting (#223832) (#224344)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
ab128c2320
|
[8.18] [Connectors] Fix Bedrock connector not using the action proxy configuration (#224130) (#224328)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
dfef34ccc9
|
[8.18] [Security Solution] Fix rule filters display issues (#222963) (#224301)
# Backport This will backport the following commits from `main` to `8.18`: - [[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> |
||
Dima Arnautov
|
7da29174c7
|
[8.18] Support local file path for xpack.productDocBase.artifactRepositoryUrl (#217046) (#224284)
# Backport This will backport the following commits from `main` to `8.18`: - [Support local file path for `xpack.productDocBase.artifactRepositoryUrl` (#217046)](https://github.com/elastic/kibana/pull/217046) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-04-14T13:27:41Z","message":"Support local file path for `xpack.productDocBase.artifactRepositoryUrl` (#217046)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216583\n\nAdds support for a local file path in\n`xpack.productDocBase.artifactRepositoryUrl` setting.\nIf local path with `file://` protocol is provided, it has to contain a\npath to a directory with the artifacts and the `index.xml` file.\n\n#### How to test \n\n1. Download the XML and zip files from\nhttps://kibana-knowledge-base-artifacts.elastic.co\n2. Create a folder, e.g. `mkdir /Users/<my_user>/test_artifacts` and\nplace all the files there. The XML file has to be called `index.xml`\n3. Add `xpack.productDocBase.artifactRepositoryUrl:\n'file:///Users/<my_user>/test_artifacts'` to your `kibana.dev.yml`\n4. Go to `/app/management/kibana/observabilityAiAssistantManagement` in\nKibana and install Elastic documentation\n5. Kibana dev server should report `[2025-04-07T14:05:10.640+02:00][INFO\n][plugins.productDocBase.package-installer] Documentation installation\nsuccessful for product [security] and version [8.17]`\n6. Check `data/ai-kb-artifacts` folder in your Kibana repo, it should\ncontain zip files with docs\n\n### Checklist\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- [x]\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- [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":"6722f142a4d36f0c84c9eb258287900f2f559389","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Team:ML","backport:version","v9.1.0","v8.19.0"],"title":"Support local file path for `xpack.productDocBase.artifactRepositoryUrl`","number":217046,"url":"https://github.com/elastic/kibana/pull/217046","mergeCommit":{"message":"Support local file path for `xpack.productDocBase.artifactRepositoryUrl` (#217046)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216583\n\nAdds support for a local file path in\n`xpack.productDocBase.artifactRepositoryUrl` setting.\nIf local path with `file://` protocol is provided, it has to contain a\npath to a directory with the artifacts and the `index.xml` file.\n\n#### How to test \n\n1. Download the XML and zip files from\nhttps://kibana-knowledge-base-artifacts.elastic.co\n2. Create a folder, e.g. `mkdir /Users/<my_user>/test_artifacts` and\nplace all the files there. The XML file has to be called `index.xml`\n3. Add `xpack.productDocBase.artifactRepositoryUrl:\n'file:///Users/<my_user>/test_artifacts'` to your `kibana.dev.yml`\n4. Go to `/app/management/kibana/observabilityAiAssistantManagement` in\nKibana and install Elastic documentation\n5. Kibana dev server should report `[2025-04-07T14:05:10.640+02:00][INFO\n][plugins.productDocBase.package-installer] Documentation installation\nsuccessful for product [security] and version [8.17]`\n6. Check `data/ai-kb-artifacts` folder in your Kibana repo, it should\ncontain zip files with docs\n\n### Checklist\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- [x]\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- [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":"6722f142a4d36f0c84c9eb258287900f2f559389"}},"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/217046","number":217046,"mergeCommit":{"message":"Support local file path for `xpack.productDocBase.artifactRepositoryUrl` (#217046)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/216583\n\nAdds support for a local file path in\n`xpack.productDocBase.artifactRepositoryUrl` setting.\nIf local path with `file://` protocol is provided, it has to contain a\npath to a directory with the artifacts and the `index.xml` file.\n\n#### How to test \n\n1. Download the XML and zip files from\nhttps://kibana-knowledge-base-artifacts.elastic.co\n2. Create a folder, e.g. `mkdir /Users/<my_user>/test_artifacts` and\nplace all the files there. The XML file has to be called `index.xml`\n3. Add `xpack.productDocBase.artifactRepositoryUrl:\n'file:///Users/<my_user>/test_artifacts'` to your `kibana.dev.yml`\n4. Go to `/app/management/kibana/observabilityAiAssistantManagement` in\nKibana and install Elastic documentation\n5. Kibana dev server should report `[2025-04-07T14:05:10.640+02:00][INFO\n][plugins.productDocBase.package-installer] Documentation installation\nsuccessful for product [security] and version [8.17]`\n6. Check `data/ai-kb-artifacts` folder in your Kibana repo, it should\ncontain zip files with docs\n\n### Checklist\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- [x]\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- [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":"6722f142a4d36f0c84c9eb258287900f2f559389"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/219083","number":219083,"branch":"8.19","state":"MERGED","mergeCommit":{"sha":"de3d30aeda57436d96a0d6142e315bc076376657","message":"[8.19] Support local file path for `xpack.productDocBase.artifactRepositoryUrl` (#217046) (#219083)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Support local file path for\n`xpack.productDocBase.artifactRepositoryUrl`\n(#217046)](https://github.com/elastic/kibana/pull/217046)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}}]}] BACKPORT--> |
||
natasha-moore-elastic
|
36fed063f1
|
[8.18] Replace old Security API doc links with API ref links in doc link service (#223388) (#224208)
This will backport the following commits from `8.19` to `8.18`: * https://github.com/elastic/kibana/pull/223388 Co-authored-by: Lisa Cawley <lcawley@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
|
Kibana Machine
|
4ce8f1dd5c
|
[8.18] [Synthetics] Last Successful screenshots match the step (#224220) (#224250)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
c9f6c3d8d3
|
[8.18] [a11y][ml] Add visually hidden label for screenreader for open documentation button (#224047) (#224238)
# Backport This will backport the following commits from `main` to `8.18`: - [[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> |
||
|
Kibana Machine
|
348ae36a9c
|
[8.18] Fix that gap can be stuck "in-progress" (#221473) (#224176)
# Backport
This will backport the following commits from `main` to `8.18`:
- Fix that gap can be stuck "in-progress" (#221473) (
|
||
|
Kibana Machine
|
3ff5b72f52
|
[8.18] [Inspector]: fix pagination not working (#223537) (#224215)
# Backport This will backport the following commits from `main` to `8.18`: - [[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ță
|
d73e7250ec
|
[8.18] [ResponseOps][Cases]Allow dashes in host names in Observables (#219038) (#224204)
# Backport This will backport the following commits from `main` to `8.18`: - [[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]
|
541654fc7d
|
[8.18] Sync bundled packages with Package Storage (#224017)
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> |
||
Angela Chuang
|
cae09d0785
|
[8.18][Security Assistant] EIS usage callout (#221566) (#224107)
# 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> |
||
Alexi Doak
|
9799132aae
|
[8.18] Upgrade Puppeteer to v24.10.1 (#223985) (#224147)
# Backport This will backport the following commits from `main` to `8.18`: - [Upgrade Puppeteer to v24.10.1 (#223985)](https://github.com/elastic/kibana/pull/223985) <!--- Backport version: 10.0.1 --> ### 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.17","8.18"],"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,"url":"https://github.com/elastic/kibana/pull/224115","number":224115,"state":"MERGED","mergeCommit":{"sha":"fe622ec8cfa8c3d945e61c7a940a5c3413b07aed","message":"[8.19] Upgrade Puppeteer to v24.10.1 (#223985) (#224115)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.19`:\n- [Upgrade Puppeteer to v24.10.1\n(#223985)](https://github.com/elastic/kibana/pull/223985)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com>\nCo-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>\nCo-authored-by: Alexandra Doak <alexandra.doak@elastic.co>"}},{"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,"url":"https://github.com/elastic/kibana/pull/224116","number":224116,"state":"MERGED","mergeCommit":{"sha":"d322792ae59cbe58c8df8db82e64dc8a1ca8fbfc","message":"[9.0] Upgrade Puppeteer to v24.10.1 (#223985) (#224116)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Upgrade Puppeteer to v24.10.1\n(#223985)](https://github.com/elastic/kibana/pull/223985)\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: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com>\nCo-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>\nCo-authored-by: Alexandra Doak <alexandra.doak@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Ersin Erdal <92688503+ersin-erdal@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
c1ecf25cce
|
[8.18] [UI Counters] fix flaky test retry logic (#224151) (#224165)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
e01dba894d
|
[8.18] [Security GenAI][Bug] OSS models do not work when streaming is ON (#12827) (#224129) (#224146)
# Backport This will backport the following commits from `main` to `8.18`: - [[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","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,"url":"https://github.com/elastic/kibana/pull/224145","number":224145,"state":"OPEN"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Quynh Nguyen (Quinn)
|
ef473728b6
|
[8.18] [ML] Fix OpenAI connector does not use the action proxy configuration for all subactions (#219617) (#224125)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
2de896fcbd
|
[8.18] [a11y][ml] Add visually hidden label for screenreader for select checkboxes in anomaly detection job selection flyout (#224025) (#224121)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
60b6ea2e41
|
[8.18] [Watcher] Revert back to using .watches system index (#223898) (#224078)
# Backport This will backport the following commits from `main` to `8.18`: - [[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
|
c98b3abeaf
|
[8.18] Remove tech preview designation from session invalidation API (#224076) (#224104)
# Backport This will backport the following commits from `main` to `8.18`: - [Remove tech preview designation from session invalidation API (#224076)](https://github.com/elastic/kibana/pull/224076) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2025-06-16T16:30:51Z","message":"Remove tech preview designation from session invalidation API (#224076)\n\n## Summary\n\nRemoves the tech preview designation from the session invalidation API.\n\nResolves https://github.com/elastic/kibana/issues/224070\n\n## Release Note\nThe Session Invalidation API is now marked as Stable.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"39818955b943010d7b0b8e195f3534261d98e18a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","backport:prev-major","v9.1.0"],"title":"Remove tech preview designation from session invalidation API","number":224076,"url":"https://github.com/elastic/kibana/pull/224076","mergeCommit":{"message":"Remove tech preview designation from session invalidation API (#224076)\n\n## Summary\n\nRemoves the tech preview designation from the session invalidation API.\n\nResolves https://github.com/elastic/kibana/issues/224070\n\n## Release Note\nThe Session Invalidation API is now marked as Stable.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"39818955b943010d7b0b8e195f3534261d98e18a"}},"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/224076","number":224076,"mergeCommit":{"message":"Remove tech preview designation from session invalidation API (#224076)\n\n## Summary\n\nRemoves the tech preview designation from the session invalidation API.\n\nResolves https://github.com/elastic/kibana/issues/224070\n\n## Release Note\nThe Session Invalidation API is now marked as Stable.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"39818955b943010d7b0b8e195f3534261d98e18a"}}]}] BACKPORT--> Co-authored-by: Larry Gregory <larry.gregory@elastic.co> |
||
Gergő Ábrahám
|
ee235d1a0d
|
[8.18] [EDR Workflows] Add dns event collection for macOS for Elastic Defend (#223566) (#224089)
# Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Add `dns` event collection for macOS for Elastic Defend (#223566)](https://github.com/elastic/kibana/pull/223566) <!--- Backport version: 10.0.1 --> ### 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.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,"url":"https://github.com/elastic/kibana/pull/224066","number":224066,"state":"OPEN"},{"branch":"9.0","label":"v9.0.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/224067","number":224067,"state":"OPEN"},{"branch":"8.18","label":"v8.18.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Ahmad Bamieh
|
09ac96b131
|
[8.18] Remove unnecessary try catch in the APM user filters (#224014) (#224058)
# Backport This will backport the following commits from `main` to `8.18`: - [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--> |
||
|
Kibana Machine
|
465e87889f
|
[8.18] fix(): inconsistent page_url between refresh and navigations (#224006) (#224040)
# Backport This will backport the following commits from `main` to `8.18`: - [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
|
d9f4f8dbdb
|
[8.18] Use American spelling for more occurrences (followup) (#223950) (#223964)
# Backport This will backport the following commits from `main` to `8.18`: - [Use American spelling for more occurrences (followup) (#223950)](https://github.com/elastic/kibana/pull/223950) <!--- 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-13T17:54:17Z","message":"Use American spelling for more occurrences (followup) (#223950)\n\nFollow up https://github.com/elastic/kibana/pull/223416","sha":"2cfdc72adebf5ae445740c6947adbcb800d4adfa","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:obs-ux-infra_services","Team:obs-ux-management","v9.1.0"],"title":"Use American spelling for more occurrences (followup)","number":223950,"url":"https://github.com/elastic/kibana/pull/223950","mergeCommit":{"message":"Use American spelling for more occurrences (followup) (#223950)\n\nFollow up https://github.com/elastic/kibana/pull/223416","sha":"2cfdc72adebf5ae445740c6947adbcb800d4adfa"}},"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/223950","number":223950,"mergeCommit":{"message":"Use American spelling for more occurrences (followup) (#223950)\n\nFollow up https://github.com/elastic/kibana/pull/223416","sha":"2cfdc72adebf5ae445740c6947adbcb800d4adfa"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
6a135983fb
|
[8.18] [Connectors] Apply autoFocus prop to cc and bcc elements on email connector form (#223828) (#223938)
# Backport This will backport the following commits from `main` to `8.18`: - [[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> |
||
Mark Hopkin
|
03ee259702
|
[8.18] 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) (#223909)
# Backport This will backport the following commits from `main` to `8.18`: - [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
039dc4a8a8
|
[8.18] [DOCS] Adds Experience Docs to codeowners for setting docs (#223615) (#223840)
# Backport This will backport the following commits from `main` to `8.18`: - [[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> |
||
|
Kibana Machine
|
5ca82e15a7
|
[8.18] chore(dep): bump brace-expansion from 1.1.11 to 1.11.12 and 2.0.1 to 2.0.2 (#223589) (#223623)
# Backport This will backport the following commits from `main` to `8.18`: - [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> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a4c31a0e68
|
[8.18] [APM][OTel] Java EDOT Dashboard: Extend the metrics pattern (#223539) (#223606)
# Backport This will backport the following commits from `main` to `8.18`: - [[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> |
||
Viduni Wickramarachchi
|
b23b366261
|
[8.18] [Obs AI Assistant] Avoid adding tool instructions to the system message when tools are disabled (#223278) (#223585)
# Backport This will backport the following commits from `main` to `8.18`: - [[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--> |
||
|
Kibana Machine
|
396a0b204d
|
[8.18] Add codeowner for prebuilt Security ML jobs (#223449) (#223541)
# Backport This will backport the following commits from `main` to `8.18`: - [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> |
||
Brad White
|
4410049ce6
|
[8.18] [Build] Fix parallel stderr (#223177) (#223482)
# Backport This will backport the following commits from `main` to `8.18`: - [[Build] Fix parallel stderr (#223177)](https://github.com/elastic/kibana/pull/223177) <!--- Backport version: 10.0.0 --> ### 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"}},{"url":"https://github.com/elastic/kibana/pull/223480","number":223480,"branch":"8.19","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/223481","number":223481,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
b5c3389d9b
|
[8.18] add es-cache to cleaned folders (#223373) (#223508)
# Backport This will backport the following commits from `main` to `8.18`: - [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> |
||
|
Viduni Wickramarachchi
|
5d98353fa0
|
[8.18] [Obs AI Assistant] Improve conversation callout (#223442) (#223462)
# Backport This will backport the following commits from `main` to `8.18`: - [[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--> |
||
Philippe Oberti
|
71ffec7704
|
[8.18][Security Solution] fix cell actions not working when opening a timeline from specific rules (#223302)
## 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/8.18/x-pack/solutions/security/plugins/security_solution/public/detections/components/alerts_table/actions.tsx#L488) for Threshold rule for example). We then have [a check in this hook](https://github.com/elastic/kibana/blob/8.18/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/8.18/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/2222d30d-7028-4d7e-8034-e180d21ae84b #### After https://github.com/user-attachments/assets/10cb4807-67aa-4685-b34c-f56fbac8087f ### 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._** |
||
|
Kibana Machine
|
219b2ff1a2
|
[8.18] Use American spelling for some occurrences of analyze/analyse (#223416) (#223435)
# Backport This will backport the following commits from `main` to `8.18`: - [Use American spelling for some occurrences of analyze/analyse (#223416)](https://github.com/elastic/kibana/pull/223416) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T16:10:06Z","message":"Use American spelling for some occurrences of analyze/analyse (#223416)\n\nTo align with EUI language guidelines","sha":"98701f3f5de0594319e1f325e772d7b8903d0497","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:obs-ux-infra_services","Team:obs-ux-management","v9.1.0"],"title":"Use American spelling for some occurrences of analyze/analyse","number":223416,"url":"https://github.com/elastic/kibana/pull/223416","mergeCommit":{"message":"Use American spelling for some occurrences of analyze/analyse (#223416)\n\nTo align with EUI language guidelines","sha":"98701f3f5de0594319e1f325e772d7b8903d0497"}},"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/223416","number":223416,"mergeCommit":{"message":"Use American spelling for some occurrences of analyze/analyse (#223416)\n\nTo align with EUI language guidelines","sha":"98701f3f5de0594319e1f325e772d7b8903d0497"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
|
Viduni Wickramarachchi
|
cc5b79882b
|
[8.18] [Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782) (#223287)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)](https://github.com/elastic/kibana/pull/220782) <!--- 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-10T16:44:53Z","message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\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- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:feature","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] Add Elastic Managed LLM tour callout","number":220782,"url":"https://github.com/elastic/kibana/pull/220782","mergeCommit":{"message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\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- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05"}},"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/220782","number":220782,"mergeCommit":{"message":"[Obs AI Assistant] Add Elastic Managed LLM tour callout (#220782)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/253\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/252\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/250\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/251\n\n## Summary\n\n1. Added Elastic Managed LLM connector via a tour callout when the\nconnector is present. This will be included in the AI Assistant flyout,\nAI Assistant page and contextual insights.\n2. Added a callout in the conversation when the Elastic Managed LLM is\nbeing used\n3. Added `Manage Connectors` to contextual insights action menu\n4. Added `AI Connector` updates to settings.\n\n## How to enable the Elastic LLM Connector for testing\n\n1. Run command - `VAULT_ADDR={...} vault login -method oidc`\n2. Run command - `node scripts/eis.js` (This will output the config for\nthe connector which needs to be pasted to `kibana.dev.yml`)\n3. Run Elasticsearch - `yarn es snapshot --license trial -E\nxpack.inference.elastic.url=http://localhost:8443/`\n4. Start Kibana as usual\n5. Run `yarn run ts-node --transpile-only\nx-pack/solutions/observability/packages/kbn-genai-cli/recipes/hello_world.ts`\nto test whether it works correctly.\n6. The connector should be visible in the connectors list in Kibana and\nin the AI Assistant\n\n## Screenshots\n\n### Flyout\n\n<img width=\"544\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e9f454e1-dcfe-4cf5-9929-77282764a8ce\"\n/>\n\n### Page\n\n<img width=\"1684\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/aac7c329-9918-4626-9fe9-5682902000fe\"\n/>\n\n### Contextual insights in APM\n\n<img width=\"1098\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/9eca3d33-b7ea-4128-a7de-d1b4776d8a8e\"\n/>\n\n### Callout within the conversation\n\n<img width=\"674\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/5c0b3933-b253-474e-92a5-d8793ebff819\"\n/>\n\n<img width=\"904\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2ca1ffef-0fcb-4d4f-addf-20c4927b7db0\"\n/>\n\n### Updates to AI connector title, description and buttons in Settings\n\n<img width=\"959\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/838d651d-319b-4637-a522-dc80d01bb11e\"\n/>\n\n### `Manage Connectors` link to contextual insights\n\n\n\n\n\n### Checklist\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- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cf4d23a6d42208a131c91d1481377c5950cf0b05"}},{"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
|
2d440ccef9
|
[8.18] [Synthetics] Avoid re-render when Run test finishes (#222503) (#223382)
# Backport This will backport the following commits from `main` to `8.18`: - [[Synthetics] Avoid re-render when Run test finishes (#222503)](https://github.com/elastic/kibana/pull/222503) <!--- 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-11T09:58:29Z","message":"[Synthetics] Avoid re-render when Run test finishes (#222503)\n\nThis PR closes #217482 \n\nAfter manually running a test a re-render was causing loss of unsaved\nchanges.\n\nBefore:\n\n\n |
||
|
Kibana Machine
|
5bef70e586
|
[8.18] [Lens] Limit user messages to the lens container (#202717) (#223352)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens] Limit user messages to the lens container (#202717)](https://github.com/elastic/kibana/pull/202717) <!--- 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-11T07:08:36Z","message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Lens] Limit user messages to the lens container","number":202717,"url":"https://github.com/elastic/kibana/pull/202717","mergeCommit":{"message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae"}},"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/202717","number":202717,"mergeCommit":{"message":"[Lens] Limit user messages to the lens container (#202717)\n\n## Summary\n\nThis PR fixes the wrong position of the Lens user messages caused by the\nabsolute positioning of their container within a `static` positioned\nparent.\n\n>An element with `position: absolute` is positioned relative to its\nnearest positioned ancestor. A \"positioned\" ancestor has a position\nvalue other than static (the default).\nIf no such ancestor exists, the element will be positioned relative to\nthe initial containing block, which is usually the <html> element.\n\nThe `LensEmbeddableComponent` root div was with a `position:static` by\ndefault, causing the absolute positioned badge/user message icon to be\npositioned in the nearest positioned ancestor.\n\nFix https://github.com/elastic/kibana/issues/189344\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6eec63d5f186d827ef7d6952ee5c78c7ea78c6ae"}}]}] BACKPORT--> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> |
||
Davis McPhee
|
7a9ec17b95
|
[8.18] Revert "[ES|QL] Fix CSV report time range when exporting from Discover (#216792)" (#223249) (#223343)
# Backport This will backport the following commits from `main` to `8.18`: - [Revert "[ES|QL] Fix CSV report time range when exporting from Discover (#216792)" (#223249)](https://github.com/elastic/kibana/pull/223249) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-06-11T02:57:09Z","message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [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)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:DataDiscovery","backport:version","v9.1.0","v8.19.0","v9.0.3","v8.18.3"],"title":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\"","number":223249,"url":"https://github.com/elastic/kibana/pull/223249","mergeCommit":{"message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [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)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b"}},"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/223249","number":223249,"mergeCommit":{"message":"Revert \"[ES|QL] Fix CSV report time range when exporting from Discover (#216792)\" (#223249)\n\n## Summary\n\nThis reverts commit 6a0c173b1ad6152ee75bc2e74dfd71e74fa6b54a.\n\nFixes #223171.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [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)","sha":"9b18d391b119477624e6fcaec5059e0c641f341b"}},{"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
|
970bc4bf7a
|
[8.18] Update dependency blurhash to ^2.0.5 (main) (#219584) (#223330)
# Backport This will backport the following commits from `main` to `8.18`: - [Update dependency blurhash to ^2.0.5 (main) (#219584)](https://github.com/elastic/kibana/pull/219584) <!--- 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-10T23:39:46Z","message":"Update dependency blurhash to ^2.0.5 (main) (#219584)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [blurhash](https://blurha.sh/)\n([source](https://redirect.github.com/woltapp/blurhash/tree/HEAD/TypeScript))\n| dependencies | patch | [`^2.0.1` ->\n`^2.0.5`](https://renovatebot.com/diffs/npm/blurhash/2.0.1/2.0.5) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>woltapp/blurhash (blurhash)</summary>\n\n###\n[`v2.0.4`]( |
||
|
Kibana Machine
|
93df0744c1
|
[8.18] Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582) (#223323)
# Backport This will backport the following commits from `main` to `8.18`: - [Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)](https://github.com/elastic/kibana/pull/219582) <!--- 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-10T23:20:00Z","message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\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🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\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>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18","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 dependency @types/deep-freeze-strict to ^1.1.2 (main)","number":219582,"url":"https://github.com/elastic/kibana/pull/219582","mergeCommit":{"message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\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🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\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>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18"}},"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/219582","number":219582,"mergeCommit":{"message":"Update dependency @types/deep-freeze-strict to ^1.1.2 (main) (#219582)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[@types/deep-freeze-strict](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/deep-freeze-strict)\n([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/deep-freeze-strict))\n| devDependencies | patch | [`^1.1.0` ->\n`^1.1.2`](https://renovatebot.com/diffs/npm/@types%2fdeep-freeze-strict/1.1.0/1.1.2)\n|\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🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\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>","sha":"0711625608d76f193f72dbfe73849ae8949bfd18"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
f3c822494f
|
[8.18] Update TTFMP documentation for meta fields. (#221807) (#223315)
# Backport This will backport the following commits from `main` to `8.18`: - [Update TTFMP documentation for meta fields. (#221807)](https://github.com/elastic/kibana/pull/221807) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-06-10T22:14:05Z","message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.18.0","v9.1.0","v8.19.0"],"title":"Update TTFMP documentation for meta fields.","number":221807,"url":"https://github.com/elastic/kibana/pull/221807","mergeCommit":{"message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1"}},"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/221807","number":221807,"mergeCommit":{"message":"Update TTFMP documentation for meta fields. (#221807)\n\nEnhances the performance metrics documentation by explaining how\nto use the `meta.description` field for contextualizing render time\nevents and how to track subsequent page or section loads using\n`onPageRefreshStart`.\n\n\n- Added a section describing the default meaning of render time and how\nto provide a custom `description` in the `meta` field of `onPageReady`\nfor more precise event context.\n- Documented the use of `onPageRefreshStart` to distinguish between\ninitial loads and subsequent refreshes, clarifying that\n`meta.isInitialLoad` is set to `false` for refreshes and `true` by\ndefault.\n- Included code examples and sample indexed event structures for both\nfeatures.","sha":"ca05a06f00e013a18198cb46ce051d64f0d3f4b1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com> |
||
|
Kibana Machine
|
1d816dfa41
|
[8.18] Update papaparse (main) (manual) (#220930) (#223266)
# Backport This will backport the following commits from `main` to `8.18`: - [Update papaparse (main) (manual) (#220930)](https://github.com/elastic/kibana/pull/220930) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-10T16:46:29Z","message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","backport:version","v9.1.0","v8.19.0","v8.17.7","v8.18.2","v9.0.2"],"title":"Update papaparse (main) (manual)","number":220930,"url":"https://github.com/elastic/kibana/pull/220930","mergeCommit":{"message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","8.17","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220930","number":220930,"mergeCommit":{"message":"Update papaparse (main) (manual) (#220930)\n\n## Summary\n\nManual version of https://github.com/elastic/kibana/pull/206182 due to\nbreaking type changes in papaparse\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"ea71069d09d1b802bf29e4d113ff75d022f30789"}},{"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: Marshall Main <55718608+marshallmain@users.noreply.github.com> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |