mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 16:29:04 -04:00
80884 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Som
|
f8816ac929
|
Update session-management.asciidoc | ||
Kibana Machine
|
320c031d91
|
[8.17] Update dependency cytoscape to ^3.31.1 (main) (#213334) (#213895)
# Backport This will backport the following commits from `main` to `8.17`: - [Update dependency cytoscape to ^3.31.1 (main) (#213334)](https://github.com/elastic/kibana/pull/213334) <!--- 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-11T10:29:18Z","message":"Update dependency cytoscape to ^3.31.1 (main) (#213334)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js)) |\ndependencies | patch | [`^3.31.0` ->\n`^3.31.1`](https://renovatebot.com/diffs/npm/cytoscape/3.31.0/3.31.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>cytoscape/cytoscape.js (cytoscape)</summary>\n\n###\n[`v3.31.1`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.1)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.0...v3.31.1)\n\nRelease version v3.31.1\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **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>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>","sha":"c348bd1df57f6ef268622c8ec992cae69b71098b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Update dependency cytoscape to ^3.31.1 (main)","number":213334,"url":"https://github.com/elastic/kibana/pull/213334","mergeCommit":{"message":"Update dependency cytoscape to ^3.31.1 (main) (#213334)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js)) |\ndependencies | patch | [`^3.31.0` ->\n`^3.31.1`](https://renovatebot.com/diffs/npm/cytoscape/3.31.0/3.31.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>cytoscape/cytoscape.js (cytoscape)</summary>\n\n###\n[`v3.31.1`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.1)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.0...v3.31.1)\n\nRelease version v3.31.1\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **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>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>","sha":"c348bd1df57f6ef268622c8ec992cae69b71098b"}},"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/213334","number":213334,"mergeCommit":{"message":"Update dependency cytoscape to ^3.31.1 (main) (#213334)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [cytoscape](http://js.cytoscape.org)\n([source](https://redirect.github.com/cytoscape/cytoscape.js)) |\ndependencies | patch | [`^3.31.0` ->\n`^3.31.1`](https://renovatebot.com/diffs/npm/cytoscape/3.31.0/3.31.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>cytoscape/cytoscape.js (cytoscape)</summary>\n\n###\n[`v3.31.1`](https://redirect.github.com/cytoscape/cytoscape.js/releases/tag/v3.31.1)\n\n[Compare\nSource](https://redirect.github.com/cytoscape/cytoscape.js/compare/v3.31.0...v3.31.1)\n\nRelease version v3.31.1\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **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>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>","sha":"c348bd1df57f6ef268622c8ec992cae69b71098b"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
jennypavlova
|
3e296b64e5
|
[8.17] [APM] Fix: Span Links with OTel data (#212806) (#213886)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Fix: Span Links with OTel data (#212806)](https://github.com/elastic/kibana/pull/212806) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-10T18:47:07Z","message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix: Span Links with OTel data","number":212806,"url":"https://github.com/elastic/kibana/pull/212806","mergeCommit":{"message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212806","number":212806,"mergeCommit":{"message":"[APM] Fix: Span Links with OTel data (#212806)\n\nCloses #212796 \n\nThis PR fixes OTel span links\n\n## Testing\n\n- Using the edge oblt go to Service inventory and find the `accounting`\nservice and click on it\n- Click on the transactions tab and scroll to the waterfall\n- Click on the Span link inside the Span\n- Navigate to the linked service \n- Then try the navigation back by finding the span link again in the\nwaterfall and go back to the accounting service / its trace\n\n\n\n\nhttps://github.com/user-attachments/assets/83bb6ec3-86d5-45ad-8b81-6df73751fa31\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"662c30a260f676c9e1180e7d413553d0166726d7"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Cauê Marcondes
|
eee5d76723
|
[8.17] [APM] Breakdown Top dependencies API (#211441) (#213795)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Breakdown Top dependencies API (#211441)](https://github.com/elastic/kibana/pull/211441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-10T16:24:37Z","message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Breakdown Top dependencies API","number":211441,"url":"https://github.com/elastic/kibana/pull/211441","mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211441","number":211441,"mergeCommit":{"message":"[APM] Breakdown Top dependencies API (#211441)\n\ncloses https://github.com/elastic/kibana/issues/210552\n\nBefore:\n- Top dependencies API returned baseline and comparison timeseries data.\n\n<img width=\"1208\" alt=\"Screenshot 2025-02-14 at 14 27 28\"\nsrc=\"https://github.com/user-attachments/assets/f7770395-0575-4950-9acd-8808de5794b7\"\n/>\n\n\nAfter:\n- Removing timeseries and comparison data.\n- The API is ~2s faster than before.\n- Response size is also smaller after removing the timeseries data.\n\n<img width=\"1203\" alt=\"Screenshot 2025-02-14 at 14 26 34\"\nsrc=\"https://github.com/user-attachments/assets/5bd2ed09-1d2e-4ef1-8e55-6c3e9fba6348\"\n/>\n\nCreated a new API: `POST\n/internal/apm/dependencies/top_dependencies/statistics` to fetch the\nstatistics for the visible dependencies.\n\n---------\n\nCo-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>\nCo-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com>","sha":"a6fd5b7e101b7e0d13b15220a247d4a29e5c0405"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Christos Nasikas
|
f8ff8466dd
|
[8.17] [ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658) (#213865)
# Backport This will backport the following commits from `main` to `8.17`: - [[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)](https://github.com/elastic/kibana/pull/213658) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-10T18:53:48Z","message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v9.0.0","Feature:Actions/ConnectorTypes","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector","number":213658,"url":"https://github.com/elastic/kibana/pull/213658","mergeCommit":{"message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213818","number":213818,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213816","number":213816,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213658","number":213658,"mergeCommit":{"message":"[ResponseOps][Connectors] Fix bug with OAuth form in the ServiceNow connector (#213658)\n\n## Summary\n\nThis PR fixes a bug where users could not create a ServiceNow connector\nwith OAuth configuration. In addition to the fix, I decided to improve\nthe error messages and show the callout to install our SN applications\nonly on CORS errors. The rest of the errors will be shown on a generic\nerror callout.\n\n<img width=\"1246\" alt=\"Screenshot 2025-03-08 at 1 54 56 PM\"\nsrc=\"https://github.com/user-attachments/assets/5dac9662-be9b-474a-a0ca-d6d1a14baa53\"\n/>\n<img width=\"1248\" alt=\"Screenshot 2025-03-08 at 1 55 16 PM\"\nsrc=\"https://github.com/user-attachments/assets/fc548263-ebd3-4ce6-aac1-725236b626b5\"\n/>\n\n\nFixes: https://github.com/elastic/kibana/issues/212790\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release notes\nFix a bug with ServiceNow where users could not create the connector\nfrom the UI form using OAuth.","sha":"2839562b8a7c8016582cbb0d5fc35e2a71cdaccf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213817","number":213817,"state":"OPEN"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
elastic-renovate-prod[bot]
|
5b945f74f5
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to a37e513 (8.17) (#213664)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `10f7cda` -> `a37e513` | --- ### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Sergi Massaneda
|
d62cf5b255
|
[8.17] [Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563) (#213615)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)](https://github.com/elastic/kibana/pull/212563) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T17:43:24Z","message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Security Solution][Connectors] Torq connector allow EU hooks hostname","number":212563,"url":"https://github.com/elastic/kibana/pull/212563","mergeCommit":{"message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213613","number":213613,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213611","number":213611,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212563","number":212563,"mergeCommit":{"message":"[Security Solution][Connectors] Torq connector allow EU hooks hostname (#212563)\n\n## Summary\n\nFrom: https://github.com/elastic/kibana/issues/212511\n\nAdd support for EU domains\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"723a33b7de7b776f39ae816c42eaf2abd07734ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213612","number":213612,"state":"OPEN"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Alex Szabo
|
4a7a5d56eb
|
[8.17] [ci] Trigger VM image rebuild for cache rebuild only (#213497) (#213722)
# Backport This will backport the following commits from `main` to `8.17`: - [[ci] Trigger VM image rebuild for cache rebuild only (#213497)](https://github.com/elastic/kibana/pull/213497) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-10T09:56:15Z","message":"[ci] Trigger VM image rebuild for cache rebuild only (#213497)\n\n## Summary\nWhen VM image rebuild is triggered after ES promotion, only the cache\nwarmup should be built.\n\nThis PR also separates the daily full build to a daily base + cache\nbuild (in case ES promotions are failing for some reason, we should\nstill have a daily cache refresh).\n\nRequires: https://github.com/elastic/ci-agent-images/pull/1295\n\nWith this, we'd run a daily base image build and cache build (~40m +\n25m) + cache warmups for every promotion (~4x 25m) instead of a full\nbuild and promotion per build (~4x 55m). Ultimately not that much of a\ngain 🤷 (4*55=220m => 40+5x25=165m)","sha":"830dbd4ed72cb05829dbc1ee383dee9f9cbcdac8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","skip-ci","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[ci] Trigger VM image rebuild for cache rebuild only","number":213497,"url":"https://github.com/elastic/kibana/pull/213497","mergeCommit":{"message":"[ci] Trigger VM image rebuild for cache rebuild only (#213497)\n\n## Summary\nWhen VM image rebuild is triggered after ES promotion, only the cache\nwarmup should be built.\n\nThis PR also separates the daily full build to a daily base + cache\nbuild (in case ES promotions are failing for some reason, we should\nstill have a daily cache refresh).\n\nRequires: https://github.com/elastic/ci-agent-images/pull/1295\n\nWith this, we'd run a daily base image build and cache build (~40m +\n25m) + cache warmups for every promotion (~4x 25m) instead of a full\nbuild and promotion per build (~4x 55m). Ultimately not that much of a\ngain 🤷 (4*55=220m => 40+5x25=165m)","sha":"830dbd4ed72cb05829dbc1ee383dee9f9cbcdac8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213697","number":213697,"state":"MERGED","mergeCommit":{"sha":"e3b7db6f446a8daedb965cbe0f6823c91747c10c","message":"[9.0] [ci] Trigger VM image rebuild for cache rebuild only (#213497) (#213697)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[ci] Trigger VM image rebuild for cache rebuild only\n(#213497)](https://github.com/elastic/kibana/pull/213497)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alex Szabo <alex.szabo@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213497","number":213497,"mergeCommit":{"message":"[ci] Trigger VM image rebuild for cache rebuild only (#213497)\n\n## Summary\nWhen VM image rebuild is triggered after ES promotion, only the cache\nwarmup should be built.\n\nThis PR also separates the daily full build to a daily base + cache\nbuild (in case ES promotions are failing for some reason, we should\nstill have a daily cache refresh).\n\nRequires: https://github.com/elastic/ci-agent-images/pull/1295\n\nWith this, we'd run a daily base image build and cache build (~40m +\n25m) + cache warmups for every promotion (~4x 25m) instead of a full\nbuild and promotion per build (~4x 55m). Ultimately not that much of a\ngain 🤷 (4*55=220m => 40+5x25=165m)","sha":"830dbd4ed72cb05829dbc1ee383dee9f9cbcdac8"}}]}] BACKPORT--> |
||
Carlos Crespo
|
7478f4d0c0
|
[8.17] [Infra] Fix hosts total count query (#212749) (#213691)
# Backport This will backport the following commits from `main` to `8.17`: - [[Infra] Fix hosts total count query (#212749)](https://github.com/elastic/kibana/pull/212749) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-04T15:46:21Z","message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[Infra] Fix hosts total count query","number":212749,"url":"https://github.com/elastic/kibana/pull/212749","mergeCommit":{"message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212749","number":212749,"mergeCommit":{"message":"[Infra] Fix hosts total count query (#212749)\n\nFixes [#212745](https://github.com/elastic/kibana/issues/212745)\n\n## Summary\n\nFix for the hosts total count query, which was not correctly filtering\nhosts from system integration and APM\n\n<img width=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/05c3b244-3a0f-425a-82db-3498c1a6dbb7\"\n/>\n\n\n### How to test\n- Connect Kibana to an edge cluster\n- Navigate to Infrastructure > Hosts\n- The total number of items on the table should be equal to the number\nin the hosts count KPI\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8e5b8580f461b4f057ade98cf340e3a8bf8b9d6f"}}]}] BACKPORT--> |
||
|
elastic-renovate-prod[bot]
|
a887cffdec
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 10f7cda (8.17) (#213523)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `6dcddd8` -> `10f7cda` | --- ### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
ab85531373
|
[8.17] [APM][Errors] Fix: Missing summary data in in error sample (#213430) (#213572)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM][Errors] Fix: Missing summary data in in error sample (#213430)](https://github.com/elastic/kibana/pull/213430) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T14:08:39Z","message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][Errors] Fix: Missing summary data in in error sample","number":213430,"url":"https://github.com/elastic/kibana/pull/213430","mergeCommit":{"message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213430","number":213430,"mergeCommit":{"message":"[APM][Errors] Fix: Missing summary data in in error sample (#213430)\n\nCloses #213418 \n## Summary\n\nThis PR fixes the missing error sample summary by adding the missing\nfields\n\nBug (Before) | Fix (After)\n|-----------------------|-----------|\n| <img width=\"1912\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f7a9b007-529d-422d-b0e2-eac2e06c26b1\"\n/> |\n\n|\n\n## Testing\n- Find a service with errors (using edge oblt data or any data that\nincludes the field values shown)\n- Click on the service and navigate to Errors tab \n- The Error sample should include the summary data \n\n","sha":"36e930c27346b1a729bea7fc663b6934bbfca403"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Michael Olorunnisola
|
2bd9fede4b
|
[8.17] [Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343) (#213491)
# Backport This will backport the following commits from `main` to `8.17`: - [[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)](https://github.com/elastic/kibana/pull/211343) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T21:09:22Z","message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.16.6","v8.17.4"],"title":"[Bug][Security Solution] - Reliably persist dataview selections for timeline","number":211343,"url":"https://github.com/elastic/kibana/pull/211343","mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213488","number":213488,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211343","number":211343,"mergeCommit":{"message":"[Bug][Security Solution] - Reliably persist dataview selections for timeline (#211343)\n\nresolves https://github.com/elastic/kibana/issues/198944\n\n## Summary\n\nCurrently, the redux store can become out of sync with the state in the\nUI, leading to the selected dataview not being preserved in the store,\nand thereby not being saved when the timeline is saved. This PR sets the\nselected dataview and patterns at the point of saving to ensure that\nthey are set and not overriden.\n\nFor additional background, see referenced issues.","sha":"4abf1a151e9b10a02a633a5f9e88607a55e3f4ba"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
elastic-renovate-prod[bot]
|
79eba914a0
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 6dcddd8 (8.17) (#213342)
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
04dc0da349
|
[8.17] [Fleet] unskip test (#213365) (#213401)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] unskip test (#213365)](https://github.com/elastic/kibana/pull/213365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-06T14:20:39Z","message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] unskip test","number":213365,"url":"https://github.com/elastic/kibana/pull/213365","mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213365","number":213365,"mergeCommit":{"message":"[Fleet] unskip test (#213365)\n\nCloses https://github.com/elastic/kibana/issues/192793\nCloses https://github.com/elastic/kibana/issues/192792","sha":"198b99ee102d02120e0f4e61663e061dd384227c"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Sandra G
|
1eebc6eef3
|
[8.17] [Obs AI Assistant] fix flaky test and add back test in settings (#213196) (#213320)
# Backport This will backport the following commits from `main` to `8.17`: - [[Obs AI Assistant] fix flaky test and add back test in settings (#213196)](https://github.com/elastic/kibana/pull/213196) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-05T16:46:02Z","message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0","v8.16.6"],"title":"[Obs AI Assistant] fix flaky test and add back test in settings","number":213196,"url":"https://github.com/elastic/kibana/pull/213196","mergeCommit":{"message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252"}},"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/213196","number":213196,"mergeCommit":{"message":"[Obs AI Assistant] fix flaky test and add back test in settings (#213196)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/191707\n\nSummarize your PR. If it involves visual changes include a screenshot or\ngif.\n\n- Fixes flaky test`allows updating of an advanced setting` by making\nsure to wait for page refresh\n- Adds back test to check for toast on error\nhttps://github.com/elastic/kibana/pull/191531\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"bccbb933c0e2dea4c4d23c7174bbe0be638db252"}},{"branch":"8.16","label":"v8.16.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213271","number":213271,"state":"MERGED","mergeCommit":{"sha":"b400d81dfeff4274d6a708503c956f3b852cb10c","message":"[8.16] [Obs AI Assistant] fix flaky test and add back test in settings (#213196) (#213271)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Obs AI Assistant] fix flaky test and add back test in settings\n(#213196)](https://github.com/elastic/kibana/pull/213196)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Sandra G <neptunian@users.noreply.github.com>"}},{"url":"https://github.com/elastic/kibana/pull/213272","number":213272,"branch":"9.0","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/213316","number":213316,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/213318","number":213318,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
a5e245337a
|
[8.17] fix: Product Documentation function not available error (#212676) (#213226)
# Backport This will backport the following commits from `main` to `8.17`: - [fix: Product Documentation function not available error (#212676)](https://github.com/elastic/kibana/pull/212676) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-03-05T11:43:16Z","message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","ci:project-deploy-observability","v9.1.0"],"title":"fix: Product Documentation function not available error","number":212676,"url":"https://github.com/elastic/kibana/pull/212676","mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212676","number":212676,"mergeCommit":{"message":"fix: Product Documentation function not available error (#212676)\n\n## Summary\nCloses [#212655](https://github.com/elastic/kibana/issues/212655)\nFIX:\nWhen a user asks a question about the Elastic stack, we expect the LLM\nto request the `retrieve_elastic_doc` function. However, due to the\nlimit of number of functions we can register, it errors out because the\nfunction is not available.\n\n\n","sha":"cb4e2023b4a7041aa3173b4135debc96ef8fb9c8"}}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
Tiago Costa
|
5e8c27aaa3
|
chore(NA): bump version to 8.17.4 (#213142)
Usually bump from 8.17.3 to 8.17.4 |
||
|
elastic-renovate-prod[bot]
|
ad85e0c06a
|
Update ftr (8.17) (#211971)
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]
|
71b8882bb9
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 15a4191 (8.17) (#212963)
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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
07d90832af
|
[8.17] [controls] fix Korean characters split into 2 characters with space in between when typing in options list search input (#213164) (#213176)
# Backport This will backport the following commits from `main` to `8.17`: - [[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> |
||
|
Michael Olorunnisola
|
543bf80673
|
[8.17] [Performance][Security Solution][1/4] - Field Browser Performance (#212469) (#213025)
# Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][1/4] - Field Browser Performance (#212469)](https://github.com/elastic/kibana/pull/212469) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T01:22:25Z","message":"[Performance][Security Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart 1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n- Security solution field browser component\n- Flyout table tab.\n\n### Background\n\nWhen investigating the performance of the security solution application,\none of the issues that was observed was locking of the page and field\nbrowser component when the total number of fields returned were\nsignificantly high.\n\nThis led to cell values not rendering in the alert table, and the field\nbrowser in all the security solution pages causing the page to crash.\nThe relevant images can be seen at the bottom of this description\n\nIn short: The `push(...fields)` is non-performant at scale, and at a\nsignificant enough scale (Testing was done with 500k mapped fields),\nfails to run due to excessive arguments provided to the `push` method.\nIn this PR improvements are made in the `browserFields` transformations\nthat are done for the field browser component, expandable flyout table\ntab, and alert/rule tables via `CellValue` component.\n\nThis work was done to get immediate improvements in the security\nsolution UI, but a longer term consideration will be whether or not the\n`browserFields` is even necessary anymore as a concept based on what is\navailable via the `fields` api. We will revisit once our Sourcerer\nrefactoring work is done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15 29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18 36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19 48 AM\"\nsrc=\" |
||
|
Michael Olorunnisola
|
72460c6d64
|
[8.17] [Performance][Security Solution][4/4] - General Performance changes (#212488) (#212992)
# Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][4/4] - General Performance changes (#212488)](https://github.com/elastic/kibana/pull/212488) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T17:59:43Z","message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Performance][Security Solution][4/4] - General Performance changes","number":212488,"url":"https://github.com/elastic/kibana/pull/212488","mergeCommit":{"message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212966","number":212966,"state":"MERGED","mergeCommit":{"sha":"f93acdea1585b265c9a74be93da1c2dfa562631b","message":"[9.0] [Performance][Security Solution][4/4] - General Performance changes (#212488) (#212966)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Performance][Security Solution][4/4] - General Performance changes\n(#212488)](https://github.com/elastic/kibana/pull/212488)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212488","number":212488,"mergeCommit":{"message":"[Performance][Security Solution][4/4] - General Performance changes (#212488)\n\n## Summary\nPart 4 (Final) of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nFor testing, feel free to add a `console.count('!! - Number of\nre-renders:)` to\n`x-pack/solutions/security/plugins/security_solution/public/app/home/index.tsx`.\nThe memoization changes\n[here](https://github.com/elastic/kibana/pull/212488/files#diff-b0cdd6dc57dd06dba69d90894de8c88a7bb7c71c0e58753f324eb8ba664a0782R18)\nto the plugin template wrapper, prevented 2 extra re-renders, but there\nis still an underlying problem of how the `PageTemplateWrapper` is used,\nas it causes unmounting and remounting of the security views when\nnavigating between pages.\n\nThe only other change was to rely on React's built in diffing on the\nalerts page for the page level filters","sha":"7f32eb0225a9bb91167f4968548cfa46489521e7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Sander Philipse
|
448cc588d8
|
[8.17] [Search] Don't error out on missing connectors permissions (#212622) (#213091)
# Backport This will backport the following commits from `main` to `8.17`: - [[Search] Don't error out on missing connectors permissions (#212622)](https://github.com/elastic/kibana/pull/212622) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-28T12:36:37Z","message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Search] Don't error out on missing connectors permissions","number":212622,"url":"https://github.com/elastic/kibana/pull/212622","mergeCommit":{"message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212763","number":212763,"state":"MERGED","mergeCommit":{"sha":"e32f93a3f59c104f0f658ba4d5a7fc6431cb5096","message":"[9.0] [Search] Don't error out on missing connectors permissions (#212622) (#212763)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Search] Don't error out on missing connectors permissions\n(#212622)](https://github.com/elastic/kibana/pull/212622)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212622","number":212622,"mergeCommit":{"message":"[Search] Don't error out on missing connectors permissions (#212622)\n\n## Summary\n\nThis stops errors on missing connectors permissions when fetching\nindices, which was preventing users without connectors permissions but\nwith listing and write permissions to indices generally from seeing\nindices in the Search UI.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7590205f9a9dd79c8a204eb75b69782503d30937"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
79d1c6029b
|
[8.17] [Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783) (#213049) (#213086)
# Backport This will backport the following commits from `main` to `8.17`: - [[Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783) (#213049)](https://github.com/elastic/kibana/pull/213049) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T12:05:51Z","message":"[Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783) (#213049)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the\n`conversationId` can be passed as an empty string. This may lead to\nunexpected results described in\nhttps://github.com/elastic/security-team/issues/11783#issuecomment-2696529040.\n\n### Expected behaviour\n\nWe should throw a bad request (400) http error when empty\n`conversationId` has been passed.\n\n### Testing\n\n* Use this `curl` command to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\nYou should see next error as a response:\n\n```\n{\n \"statusCode\": 400,\n \"error\": \"Bad Request\",\n \"message\": \"[request body]: conversationId: String must contain at least 1 character(s), conversationId: No empty strings allowed\"\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7db897a5393f2d776eca1d9760801dc2fa72ad9d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783)","number":213049,"url":"https://github.com/elastic/kibana/pull/213049","mergeCommit":{"message":"[Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783) (#213049)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the\n`conversationId` can be passed as an empty string. This may lead to\nunexpected results described in\nhttps://github.com/elastic/security-team/issues/11783#issuecomment-2696529040.\n\n### Expected behaviour\n\nWe should throw a bad request (400) http error when empty\n`conversationId` has been passed.\n\n### Testing\n\n* Use this `curl` command to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\nYou should see next error as a response:\n\n```\n{\n \"statusCode\": 400,\n \"error\": \"Bad Request\",\n \"message\": \"[request body]: conversationId: String must contain at least 1 character(s), conversationId: No empty strings allowed\"\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7db897a5393f2d776eca1d9760801dc2fa72ad9d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213049","number":213049,"mergeCommit":{"message":"[Bug] [Assistant API] - Do not allow empty conversation ID in chat/complete route (#11783) (#213049)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the\n`conversationId` can be passed as an empty string. This may lead to\nunexpected results described in\nhttps://github.com/elastic/security-team/issues/11783#issuecomment-2696529040.\n\n### Expected behaviour\n\nWe should throw a bad request (400) http error when empty\n`conversationId` has been passed.\n\n### Testing\n\n* Use this `curl` command to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\nYou should see next error as a response:\n\n```\n{\n \"statusCode\": 400,\n \"error\": \"Bad Request\",\n \"message\": \"[request body]: conversationId: String must contain at least 1 character(s), conversationId: No empty strings allowed\"\n}\n```\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7db897a5393f2d776eca1d9760801dc2fa72ad9d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
a37f1d36af
|
[8.17] [Elastic Defend] Add windows.ransomware.dump_process for endpoint advanced policy setting (#212439) (#213009)
# Backport This will backport the following commits from `main` to `8.17`: - [[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)](https://github.com/elastic/kibana/pull/212439) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christophe Alladoum","email":"85187342+calladoum-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-04T00:57:20Z","message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:version","v8.18.0","v8.15.6","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting","number":212439,"url":"https://github.com/elastic/kibana/pull/212439","mergeCommit":{"message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.15","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212439","number":212439,"mergeCommit":{"message":"[Elastic Defend] Add `windows.ransomware.dump_process` for endpoint advanced policy setting (#212439)\n\n## Summary\n\nThis PR exposes `windows.ransomware.dump_process` as an advanced policy\noption for Elastic Defend.\nIf enabled, this option will make the endpoint generate a memory dump of\nthe ransomware process before killing it, assisting the ransomware\ninvestigation process.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e9813b8c72d4479c8f023a3dccc94842fdac29f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Christophe Alladoum <85187342+calladoum-elastic@users.noreply.github.com> |
||
|
Kibana Machine
|
298f53986a
|
[8.17] [Performance][Security Solution][3/4] - Sourcerer performance (#212482) (#212985)
# Backport This will backport the following commits from `main` to `8.17`: - [[Performance][Security Solution][3/4] - Sourcerer performance (#212482)](https://github.com/elastic/kibana/pull/212482) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T21:06:38Z","message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"[Performance][Security Solution][3/4] - Sourcerer performance","number":212482,"url":"https://github.com/elastic/kibana/pull/212482","mergeCommit":{"message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212482","number":212482,"mergeCommit":{"message":"[Performance][Security Solution][3/4] - Sourcerer performance (#212482)\n\n## Summary\nPart 3 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor setup see testing section here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\nTesting this work is a bit more `console.log` related, as the primary\naim of many of these changes was to limit the amount of re-renders\ncaused by state changes within many of the sourcerer utils. React is\nrelatively fast at handling many of these re-renders, but considering\nthe widespread usage of `useSourcererDataView` and the top level\nlocation of `useInitSourcerer`, it was worth taking care of some low\nhanging fruit.\n\n### Background\n\nThe changes in this PR centered around limiting the number of re-renders\nthat were being caused unnecessarily in `useSourcererDataView` and\n`useInitSourcerer` by identifying some quick wins.\n\nComments regarding the changes can be found in the PR diffs\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n### Identify risks\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98b52804d500f31f2fc80f47f478427a52f20630"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> |
||
wajihaparvez
|
3176d535c7
|
[Docs] Backport 8.17.3 release notes to 8.17 (#212942)
## Summary Backporting [8.17.3 release notes](https://github.com/elastic/kibana/pull/212693) to 8.17. Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
wajihaparvez
|
ed3c649d10
|
[Docs] Backport 8.16.5 release notes to 8.17 (#212938)
## Summary Backporting [8.16.5 release notes](https://github.com/elastic/kibana/pull/212688) to 8.17. |
||
|
Kibana Machine
|
fc2d320775
|
[8.17] adds thumbnail for elasticsearch logs integration (#212877) (#212907)
# Backport This will backport the following commits from `main` to `8.17`: - [adds thumbnail for elasticsearch logs integration (#212877)](https://github.com/elastic/kibana/pull/212877) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-03T12:53:05Z","message":"adds thumbnail for elasticsearch logs integration (#212877)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/204328\n\n## Visuals\n<img width=\"1313\" alt=\"Screenshot 2025-03-03 at 12 11 16\"\nsrc=\"https://github.com/user-attachments/assets/99e627fe-6136-4a1e-8178-f8afd9bb9e27\"\n/>\n\n\n","sha":"883bc1794b07658b4ffe4ec387f38b87c22ca03e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"adds thumbnail for elasticsearch logs integration","number":212877,"url":"https://github.com/elastic/kibana/pull/212877","mergeCommit":{"message":"adds thumbnail for elasticsearch logs integration (#212877)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/204328\n\n## Visuals\n<img width=\"1313\" alt=\"Screenshot 2025-03-03 at 12 11 16\"\nsrc=\"https://github.com/user-attachments/assets/99e627fe-6136-4a1e-8178-f8afd9bb9e27\"\n/>\n\n\n","sha":"883bc1794b07658b4ffe4ec387f38b87c22ca03e"}},"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/212877","number":212877,"mergeCommit":{"message":"adds thumbnail for elasticsearch logs integration (#212877)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/204328\n\n## Visuals\n<img width=\"1313\" alt=\"Screenshot 2025-03-03 at 12 11 16\"\nsrc=\"https://github.com/user-attachments/assets/99e627fe-6136-4a1e-8178-f8afd9bb9e27\"\n/>\n\n\n","sha":"883bc1794b07658b4ffe4ec387f38b87c22ca03e"}}]}] BACKPORT--> Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com> |
||
Konrad Szwarc
|
f6a3d1258e
|
[8.17] [EDR Workflows] OpenApi Missing Content - Response Actions (#212510) (#212870)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)](https://github.com/elastic/kibana/pull/212510) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-28T16:44:00Z","message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] OpenApi Missing Content - Response Actions","number":212510,"url":"https://github.com/elastic/kibana/pull/212510","mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212794","number":212794,"state":"MERGED","mergeCommit":{"sha":"3ceba17cbd76f89b72986190b8c77f5079706282","message":"[9.0] [EDR Workflows] OpenApi Missing Content - Response Actions (#212510) (#212794)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[EDR Workflows] OpenApi Missing Content - Response Actions\n(#212510)](https://github.com/elastic/kibana/pull/212510)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212510","number":212510,"mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Response Actions (#212510)\n\n## For reviewers:\nOnly `*.schema.yml` files were edited (excluding\n`*.bundled.schema.yml`). Rest of the changes comes from auto generation\nand can be ignored.\n\n## Description\n\nPart of DW team effort - elastic/security-team#11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/security/8.17/management-api-overview.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"2700a2a95158dc5d5a77ff074119b1b61f949310"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
229aac1adf
|
[8.17] [Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786) (#212822)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)](https://github.com/elastic/kibana/pull/212786) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-28T21:21:37Z","message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:all-open","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k","number":212786,"url":"https://github.com/elastic/kibana/pull/212786","mergeCommit":{"message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212786","number":212786,"mergeCommit":{"message":"[Security Solution][Notes] change upper limit for max unassociated notes advanced setting to be 10k instead of 1k (#212786)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/194947) made\nthe maximum number of unassociated notes an advanced settings so that\nuser can change the value within a certain limit. The intent was to\nallow that value to be between 1 and 10,000 (see acceptance criteria of\nthe [original ticket](https://github.com/elastic/kibana/issues/193097))\nbut we missed one 0 and the maximum value allowed got set to 1000.\n\nThis PR fixes that.\n\n#### Before\n\n\n\n#### After\n\n","sha":"eabf95d6dc157d1c1ac2bb8832c7021986285aef"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
Janki Salvi
|
9415fc950d
|
[8.17] [ResponseOps][Rules] Do not show connector not registered in action connectors modal (#212660) (#212778)
# Backport This will backport the following commits from `main` to `8.17`: - [[ResponseOps][Rules] Do not show connector not registered in action connectors modal (#212660)](https://github.com/elastic/kibana/pull/212660) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Janki Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-28T13:56:35Z","message":"[ResponseOps][Rules] Do not show connector not registered in action connectors modal (#212660)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/212584\nResolves https://github.com/elastic/kibana/issues/207185\n\n<img width=\"1917\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0b50f829-60a2-435e-9b76-74231d0bb54c\"\n/>\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"83f787ac24184b87a3a0f6d41380577666faeb42","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[ResponseOps][Rules] Do not show connector not registered in action connectors modal","number":212660,"url":"https://github.com/elastic/kibana/pull/212660","mergeCommit":{"message":"[ResponseOps][Rules] Do not show connector not registered in action connectors modal (#212660)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/212584\nResolves https://github.com/elastic/kibana/issues/207185\n\n<img width=\"1917\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0b50f829-60a2-435e-9b76-74231d0bb54c\"\n/>\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"83f787ac24184b87a3a0f6d41380577666faeb42"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212775","number":212775,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212773","number":212773,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212660","number":212660,"mergeCommit":{"message":"[ResponseOps][Rules] Do not show connector not registered in action connectors modal (#212660)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/212584\nResolves https://github.com/elastic/kibana/issues/207185\n\n<img width=\"1917\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/0b50f829-60a2-435e-9b76-74231d0bb54c\"\n/>\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"83f787ac24184b87a3a0f6d41380577666faeb42"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212774","number":212774,"state":"OPEN"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Pablo Machado
|
faabb4e47a
|
[SecuritySolution] Fix 8.17.3 branch by reverting bugfix (#212729)
## Summary Revert https://github.com/elastic/kibana/pull/212378 The Entity Analytics team backported a broken fix to 8.17.3, preventing users from installing the risk engine on multiple spaces. |
||
|
Kibana Machine
|
45321f8b9a
|
[8.17] Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529) (#212722)
# Backport This will backport the following commits from `main` to `8.17`: - [Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)](https://github.com/elastic/kibana/pull/212529) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steve Gordon","email":"sgordon@hotmail.co.uk"},"sourceCommit":{"committedDate":"2025-02-28T07:02:41Z","message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.18.0","v9.1.0","v8.17.3","v8.16.5"],"title":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard","number":212529,"url":"https://github.com/elastic/kibana/pull/212529","mergeCommit":{"message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212529","number":212529,"mergeCommit":{"message":"Fix panel to remove query filter for .NET OTel runtime metrics on curated dashboard (#212529)\n\n## Summary\n\nOne of the panels was applying a query to filter the results which\nbreaks the panel when using the EDOT SDK. This PR removes that query.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- ~[ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)~\n- ~[ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials~\n- ~[ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios~\n- ~[ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~\n- ~[ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.~\n- ~[ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed~\n- ~[ ] The PR description includes the appropriate Release Notes\nsection, and the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)~\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ]","sha":"e76a1968986904d4ab80e8193dd85edcffebd13d"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steve Gordon <sgordon@hotmail.co.uk> |
||
|
Kibana Machine
|
240b79a0ee
|
[8.17] [Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690) (#212697)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)](https://github.com/elastic/kibana/pull/212690) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T21:25:44Z","message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.18.1"],"title":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline","number":212690,"url":"https://github.com/elastic/kibana/pull/212690","mergeCommit":{"message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212690","number":212690,"mergeCommit":{"message":"[Security Solution][Notes] show timeline bottom bar on the notes management page to allow user to visualize timeline (#212690)\n\n## Summary\n\nThis previous [PR](https://github.com/elastic/kibana/pull/199374) that\nunified the notes management links introduced a small issue where the\nTimeline bottom bar was not shown anymore, and Timelines couldn't be\nopened from the icon in the notes table.\n\nThis PR brings back the Timeline feature to that page, which fixes the\nissue with Timeline not opening when clicking on the button in the\ntable.\n\n#### Before\n\n\nhttps://github.com/user-attachments/assets/ce3fdf1f-f7e4-43ff-b5c8-240f0e3a6770\n\n#### After\n\n\nhttps://github.com/user-attachments/assets/a8c7a39c-8913-4c12-8191-7e171ff5050e","sha":"c0c64a848983bd5debd7883ec2dee7ea52afce2c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
elastic-renovate-prod[bot]
|
43bea7f93b
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 6387bd4 (8.17) (#212631)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `c66fdaf` -> `6387bd4` | --- ### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
4b88c78903
|
[8.17] [EDR Workflows][Osquery] OpenApi Missing Content (#212032) (#212640)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows][Osquery] OpenApi Missing Content (#212032)](https://github.com/elastic/kibana/pull/212032) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T12:29:04Z","message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows][Osquery] OpenApi Missing Content","number":212032,"url":"https://github.com/elastic/kibana/pull/212032","mergeCommit":{"message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212032","number":212032,"mergeCommit":{"message":"[EDR Workflows][Osquery] OpenApi Missing Content (#212032)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-osqueryfindlivequeries\n\nChanges:\n1. Copied missing property descriptions from AsciiDoc to OpenApi\nproperties\n2. Copied existing AsciiDoc examples for both requests and responses\n3. Fixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"92867c697dc573867e6450249178d16110d34603"}}]}] BACKPORT--> --------- Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co> |
||
|
Kibana Machine
|
1d9706caad
|
[8.17] [Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611) (#212645)
# Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)](https://github.com/elastic/kibana/pull/212611) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-27T12:32:17Z","message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","backport:version","Feature:AutomaticImport","v9.1.0","backport:8.18"],"title":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs","number":212611,"url":"https://github.com/elastic/kibana/pull/212611","mergeCommit":{"message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212611","number":212611,"mergeCommit":{"message":"[Automatic Import] Fix Structured log flow to handle different type of structured syslogs (#212611)\n\n## Release note\nFix structured log flow to handle multiple types of structured logs.\n\n## Summary\nThe structured log flow has some issues where the KV header validation\nfails for some type of logs. This PR fixes the flow to match variety of\nstructured syslog messages.\n\nA variety of logs are tested.\n\n```\n[2025-01-03T07:48:58.989821Z] [DEBUG] AuthService - EventID=361a5289eaf8e42b4c195b9b | Message=\"Session expired\" | UserID=2882 | Duration=376ms\n[2025-01-29T17:34:18.989830Z] [ERROR] InventoryService - EventID=acbb20d3c955edf718e691d9 | Message=\"Item restocked\" | UserID=9656 | Duration=421ms\n[2025-01-11T21:51:54.989839Z] [ERROR] APIGateway - EventID=9c273d43b946020d5fdbe36c | Message=\"Response sent\" | UserID=1468 | Duration=409ms\n[2025-01-20T08:40:22.989848Z] [WARN] PaymentService - EventID=ae8c1425079119b848fa451cb7a | Message=\"3D Secure required\" | UserID=9353 | Duration=270ms\n```\n\n```\n2021-10-22 22:11:32,131 DEBUG [org.keycloak.events] (default task-3) type=CODE_TO_TOKEN, realmId=test, clientId=security-admin-console, userId=ce637d23--4fca-9088-1aea1d053e19, ipAddress=10.1.2.1, token_id=561459c0-75f1-46d4-986d, grant_type=authorization_code, refresh_token_type=Refresh, scope=openid, refresh_token_id=07434488-ca99-412a-c2e47c93d6d1, code_id=bae6e56e-368f-4809-48cfb6279f5e, client_auth_method=client-secret\n2021-10-22 22:12:09,871 DEBUG [org.keycloak.events] (default task-3) operationType=CREATE, realmId=test, clientId=7bcaf1cb-820a-40f1-75ced03ef03b, userId=ce637d23-b89c-4fca-1aea1d053e19, ipAddress=10.1.2.6, resourceType=USER, resourcePath=users/07972d16-b173-803d-90f211080f40\n```\n\n```\n[18/Feb/2025:22:39:18 +0000] CONNECT conn=730729 from=10.2.2.9:56518 to=10.2.1.14:4389 protocol=LDAP\n[18/Feb/2025:22:39:16 +0000] CONNECT conn=207223 from=10.2.1.24:55730 to=10.1.3.7:4389 protocol=LDAP\n```\n\n```\n<134>1 1647479580.487048774 MX84_2 airmarshal_events type=rogue_ssid_detected ssid='' bssid='AA:17:C8:D8:51' src='AA:17:C8:D8:51' dst='FF:FF:FF:FF:FF' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='35' fc_type='0' fc_subtype='8'\n<134>1 1647479604.334549372 MX84_5 airmarshal_events type=rogue_ssid_detected ssid='' bssid='92:17:C7:D8:51' src='92:17:C8:D8:51' dst='6A:3A:3E:85:F6' wired_mac='AC:17:C7:D8:51' vlan_id='0' channel='6' rssi='23' fc_type='0' fc_subtype='5'\n```\n\n### Checklist\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"f579f2d637ce6e7e51f15e32ba8c5d8ba554478e"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
Kibana Machine
|
0ec6573aa8
|
[8.17] [Data View Field] Fix popularity score bugs (#211201) (#212614)
# Backport This will backport the following commits from `main` to `8.17`: - [[Data View Field] Fix popularity score bugs (#211201)](https://github.com/elastic/kibana/pull/211201) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T10:34:22Z","message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","v9.0.0","Team:DataDiscovery","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Data View Field] Fix popularity score bugs ","number":211201,"url":"https://github.com/elastic/kibana/pull/211201","mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211201","number":211201,"mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"97260415030a3b816b3a8507c51c4a5184ff25df"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Charlotte Alexandra Wilson
|
f3192d7aed
|
[8.17] [refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441) (#212561)
# Backport This will backport the following commits from `main` to `8.17`: - [[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)](https://github.com/elastic/kibana/pull/212441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-26T13:29:21Z","message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["refactoring","release_note:skip","v9.0.0","Theme: entity_analytics","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel ","number":212441,"url":"https://github.com/elastic/kibana/pull/212441","mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212554","number":212554,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212519","number":212519,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212441","number":212441,"mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212556","number":212556,"state":"OPEN"}]}] BACKPORT--> |
||
Philippe Oberti
|
b86ad4dac3
|
[8.17] [Security Solution] Fixed Table height row rendering - Event Rendered View (#212130) (#212597)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)](https://github.com/elastic/kibana/pull/212130) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T22:36:50Z","message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fixed Table height row rendering - Event Rendered View","number":212130,"url":"https://github.com/elastic/kibana/pull/212130","mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212596","number":212596,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212130","number":212130,"mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212594","number":212594,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
|
Kibana Machine
|
86fb404db7
|
[8.17] [Fleet] Fix API key insertion into standalone agent policy (#212440) (#212578)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] Fix API key insertion into standalone agent policy (#212440)](https://github.com/elastic/kibana/pull/212440) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Satvikkaushal","email":"39619179+Satvikkaushal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-26T19:02:11Z","message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","💝community","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] Fix API key insertion into standalone agent policy","number":212440,"url":"https://github.com/elastic/kibana/pull/212440","mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212440","number":212440,"mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}}]}] BACKPORT--> Co-authored-by: Satvikkaushal <39619179+Satvikkaushal@users.noreply.github.com> |
||
Giorgos Bamparopoulos
|
899a7eb5da
|
[8.17] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#212388)
# Backport This will backport the following commits from `main` to `8.17`: - [[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)](https://github.com/elastic/kibana/pull/205694) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Giorgos Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T15:41:28Z","message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","backport:version","v8.18.0"],"title":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow","number":205694,"url":"https://github.com/elastic/kibana/pull/205694","mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205694","number":205694,"mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207866","number":207866,"state":"MERGED","mergeCommit":{"sha":"0d22f08c4bd7da291ab6037980512be9b57ce5d7","message":"[8.x] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#207866)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Observability Onboarding] Update values.yml file URL for the OTel\nK8s flow (#205694)](https://github.com/elastic/kibana/pull/205694)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>"}}]}] BACKPORT--> |
||
Ievgen Sorokopud
|
f65b7a1d66
|
[8.17] [Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122) (#212505)
# Backport This will backport the following commits from `main` to `8.17`: - [[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)](https://github.com/elastic/kibana/pull/212122) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T11:03:09Z","message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783)","number":212122,"url":"https://github.com/elastic/kibana/pull/212122","mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212501","number":212501,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212500","number":212500,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212122","number":212122,"mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4454a54133
|
[8.17] [Docs] Add missing setting in advanced options (#212528) (#212538)
# Backport This will backport the following commits from `main` to `8.17`: - [[Docs] Add missing setting in advanced options (#212528)](https://github.com/elastic/kibana/pull/212528) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T15:23:13Z","message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52","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","v8.13.0","v8.14.0","v8.15.0","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Docs] Add missing setting in advanced options","number":212528,"url":"https://github.com/elastic/kibana/pull/212528","mergeCommit":{"message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.13","8.14","8.15","8.16","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212528","number":212528,"mergeCommit":{"message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
José Luis González
|
1e06975863
|
[8.17] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212484)
# Backport This will backport the following commits from `main` to `8.17`: - [[Search][Connectors] Fixing custom connector icon rendering (#212225)](https://github.com/elastic/kibana/pull/212225) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2025-02-25T14:49:33Z","message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major","backport:version","v9.1.0"],"title":"[Search][Connectors] Fixing custom connector icon rendering","number":212225,"url":"https://github.com/elastic/kibana/pull/212225","mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212386","number":212386,"state":"MERGED","mergeCommit":{"sha":"e6799ea001e2ef5178294d3e7dc570e7861d19c7","message":"[9.0] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212386)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Search][Connectors] Fixing custom connector icon rendering\n(#212225)](https://github.com/elastic/kibana/pull/212225)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: José Luis González <joseluisgj@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212225","number":212225,"mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}}]}] BACKPORT--> |
||
Abhishek Bhatia
|
01a430a06c
|
[8.17] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#212378)
# Backport This will backport the following commits from `main` to `8.17`: - [[Entity Analytics] API changes for right placement of deleting the old component template (#199734)](https://github.com/elastic/kibana/pull/199734) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-18T15:07:13Z","message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","QA:Validated","Team:Entity Analytics","backport:version","v8.17.0","v8.16.1","v8.18.0"],"title":"[Entity Analytics] API changes for right placement of deleting the old component template","number":199734,"url":"https://github.com/elastic/kibana/pull/199734","mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199734","number":199734,"mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200673","number":200673,"state":"MERGED","mergeCommit":{"sha":"24cbc3ee37cca9610bb8848c7361deeb4dc63ac4","message":"[8.x] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200673)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/200591\",\"number\":200591,\"state\":\"MERGED\",\"mergeCommit\":{\"sha\":\"06999139d210464c236a3784c58b7e5dcbd64ce3\",\"message\":\"[8.16]\n[Entity Analytics] API changes for right placement of deleting the old\ncomponent template (#199734) (#200591)\\n\\n# Backport\\n\\nThis will\nbackport the following commits from `main` to `8.16`:\\n- [[Entity\nAnalytics] API changes for right placement of deleting the\\nold\ncomponent\ntemplate\\n(#199734)](https://github.com/elastic/kibana/pull/199734)\\n\\n<!---\nBackport version: 8.9.8 -->\\n\\n### Questions ?\\nPlease refer to the\n[Backport\ntool\\ndocumentation](https://github.com/sqren/backport)\\n\\n<!--BACKPORT\n[{\\\"author\\\":{\\\"name\\\":\\\"Abhishek\\nBhatia\\\",\\\"email\\\":\\\"117628830+abhishekbhatia1710@users.noreply.github.com\\\"},\\\"sourceCommit\\\":{\\\"committedDate\\\":\\\"2024-11-18T15:07:13Z\\\",\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\",\\\"branchLabelMapping\\\":{\\\"^v9.0.0$\\\":\\\"main\\\",\\\"^v8.17.0$\\\":\\\"8.x\\\",\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\":\\\"$1.$2\\\"}},\\\"sourcePullRequest\\\":{\\\"labels\\\":[\\\"bug\\\",\\\"release_note:fix\\\",\\\"v9.0.0\\\",\\\"Team:Entity\\nAnalytics\\\",\\\"backport:version\\\",\\\"v8.17.0\\\",\\\"v8.16.1\\\"],\\\"number\\\":199734,\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/199734\\\",\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},\\\"sourceBranch\\\":\\\"main\\\",\\\"suggestedTargetBranches\\\":[\\\"8.x\\\",\\\"8.16\\\"],\\\"targetPullRequestStates\\\":[{\\\"branch\\\":\\\"main\\\",\\\"label\\\":\\\"v9.0.0\\\",\\\"labelRegex\\\":\\\"^v9.0.0$\\\",\\\"isSourceBranch\\\":true,\\\"state\\\":\\\"MERGED\\\",\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/199734\\\",\\\"number\\\":199734,\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},{\\\"branch\\\":\\\"8.x\\\",\\\"label\\\":\\\"v8.17.0\\\",\\\"labelRegex\\\":\\\"^v8.17.0$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"},{\\\"branch\\\":\\\"8.16\\\",\\\"label\\\":\\\"v8.16.1\\\",\\\"labelRegex\\\":\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"}]}]\\nBACKPORT-->\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200591","number":200591,"state":"MERGED","mergeCommit":{"sha":"06999139d210464c236a3784c58b7e5dcbd64ce3","message":"[8.16] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200591)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Konrad Szwarc
|
83391ca5d9
|
[8.17] [EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205) (#212387)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)](https://github.com/elastic/kibana/pull/212205) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-25T13:18:56Z","message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] OpenApi Missing Content - Endpoint Management","number":212205,"url":"https://github.com/elastic/kibana/pull/212205","mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212374","number":212374,"state":"OPEN"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212373","number":212373,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212205","number":212205,"mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
84027ef899
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to c66fdaf (8.17) (#212394)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `0801a43` -> `c66fdaf` | --- ### 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Patryk Kopyciński
|
0ccc106cac
|
[8.17] Fix calling Sonnet 3.7 (#212372) (#212411)
# Backport This will backport the following commits from `main` to `8.17`: - [Fix calling Sonnet 3.7 (#212372)](https://github.com/elastic/kibana/pull/212372) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-02-25T15:41:55Z","message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"Fix calling Sonnet 3.7","number":212372,"url":"https://github.com/elastic/kibana/pull/212372","mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212399","number":212399,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212398","number":212398,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212372","number":212372,"mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |