mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 08:19:33 -04:00
84502 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
2fd6274d4d
|
[9.0] [ML] Anomaly Explorer: Prevent crash on anomaly table filter (#213075) (#213499)
# Backport This will backport the following commits from `main` to `9.0`: - [[ML] Anomaly Explorer: Prevent crash on anomaly table filter (#213075)](https://github.com/elastic/kibana/pull/213075) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T23:18:49Z","message":"[ML] Anomaly Explorer: Prevent crash on anomaly table filter (#213075)\n\nFix for: https://github.com/elastic/kibana/issues/212569\nFrom what I found, the issue was with the `useUrlStateService` after\nchanges introduced in https://github.com/elastic/kibana/pull/203224,\nwhich made the service more generic.\n\nWhen filtering causes the `explorer` to remount the `AnomaliesTable`,\npagination state updates are triggered before the effect that sets\n`setCallback.current` executes.\n\nInitializing the ref with `setState` ensures its availability from the\nfirst render.\n\n\nhttps://github.com/user-attachments/assets/d1aa8409-56e5-4632-a5f2-82350b877db6","sha":"0210468548e3d3c68f1ffbeba196ebfe418b0c4e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","v9.0.0","Team:ML","backport:version","v8.18.0","v9.1.0"],"title":"[ML] Anomaly Explorer: Prevent crash on anomaly table filter","number":213075,"url":"https://github.com/elastic/kibana/pull/213075","mergeCommit":{"message":"[ML] Anomaly Explorer: Prevent crash on anomaly table filter (#213075)\n\nFix for: https://github.com/elastic/kibana/issues/212569\nFrom what I found, the issue was with the `useUrlStateService` after\nchanges introduced in https://github.com/elastic/kibana/pull/203224,\nwhich made the service more generic.\n\nWhen filtering causes the `explorer` to remount the `AnomaliesTable`,\npagination state updates are triggered before the effect that sets\n`setCallback.current` executes.\n\nInitializing the ref with `setState` ensures its availability from the\nfirst render.\n\n\nhttps://github.com/user-attachments/assets/d1aa8409-56e5-4632-a5f2-82350b877db6","sha":"0210468548e3d3c68f1ffbeba196ebfe418b0c4e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/213075","number":213075,"mergeCommit":{"message":"[ML] Anomaly Explorer: Prevent crash on anomaly table filter (#213075)\n\nFix for: https://github.com/elastic/kibana/issues/212569\nFrom what I found, the issue was with the `useUrlStateService` after\nchanges introduced in https://github.com/elastic/kibana/pull/203224,\nwhich made the service more generic.\n\nWhen filtering causes the `explorer` to remount the `AnomaliesTable`,\npagination state updates are triggered before the effect that sets\n`setCallback.current` executes.\n\nInitializing the ref with `setState` ensures its availability from the\nfirst render.\n\n\nhttps://github.com/user-attachments/assets/d1aa8409-56e5-4632-a5f2-82350b877db6","sha":"0210468548e3d3c68f1ffbeba196ebfe418b0c4e"}}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
Kibana Machine
|
fe7df8fbe3 | skip failing test suite (#213300) | ||
|
Kibana Machine
|
d2ec0ee20d
|
[9.0] [Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343) (#213488)
# Backport This will backport the following commits from `main` to `9.0`: - [[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)](https://github.com/elastic/kibana/pull/211343) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T21:09:22Z","message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[Bug][Security Solution] - Reliably persist dataview selections for timeline","number":211343,"url":"https://github.com/elastic/kibana/pull/211343","mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211343","number":211343,"mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> |
||
|
Kibana Machine
|
cead958f53
|
[9.0] [Stack Connectors] Add organizationId and projectId OpenAI headers, along with arbitrary headers (#213117) (#213478)
# Backport This will backport the following commits from `main` to `9.0`: - [[Stack Connectors] Add `organizationId` and `projectId` OpenAI headers, along with arbitrary headers (#213117)](https://github.com/elastic/kibana/pull/213117) <!--- Backport version: 9.6.6 --> ### 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-03-06T19:59:15Z","message":"[Stack Connectors] Add `organizationId` and `projectId` OpenAI headers, along with arbitrary headers (#213117)","sha":"1531849d6f14574dcb16e03e17b8e285f91833f3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Stack Connectors] Add `organizationId` and `projectId` OpenAI headers, along with arbitrary headers","number":213117,"url":"https://github.com/elastic/kibana/pull/213117","mergeCommit":{"message":"[Stack Connectors] Add `organizationId` and `projectId` OpenAI headers, along with arbitrary headers (#213117)","sha":"1531849d6f14574dcb16e03e17b8e285f91833f3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213117","number":213117,"mergeCommit":{"message":"[Stack Connectors] Add `organizationId` and `projectId` OpenAI headers, along with arbitrary headers (#213117)","sha":"1531849d6f14574dcb16e03e17b8e285f91833f3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
404708c4af
|
[9.0] [Logs] using All logs dataview in LOGS_LOCATOR (#211549) (#213485)
# Backport This will backport the following commits from `main` to `9.0`: - [[Logs] using All logs dataview in LOGS_LOCATOR (#211549)](https://github.com/elastic/kibana/pull/211549) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yngrid Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T20:38:00Z","message":"[Logs] using All logs dataview in LOGS_LOCATOR (#211549)\n\nCloses https://github.com/elastic/kibana/issues/209122.\n\n### 🎥 Demo\n\n\nhttps://github.com/user-attachments/assets/34d8b544-3ff6-4332-8856-57014fb1fc8a\n\n### How to test?\n1. Ingest some data using `logs_and_metrics` synthtrace scenario\n2. Go to `/app/observability/overview` or `app/metrics/hosts`\n3. Click `logs` link\n4. You should be redirected to discover and `All logs` should be set by\ndefault\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"989cf1ec3489784bd5dd13185111115a28c83980","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","Team:obs-ux-logs","v8.18.0","v9.1.0","v8.19.0"],"title":"[Logs] using All logs dataview in LOGS_LOCATOR","number":211549,"url":"https://github.com/elastic/kibana/pull/211549","mergeCommit":{"message":"[Logs] using All logs dataview in LOGS_LOCATOR (#211549)\n\nCloses https://github.com/elastic/kibana/issues/209122.\n\n### 🎥 Demo\n\n\nhttps://github.com/user-attachments/assets/34d8b544-3ff6-4332-8856-57014fb1fc8a\n\n### How to test?\n1. Ingest some data using `logs_and_metrics` synthtrace scenario\n2. Go to `/app/observability/overview` or `app/metrics/hosts`\n3. Click `logs` link\n4. You should be redirected to discover and `All logs` should be set by\ndefault\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"989cf1ec3489784bd5dd13185111115a28c83980"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211549","number":211549,"mergeCommit":{"message":"[Logs] using All logs dataview in LOGS_LOCATOR (#211549)\n\nCloses https://github.com/elastic/kibana/issues/209122.\n\n### 🎥 Demo\n\n\nhttps://github.com/user-attachments/assets/34d8b544-3ff6-4332-8856-57014fb1fc8a\n\n### How to test?\n1. Ingest some data using `logs_and_metrics` synthtrace scenario\n2. Go to `/app/observability/overview` or `app/metrics/hosts`\n3. Click `logs` link\n4. You should be redirected to discover and `All logs` should be set by\ndefault\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"989cf1ec3489784bd5dd13185111115a28c83980"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yngrid Coello <yngrid.coello@elastic.co> |
||
Philippe Oberti
|
c45a259898
|
[9.0] [Security Solution][Threat Intelligence] - fix Cypress tests (#209195) (#213471)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Threat Intelligence] - fix Cypress tests (#209195)](https://github.com/elastic/kibana/pull/209195) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T15:03:32Z","message":"[Security Solution][Threat Intelligence] - fix Cypress tests (#209195)\n\n## Summary\r\n\r\nThis PR fixes the few Threat Intelligence Cypress tests which started\r\nfailing recently.\r\n\r\n[This PR]( |
||
Steph Milovic
|
3d1411a795
|
[9.0] [Security AI Assistant] Bedrock prompt updates (#213160) (#213479)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security AI Assistant] Bedrock prompt updates (#213160)](https://github.com/elastic/kibana/pull/213160) <!--- Backport version: 9.6.6 --> ### 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-03-06T19:58:26Z","message":"[Security AI Assistant] Bedrock prompt updates (#213160)","sha":"5b8fd8f5c79c492b46493861f3e74795558927f7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security AI Assistant] Bedrock prompt updates","number":213160,"url":"https://github.com/elastic/kibana/pull/213160","mergeCommit":{"message":"[Security AI Assistant] Bedrock prompt updates (#213160)","sha":"5b8fd8f5c79c492b46493861f3e74795558927f7"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/213160","number":213160,"mergeCommit":{"message":"[Security AI Assistant] Bedrock prompt updates (#213160)","sha":"5b8fd8f5c79c492b46493861f3e74795558927f7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213475","number":213475,"state":"OPEN"}]}] BACKPORT--> |
||
Georgii Gorbachev
|
7aef4654a0
|
[9.0] [Security Solution] Account for missing base rule versions in is_customized calculation (#213250) (#213466)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)](https://github.com/elastic/kibana/pull/213250) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T18:22:17Z","message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Account for missing base rule versions in is_customized calculation","number":213250,"url":"https://github.com/elastic/kibana/pull/213250","mergeCommit":{"message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"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,"url":"https://github.com/elastic/kibana/pull/213460","number":213460,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213250","number":213250,"mergeCommit":{"message":"[Security Solution] Account for missing base rule versions in is_customized calculation (#213250)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/210358**\n\n## Summary\n\n### Editing of prebuilt rules with missing base versions\n\n**When the base version** of a currently installed prebuilt rule **is missing** among the `security-rule` asset saved objects, and the user edits this rule:\n\n- We should mark the rule as customized, only if the new rule settings are different from the current rule settings.\n - For example, adding a new tag should mark the rule as customized. Then, if the user removes this tag, the rule should remain to be marked as customized. This matches the current behavior.\n - However, if the user saves the rule without making any changes to it, it should keep its `is_customized` field as is. This is different from the current behavior.\n\n### Importing of prebuilt rules with missing base versions\n\n**When the base version** of a prebuilt rule that is being imported **is missing** among the `security-rule` asset saved objects, and the user imports this rule:\n\n- If this rule is not installed, it should be created with `is_customized` field set to `false`.\n- If this rule is already installed, it should be updated.\n - Its `is_customized` field should be set to `true` if the rule from the import payload is not equal to the installed rule.\n - Its `is_customized` field should be be kept unchanged (`false` or `true`) if the rule from the import payload is equal to the installed rule.","sha":"87e7cd94d1d649596dc0f23bf4cf730704fb4845"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213462","number":213462,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co> |
||
|
Kibana Machine
|
bbf06ab26d
|
[9.0] [Obs-UX-Mgmt] Split Up SLO Details from Overview (#212826) (#213452)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs-UX-Mgmt] Split Up SLO Details from Overview (#212826)](https://github.com/elastic/kibana/pull/212826) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T17:43:57Z","message":"[Obs-UX-Mgmt] Split Up SLO Details from Overview (#212826)\n\n## Summary \n\nIn an effort to make SLI charts more quickly visible on the SLO overview\npage, remove SLO details that do not give users valuable insight into\nkey metrics and add them to a new tab. Retain some of the SLO details\nabove the tabs like SLI value, tags, and description (see figma for the\ninspiration)\n\n\nhttps://www.figma.com/design/91R0OtRZHy5xvaE8dGStBo/SLO%2FSLI-assets?node-id=4601-59103&t=K1vI6qtXbb48XPgr-1\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-28 at 4 53 05 PM\"\nsrc=\"https://github.com/user-attachments/assets/3fdbe766-4047-45b5-a986-3a029c09bd1f\"\n/>\n\n\n\n\n## Release Notes\n\nSLO overview should give users a clear, immediate picture into key\nobjective data. Previously, the user would have had to scroll past\nstatic data that describes the SLO definition before seeing valuable\ninformation about their SLIs. This static data has been moved to a\nseparate tab, making charts more easily accessible.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"34fa3135a2b7ebd5e6792e9362a4cd4b7c7a5145","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","backport:prev-minor","Spacetime","Team:obs-ux-management","v9.1.0"],"title":"[Obs-UX-Mgmt] Split Up SLO Details from Overview","number":212826,"url":"https://github.com/elastic/kibana/pull/212826","mergeCommit":{"message":"[Obs-UX-Mgmt] Split Up SLO Details from Overview (#212826)\n\n## Summary \n\nIn an effort to make SLI charts more quickly visible on the SLO overview\npage, remove SLO details that do not give users valuable insight into\nkey metrics and add them to a new tab. Retain some of the SLO details\nabove the tabs like SLI value, tags, and description (see figma for the\ninspiration)\n\n\nhttps://www.figma.com/design/91R0OtRZHy5xvaE8dGStBo/SLO%2FSLI-assets?node-id=4601-59103&t=K1vI6qtXbb48XPgr-1\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-28 at 4 53 05 PM\"\nsrc=\"https://github.com/user-attachments/assets/3fdbe766-4047-45b5-a986-3a029c09bd1f\"\n/>\n\n\n\n\n## Release Notes\n\nSLO overview should give users a clear, immediate picture into key\nobjective data. Previously, the user would have had to scroll past\nstatic data that describes the SLO definition before seeing valuable\ninformation about their SLIs. This static data has been moved to a\nseparate tab, making charts more easily accessible.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"34fa3135a2b7ebd5e6792e9362a4cd4b7c7a5145"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212826","number":212826,"mergeCommit":{"message":"[Obs-UX-Mgmt] Split Up SLO Details from Overview (#212826)\n\n## Summary \n\nIn an effort to make SLI charts more quickly visible on the SLO overview\npage, remove SLO details that do not give users valuable insight into\nkey metrics and add them to a new tab. Retain some of the SLO details\nabove the tabs like SLI value, tags, and description (see figma for the\ninspiration)\n\n\nhttps://www.figma.com/design/91R0OtRZHy5xvaE8dGStBo/SLO%2FSLI-assets?node-id=4601-59103&t=K1vI6qtXbb48XPgr-1\n\n<img width=\"1474\" alt=\"Screenshot 2025-02-28 at 4 53 05 PM\"\nsrc=\"https://github.com/user-attachments/assets/3fdbe766-4047-45b5-a986-3a029c09bd1f\"\n/>\n\n\n\n\n## Release Notes\n\nSLO overview should give users a clear, immediate picture into key\nobjective data. Previously, the user would have had to scroll past\nstatic data that describes the SLO definition before seeing valuable\ninformation about their SLIs. This static data has been moved to a\nseparate tab, making charts more easily accessible.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"34fa3135a2b7ebd5e6792e9362a4cd4b7c7a5145"}}]}] BACKPORT--> Co-authored-by: Bailey Cash <bailey.cash@elastic.co> |
||
|
Kibana Machine
|
5edf2d1b32
|
[9.0] [Security Solution] Allow bulk upgrade rules with solvable conflicts (#213285) (#213450)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Allow bulk upgrade rules with solvable conflicts (#213285)](https://github.com/elastic/kibana/pull/213285) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T17:39:58Z","message":"[Security Solution] Allow bulk upgrade rules with solvable conflicts (#213285)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/210358\n\n## Summary\n \nThis PR implements functionality allowing users to bulk upgrade rules with solvable conflicts.\n\n## Details\n\nThe main focus of this PR is to allow users to bulk upgrade rules with solvable conflicts. To achieve that the following was done\n\n- `upgrade/_perform` dry run functionality was extended to take into account rule upgrade specifiers with resolved value\n- `upgrade/_perform`'s `on_conflict` param was extended with `UPGRADE_SOLVABLE` to allow bulk upgrading rules with solvable conflicts\n- UI logic updated accordingly to display rule upgrade modal when users have to make a choice to upgrade only rules without conflicts or upgrade also rules with solvable conflicts\n- conflict state badges were added to the rule upgrade table\n\nIt includes changes from https://github.com/elastic/kibana/pull/213027 with some modifications.\n\n## Screenshots\n\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 04\" src=\"https://github.com/user-attachments/assets/b786e813-268d-49a2-80cc-81fa95d14e85\" />\n<img width=\"1724\" alt=\"Screenshot 2025-03-06 at 12 13 30\" src=\"https://github.com/user-attachments/assets/e5e38bd9-78a3-4026-a7ea-892bd7153938\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 51\" src=\"https://github.com/user-attachments/assets/d58872c3-f197-49ad-b4f3-5f45fb1efac2\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 14 04\" src=\"https://github.com/user-attachments/assets/667a6ab2-2fdb-430d-9589-1c4a6e5cdc8b\" />\n<img width=\"1722\" alt=\"Screenshot 2025-03-06 at 12 14 17\" src=\"https://github.com/user-attachments/assets/07f4cffe-4398-4fd5-8350-a3a2978d7dcd\" />","sha":"f2077dbb3108833e76a2f1834a76c3266e22f2ac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Allow bulk upgrade rules with solvable conflicts","number":213285,"url":"https://github.com/elastic/kibana/pull/213285","mergeCommit":{"message":"[Security Solution] Allow bulk upgrade rules with solvable conflicts (#213285)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/210358\n\n## Summary\n \nThis PR implements functionality allowing users to bulk upgrade rules with solvable conflicts.\n\n## Details\n\nThe main focus of this PR is to allow users to bulk upgrade rules with solvable conflicts. To achieve that the following was done\n\n- `upgrade/_perform` dry run functionality was extended to take into account rule upgrade specifiers with resolved value\n- `upgrade/_perform`'s `on_conflict` param was extended with `UPGRADE_SOLVABLE` to allow bulk upgrading rules with solvable conflicts\n- UI logic updated accordingly to display rule upgrade modal when users have to make a choice to upgrade only rules without conflicts or upgrade also rules with solvable conflicts\n- conflict state badges were added to the rule upgrade table\n\nIt includes changes from https://github.com/elastic/kibana/pull/213027 with some modifications.\n\n## Screenshots\n\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 04\" src=\"https://github.com/user-attachments/assets/b786e813-268d-49a2-80cc-81fa95d14e85\" />\n<img width=\"1724\" alt=\"Screenshot 2025-03-06 at 12 13 30\" src=\"https://github.com/user-attachments/assets/e5e38bd9-78a3-4026-a7ea-892bd7153938\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 51\" src=\"https://github.com/user-attachments/assets/d58872c3-f197-49ad-b4f3-5f45fb1efac2\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 14 04\" src=\"https://github.com/user-attachments/assets/667a6ab2-2fdb-430d-9589-1c4a6e5cdc8b\" />\n<img width=\"1722\" alt=\"Screenshot 2025-03-06 at 12 14 17\" src=\"https://github.com/user-attachments/assets/07f4cffe-4398-4fd5-8350-a3a2978d7dcd\" />","sha":"f2077dbb3108833e76a2f1834a76c3266e22f2ac"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213285","number":213285,"mergeCommit":{"message":"[Security Solution] Allow bulk upgrade rules with solvable conflicts (#213285)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/210358\n\n## Summary\n \nThis PR implements functionality allowing users to bulk upgrade rules with solvable conflicts.\n\n## Details\n\nThe main focus of this PR is to allow users to bulk upgrade rules with solvable conflicts. To achieve that the following was done\n\n- `upgrade/_perform` dry run functionality was extended to take into account rule upgrade specifiers with resolved value\n- `upgrade/_perform`'s `on_conflict` param was extended with `UPGRADE_SOLVABLE` to allow bulk upgrading rules with solvable conflicts\n- UI logic updated accordingly to display rule upgrade modal when users have to make a choice to upgrade only rules without conflicts or upgrade also rules with solvable conflicts\n- conflict state badges were added to the rule upgrade table\n\nIt includes changes from https://github.com/elastic/kibana/pull/213027 with some modifications.\n\n## Screenshots\n\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 04\" src=\"https://github.com/user-attachments/assets/b786e813-268d-49a2-80cc-81fa95d14e85\" />\n<img width=\"1724\" alt=\"Screenshot 2025-03-06 at 12 13 30\" src=\"https://github.com/user-attachments/assets/e5e38bd9-78a3-4026-a7ea-892bd7153938\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 13 51\" src=\"https://github.com/user-attachments/assets/d58872c3-f197-49ad-b4f3-5f45fb1efac2\" />\n<img width=\"1723\" alt=\"Screenshot 2025-03-06 at 12 14 04\" src=\"https://github.com/user-attachments/assets/667a6ab2-2fdb-430d-9589-1c4a6e5cdc8b\" />\n<img width=\"1722\" alt=\"Screenshot 2025-03-06 at 12 14 17\" src=\"https://github.com/user-attachments/assets/07f4cffe-4398-4fd5-8350-a3a2978d7dcd\" />","sha":"f2077dbb3108833e76a2f1834a76c3266e22f2ac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
e6f796c6ee
|
[9.0] [scout] improve logs readability by using unique logger context per playwright worker (#213218) (#213447)
# Backport This will backport the following commits from `main` to `9.0`: - [[scout] improve logs readability by using unique logger context per playwright worker (#213218)](https://github.com/elastic/kibana/pull/213218) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T17:36:11Z","message":"[scout] improve logs readability by using unique logger context per playwright worker (#213218)\n\n## Summary\n\nPart of #203591\n\nOur current logs are confusing as it is unclear to which worker message\nis related. E.g.\n\n```\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n```\n\nit is not clear if the messages are coming from the same worker or 2\ndifferent ones.\n\nBefore\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout] Requesting url (redacted): [http://localhost:5620/s/test-space-0/internal/kibana/settings]\n debg [scout] scoutSpace:test-space-0 'uiSettings.setDefaultTime' took 116.66ms\n...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n succ [scout] import success\n debg [scout] scoutSpace:test-space-1 'savedObjects.load' took 1028.17ms\n ...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'editor'\n debg [scout] [service] scoutPage:test-space-1\n debg [scout] [service] pageObjects:test-space-1\n```\n\n\nAfter:\n\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout-worker-1] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout-worker-1] Requesting url (redacted): [http://localhost:5620/s/test-space-1/internal/kibana/settings]\n debg [scout-worker-1] test-space-1: 'uiSettings.setDefaultTime' took 131.30ms\n...\n debg [scout-worker-1] [browserAuth] loaded\n debg [scout-worker-1] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n debg [scout-worker-2] test-space-2: 'savedObjects.load' took 1005.91ms\n...\n debg [scout-worker-2] [browserAuth] loaded\n debg [scout-worker-2] Creating new local SAML session for role 'editor'\n debg [scout-worker-2] [scoutPage] loaded\n debg [scout-worker-2] [pageObjects] loaded\n```\n\n**Note**: single thread run will log under `[scout-worker]` context\n\nHow to verify:\n\n1) start servers - `node scripts/scout.js start-server --stateful`\n2) run tests - `npx playwright test --config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d958fa97e4a2343d0747c2d198d3f605239676f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] improve logs readability by using unique logger context per playwright worker","number":213218,"url":"https://github.com/elastic/kibana/pull/213218","mergeCommit":{"message":"[scout] improve logs readability by using unique logger context per playwright worker (#213218)\n\n## Summary\n\nPart of #203591\n\nOur current logs are confusing as it is unclear to which worker message\nis related. E.g.\n\n```\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n```\n\nit is not clear if the messages are coming from the same worker or 2\ndifferent ones.\n\nBefore\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout] Requesting url (redacted): [http://localhost:5620/s/test-space-0/internal/kibana/settings]\n debg [scout] scoutSpace:test-space-0 'uiSettings.setDefaultTime' took 116.66ms\n...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n succ [scout] import success\n debg [scout] scoutSpace:test-space-1 'savedObjects.load' took 1028.17ms\n ...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'editor'\n debg [scout] [service] scoutPage:test-space-1\n debg [scout] [service] pageObjects:test-space-1\n```\n\n\nAfter:\n\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout-worker-1] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout-worker-1] Requesting url (redacted): [http://localhost:5620/s/test-space-1/internal/kibana/settings]\n debg [scout-worker-1] test-space-1: 'uiSettings.setDefaultTime' took 131.30ms\n...\n debg [scout-worker-1] [browserAuth] loaded\n debg [scout-worker-1] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n debg [scout-worker-2] test-space-2: 'savedObjects.load' took 1005.91ms\n...\n debg [scout-worker-2] [browserAuth] loaded\n debg [scout-worker-2] Creating new local SAML session for role 'editor'\n debg [scout-worker-2] [scoutPage] loaded\n debg [scout-worker-2] [pageObjects] loaded\n```\n\n**Note**: single thread run will log under `[scout-worker]` context\n\nHow to verify:\n\n1) start servers - `node scripts/scout.js start-server --stateful`\n2) run tests - `npx playwright test --config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d958fa97e4a2343d0747c2d198d3f605239676f0"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213218","number":213218,"mergeCommit":{"message":"[scout] improve logs readability by using unique logger context per playwright worker (#213218)\n\n## Summary\n\nPart of #203591\n\nOur current logs are confusing as it is unclear to which worker message\nis related. E.g.\n\n```\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n proc [playwright] debg [scout] Creating new local SAML session for role 'admin'\n```\n\nit is not clear if the messages are coming from the same worker or 2\ndifferent ones.\n\nBefore\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout] Requesting url (redacted): [http://localhost:5620/s/test-space-0/internal/kibana/settings]\n debg [scout] scoutSpace:test-space-0 'uiSettings.setDefaultTime' took 116.66ms\n...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n succ [scout] import success\n debg [scout] scoutSpace:test-space-1 'savedObjects.load' took 1028.17ms\n ...\n debg [scout] [service] browserAuth\n debg [scout] Creating new local SAML session for role 'editor'\n debg [scout] [service] scoutPage:test-space-1\n debg [scout] [service] pageObjects:test-space-1\n```\n\n\nAfter:\n\n```\n[chromium] › error_handling.spec.ts:30:12 › Discover app - errors › should render invalid scripted field error @ess\n debg [scout-worker-1] applying update to kibana config: {\"timepicker:timeDefaults\":\"{ \\\"from\\\": \\\"2015-09-19T06:31:44.000Z\\\", \\\"to\\\": \\\"2015-09-23T18:31:44.000Z\\\"}\"}\n debg [scout-worker-1] Requesting url (redacted): [http://localhost:5620/s/test-space-1/internal/kibana/settings]\n debg [scout-worker-1] test-space-1: 'uiSettings.setDefaultTime' took 131.30ms\n...\n debg [scout-worker-1] [browserAuth] loaded\n debg [scout-worker-1] Creating new local SAML session for role 'viewer'\n[chromium] › saved_searches.spec.ts:66:14 › Discover app - saved searches › should customize time range on dashboards @ess @svlSearch @svlOblt\n debg [scout-worker-2] test-space-2: 'savedObjects.load' took 1005.91ms\n...\n debg [scout-worker-2] [browserAuth] loaded\n debg [scout-worker-2] Creating new local SAML session for role 'editor'\n debg [scout-worker-2] [scoutPage] loaded\n debg [scout-worker-2] [pageObjects] loaded\n```\n\n**Note**: single thread run will log under `[scout-worker]` context\n\nHow to verify:\n\n1) start servers - `node scripts/scout.js start-server --stateful`\n2) run tests - `npx playwright test --config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts`\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d958fa97e4a2343d0747c2d198d3f605239676f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Kibana Machine
|
3db6edbd1b
|
[9.0] [Security Solution] Allow prebuilt rules import and export (#212509) (#213421)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Allow prebuilt rules import and export (#212509)](https://github.com/elastic/kibana/pull/212509) <!--- 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-03-06T15:58:33Z","message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","Feature:Rule Import/Export","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Allow prebuilt rules import and export","number":212509,"url":"https://github.com/elastic/kibana/pull/212509","mergeCommit":{"message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212509","number":212509,"mergeCommit":{"message":"[Security Solution] Allow prebuilt rules import and export (#212509)\n\n**Resolves: https://github.com/elastic/security-team/issues/11502**\n(internal)\n\nThis PR implements following changes and adds API integration tests for\nthem:\n- [x] Users with any license can export prebuilt rules (with enabled\nfeature flag)\n- [x] Users with Basic/Essentials license can import prebuilt rules only\nif they are non-customized and the feature flag is enabled\n- [x] Users with Enterprise/Complete license can import prebuilt rules\nwithout restrictions\n\nFlaky test runner (had to create 4 separate runs to test all configs):\n-\n[1](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7987)\n-\n[2](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7986)\n-\n[3](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7988)\n-\n[4](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7989)","sha":"ebe90e5c80e1dbe34d96ccd8a1e8e34d032affa4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
ad401c50c3
|
[9.0] [SLOs] Allow slo query wild card filters !! (#213119) (#213432)
# Backport This will backport the following commits from `main` to `9.0`: - [[SLOs] Allow slo query wild card filters !! (#213119)](https://github.com/elastic/kibana/pull/213119) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-06T16:45:23Z","message":"[SLOs] Allow slo query wild card filters !! (#213119)\n\n## Summary\n\nAllow slo query wild card filters when kql filter and dsl filter both\nare used.\n\nFor KQL filter, allowLeadingWildcards was true by default. introduces\nthe ability to use wildcard filters in SLO queries when DSL filters are\nalso used.\n\n### Changes Made\n1. **Updated `getElasticsearchQueryOrThrow` function:**\n- Added support for `dataView` parameter in the `toElasticsearchQuery`\nfunction.\n - Included additional options for `allowLeadingWildcards`.\n- Enhanced error handling to differentiate between invalid KQL and KQL\nqueries with invalid filters.\n\n2. **Test Coverage:**\n- Added new test cases to cover scenarios with wildcard queries and\nfilters.","sha":"33f51f6d6e01638116b6201215f5f2589fc291c6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v9.1.0"],"title":"[SLOs] Allow slo query wild card filters !!","number":213119,"url":"https://github.com/elastic/kibana/pull/213119","mergeCommit":{"message":"[SLOs] Allow slo query wild card filters !! (#213119)\n\n## Summary\n\nAllow slo query wild card filters when kql filter and dsl filter both\nare used.\n\nFor KQL filter, allowLeadingWildcards was true by default. introduces\nthe ability to use wildcard filters in SLO queries when DSL filters are\nalso used.\n\n### Changes Made\n1. **Updated `getElasticsearchQueryOrThrow` function:**\n- Added support for `dataView` parameter in the `toElasticsearchQuery`\nfunction.\n - Included additional options for `allowLeadingWildcards`.\n- Enhanced error handling to differentiate between invalid KQL and KQL\nqueries with invalid filters.\n\n2. **Test Coverage:**\n- Added new test cases to cover scenarios with wildcard queries and\nfilters.","sha":"33f51f6d6e01638116b6201215f5f2589fc291c6"}},"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/213119","number":213119,"mergeCommit":{"message":"[SLOs] Allow slo query wild card filters !! (#213119)\n\n## Summary\n\nAllow slo query wild card filters when kql filter and dsl filter both\nare used.\n\nFor KQL filter, allowLeadingWildcards was true by default. introduces\nthe ability to use wildcard filters in SLO queries when DSL filters are\nalso used.\n\n### Changes Made\n1. **Updated `getElasticsearchQueryOrThrow` function:**\n- Added support for `dataView` parameter in the `toElasticsearchQuery`\nfunction.\n - Included additional options for `allowLeadingWildcards`.\n- Enhanced error handling to differentiate between invalid KQL and KQL\nqueries with invalid filters.\n\n2. **Test Coverage:**\n- Added new test cases to cover scenarios with wildcard queries and\nfilters.","sha":"33f51f6d6e01638116b6201215f5f2589fc291c6"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
19bca50081
|
[9.0] Update dependency msw to ~2.7.3 (main) (#212976) (#213429)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency msw to ~2.7.3 (main) (#212976)](https://github.com/elastic/kibana/pull/212976) <!--- 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-03-06T16:28:40Z","message":"Update dependency msw to ~2.7.3 (main) (#212976)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [msw](https://mswjs.io)\n([source](https://redirect.github.com/mswjs/msw)) | devDependencies |\npatch | [`~2.7.2` ->\n`~2.7.3`](https://renovatebot.com/diffs/npm/msw/2.7.3/2.7.3) |\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":"a9ed518545291d9a7e5dcd17641f633d3997f04b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:all-open","v9.1.0"],"title":"Update dependency msw to ~2.7.3 (main)","number":212976,"url":"https://github.com/elastic/kibana/pull/212976","mergeCommit":{"message":"Update dependency msw to ~2.7.3 (main) (#212976)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [msw](https://mswjs.io)\n([source](https://redirect.github.com/mswjs/msw)) | devDependencies |\npatch | [`~2.7.2` ->\n`~2.7.3`](https://renovatebot.com/diffs/npm/msw/2.7.3/2.7.3) |\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":"a9ed518545291d9a7e5dcd17641f633d3997f04b"}},"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/212976","number":212976,"mergeCommit":{"message":"Update dependency msw to ~2.7.3 (main) (#212976)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [msw](https://mswjs.io)\n([source](https://redirect.github.com/mswjs/msw)) | devDependencies |\npatch | [`~2.7.2` ->\n`~2.7.3`](https://renovatebot.com/diffs/npm/msw/2.7.3/2.7.3) |\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":"a9ed518545291d9a7e5dcd17641f633d3997f04b"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
e03a86b4bd
|
[9.0] [docs] Fix external links (#213437) (#213451)
# Backport This will backport the following commits from `main` to `9.0`: - [[docs] Fix external links (#213437)](https://github.com/elastic/kibana/pull/213437) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Colleen McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T17:42:56Z","message":"[docs] Fix external links (#213437)\n\nFix external links that incorrectly use `.md` instead of `.html`.","sha":"65a41a6b966ab7448927deb0ac25022d58de2e3f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","documentation","backport:version","v9.1.0"],"title":"[docs] Fix external links","number":213437,"url":"https://github.com/elastic/kibana/pull/213437","mergeCommit":{"message":"[docs] Fix external links (#213437)\n\nFix external links that incorrectly use `.md` instead of `.html`.","sha":"65a41a6b966ab7448927deb0ac25022d58de2e3f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213437","number":213437,"mergeCommit":{"message":"[docs] Fix external links (#213437)\n\nFix external links that incorrectly use `.md` instead of `.html`.","sha":"65a41a6b966ab7448927deb0ac25022d58de2e3f"}}]}] BACKPORT--> Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co> |
||
elastic-renovate-prod[bot]
|
df7fd8f7a4
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 6dcddd8 (9.0) (#213339)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `15a4191` -> `6dcddd8` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
a01e0d097f
|
[9.0] [Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial (#212807) (#213415)
# Backport This will backport the following commits from `main` to `9.0`: - [[Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial (#212807)](https://github.com/elastic/kibana/pull/212807) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nick Peihl","email":"nick.peihl@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T15:14:19Z","message":"[Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial (#212807)\n\n## Summary\n\nAdds to the Dev Docs Debugging tutorial suggested configurations for VS\nCode users for debugging Kibana server code, Jest unit tests, and\nfunctional tests.\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- [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":"d2412a5f98f341cf59e02e7340d718493d0492e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","DevDocs","backport:prev-minor","v9.1.0"],"title":"[Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial","number":212807,"url":"https://github.com/elastic/kibana/pull/212807","mergeCommit":{"message":"[Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial (#212807)\n\n## Summary\n\nAdds to the Dev Docs Debugging tutorial suggested configurations for VS\nCode users for debugging Kibana server code, Jest unit tests, and\nfunctional tests.\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- [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":"d2412a5f98f341cf59e02e7340d718493d0492e7"}},"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/212807","number":212807,"mergeCommit":{"message":"[Dev Docs] Add VS Code configurations to Dev Docs Debugging Tutorial (#212807)\n\n## Summary\n\nAdds to the Dev Docs Debugging tutorial suggested configurations for VS\nCode users for debugging Kibana server code, Jest unit tests, and\nfunctional tests.\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- [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":"d2412a5f98f341cf59e02e7340d718493d0492e7"}},{"url":"https://github.com/elastic/kibana/pull/213410","number":213410,"branch":"8.16","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/213411","number":213411,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/213412","number":213412,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/213413","number":213413,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Nick Peihl <nick.peihl@elastic.co> |
||
Shahzad
|
ec0da627b2
|
[9.0] [Synthetics] Fix tls alert data !! (#212758) (#213315)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Fix tls alert data !! (#212758)](https://github.com/elastic/kibana/pull/212758) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-05T18:40:04Z","message":"[Synthetics] Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and fixes the TLS alert data handling in the Synthetics\nplugin. Key updates include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added `agent.name`.\n- Changed optional chaining to direct property access for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n - Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added fields: `monitorName`, `monitorId`, `monitorType`, `locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3. **Observer Codec**:\n - Ensured `name` and `geo.name` are required fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to `MonitorType`.\n - Moved `@timestamp` to required fields in `PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and `getTLSAlertDocument` so that we can\nproperly generate alert document","sha":"80f4aab305eb90646f418bc704423308d133d7d2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0"],"title":"[Synthetics] Fix tls alert data !!","number":212758,"url":"https://github.com/elastic/kibana/pull/212758","mergeCommit":{"message":"[Synthetics] Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and fixes the TLS alert data handling in the Synthetics\nplugin. Key updates include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added `agent.name`.\n- Changed optional chaining to direct property access for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n - Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added fields: `monitorName`, `monitorId`, `monitorType`, `locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3. **Observer Codec**:\n - Ensured `name` and `geo.name` are required fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to `MonitorType`.\n - Moved `@timestamp` to required fields in `PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and `getTLSAlertDocument` so that we can\nproperly generate alert document","sha":"80f4aab305eb90646f418bc704423308d133d7d2"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/212758","number":212758,"mergeCommit":{"message":"[Synthetics] Fix tls alert data !! (#212758)\n\n### Summary\nThis PR improves and fixes the TLS alert data handling in the Synthetics\nplugin. Key updates include:\n\n\n### Code changes\n\n1. **Request Body Updates**:\n - Added `agent.name`.\n- Changed optional chaining to direct property access for\n`ping.monitor.name`, `ping.monitor.id`, and `ping.observer.name`.\n - Added `ping.agent.name`.\n\n2. **Cert Type Adjustments**:\n- Added fields: `monitorName`, `monitorId`, `monitorType`, `locationId`,\n`locationName`, `@timestamp`, `hostName`.\n\n3. **Observer Codec**:\n - Ensured `name` and `geo.name` are required fields.\n\n4. **Monitor Type and Ping Type**:\n - Added `name` to `MonitorType`.\n - Moved `@timestamp` to required fields in `PingType`.\n\n7. **Message Utils**:\n- Adjusted `getCertSummary` and `getTLSAlertDocument` so that we can\nproperly generate alert document","sha":"80f4aab305eb90646f418bc704423308d133d7d2"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
9ccdbfdc31
|
[9.0] [Fleet] unskip test (#213365) (#213404)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] unskip test (#213365)](https://github.com/elastic/kibana/pull/213365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T14:20:39Z","message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] unskip test","number":213365,"url":"https://github.com/elastic/kibana/pull/213365","mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213365","number":213365,"mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
de6eb8c2a5
|
[9.0] [Fleet] fix fleet proxies test (#213350) (#213394)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] fix fleet proxies test (#213350)](https://github.com/elastic/kibana/pull/213350) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T13:40:35Z","message":"[Fleet] fix fleet proxies test (#213350)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/207024\nCloses https://github.com/elastic/kibana/issues/207022\n\nIncreased retries since the bump agent policies were made async and\ntakes longer than before.","sha":"5010d1f0fa52e28085f03fb1f6e03004586eaab1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[Fleet] fix fleet proxies test","number":213350,"url":"https://github.com/elastic/kibana/pull/213350","mergeCommit":{"message":"[Fleet] fix fleet proxies test (#213350)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/207024\nCloses https://github.com/elastic/kibana/issues/207022\n\nIncreased retries since the bump agent policies were made async and\ntakes longer than before.","sha":"5010d1f0fa52e28085f03fb1f6e03004586eaab1"}},"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/213350","number":213350,"mergeCommit":{"message":"[Fleet] fix fleet proxies test (#213350)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/207024\nCloses https://github.com/elastic/kibana/issues/207022\n\nIncreased retries since the bump agent policies were made async and\ntakes longer than before.","sha":"5010d1f0fa52e28085f03fb1f6e03004586eaab1"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
a5aa01c4f3
|
[9.0] [ML] Anomaly Explorer: Fix incorrect overall swim lane height in Anomaly Explorer (#213245) (#213386)
# Backport This will backport the following commits from `main` to `9.0`: - [[ML] Anomaly Explorer: Fix incorrect overall swim lane height in Anomaly Explorer (#213245)](https://github.com/elastic/kibana/pull/213245) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T13:33:20Z","message":"[ML] Anomaly Explorer: Fix incorrect overall swim lane height in Anomaly Explorer (#213245)\n\nFix for: https://github.com/elastic/kibana/issues/211017\n\nWe were using legacy theme which introduced some margins to the chart.\nHowever, the issue is visible from `69.1.0` (introduced in Kibana `9.0`)\nversion of `@elastic/charts` as they have fixed heatmap margins and\npaddings - https://github.com/elastic/elastic-charts/issues/2577.\n\nAfter the fix:\n\n (#213381)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search] Removing elastic managed connectors misleading content (#213335)](https://github.com/elastic/kibana/pull/213335) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2025-03-06T13:24:11Z","message":"[Search] Removing elastic managed connectors misleading content (#213335)\n\n## Summary\n\nFixing misleading info noted in this GH issue ticket\nhttps://github.com/elastic/search-team/issues/9483 regarding Elastic\nmanaged connectors that are not available in Serverless\n\n\nConnectors empty state page:\n\n\n\nConnectors list page (without the Callout banner on top):\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c67a239e457b9c6a78c65d48658f2d69e9e20e1b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"[Search] Removing elastic managed connectors misleading content","number":213335,"url":"https://github.com/elastic/kibana/pull/213335","mergeCommit":{"message":"[Search] Removing elastic managed connectors misleading content (#213335)\n\n## Summary\n\nFixing misleading info noted in this GH issue ticket\nhttps://github.com/elastic/search-team/issues/9483 regarding Elastic\nmanaged connectors that are not available in Serverless\n\n\nConnectors empty state page:\n\n\n\nConnectors list page (without the Callout banner on top):\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c67a239e457b9c6a78c65d48658f2d69e9e20e1b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213335","number":213335,"mergeCommit":{"message":"[Search] Removing elastic managed connectors misleading content (#213335)\n\n## Summary\n\nFixing misleading info noted in this GH issue ticket\nhttps://github.com/elastic/search-team/issues/9483 regarding Elastic\nmanaged connectors that are not available in Serverless\n\n\nConnectors empty state page:\n\n\n\nConnectors list page (without the Callout banner on top):\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c67a239e457b9c6a78c65d48658f2d69e9e20e1b"}}]}] BACKPORT--> Co-authored-by: José Luis González <joseluisgj@gmail.com> |
||
|
Kibana Machine
|
19f4e47711
|
[9.0] [ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822) (#213374)
# Backport This will backport the following commits from `main` to `9.0`: - [[ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822)](https://github.com/elastic/kibana/pull/211822) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T12:52:44Z","message":"[ObsUX] [APM] [OTel] Runtime metrics show dashboards with different ingest path (#211822)\n\nCloses #211783\nPart of https://github.com/elastic/kibana/issues/195857\n\n## Summary\n\nThis PR expands the logic to get the dashboard files based on the agent.\nWe have many different ways to ingest data so we want to add more\nmetrics dashboards to the APM metrics tab. The different ingest paths we\nhave:\nClassic APM Agent --> APM Server --> ES\nVanilla OTel SDKs --> APM Server --> ES\nEDOT OTel SDKs --> APM Server --> ES\nClassic APM Agent --> EDOT Collector --> ES\nVanilla OTel SDKs. --> EDOT Collector --> ES\nEDOT OTel SDKs --> EDOT Collector --> ES\nWe agreed on having a dashboard filename pattern to make showing the\ncorrect dashboard easier described\n[here](https://github.com/elastic/kibana/issues/195857#issue-2580733648)\n\nFirst, we determine if the ingest path is through APM Server or EDOT\nCollector by checking the `telemtry.sdk` fields.\n\n## TODOs / Reviewer notes\n- [ ] Currently, we have a fallback to metrics charts which is valid\nonly if we have APM agent so this PR adds an empty state message:\n\"Runtime metrics are not available for this Agent / SDK type.\" in case\nthere is no dashboard for the service language. To be improved in\nhttps://github.com/elastic/kibana/issues/211774 and will be updated in\nthis PR when ready - I will still open it for review as the other logic\ncan be reviewed\n- The dashboards are to be updated (by the agent team so not part of the\nchanges here)\n\n## Testing: \n- Using e2e PoC \n- The available dashboard cases can be found in\n[loadDashboardFile]( |
||
|
Kibana Machine
|
ab00e34c1c
|
[9.0] Upgrade EUI to v100.0.0 (#213292) (#213369)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade EUI to v100.0.0 (#213292)](https://github.com/elastic/kibana/pull/213292) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tomasz Kajtoch","email":"tomasz.kajtoch@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T12:28:21Z","message":"Upgrade EUI to v100.0.0 (#213292)\n\n`99.4.0-borealis.0` ⏩ `100.0.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n---\n\nFirst of all, 💯 🎉!\n\n> [!Warning]\n> Please note that the [public changelog for EUI\nv100.0.0](https://github.com/elastic/eui/releases/tag/v100.0.0) is\nlonger than what's included below.\n>\n> Kibana has been using Borealis-specific builds of EUI since November\nlast year (suffixed with `-borealis.X`), which were built from a\njust-merged EUI feature branch.\n> Since that feature branch just got merged and released with EUI\nv100.0.0, **the public changelog differs from what Kibana should be\nconcerned about** due to updating from a custom Borealis-enabled version\nof EUI.\n>\n> You can find the list of all (one 👀) changes made between version\n`99.4.0-borealis.0` and `100.0.0` below.\n\n## [`v100.0.0`](https://github.com/elastic/eui/releases/v100.0.0)\n\n**Bug fixes**\n\n- Fixed `EuiComboBox` by cleaning duplicated values when having a\ndelimiter prop. ([#8335](https://github.com/elastic/eui/pull/8335))\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"18fa931a2651f933cc3ebf26109a1fc22fb1ea3a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:cloud-deploy","ci:project-deploy-observability","v9.1.0"],"title":"Upgrade EUI to v100.0.0","number":213292,"url":"https://github.com/elastic/kibana/pull/213292","mergeCommit":{"message":"Upgrade EUI to v100.0.0 (#213292)\n\n`99.4.0-borealis.0` ⏩ `100.0.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n---\n\nFirst of all, 💯 🎉!\n\n> [!Warning]\n> Please note that the [public changelog for EUI\nv100.0.0](https://github.com/elastic/eui/releases/tag/v100.0.0) is\nlonger than what's included below.\n>\n> Kibana has been using Borealis-specific builds of EUI since November\nlast year (suffixed with `-borealis.X`), which were built from a\njust-merged EUI feature branch.\n> Since that feature branch just got merged and released with EUI\nv100.0.0, **the public changelog differs from what Kibana should be\nconcerned about** due to updating from a custom Borealis-enabled version\nof EUI.\n>\n> You can find the list of all (one 👀) changes made between version\n`99.4.0-borealis.0` and `100.0.0` below.\n\n## [`v100.0.0`](https://github.com/elastic/eui/releases/v100.0.0)\n\n**Bug fixes**\n\n- Fixed `EuiComboBox` by cleaning duplicated values when having a\ndelimiter prop. ([#8335](https://github.com/elastic/eui/pull/8335))\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"18fa931a2651f933cc3ebf26109a1fc22fb1ea3a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213292","number":213292,"mergeCommit":{"message":"Upgrade EUI to v100.0.0 (#213292)\n\n`99.4.0-borealis.0` ⏩ `100.0.0`\n\n[Questions? Please see our Kibana upgrade\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)\n\n---\n\nFirst of all, 💯 🎉!\n\n> [!Warning]\n> Please note that the [public changelog for EUI\nv100.0.0](https://github.com/elastic/eui/releases/tag/v100.0.0) is\nlonger than what's included below.\n>\n> Kibana has been using Borealis-specific builds of EUI since November\nlast year (suffixed with `-borealis.X`), which were built from a\njust-merged EUI feature branch.\n> Since that feature branch just got merged and released with EUI\nv100.0.0, **the public changelog differs from what Kibana should be\nconcerned about** due to updating from a custom Borealis-enabled version\nof EUI.\n>\n> You can find the list of all (one 👀) changes made between version\n`99.4.0-borealis.0` and `100.0.0` below.\n\n## [`v100.0.0`](https://github.com/elastic/eui/releases/v100.0.0)\n\n**Bug fixes**\n\n- Fixed `EuiComboBox` by cleaning duplicated values when having a\ndelimiter prop. ([#8335](https://github.com/elastic/eui/pull/8335))\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"18fa931a2651f933cc3ebf26109a1fc22fb1ea3a"}}]}] BACKPORT--> Co-authored-by: Tomasz Kajtoch <tomasz.kajtoch@elastic.co> |
||
|
Kibana Machine
|
fd4c5b0604
|
[9.0] [Siem Migrations] GET /integrations integration Test (#213251) (#213358)
# Backport This will backport the following commits from `main` to `9.0`: - [[Siem Migrations] `GET /integrations` integration Test (#213251)](https://github.com/elastic/kibana/pull/213251) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T11:19:28Z","message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migrations] `GET /integrations` integration Test","number":213251,"url":"https://github.com/elastic/kibana/pull/213251","mergeCommit":{"message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213251","number":213251,"mergeCommit":{"message":"[Siem Migrations] `GET /integrations` integration Test (#213251)\n\n## Summary\n\nAdds a smoke test for `GET /integrations` endpoint.\n\nHandles\n\n- https://github.com/elastic/security-team/issues/11232","sha":"60a9ac4f45b042884268387e5c34288e175057db"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
Pablo Machado
|
e2ad570025
|
[9.0] [SecuritySolution] Fix risk engine component template renaming (#212853) (#213330)
# Backport This will backport the following commits from `8.18` to `9.0`: - [[SecuritySolution] Fix risk engine component template renaming (#212853)](https://github.com/elastic/kibana/pull/212853) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T09:50:31Z","message":"[SecuritySolution] Fix risk engine component template renaming (#212853)\n\n## Summary\n\nThe previous implementation tried to rename the index template during\n`init` and did not consider multiple spaces. to fix it, I have:\n* Delete the previous code from `init`\n* Created a new migration that created the new component templates and\nupdated the index templates\n* Deleted the old component template after all spaces migration ran\n* Add support for multiple spaces\n* I also renamed a function inside `init` to make the code more clear\n* Added error handling code that concatenates error messages and logs\nall of them at the end\n\n\n### How to test it:\n\n**Scenario 1**\n\n* The usual way to desk test this PR would be\n* Create a cluster with 8.17\n* Enable the risk Engine in 8.17\n* Create a new space in 8.17\n* Upgrade the cluster to 8.18 (this branch)\n* Enable the risk engine in the second space.\n\n**Scenario 2**\n* Create a cluster with 8.17\n* Enable the risk engine\n* Create a space\n* Enable another risk engine\n* Create another space\n* Upgrade the cluster to 8.18 (this branch)\n* Check if the migration ran in the logs\n* Check if all risk engines are installed and the index templates and\nindex components are there.\n* Install a new risk engine in the space where it isn't installed.\n* Restart Kibana and make sure the migrations didn't run a second time\n\n### Checklist\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- [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### Identify risks\n\n[ ] This PR needs to be tested for upgrades between different versions\nand a diverse number of spaces and risk engines installed\n\n---------\n\nCo-authored-by: abhishekbhatia1710 <abhishek.bhatia@elastic.co>","sha":"b7908a4c6f91c79459f7b509bfd444ad169d6770","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","Team: SecuritySolution","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution] Fix risk engine component template renaming","number":212853,"url":"https://github.com/elastic/kibana/pull/212853","mergeCommit":{"message":"[SecuritySolution] Fix risk engine component template renaming (#212853)\n\n## Summary\n\nThe previous implementation tried to rename the index template during\n`init` and did not consider multiple spaces. to fix it, I have:\n* Delete the previous code from `init`\n* Created a new migration that created the new component templates and\nupdated the index templates\n* Deleted the old component template after all spaces migration ran\n* Add support for multiple spaces\n* I also renamed a function inside `init` to make the code more clear\n* Added error handling code that concatenates error messages and logs\nall of them at the end\n\n\n### How to test it:\n\n**Scenario 1**\n\n* The usual way to desk test this PR would be\n* Create a cluster with 8.17\n* Enable the risk Engine in 8.17\n* Create a new space in 8.17\n* Upgrade the cluster to 8.18 (this branch)\n* Enable the risk engine in the second space.\n\n**Scenario 2**\n* Create a cluster with 8.17\n* Enable the risk engine\n* Create a space\n* Enable another risk engine\n* Create another space\n* Upgrade the cluster to 8.18 (this branch)\n* Check if the migration ran in the logs\n* Check if all risk engines are installed and the index templates and\nindex components are there.\n* Install a new risk engine in the space where it isn't installed.\n* Restart Kibana and make sure the migrations didn't run a second time\n\n### Checklist\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- [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### Identify risks\n\n[ ] This PR needs to be tested for upgrades between different versions\nand a diverse number of spaces and risk engines installed\n\n---------\n\nCo-authored-by: abhishekbhatia1710 <abhishek.bhatia@elastic.co>","sha":"b7908a4c6f91c79459f7b509bfd444ad169d6770"}},"sourceBranch":"8.18","suggestedTargetBranches":["9.0","main","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212853","number":212853,"mergeCommit":{"message":"[SecuritySolution] Fix risk engine component template renaming (#212853)\n\n## Summary\n\nThe previous implementation tried to rename the index template during\n`init` and did not consider multiple spaces. to fix it, I have:\n* Delete the previous code from `init`\n* Created a new migration that created the new component templates and\nupdated the index templates\n* Deleted the old component template after all spaces migration ran\n* Add support for multiple spaces\n* I also renamed a function inside `init` to make the code more clear\n* Added error handling code that concatenates error messages and logs\nall of them at the end\n\n\n### How to test it:\n\n**Scenario 1**\n\n* The usual way to desk test this PR would be\n* Create a cluster with 8.17\n* Enable the risk Engine in 8.17\n* Create a new space in 8.17\n* Upgrade the cluster to 8.18 (this branch)\n* Enable the risk engine in the second space.\n\n**Scenario 2**\n* Create a cluster with 8.17\n* Enable the risk engine\n* Create a space\n* Enable another risk engine\n* Create another space\n* Upgrade the cluster to 8.18 (this branch)\n* Check if the migration ran in the logs\n* Check if all risk engines are installed and the index templates and\nindex components are there.\n* Install a new risk engine in the space where it isn't installed.\n* Restart Kibana and make sure the migrations didn't run a second time\n\n### Checklist\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- [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### Identify risks\n\n[ ] This PR needs to be tested for upgrades between different versions\nand a diverse number of spaces and risk engines installed\n\n---------\n\nCo-authored-by: abhishekbhatia1710 <abhishek.bhatia@elastic.co>","sha":"b7908a4c6f91c79459f7b509bfd444ad169d6770"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ef99401f1a
|
[9.0] [Synthetics] Fix monitor status rule for empty kql query results !! (#208922) (#213326)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Fix monitor status rule for empty kql query results !! (#208922)](https://github.com/elastic/kibana/pull/208922) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-01-31T17:45:41Z","message":"[Synthetics] Fix monitor status rule for empty kql query results !! (#208922)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/208915 !!\n\nFix monitor status rule for empty kql query results !!\n\n1. Made sure if kql filter return no configs ids, rule break early to\nnot cover all monitors\n\n### Testing\n\nCreate a synthetics rule with a kql filter which matches no monitors and\nmake sure rule doesn't trigger for other down monitors in the system\n<img width=\"661\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed0b3a1f-e8d1-4e22-a77d-1237ce557ac5\"\n/>\n\n\n### Before\n\nCreate a rule and you can observe that rule would get triggered for all\nmonitors down in the system with matching condition criteria","sha":"5c350b4492afaf04cdc103ce237fc579224e652d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v8.18.0","v8.17.2","v9.1.0","v8.19.0"],"title":"[Synthetics] Fix monitor status rule for empty kql query results !!","number":208922,"url":"https://github.com/elastic/kibana/pull/208922","mergeCommit":{"message":"[Synthetics] Fix monitor status rule for empty kql query results !! (#208922)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/208915 !!\n\nFix monitor status rule for empty kql query results !!\n\n1. Made sure if kql filter return no configs ids, rule break early to\nnot cover all monitors\n\n### Testing\n\nCreate a synthetics rule with a kql filter which matches no monitors and\nmake sure rule doesn't trigger for other down monitors in the system\n<img width=\"661\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed0b3a1f-e8d1-4e22-a77d-1237ce557ac5\"\n/>\n\n\n### Before\n\nCreate a rule and you can observe that rule would get triggered for all\nmonitors down in the system with matching condition criteria","sha":"5c350b4492afaf04cdc103ce237fc579224e652d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209155","number":209155,"state":"MERGED","mergeCommit":{"sha":"db7d058f44bcb14d5c729a7665c524ea4794cf9b","message":"[8.18] [Synthetics] Fix monitor status rule for empty kql query results !! (#208922) (#209155)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Synthetics] Fix monitor status rule for empty kql query results !!\n(#208922)](https://github.com/elastic/kibana/pull/208922)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209265","number":209265,"state":"MERGED","mergeCommit":{"sha":"9d2b22f8ac982f175d7971c165270e6c1a880ed6","message":"[8.17] [Synthetics] Fix monitor status rule for empty kql query results !! (#208922) (#209265)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Synthetics] Fix monitor status rule for empty kql query results !!\n(#208922)](https://github.com/elastic/kibana/pull/208922)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\\n\\n### Questions ?\\nPlease refer to the\n[Backport\ntool\\ndocumentation](https://github.com/sqren/backport)\\n\\n\\n\\nCo-authored-by:\nShahzad\n<shahzad31comp@gmail.com>\"}},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/208922\",\"number\":208922,\"mergeCommit\":{\"message\":\"[Synthetics]\nFix monitor status rule for empty kql query results !! (#208922)\\n\\n##\nSummary\\n\\nFixes https://github.com/elastic/kibana/issues/208915\n!!\\n\\nFix monitor status rule for empty kql query results !!\\n\\n1. Made\nsure if kql filter return no configs ids, rule break early to\\nnot cover\nall monitors\\n\\n### Testing\\n\\nCreate a synthetics rule with a kql\nfilter which matches no monitors and\\nmake sure rule doesn't trigger for\nother down monitors in the system\\n<img width=\\\"661\\\"\nalt=\\\"image\\\"\\nsrc=\\\"https://github.com/user-attachments/assets/ed0b3a1f-e8d1-4e22-a77d-1237ce557ac5\\\"\\n/>\\n\\n\\n###\nBefore\\n\\nCreate a rule and you can observe that rule would get\ntriggered for all\\nmonitors down in the system with matching condition\ncriteria\",\"sha\":\"5c350b4492afaf04cdc103ce237fc579224e652d\"}},{\"url\":\"https://github.com/elastic/kibana/pull/209156\",\"number\":209156,\"branch\":\"8.x\",\"state\":\"OPEN\"}]}]\nBACKPORT-->"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208922","number":208922,"mergeCommit":{"message":"[Synthetics] Fix monitor status rule for empty kql query results !! (#208922)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/208915 !!\n\nFix monitor status rule for empty kql query results !!\n\n1. Made sure if kql filter return no configs ids, rule break early to\nnot cover all monitors\n\n### Testing\n\nCreate a synthetics rule with a kql filter which matches no monitors and\nmake sure rule doesn't trigger for other down monitors in the system\n<img width=\"661\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ed0b3a1f-e8d1-4e22-a77d-1237ce557ac5\"\n/>\n\n\n### Before\n\nCreate a rule and you can observe that rule would get triggered for all\nmonitors down in the system with matching condition criteria","sha":"5c350b4492afaf04cdc103ce237fc579224e652d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209156","number":209156,"state":"MERGED","mergeCommit":{"sha":"d3a3c3c4b2f9b51554262509269fa13b679bc249","message":"[8.x] [Synthetics] Fix monitor status rule for empty kql query results !! (#208922) (#209156)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Synthetics] Fix monitor status rule for empty kql query results !!\n(#208922)](https://github.com/elastic/kibana/pull/208922)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
465ffd6599
|
[9.0] [ES|QL] Fixes some problems with numeric control values (#213204) (#213314)
# Backport This will backport the following commits from `main` to `9.0`: - [[ES|QL] Fixes some problems with numeric control values (#213204)](https://github.com/elastic/kibana/pull/213204) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T07:02:21Z","message":"[ES|QL] Fixes some problems with numeric control values (#213204)\n\n## Summary\n\nES|QL doesnt have sometimes the ability to compare a numeric field with\na string when this string is a numeric value. For example:\n\n```\nFROM kibana_sample_data_logs | WHERE bytes > \"6193\"\n```\n\nThis is going to fail, the value should be numeric to work as expected.\nFor this reason controls that have numeric values do not work correctly.\nThis PR is fixing this","sha":"bf84c2aaddd7ed3d3d36bff4793ebf05a1715445","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fixes some problems with numeric control values","number":213204,"url":"https://github.com/elastic/kibana/pull/213204","mergeCommit":{"message":"[ES|QL] Fixes some problems with numeric control values (#213204)\n\n## Summary\n\nES|QL doesnt have sometimes the ability to compare a numeric field with\na string when this string is a numeric value. For example:\n\n```\nFROM kibana_sample_data_logs | WHERE bytes > \"6193\"\n```\n\nThis is going to fail, the value should be numeric to work as expected.\nFor this reason controls that have numeric values do not work correctly.\nThis PR is fixing this","sha":"bf84c2aaddd7ed3d3d36bff4793ebf05a1715445"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213204","number":213204,"mergeCommit":{"message":"[ES|QL] Fixes some problems with numeric control values (#213204)\n\n## Summary\n\nES|QL doesnt have sometimes the ability to compare a numeric field with\na string when this string is a numeric value. For example:\n\n```\nFROM kibana_sample_data_logs | WHERE bytes > \"6193\"\n```\n\nThis is going to fail, the value should be numeric to work as expected.\nFor this reason controls that have numeric values do not work correctly.\nThis PR is fixing this","sha":"bf84c2aaddd7ed3d3d36bff4793ebf05a1715445"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
863c23861c
|
[9.0] Fix wrong permission key for dashboard in analytics overview (#213295) (#213299)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix wrong permission key for dashboard in analytics overview (#213295)](https://github.com/elastic/kibana/pull/213295) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T00:17:35Z","message":"Fix wrong permission key for dashboard in analytics overview (#213295)\n\n## Summary\n\nThis PR fixes a bug introduced in #213198 - wrong capability name was\nbeing used.\n\nRelated to the fix from https://github.com/elastic/kibana/issues/212171","sha":"e73fd1fd839ea924935988179a9a61fe00b59e4d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:SharedUX","backport:prev-minor","v9.1.0"],"title":"Fix wrong permission key for dashboard in analytics overview","number":213295,"url":"https://github.com/elastic/kibana/pull/213295","mergeCommit":{"message":"Fix wrong permission key for dashboard in analytics overview (#213295)\n\n## Summary\n\nThis PR fixes a bug introduced in #213198 - wrong capability name was\nbeing used.\n\nRelated to the fix from https://github.com/elastic/kibana/issues/212171","sha":"e73fd1fd839ea924935988179a9a61fe00b59e4d"}},"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/213295","number":213295,"mergeCommit":{"message":"Fix wrong permission key for dashboard in analytics overview (#213295)\n\n## Summary\n\nThis PR fixes a bug introduced in #213198 - wrong capability name was\nbeing used.\n\nRelated to the fix from https://github.com/elastic/kibana/issues/212171","sha":"e73fd1fd839ea924935988179a9a61fe00b59e4d"}}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
e441962a67
|
[9.0] [Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862) (#213234)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)](https://github.com/elastic/kibana/pull/211862) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T12:14:31Z","message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\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 guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules","number":211862,"url":"https://github.com/elastic/kibana/pull/211862","mergeCommit":{"message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\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 guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211862","number":211862,"mergeCommit":{"message":"[Security Solution] Add UI incentivizers to upgrade prebuilt rules (#211862)\n\n## Summary\n\nPartially addresses https://github.com/elastic/kibana/issues/210358\n\nAdds all callouts and logic to incentivize users to upgrade their rules asap. These include:\n\n- [x] Showing a callout on the Rule Management page\n- [x] Showing a callout on the Rule Details page\n - [x] Letting users open the Rule Upgrade flyout from the Rule Details page\n- [x] Showing a callout on the Rule Editing page\n- [x] Showing a callout in the Rule Upgrade flyout if rule has missing base version\n\nThis PR also adds related updates to the rule diff algorithms in order to facilitate an easier upgrade experience when rules have missing base versions. These include:\n\n- [x] When the rule has a missing base version and is NOT marked as customized:\n - [x] We should return all the target fields from the diff algorithm as NO_CONFLICT\n- [x] When the rule has a missing base version and is marked as customized:\n - [x] We should attempt to merge all non-functional mergeable fields (any field that doesn't have consequences with how the rule runs e.g. tags) and return them as `SOLVABLE_CONFLICT`.\n - **NOTE**: When base versions are missing and the rule is customized, we attempt to merge all mergable, non-functional rule fields. These include all fields covered by the scalar diff array (`tags`, `references`, `new_terms_fields`, `threat_index`). We typically also consider multi-line string fields as mergeable but without three versions of the string, we are currently unable to merge the strings together, so we just return target version.\n - [x] We should pick the target version for all functional mergeable fields (e.g. `index`) and non-mergeable fields and return them as `SOLVABLE_CONFLICT`.\n\n\n### Screenshots\n\n\n**Callout on Rule details page w/ flyout button**\n\n\n---\n\n**Upgrade flyout now accessible from rule details page**\n\n\n---\n\n**Callout on rule editing page**\n\n\n---\n\n**Dismissible callout on rule management page**\n\n\n---\n\n**Callout in rule upgrade flyout when rule has missing base version**\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 guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"461787bea6a48cc2c55514843adedc9ca5bb5032"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
0b7887efd7
|
[9.0] [Unified search] Change codeowners to presentation team (#212855) (#213284)
# Backport This will backport the following commits from `main` to `9.0`: - [[Unified search] Change codeowners to presentation team (#212855)](https://github.com/elastic/kibana/pull/212855) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T20:18:10Z","message":"[Unified search] Change codeowners to presentation team (#212855)\n\n## Summary\n\nUnified Search belongs to presentations team so I'm changing the\ncodeowners entry. There was a [previous\nattempt](https://github.com/elastic/kibana/pull/208381/files) of doing\nthe same thing, but the auto-commit kicked in and reverted the change\nfor unified_search plugin, since we forgot to add the entry\nin`kibana.jsonc`.","sha":"e9f852ecc3fca4ff8b0049da350ecabf69b803ab","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","Team:Visualizations","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"[Unified search] Change codeowners to presentation team","number":212855,"url":"https://github.com/elastic/kibana/pull/212855","mergeCommit":{"message":"[Unified search] Change codeowners to presentation team (#212855)\n\n## Summary\n\nUnified Search belongs to presentations team so I'm changing the\ncodeowners entry. There was a [previous\nattempt](https://github.com/elastic/kibana/pull/208381/files) of doing\nthe same thing, but the auto-commit kicked in and reverted the change\nfor unified_search plugin, since we forgot to add the entry\nin`kibana.jsonc`.","sha":"e9f852ecc3fca4ff8b0049da350ecabf69b803ab"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212855","number":212855,"mergeCommit":{"message":"[Unified search] Change codeowners to presentation team (#212855)\n\n## Summary\n\nUnified Search belongs to presentations team so I'm changing the\ncodeowners entry. There was a [previous\nattempt](https://github.com/elastic/kibana/pull/208381/files) of doing\nthe same thing, but the auto-commit kicked in and reverted the change\nfor unified_search plugin, since we forgot to add the entry\nin`kibana.jsonc`.","sha":"e9f852ecc3fca4ff8b0049da350ecabf69b803ab"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> |
||
|
Kibana Machine
|
ab49592d2a
|
[9.0] Set from & to as optional args in @kbn/grouping (#213212) (#213265)
# Backport This will backport the following commits from `main` to `9.0`: - [Set from & to as optional args in @kbn/grouping (#213212)](https://github.com/elastic/kibana/pull/213212) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alberto Blázquez","email":"albertoblaz@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T16:21:54Z","message":"Set from & to as optional args in @kbn/grouping (#213212)\n\n## Summary\n\nSet `from` and `to` as optional args in `getGroupingQuery`, a function\nexposed by `@kbn/grouping`.\n\nIt will unblock this PR:\n- https://github.com/elastic/kibana/pull/212955\n\n### Motivation \n\n`getGroupingQuery` returns an ES aggregation for grouping documents.\nThis function assumes data will be queried in a certain interval of\ntime. However, Asset Inventory needs to query data from the beginning of\ntime because the UI will not provide any time-range filter. So in order\nto reuse this logic, we need to set both args as optional.\n\nReason for wrapping both fields in an optional `timeRange` record is to\nhave either both present or both undefined, not only one of them\npresent.\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- [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- [x] 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- [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### Risks\n\nNo risk at all. It would be a breaking change otherwise, if we had to\nrequire args that were optional before.","sha":"af147b5cc6612bc9e5632c2004f868f8c2b2a7f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:prev-minor","v9.1.0"],"title":"Set from & to as optional args in @kbn/grouping","number":213212,"url":"https://github.com/elastic/kibana/pull/213212","mergeCommit":{"message":"Set from & to as optional args in @kbn/grouping (#213212)\n\n## Summary\n\nSet `from` and `to` as optional args in `getGroupingQuery`, a function\nexposed by `@kbn/grouping`.\n\nIt will unblock this PR:\n- https://github.com/elastic/kibana/pull/212955\n\n### Motivation \n\n`getGroupingQuery` returns an ES aggregation for grouping documents.\nThis function assumes data will be queried in a certain interval of\ntime. However, Asset Inventory needs to query data from the beginning of\ntime because the UI will not provide any time-range filter. So in order\nto reuse this logic, we need to set both args as optional.\n\nReason for wrapping both fields in an optional `timeRange` record is to\nhave either both present or both undefined, not only one of them\npresent.\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- [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- [x] 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- [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### Risks\n\nNo risk at all. It would be a breaking change otherwise, if we had to\nrequire args that were optional before.","sha":"af147b5cc6612bc9e5632c2004f868f8c2b2a7f9"}},"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/213212","number":213212,"mergeCommit":{"message":"Set from & to as optional args in @kbn/grouping (#213212)\n\n## Summary\n\nSet `from` and `to` as optional args in `getGroupingQuery`, a function\nexposed by `@kbn/grouping`.\n\nIt will unblock this PR:\n- https://github.com/elastic/kibana/pull/212955\n\n### Motivation \n\n`getGroupingQuery` returns an ES aggregation for grouping documents.\nThis function assumes data will be queried in a certain interval of\ntime. However, Asset Inventory needs to query data from the beginning of\ntime because the UI will not provide any time-range filter. So in order\nto reuse this logic, we need to set both args as optional.\n\nReason for wrapping both fields in an optional `timeRange` record is to\nhave either both present or both undefined, not only one of them\npresent.\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- [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- [x] 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- [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### Risks\n\nNo risk at all. It would be a breaking change otherwise, if we had to\nrequire args that were optional before.","sha":"af147b5cc6612bc9e5632c2004f868f8c2b2a7f9"}}]}] BACKPORT--> Co-authored-by: Alberto Blázquez <albertoblaz@users.noreply.github.com> |
||
|
Kibana Machine
|
9bb526a47c
|
[9.0] [Siem Migrations] Translated Rules Upsell Page (#212777) (#213253)
# Backport This will backport the following commits from `main` to `9.0`: - [[Siem Migrations] Translated Rules Upsell Page (#212777)](https://github.com/elastic/kibana/pull/212777) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T14:53:26Z","message":"[Siem Migrations] Translated Rules Upsell Page (#212777)\n\n## Summary\n\nThis PR adds the Upsell for `Translated Rules` Page as per\n[design](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=oJug1zebtufPlNKM-0).\n\n\nBelow is the Demo for the same.\n\n|Instance|Demo|\n|---|---|\n|ESS|<video\nsrc=\" |
||
|
Kibana Machine
|
f62e695b59
|
[9.0] [Siem Migration] - Start/Stop Translation integration tests (#212030) (#213221)
# Backport This will backport the following commits from `main` to `9.0`: - [[Siem Migration] - Start/Stop Translation integration tests (#212030)](https://github.com/elastic/kibana/pull/212030) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T11:06:06Z","message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migration] - Start/Stop Translation integration tests","number":212030,"url":"https://github.com/elastic/kibana/pull/212030","mergeCommit":{"message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212030","number":212030,"mergeCommit":{"message":"[Siem Migration] - Start/Stop Translation integration tests (#212030)\n\n## Summary\n\nHandles\n- https://github.com/elastic/security-team/issues/11232\n\nThis PR adds the integration tests for \n- Start Translation API\n- Stop Translation API","sha":"4998b75677557f4781b94bd58cf04eae118943d6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
|
Kibana Machine
|
3bf69b05cf
|
[9.0] Hide main analytics applications on overview page if unavailable (#213198) (#213248)
# Backport This will backport the following commits from `main` to `9.0`: - [Hide main analytics applications on overview page if unavailable (#213198)](https://github.com/elastic/kibana/pull/213198) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T14:17:55Z","message":"Hide main analytics applications on overview page if unavailable (#213198)\n\n## Summary\n\nThis PR fixes a bug where unavailable (due to lack of permissions)\n\"main\" analytics applications would show for users on Kibana overview\npage.\nCloses: #212171","sha":"d5d1c8fa75e85740db0fc63648c65728e5b49184","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:SharedUX","backport:prev-minor","v9.1.0"],"title":"Hide main analytics applications on overview page if unavailable","number":213198,"url":"https://github.com/elastic/kibana/pull/213198","mergeCommit":{"message":"Hide main analytics applications on overview page if unavailable (#213198)\n\n## Summary\n\nThis PR fixes a bug where unavailable (due to lack of permissions)\n\"main\" analytics applications would show for users on Kibana overview\npage.\nCloses: #212171","sha":"d5d1c8fa75e85740db0fc63648c65728e5b49184"}},"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/213198","number":213198,"mergeCommit":{"message":"Hide main analytics applications on overview page if unavailable (#213198)\n\n## Summary\n\nThis PR fixes a bug where unavailable (due to lack of permissions)\n\"main\" analytics applications would show for users on Kibana overview\npage.\nCloses: #212171","sha":"d5d1c8fa75e85740db0fc63648c65728e5b49184"}}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
Tim Sullivan
|
ba81d34bc3
|
[9.0] Fix toggling of the secondary panel for non-landing page nav item buttons (#211852) (#213170)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix toggling of the secondary panel for non-landing page nav item buttons (#211852)](https://github.com/elastic/kibana/pull/211852) <!--- Backport version: 9.6.6 --> ### 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-03-04T15:05:26Z","message":"Fix toggling of the secondary panel for non-landing page nav item buttons (#211852)\n\n## Summary\n\nCloses https://github.com/elastic/kibana-team/issues/1514\n\n**Release note:** Fixed an issue with the side navigation of solution\nprojects where clicking the nav item label would open but not close the\nsecondary navigation panel.\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- [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":"52bbc243875d29a08cd648ac06fd0d9a4da2adc3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Fix toggling of the secondary panel for non-landing page nav item buttons","number":211852,"url":"https://github.com/elastic/kibana/pull/211852","mergeCommit":{"message":"Fix toggling of the secondary panel for non-landing page nav item buttons (#211852)\n\n## Summary\n\nCloses https://github.com/elastic/kibana-team/issues/1514\n\n**Release note:** Fixed an issue with the side navigation of solution\nprojects where clicking the nav item label would open but not close the\nsecondary navigation panel.\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- [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":"52bbc243875d29a08cd648ac06fd0d9a4da2adc3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211852","number":211852,"mergeCommit":{"message":"Fix toggling of the secondary panel for non-landing page nav item buttons (#211852)\n\n## Summary\n\nCloses https://github.com/elastic/kibana-team/issues/1514\n\n**Release note:** Fixed an issue with the side navigation of solution\nprojects where clicking the nav item label would open but not close the\nsecondary navigation panel.\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- [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":"52bbc243875d29a08cd648ac06fd0d9a4da2adc3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
1fd3c6bbf5
|
[9.0] [scout] fix playwright configs discovery script and add save flag for CI (#213147) (#213242)
# Backport This will backport the following commits from `main` to `9.0`: - [[scout] fix playwright configs discovery script and add `save` flag for CI (#213147)](https://github.com/elastic/kibana/pull/213147) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T13:49:43Z","message":"[scout] fix playwright configs discovery script and add `save` flag for CI (#213147)\n\n## Summary\n\nThis PR fixes the search logic to look for playwright configs in all\npossible & expected locations (`src/*` was not working), matching one of\n3 regexp:\n```\n /(x-pack\\/platform\\/plugins\\/(?:private|shared|[^\\/]+)\\/([^\\/]+))\\/ui_tests\\//,\n /(x-pack\\/solutions\\/[^\\/]+\\/plugins\\/([^\\/]+))\\/ui_tests\\//,\n /(src\\/platform\\/plugins\\/(?:private|shared)?\\/?([^\\/]+))\\/ui_tests\\//,\n```\n\nFor each plugin we also have `usesParallelWorkers` prop (`true` if at\nleast 1 config runs with concurrent workers) to decide later, if we need\nworker with 4 or 8 VCPUs.\n\nThe idea is to run `node scripts/scout discover-playwright-configs\n--save` on CI and use generated json as source to build test run\npipeline.\n\nCurrent output:\n\n```\n{\n \"discover_enhanced\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/private/discover_enhanced\",\n \"configs\": [\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n },\n \"maps\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/shared/maps\",\n \"configs\": [\n \"x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": false\n },\n \"observability_onboarding\": {\n \"group\": \"observability\",\n \"pluginPath\": \"x-pack/solutions/observability/plugins/observability_onboarding\",\n \"configs\": [\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n }\n}\n```","sha":"1e3bb05734ed5825df802fb32a31b3c07106bee4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] fix playwright configs discovery script and add `save` flag for CI","number":213147,"url":"https://github.com/elastic/kibana/pull/213147","mergeCommit":{"message":"[scout] fix playwright configs discovery script and add `save` flag for CI (#213147)\n\n## Summary\n\nThis PR fixes the search logic to look for playwright configs in all\npossible & expected locations (`src/*` was not working), matching one of\n3 regexp:\n```\n /(x-pack\\/platform\\/plugins\\/(?:private|shared|[^\\/]+)\\/([^\\/]+))\\/ui_tests\\//,\n /(x-pack\\/solutions\\/[^\\/]+\\/plugins\\/([^\\/]+))\\/ui_tests\\//,\n /(src\\/platform\\/plugins\\/(?:private|shared)?\\/?([^\\/]+))\\/ui_tests\\//,\n```\n\nFor each plugin we also have `usesParallelWorkers` prop (`true` if at\nleast 1 config runs with concurrent workers) to decide later, if we need\nworker with 4 or 8 VCPUs.\n\nThe idea is to run `node scripts/scout discover-playwright-configs\n--save` on CI and use generated json as source to build test run\npipeline.\n\nCurrent output:\n\n```\n{\n \"discover_enhanced\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/private/discover_enhanced\",\n \"configs\": [\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n },\n \"maps\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/shared/maps\",\n \"configs\": [\n \"x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": false\n },\n \"observability_onboarding\": {\n \"group\": \"observability\",\n \"pluginPath\": \"x-pack/solutions/observability/plugins/observability_onboarding\",\n \"configs\": [\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n }\n}\n```","sha":"1e3bb05734ed5825df802fb32a31b3c07106bee4"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213147","number":213147,"mergeCommit":{"message":"[scout] fix playwright configs discovery script and add `save` flag for CI (#213147)\n\n## Summary\n\nThis PR fixes the search logic to look for playwright configs in all\npossible & expected locations (`src/*` was not working), matching one of\n3 regexp:\n```\n /(x-pack\\/platform\\/plugins\\/(?:private|shared|[^\\/]+)\\/([^\\/]+))\\/ui_tests\\//,\n /(x-pack\\/solutions\\/[^\\/]+\\/plugins\\/([^\\/]+))\\/ui_tests\\//,\n /(src\\/platform\\/plugins\\/(?:private|shared)?\\/?([^\\/]+))\\/ui_tests\\//,\n```\n\nFor each plugin we also have `usesParallelWorkers` prop (`true` if at\nleast 1 config runs with concurrent workers) to decide later, if we need\nworker with 4 or 8 VCPUs.\n\nThe idea is to run `node scripts/scout discover-playwright-configs\n--save` on CI and use generated json as source to build test run\npipeline.\n\nCurrent output:\n\n```\n{\n \"discover_enhanced\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/private/discover_enhanced\",\n \"configs\": [\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/platform/plugins/private/discover_enhanced/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n },\n \"maps\": {\n \"group\": \"platform\",\n \"pluginPath\": \"x-pack/platform/plugins/shared/maps\",\n \"configs\": [\n \"x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": false\n },\n \"observability_onboarding\": {\n \"group\": \"observability\",\n \"pluginPath\": \"x-pack/solutions/observability/plugins/observability_onboarding\",\n \"configs\": [\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/parallel.playwright.config.ts\",\n \"x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts\"\n ],\n \"usesParallelWorkers\": true\n }\n}\n```","sha":"1e3bb05734ed5825df802fb32a31b3c07106bee4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Kibana Machine
|
202020fdfc
|
[9.0] Upgrade EUI to v99.4.0 (#212974) (#213237)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade EUI to v99.4.0 (#212974)](https://github.com/elastic/kibana/pull/212974) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tomasz Kajtoch","email":"tomasz.kajtoch@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T13:09:55Z","message":"Upgrade EUI to v99.4.0 (#212974)","sha":"75f9c6113d7815f542f97ad37dcec7ffe6263f23","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v9.1.0"],"title":"Upgrade EUI to v99.4.0","number":212974,"url":"https://github.com/elastic/kibana/pull/212974","mergeCommit":{"message":"Upgrade EUI to v99.4.0 (#212974)","sha":"75f9c6113d7815f542f97ad37dcec7ffe6263f23"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212974","number":212974,"mergeCommit":{"message":"Upgrade EUI to v99.4.0 (#212974)","sha":"75f9c6113d7815f542f97ad37dcec7ffe6263f23"}}]}] BACKPORT--> Co-authored-by: Tomasz Kajtoch <tomasz.kajtoch@elastic.co> |
||
Kevin Delemme
|
c897692644
|
[9.0] feat(slo): update preview data API to show groups (#211801) (#213168)
# Backport This will backport the following commits from `main` to `9.0`: - [feat(slo): update preview data API to show groups (#211801)](https://github.com/elastic/kibana/pull/211801) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T22:04:10Z","message":"feat(slo): update preview data API to show groups (#211801)","sha":"df59c2608302372273d573b6a9013944361ffeb4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-management","v9.1.0"],"title":"feat(slo): update preview data API to show groups","number":211801,"url":"https://github.com/elastic/kibana/pull/211801","mergeCommit":{"message":"feat(slo): update preview data API to show groups (#211801)","sha":"df59c2608302372273d573b6a9013944361ffeb4"}},"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/211801","number":211801,"mergeCommit":{"message":"feat(slo): update preview data API to show groups (#211801)","sha":"df59c2608302372273d573b6a9013944361ffeb4"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
4fbbea96bc
|
[9.0] fix: Product Documentation function not available error (#212676) (#213230)
# Backport This will backport the following commits from `main` to `9.0`: - [fix: Product Documentation function not available error (#212676)](https://github.com/elastic/kibana/pull/212676) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T11:43:16Z","message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0"],"title":"fix: Product Documentation function not available error","number":212676,"url":"https://github.com/elastic/kibana/pull/212676","mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212676","number":212676,"mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
|
Kibana Machine
|
c6c2ceac4f
|
[9.0] [Obs AI Assistant] Add API test for get_alerts_dataset_info tool (#212858) (#213203)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)](https://github.com/elastic/kibana/pull/212858) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T08:09:22Z","message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0"],"title":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool","number":212858,"url":"https://github.com/elastic/kibana/pull/212858","mergeCommit":{"message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3"}},"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/212858","number":212858,"mergeCommit":{"message":"[Obs AI Assistant] Add API test for `get_alerts_dataset_info` tool (#212858)\n\nFollow-up to: https://github.com/elastic/kibana/pull/212077\n\nThis PR includes an API test that covers `get_alerts_dataset_info` and\nwould have caught the bug fixed in\nhttps://github.com/elastic/kibana/pull/212077.\n\nIt also contains the following bug fixes:\n\n- Fix system message in `select_relevant_fields`\n- Change prompt in `select_relevant_fields` so that the LLM consistently\nuses the right format when responding.","sha":"0fb83efd82ae3ebd8a9fe27813e436b80cd240d3"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Jatin Kathuria
|
44d6892766
|
[9.0] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) (#213044)
# Backport This will backport the following commits from `main` to `9.0`: - [[ Siem Migrations ] Upsell Siem Migrations Start (#212607)](https://github.com/elastic/kibana/pull/212607) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-28T03:51:31Z","message":"[ Siem Migrations ] Upsell Siem Migrations Start (#212607)\n\n## Summary\n\nThis PR adds the Upsell section for SIEM Migration Start section.\n\n- [Design\nSource](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=8x9RlFegceXzwYQf-0)\n\nSIEM migrations has below requirements in ESS and Serverless and if\nthese requirements are not met, We show the upsell sections.\n\n- ESS\n - `Enterprise` license.\n- Serverless\n - `Complete` Product tier\n\n## Demo\n\n|Instance|Demo|\n|---|---|\n|Serverless|<video\nsrc=\" |
||
florent-leborgne
|
6517579518
|
[9.0] [docs] Migrate docs from AsciiDoc to Markdown (#212558) (#213145)
# Backport This will backport the following commits from `main` to `9.0`: - [[docs] Migrate docs from AsciiDoc to Markdown (#212558)](https://github.com/elastic/kibana/pull/212558) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Colleen McGinnis","email":"colleen.mcginnis@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T13:56:07Z","message":"[docs] Migrate docs from AsciiDoc to Markdown (#212558)\n\nMigrate docs from AsciiDoc to Markdown. The preview can be built after\n#212557 is merged.\n\n@florent-leborgne please tag reviewers, add the appropriate label(s),\nand take this out of draft when you're ready.\n\nNote: More files are deleted than added here because the content from\nsome files was moved to\n[elastic/docs-content](https://github.com/elastic/docs-content).\n\n**What has moved to\n[elastic/docs-content](https://github.com/elastic/docs-content)?**\n\nPublic-facing narrative and conceptual docs have moved. Most can now be\nfound under the following directories in the new docs:\n- explore-analyze: Discover, Dashboards, Visualizations, Reporting,\nAlerting, dev tools...\n- deploy-manage: Stack management (Spaces, user management, remote\nclusters...)\n- troubleshooting: .... troubleshooting pages\n\n**What is staying in the Kibana repo?**\n\n- Reference content (= anything that is or could be auto-generated):\nSettings, syntax references\n- Release notes\n- Developer guide\n\n---------\n\nCo-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>","sha":"1814c60017da172427cd270bf2c99a8e144d378c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","backport:version","v9.1.0"],"number":212558,"url":"https://github.com/elastic/kibana/pull/212558","mergeCommit":{"message":"[docs] Migrate docs from AsciiDoc to Markdown (#212558)\n\nMigrate docs from AsciiDoc to Markdown. The preview can be built after\n#212557 is merged.\n\n@florent-leborgne please tag reviewers, add the appropriate label(s),\nand take this out of draft when you're ready.\n\nNote: More files are deleted than added here because the content from\nsome files was moved to\n[elastic/docs-content](https://github.com/elastic/docs-content).\n\n**What has moved to\n[elastic/docs-content](https://github.com/elastic/docs-content)?**\n\nPublic-facing narrative and conceptual docs have moved. Most can now be\nfound under the following directories in the new docs:\n- explore-analyze: Discover, Dashboards, Visualizations, Reporting,\nAlerting, dev tools...\n- deploy-manage: Stack management (Spaces, user management, remote\nclusters...)\n- troubleshooting: .... troubleshooting pages\n\n**What is staying in the Kibana repo?**\n\n- Reference content (= anything that is or could be auto-generated):\nSettings, syntax references\n- Release notes\n- Developer guide\n\n---------\n\nCo-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>","sha":"1814c60017da172427cd270bf2c99a8e144d378c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","labelRegex":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212558","number":212558,"mergeCommit":{"message":"[docs] Migrate docs from AsciiDoc to Markdown (#212558)\n\nMigrate docs from AsciiDoc to Markdown. The preview can be built after\n#212557 is merged.\n\n@florent-leborgne please tag reviewers, add the appropriate label(s),\nand take this out of draft when you're ready.\n\nNote: More files are deleted than added here because the content from\nsome files was moved to\n[elastic/docs-content](https://github.com/elastic/docs-content).\n\n**What has moved to\n[elastic/docs-content](https://github.com/elastic/docs-content)?**\n\nPublic-facing narrative and conceptual docs have moved. Most can now be\nfound under the following directories in the new docs:\n- explore-analyze: Discover, Dashboards, Visualizations, Reporting,\nAlerting, dev tools...\n- deploy-manage: Stack management (Spaces, user management, remote\nclusters...)\n- troubleshooting: .... troubleshooting pages\n\n**What is staying in the Kibana repo?**\n\n- Reference content (= anything that is or could be auto-generated):\nSettings, syntax references\n- Release notes\n- Developer guide\n\n---------\n\nCo-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>","sha":"1814c60017da172427cd270bf2c99a8e144d378c"}}]}] BACKPORT--> Co-authored-by: Colleen McGinnis <colleen.mcginnis@elastic.co> |
||
|
Kibana Machine
|
6b23d94eba
|
[9.0] [Playground] Increase the height of the indices container (#212827) (#213180)
# Backport This will backport the following commits from `main` to `9.0`: - [[Playground] Increase the height of the indices container (#212827)](https://github.com/elastic/kibana/pull/212827) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Saikat Sarkar","email":"132922331+saikatsarkar056@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T00:34:42Z","message":"[Playground] Increase the height of the indices container (#212827)\n\nThis PR increase the height of the container for indices in the\nplayground\n\n\n\n\nhttps://github.com/user-attachments/assets/0fbacb11-ce8e-4566-b07e-b6058de89af0","sha":"1e00a04c2b11cf69866bfc255486a286d54654b2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.18.0","v9.1.0"],"title":"[Playground] Increase the height of the indices container","number":212827,"url":"https://github.com/elastic/kibana/pull/212827","mergeCommit":{"message":"[Playground] Increase the height of the indices container (#212827)\n\nThis PR increase the height of the container for indices in the\nplayground\n\n\n\n\nhttps://github.com/user-attachments/assets/0fbacb11-ce8e-4566-b07e-b6058de89af0","sha":"1e00a04c2b11cf69866bfc255486a286d54654b2"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/212827","number":212827,"mergeCommit":{"message":"[Playground] Increase the height of the indices container (#212827)\n\nThis PR increase the height of the container for indices in the\nplayground\n\n\n\n\nhttps://github.com/user-attachments/assets/0fbacb11-ce8e-4566-b07e-b6058de89af0","sha":"1e00a04c2b11cf69866bfc255486a286d54654b2"}}]}] BACKPORT--> Co-authored-by: Saikat Sarkar <132922331+saikatsarkar056@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
d5b2c4733b
|
Update ftr (9.0) (#211968)
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://redirect.github.com/giggio/node-chromedriver) | devDependencies | patch | [`^133.0.0` -> `^133.0.2`](https://renovatebot.com/diffs/npm/chromedriver/133.0.0/133.0.2) | `133.0.3` | | [selenium-webdriver](https://redirect.github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver#readme) ([source](https://redirect.github.com/SeleniumHQ/selenium)) | devDependencies | minor | [`^4.28.1` -> `^4.29.0`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.28.1/4.29.0) | | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v133.0.2`](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.1...133.0.2) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.1...133.0.2) ### [`v133.0.1`](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.0...133.0.1) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/133.0.0...133.0.1) </details> <details> <summary>SeleniumHQ/selenium (selenium-webdriver)</summary> ### [`v4.29.0`]( |
||
|
elastic-renovate-prod[bot]
|
67e3977de5
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 15a4191 (9.0) (#212960)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `6387bd4` -> `15a4191` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
c9987a1293
|
[9.0] [controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164) (#213179)
# Backport This will backport the following commits from `main` to `9.0`: - [[controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164)](https://github.com/elastic/kibana/pull/213164) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T23:43:38Z","message":"[controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164)\n\nCloses https://github.com/elastic/kibana/issues/213150\n\nTest steps\n* Follow https://www.youtube.com/watch?v=vjulSf3Kwu4 to setup duel\nlanguage inputs with English and Korean.\n* Create a dashboard with an options list. Switch to Korean input and\ntype in option list control. Type the characters `d` and `k` on an\nenglish keyboard.\n* Ensure input treats value as a single character.\n<img width=\"591\" alt=\"Screenshot 2025-03-04 at 1 52 14 PM\"\nsrc=\"https://github.com/user-attachments/assets/c7cfe0f5-156d-4949-932a-96067bf20fd6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ce9019ce3260d9155827edd97bb80dea439bc5a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[controls] fix Korean characters split into 2 characters with space in between when typing in options list search input","number":213164,"url":"https://github.com/elastic/kibana/pull/213164","mergeCommit":{"message":"[controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164)\n\nCloses https://github.com/elastic/kibana/issues/213150\n\nTest steps\n* Follow https://www.youtube.com/watch?v=vjulSf3Kwu4 to setup duel\nlanguage inputs with English and Korean.\n* Create a dashboard with an options list. Switch to Korean input and\ntype in option list control. Type the characters `d` and `k` on an\nenglish keyboard.\n* Ensure input treats value as a single character.\n<img width=\"591\" alt=\"Screenshot 2025-03-04 at 1 52 14 PM\"\nsrc=\"https://github.com/user-attachments/assets/c7cfe0f5-156d-4949-932a-96067bf20fd6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ce9019ce3260d9155827edd97bb80dea439bc5a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213164","number":213164,"mergeCommit":{"message":"[controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164)\n\nCloses https://github.com/elastic/kibana/issues/213150\n\nTest steps\n* Follow https://www.youtube.com/watch?v=vjulSf3Kwu4 to setup duel\nlanguage inputs with English and Korean.\n* Create a dashboard with an options list. Switch to Korean input and\ntype in option list control. Type the characters `d` and `k` on an\nenglish keyboard.\n* Ensure input treats value as a single character.\n<img width=\"591\" alt=\"Screenshot 2025-03-04 at 1 52 14 PM\"\nsrc=\"https://github.com/user-attachments/assets/c7cfe0f5-156d-4949-932a-96067bf20fd6\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3ce9019ce3260d9155827edd97bb80dea439bc5a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
|
Kibana Machine
|
335a6084ed
|
[9.0] [artifacts] Remove default --openssl-legacy-provider (#213123) (#213173)
# Backport This will backport the following commits from `main` to `9.0`: - [[artifacts] Remove default --openssl-legacy-provider (#213123)](https://github.com/elastic/kibana/pull/213123) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T22:51:46Z","message":"[artifacts] Remove default --openssl-legacy-provider (#213123)\n\n# Release note\n\nLegacy OpenSSL algorithms have been disabled by default. Further\ninformation on which algorithms can be found at\nhttps://docs.openssl.org/3.0/man7/OSSL_PROVIDER-legacy. These can be\nre-enabled by adding `--openssl-legacy-provider` to\n`$KBN_PATH_CONF/node.options`","sha":"98a7259ee148c64392c7df5995d18067a464389a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:breaking","Team:Operations","v9.0.0","ci:all-cypress-suites","ci:cloud-deploy","ci:project-deploy-elasticsearch","backport:version","v9.1.0"],"title":"[artifacts] Remove default --openssl-legacy-provider","number":213123,"url":"https://github.com/elastic/kibana/pull/213123","mergeCommit":{"message":"[artifacts] Remove default --openssl-legacy-provider (#213123)\n\n# Release note\n\nLegacy OpenSSL algorithms have been disabled by default. Further\ninformation on which algorithms can be found at\nhttps://docs.openssl.org/3.0/man7/OSSL_PROVIDER-legacy. These can be\nre-enabled by adding `--openssl-legacy-provider` to\n`$KBN_PATH_CONF/node.options`","sha":"98a7259ee148c64392c7df5995d18067a464389a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213123","number":213123,"mergeCommit":{"message":"[artifacts] Remove default --openssl-legacy-provider (#213123)\n\n# Release note\n\nLegacy OpenSSL algorithms have been disabled by default. Further\ninformation on which algorithms can be found at\nhttps://docs.openssl.org/3.0/man7/OSSL_PROVIDER-legacy. These can be\nre-enabled by adding `--openssl-legacy-provider` to\n`$KBN_PATH_CONF/node.options`","sha":"98a7259ee148c64392c7df5995d18067a464389a"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
|
Kibana Machine
|
029cde7af0
|
[9.0] [Lens] Fix partition chart color assignments (#207178) (#213149)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens] Fix partition chart color assignments (#207178)](https://github.com/elastic/kibana/pull/207178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T17:20:43Z","message":"[Lens] Fix partition chart color assignments (#207178)\n\nFixes the color assignment for partition charts consistent with the legend ordering. Aligns legacy and color mapping color logic.","sha":"28dc0f6ffcf82279dc3fcaee477b4727b8bbdd0a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","v9.1.0"],"title":"[Lens] Fix partition chart color assignments","number":207178,"url":"https://github.com/elastic/kibana/pull/207178","mergeCommit":{"message":"[Lens] Fix partition chart color assignments (#207178)\n\nFixes the color assignment for partition charts consistent with the legend ordering. Aligns legacy and color mapping color logic.","sha":"28dc0f6ffcf82279dc3fcaee477b4727b8bbdd0a"}},"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/207178","number":207178,"mergeCommit":{"message":"[Lens] Fix partition chart color assignments (#207178)\n\nFixes the color assignment for partition charts consistent with the legend ordering. Aligns legacy and color mapping color logic.","sha":"28dc0f6ffcf82279dc3fcaee477b4727b8bbdd0a"}}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
4c2c6a79e1
|
[9.0] [Obs AI Assistant] Update date category label (#213108) (#213138)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Update date category label (#213108)](https://github.com/elastic/kibana/pull/213108) <!--- Backport version: 9.6.6 --> ### 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-03-04T16:20:12Z","message":"[Obs AI Assistant] Update date category label (#213108)","sha":"ad8c3e7be5947931a25d6e07fabf13bef4230d89","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Update date category label","number":213108,"url":"https://github.com/elastic/kibana/pull/213108","mergeCommit":{"message":"[Obs AI Assistant] Update date category label (#213108)","sha":"ad8c3e7be5947931a25d6e07fabf13bef4230d89"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213108","number":213108,"mergeCommit":{"message":"[Obs AI Assistant] Update date category label (#213108)","sha":"ad8c3e7be5947931a25d6e07fabf13bef4230d89"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |