mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 00:13:52 -04:00
81046 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Nick Partridge
|
6a61db01b9
|
[8.17] [Lens] Restore dynamic colouring by value for Last value agg (#209110) (#210878)
# Backport This will backport the following commits from `main` to `8.17`: - [[Lens] Restore dynamic colouring by value for Last value agg (#209110)](https://github.com/elastic/kibana/pull/209110) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T14:55:35Z","message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport missing","backport:prev-major","v9.1.0"],"title":"[Lens] Restore dynamic colouring by value for Last value agg","number":209110,"url":"https://github.com/elastic/kibana/pull/209110","mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209110","number":209110,"mergeCommit":{"message":"[Lens] Restore dynamic colouring by value for Last value agg (#209110)\n\n## Summary\n\nFixes #208924\n\nThis PR improves the numeric check for the Last value agg within the\nMetric chart type avoiding completely to access the active data and\nrather rely on the datasource configuration.\nThe new utility function in fact won't rely any more on active data\nrather on the Lens configuration itself, which is more robust, faster\nand flexible.\n\n<img width=\"2552\" alt=\"Screenshot 2025-01-31 at 14 30 12\"\nsrc=\"https://github.com/user-attachments/assets/5f8792db-40ff-497b-8e2f-0737c2932f92\"\n/>\n\n\n### Notes for testing\n\nI've created a testing dashboard with all the possible combinations of\ncolouring for metric and tables.\n\n\n[last_value_dashboard.ndjson.txt](https://github.com/user-attachments/files/18618905/last_value_dashboard.ndjson.txt)\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Release note\n\nThis fixes an issue where dynamic colouring has been disabled from Last\nvalue aggregation types.","sha":"abba6675e29b28b91daea1f46d2ff48363ab78ab"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
Konrad Szwarc
|
244d3a654c
|
[8.17] [EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348) (#210833)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)](https://github.com/elastic/kibana/pull/210348) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T13:02:00Z","message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts","number":210348,"url":"https://github.com/elastic/kibana/pull/210348","mergeCommit":{"message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210822","number":210822,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210830","number":210830,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210348","number":210348,"mergeCommit":{"message":"[EDR Workflows] Unskip uninstall_agent_from_host.cy.ts (#210348)\n\nIt seems the reason for skipping was a temporary hiccup that is no\nlonger occurring. Unskipping after verifying with the flaky test runner.\n\ncloses https://github.com/elastic/kibana/issues/183638\ncloses https://github.com/elastic/kibana/issues/207423\n\nFlaky test runner (x50)\n✅ `main`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7857\n✅ `9.0`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7858\n✅ `8.18`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7859\n✅ `8.17`\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7860","sha":"bc08247b7f5eb46fb3d7d1624d74bef6ba195a06"}}]}] BACKPORT--> |
||
Julian Gernun
|
aba27b870c
|
[8.17] [Response Ops][Cases] Cases with empty string assignees throwing error (#209973) (#210755)
# Backport This will backport the following commits from `main` to `8.17`: - [[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)](https://github.com/elastic/kibana/pull/209973) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T06:06:44Z","message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996","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:Cases","backport:prev-major","v8.18.0","v8.16.4","v8.17.2","v9.1.0","v8.19.0"],"title":"[Response Ops][Cases] Cases with empty string assignees throwing error","number":209973,"url":"https://github.com/elastic/kibana/pull/209973","mergeCommit":{"message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996"}},"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/210733","number":210733,"state":"MERGED","mergeCommit":{"sha":"ee04349a417e47004062aeb796092f6813122192","message":"[9.0] [Response Ops][Cases] Cases with empty string assignees throwing error (#209973) (#210733)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Response Ops][Cases] Cases with empty string assignees throwing\nerror (#209973)](https://github.com/elastic/kibana/pull/209973)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Julian\nGernun\",\"email\":\"17549662+jcger@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T06:06:44Z\",\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\",\"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:Cases\",\"backport:prev-major\",\"v8.18.0\",\"v8.16.4\",\"v8.17.2\",\"v9.1.0\"],\"title\":\"[Response\nOps][Cases] Cases with empty string assignees throwing\nerror\",\"number\":209973,\"url\":\"https://github.com/elastic/kibana/pull/209973\",\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"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\":\"8.16\",\"label\":\"v8.16.4\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.2\",\"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/209973\",\"number\":209973,\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210731","number":210731,"state":"OPEN"},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/209973","number":209973,"mergeCommit":{"message":"[Response Ops][Cases] Cases with empty string assignees throwing error (#209973)\n\n## Summary\nCloses https://github.com/elastic/kibana/issues/209950\n\nTesting steps in referenced issue\n\n## Release note\nFix error message in cases list if case assignee is an empty string","sha":"0897d0878622db9d9747e2bc1292d647c09ad996"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210732","number":210732,"state":"MERGED","mergeCommit":{"sha":"8b98614e9dbdaaeaebac56d633cd2b7c35af01bd","message":"[8.x] [Response Ops][Cases] Cases with empty string assignees throwing error (#209973) (#210732)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Response Ops][Cases] Cases with empty string assignees throwing\nerror (#209973)](https://github.com/elastic/kibana/pull/209973)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Julian\nGernun\",\"email\":\"17549662+jcger@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T06:06:44Z\",\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\",\"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:Cases\",\"backport:prev-major\",\"v8.18.0\",\"v8.16.4\",\"v8.17.2\",\"v9.1.0\"],\"title\":\"[Response\nOps][Cases] Cases with empty string assignees throwing\nerror\",\"number\":209973,\"url\":\"https://github.com/elastic/kibana/pull/209973\",\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"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\":\"8.16\",\"label\":\"v8.16.4\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.2\",\"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/209973\",\"number\":209973,\"mergeCommit\":{\"message\":\"[Response\nOps][Cases] Cases with empty string assignees throwing error\n(#209973)\\n\\n## Summary\\nCloses\nhttps://github.com/elastic/kibana/issues/209950\\n\\nTesting steps in\nreferenced issue\\n\\n## Release note\\nFix error message in cases list if\ncase assignee is an empty\nstring\",\"sha\":\"0897d0878622db9d9747e2bc1292d647c09ad996\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>"}}]}] BACKPORT--> |
||
Yngrid Coello
|
0293ec13ce
|
[8.17][Dataset quality] 🐞 Rely solely on _index instead of data_stream properties (#210329) (#210777)
Manual backport of https://github.com/elastic/kibana/pull/210329 |
||
Kibana Machine
|
9751086d56
|
[8.17] [SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748) (#210786)
# Backport This will backport the following commits from `main` to `8.17`: - [[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)](https://github.com/elastic/kibana/pull/210748) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T11:19:11Z","message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com/elastic/kibana/pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test","number":210748,"url":"https://github.com/elastic/kibana/pull/210748","mergeCommit":{"message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com/elastic/kibana/pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7"}},"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/210748","number":210748,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Remove hardcoded agent version check for scan test (#210748)\n\n## Summary\n\n> [!NOTE]\n> This PR is NOT unskipping the test to minimize conflicts during\nbackports.\n> Manual backports maybe needed as some auto backports may fail as\n`security_solution` folder has moved between `8.16` and `8.17`\n\nRemoves hardcoded agent version for test setup that was added before\n8.15 GA.\n\nrefs\nhttps://github.com/elastic/kibana/pull/189174#discussion_r1700257185\ncloses https://github.com/elastic/kibana/issues/210364\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"60918882ead47a8b94bff7716e79bdd6083a98a7"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com> |
||
Dmitrii Shevchenko
|
6259401adf
|
[8.17] [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551) (#210773)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551)](https://github.com/elastic/kibana/pull/209551) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T17:12:03Z","message":"[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551)\n\n**Resolves: https://github.com/elastic/kibana/issues/208357**\n**Resolves: https://github.com/elastic/kibana/issues/208355**\n\n## Summary \n\nTo prevent possible OOM errors, we need to limit concurrent requests to\nprebuilt rule routes (see attached tickets for more details).\n\n- `installation/_perform` and `upgrade/_perform` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons\n\n- `prebuilt_rules/_bootstrap` endpoint\n- Install prebuilt rules and endpoint packages sequentially instead of\nin parallel to prevent from having them both downloaded into memory\nsimultaneously.\n- Added a 30-minute socket timeout to prevent the proxy from closing the\nconnection while rule installation is in progress.\n- Introduced a `throttleRequests` wrapper, ensuring the endpoint handler\nis called only once when multiple concurrent requests are received.\n- The first request triggers the handler, while subsequent requests wait\nfor the first one to complete and reuse its result.\n- This prevents costly prebuilt rule package installation from running\nin parallel.\n- Reusing the response ensures the frontend correctly invalidates cached\nprebuilt rule queries. Since concurrent frontend requests should receive\nthe same installed package information, responding with 421 and using\nthe retry logic as in cases above is not an option here because the\nsecond request would receive a package installation skipped response\nleading to no cache invalidation.\n\n- `installation/_review` and `upgrade/_review` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons","sha":"c5557f33213f699acd9bb656af9166b1449d18f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","performance","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3"],"title":"[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes","number":209551,"url":"https://github.com/elastic/kibana/pull/209551","mergeCommit":{"message":"[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551)\n\n**Resolves: https://github.com/elastic/kibana/issues/208357**\n**Resolves: https://github.com/elastic/kibana/issues/208355**\n\n## Summary \n\nTo prevent possible OOM errors, we need to limit concurrent requests to\nprebuilt rule routes (see attached tickets for more details).\n\n- `installation/_perform` and `upgrade/_perform` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons\n\n- `prebuilt_rules/_bootstrap` endpoint\n- Install prebuilt rules and endpoint packages sequentially instead of\nin parallel to prevent from having them both downloaded into memory\nsimultaneously.\n- Added a 30-minute socket timeout to prevent the proxy from closing the\nconnection while rule installation is in progress.\n- Introduced a `throttleRequests` wrapper, ensuring the endpoint handler\nis called only once when multiple concurrent requests are received.\n- The first request triggers the handler, while subsequent requests wait\nfor the first one to complete and reuse its result.\n- This prevents costly prebuilt rule package installation from running\nin parallel.\n- Reusing the response ensures the frontend correctly invalidates cached\nprebuilt rule queries. Since concurrent frontend requests should receive\nthe same installed package information, responding with 421 and using\nthe retry logic as in cases above is not an option here because the\nsecond request would receive a package installation skipped response\nleading to no cache invalidation.\n\n- `installation/_review` and `upgrade/_review` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons","sha":"c5557f33213f699acd9bb656af9166b1449d18f9"}},"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/210642","number":210642,"state":"MERGED","mergeCommit":{"sha":"df87081d8a574c6b0bb2d9fc026776502622dc11","message":"[9.0] [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551) (#210642)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Security Solution] Added concurrency limits and request throttling\nto prebuilt rule routes\n(#209551)](https://github.com/elastic/kibana/pull/209551)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-11T17:12:03Z\",\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"performance\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\",\"v8.17.3\"],\"title\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule\nroutes\",\"number\":209551,\"url\":\"https://github.com/elastic/kibana/pull/209551\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},\"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/209551\",\"number\":209551,\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},{\"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\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210640","number":210640,"state":"MERGED","mergeCommit":{"sha":"2bd85b19aa84575ec0745ba2ad24d4c7718d824f","message":"[8.18] [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551) (#210640)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Security Solution] Added concurrency limits and request throttling\nto prebuilt rule routes\n(#209551)](https://github.com/elastic/kibana/pull/209551)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-11T17:12:03Z\",\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"performance\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\",\"v8.17.3\"],\"title\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule\nroutes\",\"number\":209551,\"url\":\"https://github.com/elastic/kibana/pull/209551\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},\"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/209551\",\"number\":209551,\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},{\"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\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209551","number":209551,"mergeCommit":{"message":"[Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551)\n\n**Resolves: https://github.com/elastic/kibana/issues/208357**\n**Resolves: https://github.com/elastic/kibana/issues/208355**\n\n## Summary \n\nTo prevent possible OOM errors, we need to limit concurrent requests to\nprebuilt rule routes (see attached tickets for more details).\n\n- `installation/_perform` and `upgrade/_perform` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons\n\n- `prebuilt_rules/_bootstrap` endpoint\n- Install prebuilt rules and endpoint packages sequentially instead of\nin parallel to prevent from having them both downloaded into memory\nsimultaneously.\n- Added a 30-minute socket timeout to prevent the proxy from closing the\nconnection while rule installation is in progress.\n- Introduced a `throttleRequests` wrapper, ensuring the endpoint handler\nis called only once when multiple concurrent requests are received.\n- The first request triggers the handler, while subsequent requests wait\nfor the first one to complete and reuse its result.\n- This prevents costly prebuilt rule package installation from running\nin parallel.\n- Reusing the response ensures the frontend correctly invalidates cached\nprebuilt rule queries. Since concurrent frontend requests should receive\nthe same installed package information, responding with 421 and using\nthe retry logic as in cases above is not an option here because the\nsecond request would receive a package installation skipped response\nleading to no cache invalidation.\n\n- `installation/_review` and `upgrade/_review` endpoints\n- Concurrency is limited to one parallel call. If another call is made\nsimultaneously, the server responds with 429 Too Many Requests.\n- On the front end, all rule install and upgrade operations are retried\nin case of a 429 response. This ensures proper handling when a user\nclicks multiple times an update or install rule buttons","sha":"c5557f33213f699acd9bb656af9166b1449d18f9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210641","number":210641,"state":"MERGED","mergeCommit":{"sha":"8018c82f7d92b1d4798dea3c0a677bae740d4f8a","message":"[8.x] [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (#209551) (#210641)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Security Solution] Added concurrency limits and request throttling\nto prebuilt rule routes\n(#209551)](https://github.com/elastic/kibana/pull/209551)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dmitrii\nShevchenko\",\"email\":\"dmitrii.shevchenko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-11T17:12:03Z\",\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"performance\",\"v9.0.0\",\"Team:Detections\nand Resp\",\"Team: SecuritySolution\",\"Team:Detection Rule\nManagement\",\"Feature:Prebuilt Detection\nRules\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\",\"v8.17.3\"],\"title\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule\nroutes\",\"number\":209551,\"url\":\"https://github.com/elastic/kibana/pull/209551\",\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},\"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/209551\",\"number\":209551,\"mergeCommit\":{\"message\":\"[Security\nSolution] Added concurrency limits and request throttling to prebuilt\nrule routes (#209551)\\n\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208357**\\n**Resolves:\nhttps://github.com/elastic/kibana/issues/208355**\\n\\n## Summary \\n\\nTo\nprevent possible OOM errors, we need to limit concurrent requests\nto\\nprebuilt rule routes (see attached tickets for more details).\\n\\n-\n`installation/_perform` and `upgrade/_perform` endpoints\\n- Concurrency\nis limited to one parallel call. If another call is\nmade\\nsimultaneously, the server responds with 429 Too Many Requests.\\n-\nOn the front end, all rule install and upgrade operations are\nretried\\nin case of a 429 response. This ensures proper handling when a\nuser\\nclicks multiple times an update or install rule buttons\\n\\n-\n`prebuilt_rules/_bootstrap` endpoint\\n- Install prebuilt rules and\nendpoint packages sequentially instead of\\nin parallel to prevent from\nhaving them both downloaded into memory\\nsimultaneously.\\n- Added a\n30-minute socket timeout to prevent the proxy from closing\nthe\\nconnection while rule installation is in progress.\\n- Introduced a\n`throttleRequests` wrapper, ensuring the endpoint handler\\nis called\nonly once when multiple concurrent requests are received.\\n- The first\nrequest triggers the handler, while subsequent requests wait\\nfor the\nfirst one to complete and reuse its result.\\n- This prevents costly\nprebuilt rule package installation from running\\nin parallel.\\n- Reusing\nthe response ensures the frontend correctly invalidates cached\\nprebuilt\nrule queries. Since concurrent frontend requests should receive\\nthe\nsame installed package information, responding with 421 and using\\nthe\nretry logic as in cases above is not an option here because the\\nsecond\nrequest would receive a package installation skipped response\\nleading\nto no cache invalidation.\\n\\n- `installation/_review` and\n`upgrade/_review` endpoints\\n- Concurrency is limited to one parallel\ncall. If another call is made\\nsimultaneously, the server responds with\n429 Too Many Requests.\\n- On the front end, all rule install and upgrade\noperations are retried\\nin case of a 429 response. This ensures proper\nhandling when a user\\nclicks multiple times an update or install rule\nbuttons\",\"sha\":\"c5557f33213f699acd9bb656af9166b1449d18f9\"}},{\"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\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Sergi Romeu
|
3014b85ac7
|
[8.17] [APM] Remove error.id in getErrorGroupMainStatistics query as it's not used (#210613) (#210763)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (#210613)](https://github.com/elastic/kibana/pull/210613) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T18:13:51Z","message":"[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (#210613)\n\n## Summary\n\nCloses #210610\n\nThis PR removes `error.id` field from being queried at\n`getErrorGroupMainStatistics`, as it was not being used, as it was\nrequired. If we didn't have this field, the endpoint call would crash.","sha":"46cd29e60be24fa3d39b2b364973e0e9b10659b7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","backport:8.17","v9.1.0","backport:8.18"],"title":"[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used","number":210613,"url":"https://github.com/elastic/kibana/pull/210613","mergeCommit":{"message":"[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (#210613)\n\n## Summary\n\nCloses #210610\n\nThis PR removes `error.id` field from being queried at\n`getErrorGroupMainStatistics`, as it was not being used, as it was\nrequired. If we didn't have this field, the endpoint call would crash.","sha":"46cd29e60be24fa3d39b2b364973e0e9b10659b7"}},"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/210677","number":210677,"state":"MERGED","mergeCommit":{"sha":"dbe7cc3b4f4b21484f5bb4b26e47fbe541b83fab","message":"[9.0] [APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (#210613) (#210677)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[APM] Remove `error.id` in\n`getErrorGroupMainStatistics` query as it's not used\n(#210613)](https://github.com/elastic/kibana/pull/210613)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Sergi\nRomeu\",\"email\":\"sergi.romeu@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-11T18:13:51Z\",\"message\":\"[APM]\nRemove `error.id` in `getErrorGroupMainStatistics` query as it's not\nused (#210613)\\n\\n## Summary\\n\\nCloses #210610\\n\\nThis PR removes\n`error.id` field from being queried at\\n`getErrorGroupMainStatistics`,\nas it was not being used, as it was\\nrequired. If we didn't have this\nfield, the endpoint call would\ncrash.\",\"sha\":\"46cd29e60be24fa3d39b2b364973e0e9b10659b7\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"v9.0.0\",\"apm\",\"Team:obs-ux-infra_services\",\"backport:version\",\"backport:8.17\",\"v9.1.0\",\"backport:8.18\"],\"title\":\"[APM]\nRemove `error.id` in `getErrorGroupMainStatistics` query as it's not\nused\",\"number\":210613,\"url\":\"https://github.com/elastic/kibana/pull/210613\",\"mergeCommit\":{\"message\":\"[APM]\nRemove `error.id` in `getErrorGroupMainStatistics` query as it's not\nused (#210613)\\n\\n## Summary\\n\\nCloses #210610\\n\\nThis PR removes\n`error.id` field from being queried at\\n`getErrorGroupMainStatistics`,\nas it was not being used, as it was\\nrequired. If we didn't have this\nfield, the endpoint call would\ncrash.\",\"sha\":\"46cd29e60be24fa3d39b2b364973e0e9b10659b7\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/210613\",\"number\":210613,\"mergeCommit\":{\"message\":\"[APM]\nRemove `error.id` in `getErrorGroupMainStatistics` query as it's not\nused (#210613)\\n\\n## Summary\\n\\nCloses #210610\\n\\nThis PR removes\n`error.id` field from being queried at\\n`getErrorGroupMainStatistics`,\nas it was not being used, as it was\\nrequired. If we didn't have this\nfield, the endpoint call would\ncrash.\",\"sha\":\"46cd29e60be24fa3d39b2b364973e0e9b10659b7\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Sergi Romeu <sergi.romeu@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210613","number":210613,"mergeCommit":{"message":"[APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (#210613)\n\n## Summary\n\nCloses #210610\n\nThis PR removes `error.id` field from being queried at\n`getErrorGroupMainStatistics`, as it was not being used, as it was\nrequired. If we didn't have this field, the endpoint call would crash.","sha":"46cd29e60be24fa3d39b2b364973e0e9b10659b7"}},{"url":"https://github.com/elastic/kibana/pull/210761","number":210761,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/210762","number":210762,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> |
||
Khristinin Nikita
|
c16c2de770
|
Revert "[8.17] Remove beta badge for manual rule run (#209535) (#2100… (#210206)
Should be only at 8.18 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Tiago Costa
|
4bb4532af6
|
chore(NA): bump version to 8.17.3 (#210655)
Usually bump from 8.17.2 to 8.17.3 |
||
|
Tiago Costa
|
670073a0bd
|
skip flaky suite (#183638) | ||
|
Kibana Machine
|
6c01dd6329
|
[8.17] chore(dep): bump `store2` from `2.12.0` to `2.14.4` (#210530) (#210661)
# Backport This will backport the following commits from `main` to `8.17`: - [chore(dep): bump `store2` from `2.12.0` to `2.14.4` (#210530)](https://github.com/elastic/kibana/pull/210530) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T17:39:48Z","message":"chore(dep): bump `store2` from `2.12.0` to `2.14.4` (#210530)\n\n## Summary\n\nBump `store2` from `2.12.0` to `2.14.4` (transitive dependency of the\nstorybook package).","sha":"069734d9db47f8f252446749808409ed198b8e16","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","dependencies","backport:all-open","v9.1.0"],"title":"chore(dep): bump `store2` from `2.12.0` to `2.14.4`","number":210530,"url":"https://github.com/elastic/kibana/pull/210530","mergeCommit":{"message":"chore(dep): bump `store2` from `2.12.0` to `2.14.4` (#210530)\n\n## Summary\n\nBump `store2` from `2.12.0` to `2.14.4` (transitive dependency of the\nstorybook package).","sha":"069734d9db47f8f252446749808409ed198b8e16"}},"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/210530","number":210530,"mergeCommit":{"message":"chore(dep): bump `store2` from `2.12.0` to `2.14.4` (#210530)\n\n## Summary\n\nBump `store2` from `2.12.0` to `2.14.4` (transitive dependency of the\nstorybook package).","sha":"069734d9db47f8f252446749808409ed198b8e16"}}]}] BACKPORT--> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> |
||
|
Kibana Machine
|
42ae1bc925
|
[8.17] [Synthetics] Fix flaky tests for alerting default !! (#203220) (#210570)
# Backport This will backport the following commits from `main` to `8.17`: - [[Synthetics] Fix flaky tests for alerting default !! (#203220)](https://github.com/elastic/kibana/pull/203220) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-12-06T11:54:07Z","message":"[Synthetics] Fix flaky tests for alerting default !! (#203220)\n\n## Summary\r\n\r\nFix flaky tests for alerting default, removed unecessary code.\r\n\r\nI tested locally 30 times and it has been fixed now.","sha":"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff","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","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Synthetics] Fix flaky tests for alerting default !!","number":203220,"url":"https://github.com/elastic/kibana/pull/203220","mergeCommit":{"message":"[Synthetics] Fix flaky tests for alerting default !! (#203220)\n\n## Summary\r\n\r\nFix flaky tests for alerting default, removed unecessary code.\r\n\r\nI tested locally 30 times and it has been fixed now.","sha":"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203220","number":203220,"mergeCommit":{"message":"[Synthetics] Fix flaky tests for alerting default !! (#203220)\n\n## Summary\r\n\r\nFix flaky tests for alerting default, removed unecessary code.\r\n\r\nI tested locally 30 times and it has been fixed now.","sha":"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/203232","number":203232,"state":"MERGED","mergeCommit":{"sha":"9cdf4d21a2adf8cf14abad6f18375e993942dabc","message":"[8.x] [Synthetics] Fix flaky tests for alerting default !! (#203220) (#203232)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Synthetics] Fix flaky tests for alerting default !!\n(#203220)](https://github.com/elastic/kibana/pull/203220)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Shahzad\",\"email\":\"shahzad31comp@gmail.com\"},\"sourceCommit\":{\"committedDate\":\"2024-12-06T11:54:07Z\",\"message\":\"[Synthetics]\nFix flaky tests for alerting default !! (#203220)\\n\\n##\nSummary\\r\\n\\r\\nFix flaky tests for alerting default, removed unecessary\ncode.\\r\\n\\r\\nI tested locally 30 times and it has been fixed\nnow.\",\"sha\":\"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"ci:project-deploy-observability\",\"Team:obs-ux-management\"],\"title\":\"[Synthetics]\nFix flaky tests for alerting default\n!!\",\"number\":203220,\"url\":\"https://github.com/elastic/kibana/pull/203220\",\"mergeCommit\":{\"message\":\"[Synthetics]\nFix flaky tests for alerting default !! (#203220)\\n\\n##\nSummary\\r\\n\\r\\nFix flaky tests for alerting default, removed unecessary\ncode.\\r\\n\\r\\nI tested locally 30 times and it has been fixed\nnow.\",\"sha\":\"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff\"}},\"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/203220\",\"number\":203220,\"mergeCommit\":{\"message\":\"[Synthetics]\nFix flaky tests for alerting default !! (#203220)\\n\\n##\nSummary\\r\\n\\r\\nFix flaky tests for alerting default, removed unecessary\ncode.\\r\\n\\r\\nI tested locally 30 times and it has been fixed\nnow.\",\"sha\":\"dc77e8c149abc7a0bc2d9d3c65db0533ce45e4ff\"}}]}] BACKPORT-->\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
bb332236e6
|
[8.17] [Fleet] EPM - Fix error message for data stream settings update (#210330) (#210540)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] EPM - Fix error message for data stream settings update (#210330)](https://github.com/elastic/kibana/pull/210330) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T11:25:13Z","message":"[Fleet] EPM - Fix error message for data stream settings update (#210330)\n\n## Summary\r\n\r\nDuring package installation, failure to update the default pipeline for\r\ndata streams currently has a misleading error message. This PR corrects\r\nthis and adds the original error message to improve clarity.\r\n\r\n### Identify risks\r\n\r\nN/A\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2f4fb3ff2f28384ed2e2ffabee74b678651f5bb9","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] EPM - Fix error message for data stream settings update","number":210330,"url":"https://github.com/elastic/kibana/pull/210330","mergeCommit":{"message":"[Fleet] EPM - Fix error message for data stream settings update (#210330)\n\n## Summary\r\n\r\nDuring package installation, failure to update the default pipeline for\r\ndata streams currently has a misleading error message. This PR corrects\r\nthis and adds the original error message to improve clarity.\r\n\r\n### Identify risks\r\n\r\nN/A\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2f4fb3ff2f28384ed2e2ffabee74b678651f5bb9"}},"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/210330","number":210330,"mergeCommit":{"message":"[Fleet] EPM - Fix error message for data stream settings update (#210330)\n\n## Summary\r\n\r\nDuring package installation, failure to update the default pipeline for\r\ndata streams currently has a misleading error message. This PR corrects\r\nthis and adds the original error message to improve clarity.\r\n\r\n### Identify risks\r\n\r\nN/A\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"2f4fb3ff2f28384ed2e2ffabee74b678651f5bb9"}}]}] BACKPORT--> Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co> |
||
|
Kibana Machine
|
465bb1a018
|
[8.17] [Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141) (#210525)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)](https://github.com/elastic/kibana/pull/209141) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kenneth Kreindler","email":"42113355+KDKHD@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T10:18:02Z","message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x]\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- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### 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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:Security Generative AI","v9.1.0"],"title":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table","number":209141,"url":"https://github.com/elastic/kibana/pull/209141","mergeCommit":{"message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x]\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- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### 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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43"}},"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/209141","number":209141,"mergeCommit":{"message":"[Security Solution] [KB Management] Fix sorting by name in the kb entries table (#209141)\n\nFixes https://github.com/elastic/kibana/issues/199253\r\n\r\n## Summary\r\n\r\nFixes the issue where KB entries in knowledge base management were not\r\nsorting correctly by name. Previously, entries with names starting with\r\nuppercase letters appeared before those with lowercase names, instead of\r\nfollowing a case-insensitive alphabetical order. This update ensures\r\nproper sorting regardless of letter case.\r\n\r\nBefore:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1657fce4-abba-4672-aaa8-8c5c6c660c98\"\r\n/>\r\n\r\n\r\nAfter:\r\n<img width=\"3120\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/10d1f3fc-f6db-4b5b-b67b-8b8ae7250dd4\"\r\n/>\r\n\r\n\r\n\r\nHow to test:\r\n- See instructions in the issue. Create uppercase and lowercase KB\r\nentries (e.g. A,a,b,B,c,C. Create the entries in that order).\r\n- Reorder the table based on name and check the ordering makes sense.\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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x]\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- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] 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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### 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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a1356ffb9f10b0958553ddab2b7d8332fc495f43"}}]}] BACKPORT--> --------- Co-authored-by: Kenneth Kreindler <42113355+KDKHD@users.noreply.github.com> |
||
Julia Bardi
|
1d710a2b1a
|
[8.17][Fleet] update component templates with deprecated setting (#210200) (#210350)
Backport https://github.com/elastic/kibana/pull/210200 to 8.17 |
||
|
Kibana Machine
|
a74534fb87
|
[8.17] [Automatic Import] Handle empty categorization results (#210420) (#210447)
# Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Handle empty categorization results (#210420)](https://github.com/elastic/kibana/pull/210420) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T19:07:05Z","message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Handle empty categorization results","number":210420,"url":"https://github.com/elastic/kibana/pull/210420","mergeCommit":{"message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b"}},"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/210420","number":210420,"mergeCommit":{"message":"[Automatic Import] Handle empty categorization results (#210420)","sha":"3ba912f6c21e1d1fecdcdf99a5fcfd1ccd1f586b"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Umberto Pepato
|
1463a469bf
|
[8.17] [ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action (#209559) (#210387)
# Backport This will backport the following commits from `main` to `8.17`: - [[ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action (#209559)](https://github.com/elastic/kibana/pull/209559) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T12:52:07Z","message":"[ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action (#209559)\n\n## Summary\r\n\r\nWraps the stack alerts page search bar's filter controls embeddable into\r\nan `ErrorBoundary`, showing a fallback callout with a call-to-action to\r\nreset the persisted state of the filters. This prevents the whole page\r\nfrom crashing in case of errors in the embeddable, and provides a more\r\nuser-friendly way to gracefully recover from the error caused by\r\nhttps://github.com/elastic/kibana/pull/190561 in the condition that\r\nmakes [our fix](https://github.com/elastic/kibana/pull/194785)\r\nineffective ([visiting the page on `8.15` and then updating to\r\n`8.16+`](https://github.com/elastic/sdh-kibana/issues/5219#issuecomment-2633560380)).\r\n\r\n<img width=\"1007\" alt=\"Alert filter controls error callout\"\r\nsrc=\"https://github.com/user-attachments/assets/0c447f89-24f6-4d07-b7a1-97b13a267121\"\r\n/>\r\n\r\n## Release Notes\r\n\r\nProvides a fallback view to recover from Stack Alerts page filters bar\r\nerrors.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fca78b9826133c81d737f3d052f3423d5ddd6027","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v9.0.0","backport:prev-major","v8.18.0","v8.16.4","v8.17.2","v9.1.0"],"title":"[ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action","number":209559,"url":"https://github.com/elastic/kibana/pull/209559","mergeCommit":{"message":"[ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action (#209559)\n\n## Summary\r\n\r\nWraps the stack alerts page search bar's filter controls embeddable into\r\nan `ErrorBoundary`, showing a fallback callout with a call-to-action to\r\nreset the persisted state of the filters. This prevents the whole page\r\nfrom crashing in case of errors in the embeddable, and provides a more\r\nuser-friendly way to gracefully recover from the error caused by\r\nhttps://github.com/elastic/kibana/pull/190561 in the condition that\r\nmakes [our fix](https://github.com/elastic/kibana/pull/194785)\r\nineffective ([visiting the page on `8.15` and then updating to\r\n`8.16+`](https://github.com/elastic/sdh-kibana/issues/5219#issuecomment-2633560380)).\r\n\r\n<img width=\"1007\" alt=\"Alert filter controls error callout\"\r\nsrc=\"https://github.com/user-attachments/assets/0c447f89-24f6-4d07-b7a1-97b13a267121\"\r\n/>\r\n\r\n## Release Notes\r\n\r\nProvides a fallback view to recover from Stack Alerts page filters bar\r\nerrors.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fca78b9826133c81d737f3d052f3423d5ddd6027"}},"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/210362","number":210362,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210360","number":210360,"state":"OPEN"},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/209559","number":209559,"mergeCommit":{"message":"[ResponseOps][Alerts] Wrap Stack Alerts page filter controls in error boundary with fix call-to-action (#209559)\n\n## Summary\r\n\r\nWraps the stack alerts page search bar's filter controls embeddable into\r\nan `ErrorBoundary`, showing a fallback callout with a call-to-action to\r\nreset the persisted state of the filters. This prevents the whole page\r\nfrom crashing in case of errors in the embeddable, and provides a more\r\nuser-friendly way to gracefully recover from the error caused by\r\nhttps://github.com/elastic/kibana/pull/190561 in the condition that\r\nmakes [our fix](https://github.com/elastic/kibana/pull/194785)\r\nineffective ([visiting the page on `8.15` and then updating to\r\n`8.16+`](https://github.com/elastic/sdh-kibana/issues/5219#issuecomment-2633560380)).\r\n\r\n<img width=\"1007\" alt=\"Alert filter controls error callout\"\r\nsrc=\"https://github.com/user-attachments/assets/0c447f89-24f6-4d07-b7a1-97b13a267121\"\r\n/>\r\n\r\n## Release Notes\r\n\r\nProvides a fallback view to recover from Stack Alerts page filters bar\r\nerrors.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fca78b9826133c81d737f3d052f3423d5ddd6027"}},{"url":"https://github.com/elastic/kibana/pull/210361","number":210361,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Yara Tercero
|
48f3d1303c
|
[8.17] [Detection Engine][Docs] Updating examples to meet old ascii docs (#207558) (#209943)
# Backport This will backport the following commits from `main` to `8.17`: - [[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)](https://github.com/elastic/kibana/pull/207558) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-05T07:02:48Z","message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74","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:Detection Engine","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[Detection Engine][Docs] Updating examples to meet old ascii docs","number":207558,"url":"https://github.com/elastic/kibana/pull/207558","mergeCommit":{"message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74"}},"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/207558","number":207558,"mergeCommit":{"message":"[Detection Engine][Docs] Updating examples to meet old ascii docs (#207558)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Alert and migration APIs.","sha":"d4199dcac1f0bff5f3511e79a860c77534b35c74"}}]}] BACKPORT--> |
||
Cauê Marcondes
|
e0a4cab1cd
|
[8.17] [APM] Missing items in the trace waterfall shouldn't break it entirely (#210210) (#210397)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)](https://github.com/elastic/kibana/pull/210210) <!--- Backport version: 9.6.4 --> ### 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-02-10T14:04:33Z","message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7","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] Missing items in the trace waterfall shouldn't break it entirely","number":210210,"url":"https://github.com/elastic/kibana/pull/210210","mergeCommit":{"message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7"}},"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/210210","number":210210,"mergeCommit":{"message":"[APM] Missing items in the trace waterfall shouldn't break it entirely (#210210)\n\ncloses https://github.com/elastic/kibana/issues/120464\r\n\r\nWhen orphan items are found, I am re-parenting them to the root\r\ntransaction and adding an indication.\r\n\r\nTest architecture:\r\nAPP_A -> APP_B -> APP_C\r\n\r\n`APP_B` is not instrumented with Elastic APM, so it is not available in\r\nthe trace, thus APP_C has a parent which is not available in the current\r\ntrace. `APP_C` is reparented to point to `APP_A`.\r\n\r\nBefore:\r\n<img width=\"1509\" alt=\"Screenshot 2025-02-07 at 12 55 06\"\r\nsrc=\"https://github.com/user-attachments/assets/a973fa5d-1acf-4fff-b525-01957490494e\"\r\n/>\r\n\r\n\r\nAfter [1]:\r\n<img width=\"1499\" alt=\"Screenshot 2025-02-07 at 12 03 34\"\r\nsrc=\"https://github.com/user-attachments/assets/8c49df04-de09-4d17-b6f8-f4b848e89f91\"\r\n/>\r\n\r\nAfter [2]:\r\n<img width=\"712\" alt=\"Screenshot 2025-02-07 at 11 35 28\"\r\nsrc=\"https://github.com/user-attachments/assets/2b62a7cf-5979-4636-bc05-c25c96e9d71b\"\r\n/>\r\n\r\n## How to test it:\r\n- Run synthtrace `distributed_trace.ts` scenario.\r\n- Find a trace.id\r\n- Remove one of the elements from the trace.","sha":"9bc9643e80d8b0dc7e2a81bf79c450446c16fcb7"}},{"url":"https://github.com/elastic/kibana/pull/210390","number":210390,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/210391","number":210391,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/210393","number":210393,"branch":"9.0","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/210395","number":210395,"branch":"8.16","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
33a9b8a99b
|
[8.17] Only show data warning screen on Serverless (#201920) (#210383)
# Backport This will backport the following commits from `main` to `8.17`: - [Only show data warning screen on Serverless (#201920)](https://github.com/elastic/kibana/pull/201920) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-28T10:23:07Z","message":"Only show data warning screen on Serverless (#201920)\n\n## Summary\r\n\r\nThis PR resolves\r\n[#11064](https://github.com/elastic/security-team/issues/11064), where\r\nthe warning was previously shown in both serverless and non-serverless\r\ninstances. A quick fix removed the message entirely, and this update\r\nreintroduces it for serverless environments only.\r\n\r\nThis PR adds a data warning specific to serverless environments using\r\nupselling with the callout component from serverless solution\r\ncomponents. The idea being to avoid adding a lot of `if serverless`\r\nchecks throughout the component as mentioned\r\nhttps://github.com/elastic/security-team/issues/11064#issuecomment-2461712849\r\n\r\n### To Test \r\n\r\n**Start a serverless instance** using these doccos:\r\nhttps://docs.elastic.dev/security-solution/dev-docs/serverless or\r\nfollowing steps locally:\r\n\r\n1. Using VSCode, Reopen PR in container. \r\n2. Start ElasticSearch: yarn es serverless --projectType security --ssl\r\n--kill\r\n3. Start Kibana (this is the only way I can make it work...): yarn start\r\n--serverless=security --username=your_username --password=your_password\r\n\r\n**Test the modal works as expected**: \r\n\r\n1. Remove / disable the 'entitytStoreDisable' flag here\r\n**/config/serverless.security.yml** (I commented it out) for modal to\r\nthen show\r\n2. Go to dashboards - Entity Analytics, hit the enable button and view\r\nmodal.\r\n\r\n### Before \r\n\r\n\r\n\r\n\r\n### After \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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e9ee5b4765f89f236916c9d2952006f78d6519a7","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team: SecuritySolution","backport:prev-major","Team:Entity Analytics","8.17 candidate","backport:version","v9.1.0"],"title":"Only show data warning screen on Serverless","number":201920,"url":"https://github.com/elastic/kibana/pull/201920","mergeCommit":{"message":"Only show data warning screen on Serverless (#201920)\n\n## Summary\r\n\r\nThis PR resolves\r\n[#11064](https://github.com/elastic/security-team/issues/11064), where\r\nthe warning was previously shown in both serverless and non-serverless\r\ninstances. A quick fix removed the message entirely, and this update\r\nreintroduces it for serverless environments only.\r\n\r\nThis PR adds a data warning specific to serverless environments using\r\nupselling with the callout component from serverless solution\r\ncomponents. The idea being to avoid adding a lot of `if serverless`\r\nchecks throughout the component as mentioned\r\nhttps://github.com/elastic/security-team/issues/11064#issuecomment-2461712849\r\n\r\n### To Test \r\n\r\n**Start a serverless instance** using these doccos:\r\nhttps://docs.elastic.dev/security-solution/dev-docs/serverless or\r\nfollowing steps locally:\r\n\r\n1. Using VSCode, Reopen PR in container. \r\n2. Start ElasticSearch: yarn es serverless --projectType security --ssl\r\n--kill\r\n3. Start Kibana (this is the only way I can make it work...): yarn start\r\n--serverless=security --username=your_username --password=your_password\r\n\r\n**Test the modal works as expected**: \r\n\r\n1. Remove / disable the 'entitytStoreDisable' flag here\r\n**/config/serverless.security.yml** (I commented it out) for modal to\r\nthen show\r\n2. Go to dashboards - Entity Analytics, hit the enable button and view\r\nmodal.\r\n\r\n### Before \r\n\r\n\r\n\r\n\r\n### After \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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e9ee5b4765f89f236916c9d2952006f78d6519a7"}},"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/201920","number":201920,"mergeCommit":{"message":"Only show data warning screen on Serverless (#201920)\n\n## Summary\r\n\r\nThis PR resolves\r\n[#11064](https://github.com/elastic/security-team/issues/11064), where\r\nthe warning was previously shown in both serverless and non-serverless\r\ninstances. A quick fix removed the message entirely, and this update\r\nreintroduces it for serverless environments only.\r\n\r\nThis PR adds a data warning specific to serverless environments using\r\nupselling with the callout component from serverless solution\r\ncomponents. The idea being to avoid adding a lot of `if serverless`\r\nchecks throughout the component as mentioned\r\nhttps://github.com/elastic/security-team/issues/11064#issuecomment-2461712849\r\n\r\n### To Test \r\n\r\n**Start a serverless instance** using these doccos:\r\nhttps://docs.elastic.dev/security-solution/dev-docs/serverless or\r\nfollowing steps locally:\r\n\r\n1. Using VSCode, Reopen PR in container. \r\n2. Start ElasticSearch: yarn es serverless --projectType security --ssl\r\n--kill\r\n3. Start Kibana (this is the only way I can make it work...): yarn start\r\n--serverless=security --username=your_username --password=your_password\r\n\r\n**Test the modal works as expected**: \r\n\r\n1. Remove / disable the 'entitytStoreDisable' flag here\r\n**/config/serverless.security.yml** (I commented it out) for modal to\r\nthen show\r\n2. Go to dashboards - Entity Analytics, hit the enable button and view\r\nmodal.\r\n\r\n### Before \r\n\r\n\r\n\r\n\r\n### After \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- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e9ee5b4765f89f236916c9d2952006f78d6519a7"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com> |
||
|
Kibana Machine
|
41f1d2b174
|
[8.17] [Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383) (#210342)
# Backport This will backport the following commits from `main` to `8.17`: - [[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)](https://github.com/elastic/kibana/pull/207383) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T11:57:22Z","message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\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-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:SharingURLs","Team:SharedUX","backport:prev-major","v9.1.0"],"title":"[Share Modal] Reinstate switch to support generating public urls for embed when supported","number":207383,"url":"https://github.com/elastic/kibana/pull/207383","mergeCommit":{"message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\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-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e"}},"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/207383","number":207383,"mergeCommit":{"message":"[Share Modal] Reinstate switch to support generating public urls for embed when supported (#207383)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/194105\n\nThis PR aims to resolve a regression with the share embed option, prior\nto 8.14.0 there was a functionality that provided the ability for users\nto get an embed link that would allow public access to the object of the\nshare (i.e. dashboards, visualisations) if they had the right\nconfiguration ([see\nhere](https://www.elastic.co/guide/en/kibana/8.13/kibana-authentication.html#anonymous-access-and-embedding)\non how to).\n\n## How to test\n- Attempt to get an embed link from for example the dashboard, the user\nshouldn't not be present with an option to create a url with public\naccess.\n- Now configure anonymous login in your `kibana.dev.yml`, like so; \n\n\t```\n\txpack.security.authc.providers:\n\t basic.basic1:\n\t order: 0\n\t anonymous.anonymous1:\n\t order: 1\n\t credentials:\n\t username: \"elastic\"\n\t password: \"changeme\"\n\t```\n- On doing this, you should be presented with the option to create a\npublic URL using the toggle switch similar to the image below, select\nthis option.\n\n<img width=\"602\" alt=\"Screenshot 2025-01-20 at 15 07 03\"\nsrc=\"https://github.com/user-attachments/assets/2af9082b-c44c-4cd0-89ae-de423bc7d18d\"\n/>\n\n- Click copy code button\n\n- Next, we'll create a dummy html document to verify the code copied\nworks, in your terminal simply run;\n ```bash\n\ttouch embed.html\n\techo \"paste embed code content here\" >> embed.html\n\tnpx --package=serve@latest -y serve\n ```\n- On running the commands above, we can try out the embed by opening up\nthe URL at `http://localhost:3000/embed`\n- Ideally if all the steps were followed we should have a page that\nloads up the object which the share URL was generated from.\n\n\nhttps://github.com/user-attachments/assets/c5c873a4-5417-4bcf-b0cb-132d9073992f\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-->","sha":"7b2631a21d9e7e4099a869587769d0b210e65a1e"}}]}] BACKPORT--> Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com> |
||
|
Kibana Machine
|
e4c6713f80
|
[8.17] [APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999) (#210317)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)](https://github.com/elastic/kibana/pull/209999) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-10T09:52:00Z","message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","apm","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage","number":209999,"url":"https://github.com/elastic/kibana/pull/209999","mergeCommit":{"message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb"}},"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/209999","number":209999,"mergeCommit":{"message":"[APM] Improve performance in `dependencies` endpoints to prevent high CPU usage (#209999)\n\n## Summary\r\n\r\nAfter investigating a high CPU spike in the `dependencies` endpoints for\r\nlarge quantities of data, we identified the issue as a slow deep merge\r\nof objects. The merge operation was growing exponentially in size based\r\non the number of objects found with the same `id`.\r\n\r\nWe improved performance by excluding the stats object from unnecessary\r\nmerges and instead joining it using the spread operator. The results\r\nshow a significant reduction in CPU usage, preventing the event loop\r\nfrom being blocked and ensuring better resource availability.\r\n\r\n|Before|After|\r\n|-|-|\r\n|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 12 50 41\"\r\nsrc=\"https://github.com/user-attachments/assets/6cd2bd68-6f19-42e2-bc2a-ed01a9f187c0\"\r\n/>|<img width=\"1728\" alt=\"Screenshot 2025-02-06 at 13 11 20\"\r\nsrc=\"https://github.com/user-attachments/assets/3ab7d9fb-0156-4d7e-a788-95cae11131f6\"\r\n/>|\r\n|<img width=\"2559\" alt=\"Screenshot 2025-02-06 at 14 34 24\"\r\nsrc=\"https://github.com/user-attachments/assets/3950525c-f5fa-4895-ae38-7927e5497d80\"\r\n/>|<img width=\"2558\" alt=\"Screenshot 2025-02-06 at 14 29 08\"\r\nsrc=\"https://github.com/user-attachments/assets/f05b6747-077b-49ea-a4ac-8528f6e2eb8f\"\r\n/>|","sha":"0c7fb00dee6ba4cf84e8a4d2d15ab5ab70e404cb"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com> |
||
elastic-vault-github-plugin-prod[bot]
|
04d922e15a
|
[8.17] Sync bundled packages with Package Storage (#210237)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2233 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Achyut Jhunjhunwala
|
de310fbf7b
|
[8.17] [Logs Explorer] Fix show all logs issue with data source selector (#210158) (#210306)
# Backport This will backport the following commits from `8.x` to `8.17`: - [[Logs Explorer] Fix show all logs issue with data source selector (#210158)](https://github.com/elastic/kibana/pull/210158) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Achyut Jhunjhunwala","email":"achyut.jhunjhunwala@elastic.co"},"sourceCommit":{"committedDate":"2025-02-07T12:34:22Z","message":"[Logs Explorer] Fix show all logs issue with data source selector (#210158)\n\n## Summary\n\nCloses - https://github.com/elastic/kibana/issues/208557\n\n1 word change\n\n## What was the issue\n\nUser selected `logSources` setting was not respected by Logs Explorer\nData Source Selector\n\n\n\n\n## What was done to fix it ?\n\n- We fetch the `logSources` from Kibana Advance Settings. This part\nstill happens.\n- When the page load, we initialize 3 state machines in order\n- Observability Logs Explorer - This state machine does the call to\n`uiSettings` to get the default list of `logSources` which the user has\nset. For example -\n`remote_cluster:filebeat-*,remote_cluster:logs-*,remote_cluster:kibana_sample_data_logs*,filebeat-*,kibana_sample_data_logs*,logs-*`\n- Now the `Observability Logs Explorer` state machine initializes the\n`Logs Explorer` state machine and passes this value of `allSelection`\ninside the `initialState` property to this state machine.\n- Now the `Logs Explorer` state machine initialises the `Data Source\nSelector` state machine where it passes a default `initialState` to this\nmachine but misses to pass the definition of `allSelection`.\n \nDue to which this state machine uses a default value for `allSelection`\nwhich is set to `logs-*-*` hardcoded in the code.\n \nHence the value which the user has set in Kibana Advance Settings is not\nrespected any more.\n \nThe way the state machines are designed, 1st time when page loads, the\nuser selected value is passed as selected value. Where as when user\nmanually changes to different data source and then again clicks on `All\nLogs`, since this `DataSourceSelector` state machine, does not know the\nset value for `allSelection` it uses a hard coded value from the code\nwhich is `logs-*-*` instead of the one retrieved from `logSources`\nsettings","sha":"c43e21254b18acd3b3d0eb9790a00b3d82b93c0c","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-logs","backport:version","v8.18.0","v8.17.3"],"title":"[Logs Explorer] Fix show all logs issue with data source selector","number":210158,"url":"https://github.com/elastic/kibana/pull/210158","mergeCommit":{"message":"[Logs Explorer] Fix show all logs issue with data source selector (#210158)\n\n## Summary\n\nCloses - https://github.com/elastic/kibana/issues/208557\n\n1 word change\n\n## What was the issue\n\nUser selected `logSources` setting was not respected by Logs Explorer\nData Source Selector\n\n\n\n\n## What was done to fix it ?\n\n- We fetch the `logSources` from Kibana Advance Settings. This part\nstill happens.\n- When the page load, we initialize 3 state machines in order\n- Observability Logs Explorer - This state machine does the call to\n`uiSettings` to get the default list of `logSources` which the user has\nset. For example -\n`remote_cluster:filebeat-*,remote_cluster:logs-*,remote_cluster:kibana_sample_data_logs*,filebeat-*,kibana_sample_data_logs*,logs-*`\n- Now the `Observability Logs Explorer` state machine initializes the\n`Logs Explorer` state machine and passes this value of `allSelection`\ninside the `initialState` property to this state machine.\n- Now the `Logs Explorer` state machine initialises the `Data Source\nSelector` state machine where it passes a default `initialState` to this\nmachine but misses to pass the definition of `allSelection`.\n \nDue to which this state machine uses a default value for `allSelection`\nwhich is set to `logs-*-*` hardcoded in the code.\n \nHence the value which the user has set in Kibana Advance Settings is not\nrespected any more.\n \nThe way the state machines are designed, 1st time when page loads, the\nuser selected value is passed as selected value. Where as when user\nmanually changes to different data source and then again clicks on `All\nLogs`, since this `DataSourceSelector` state machine, does not know the\nset value for `allSelection` it uses a hard coded value from the code\nwhich is `logs-*-*` instead of the one retrieved from `logSources`\nsettings","sha":"c43e21254b18acd3b3d0eb9790a00b3d82b93c0c"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Philippe Oberti
|
de58f7c917
|
[8.17] [Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225) (#210289)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)](https://github.com/elastic/kibana/pull/210225) <!--- Backport version: 9.6.4 --> ### 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-07T22:34:27Z","message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\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","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967","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.17.3","v8.16.5"],"title":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel","number":210225,"url":"https://github.com/elastic/kibana/pull/210225","mergeCommit":{"message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\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","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967"}},"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/210225","number":210225,"mergeCommit":{"message":"[Security Solution][Expandable flyout] fix flyout flickering when opening/closing left panel (#210225)\n\n## Summary\r\n\r\nWe recently improved the expandable flyout by adding support for a\r\n[fully resizable flyout](https://github.com/elastic/kibana/pull/192906).\r\nThis work introduce a minor inconvenience, where the right panel gets\r\nre-rendered every time the user expands or collapses the flyout.\r\n\r\nThis PR fixes this issue by better using the EUI resizable container\r\n(see how to externally control a resizable container\r\n[here](https://eui.elastic.co/#/layout/resizable-container#collapsible-panels-with-external-control)).\r\nThe flyout is now always showing a resizable container (even in\r\ncollapsed mode) but EUI manages internally hiding the left section and\r\nthe resize button.\r\n\r\n#### Old behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4d7589ec-0edf-4690-9ce4-7b969ae0bb44\r\n\r\n#### New behavior\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7cf720b8-5b31-4cc9-b213-21472ea880d6\r\n\r\nThe rest of the flyout's behavior remains untouched:\r\n- identical default widths\r\n- user selected widths are still applied\r\n- no changes to the preview behavior\r\n\r\n### Checklist\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","sha":"7a9bf1399c39e9306bbfb23e73a4d72fe8aae967"}},{"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--> |
||
wajihaparvez
|
43a693350e
|
[Docs] Backport 8.17.2 release notes to 8.17 (#210266)
## Summary Backporting 8.17.2 release notes. Rel: [210109](https://github.com/elastic/kibana/pull/210109) |
||
|
wajihaparvez
|
530bc5c888
|
[Docs] Backport 8.16.4 release notes to 8.17 (#210260)
## Summary Backporting 8.16.4 release notes. Rel: [210108](https://github.com/elastic/kibana/pull/210108) Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
61a9b611a3 | skip failing test suite (#183638) | ||
|
Kibana Machine
|
cf849efcbd
|
[8.17] [EDR Workflows] Fix agent count on policy deploy modal (#209593) (#210042)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] Fix agent count on policy deploy modal (#209593)](https://github.com/elastic/kibana/pull/209593) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T15:17:47Z","message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\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\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5","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:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix agent count on policy deploy modal","number":209593,"url":"https://github.com/elastic/kibana/pull/209593","mergeCommit":{"message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\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\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5"}},"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/209593","number":209593,"mergeCommit":{"message":"[EDR Workflows] Fix agent count on policy deploy modal (#209593)\n\n## Summary\r\n\r\nFixes the agent count issue on the warning model when saving a Defend\r\npackage policy. Now it uses the same `active` field instead of `all`, as\r\nthe `AgentSummary` component.\r\n\r\nAlso, re-enables flaky unit test for `PolicySettingsLayout`:\r\ncloses: #179984\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\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"16fae1c86597d2f43e9120578346e26a8b5a88a5"}}]}] BACKPORT--> --------- Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |
||
Ash
|
8b86e7bc45
|
[8.17] [SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097) (#210132)
# Backport This will backport the following commits from `main` to `8.17`: - [[SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097)](https://github.com/elastic/kibana/pull/209097) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-03T10:38:14Z","message":"[SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097)","sha":"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8","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","OLM Sprint","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[SecuritySolution][Endpoint] Update request docs for isolate/release/processes","number":209097,"url":"https://github.com/elastic/kibana/pull/209097","mergeCommit":{"message":"[SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097)","sha":"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8"}},"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/209249","number":209249,"state":"MERGED","mergeCommit":{"sha":"520ee77c3ef3930f2e5dd116dca8d4bfd34a5a46","message":"[9.0] [SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097) (#209249)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[SecuritySolution][Endpoint] Update request docs for\nisolate/release/processes\n(#209097)](https://github.com/elastic/kibana/pull/209097)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Ash\",\"email\":\"1849116+ashokaditya@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-03T10:38:14Z\",\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\",\"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\nWorkflows\",\"OLM\nSprint\",\"v8.16.0\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v9.1.0\"],\"title\":\"[SecuritySolution][Endpoint]\nUpdate request docs for\nisolate/release/processes\",\"number\":209097,\"url\":\"https://github.com/elastic/kibana/pull/209097\",\"mergeCommit\":{\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\"}},\"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/209097\",\"number\":209097,\"mergeCommit\":{\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>"}},{"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/209248","number":209248,"state":"MERGED","mergeCommit":{"sha":"21237fd4e5ee6a114376c40783576d768277c120","message":"[8.18] [SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097) (#209248)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[SecuritySolution][Endpoint] Update request docs for\nisolate/release/processes\n(#209097)](https://github.com/elastic/kibana/pull/209097)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Ash\",\"email\":\"1849116+ashokaditya@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-03T10:38:14Z\",\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\",\"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\nWorkflows\",\"OLM\nSprint\",\"v8.16.0\",\"backport:version\",\"v8.17.0\",\"v8.18.0\",\"v9.1.0\"],\"title\":\"[SecuritySolution][Endpoint]\nUpdate request docs for\nisolate/release/processes\",\"number\":209097,\"url\":\"https://github.com/elastic/kibana/pull/209097\",\"mergeCommit\":{\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\"}},\"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/209097\",\"number\":209097,\"mergeCommit\":{\"message\":\"[SecuritySolution][Endpoint]\nUpdate request docs for isolate/release/processes\n(#209097)\",\"sha\":\"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209097","number":209097,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Update request docs for isolate/release/processes (#209097)","sha":"59a15be9777d206e3cc59e3ffb9dcf5d2beadbe8"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
7359e5e0bc
|
[8.17] fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075) (#210098)
# Backport This will backport the following commits from `main` to `8.17`: - [fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)](https://github.com/elastic/kibana/pull/210075) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T19:02:59Z","message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted ","number":210075,"url":"https://github.com/elastic/kibana/pull/210075","mergeCommit":{"message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8"}},"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/210075","number":210075,"mergeCommit":{"message":"fix `Cannot read properties of null (reading 'closed')` when chrome is remounted (#210075)","sha":"cd398d939462ebeb73f05c4fdd1d88db349eacf8"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
|
Yara Tercero
|
c2417d3b52
|
[8.17] [Detection Engine][API Docs] Update request/response examples for value lists APIs (#205957) (#209691)
# Backport This will backport the following commits from `main` to `8.17`: - [[Detection Engine][API Docs] Update request/response examples for value lists APIs (#205957)](https://github.com/elastic/kibana/pull/205957) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-23T15:19:45Z","message":"[Detection Engine][API Docs] Update request/response examples for value lists APIs (#205957)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Value Lists APIs.","sha":"e396ac9a1438fcb16c2e4f1b61c3633de098d9bf","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","v9.0.0","Team:Detection Engine","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Detection Engine][API Docs] Update request/response examples for value lists APIs","number":205957,"url":"https://github.com/elastic/kibana/pull/205957","mergeCommit":{"message":"[Detection Engine][API Docs] Update request/response examples for value lists APIs (#205957)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Value Lists APIs.","sha":"e396ac9a1438fcb16c2e4f1b61c3633de098d9bf"}},"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/205957","number":205957,"mergeCommit":{"message":"[Detection Engine][API Docs] Update request/response examples for value lists APIs (#205957)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Value Lists APIs.","sha":"e396ac9a1438fcb16c2e4f1b61c3633de098d9bf"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209597","number":209597,"state":"OPEN"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209586","number":209586,"state":"OPEN"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/209462","number":209462,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
795b5af054
|
[8.17] Remove beta badge for manual rule run (#209535) (#210069)
# Backport This will backport the following commits from `main` to `8.17`: - [Remove beta badge for manual rule run (#209535)](https://github.com/elastic/kibana/pull/209535) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T16:31:03Z","message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Remove beta badge for manual rule run","number":209535,"url":"https://github.com/elastic/kibana/pull/209535","mergeCommit":{"message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170"}},"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/209535","number":209535,"mergeCommit":{"message":"Remove beta badge for manual rule run (#209535)\n\n## Remove beta badge for manual rule run\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3f1c97e38e6a460c22191866797467eacf239170"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
Jatin Kathuria
|
75246f5a4c
|
[8.17] [Security Solution] Fix timeline dynamic batching (#204034) | [ Security Solution ] Fix Refetch logic with new timeline batching (#205893) (#205676)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fix timeline dynamic batching (#204034)](https://github.com/elastic/kibana/pull/204034) - https://github.com/elastic/kibana/pull/205893 <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-01-07T06:20:30Z","message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:prev-minor","v8.16.3"],"number":204034,"url":"https://github.com/elastic/kibana/pull/204034","mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204034","number":204034,"mergeCommit":{"message":"[Security Solution] Fix timeline dynamic batching (#204034)\n\n## Summary\r\n\r\nHandles :\r\n\r\n\r\n### Issue with Batches\r\n- https://github.com/elastic/kibana/issues/201405\r\n- Timeline had a bug where if users fetched multiple batches and then if\r\nuser adds a new column, the value of this new columns will only be\r\nfetched for the latest batch and not old batches.\r\n- This PR fixes that ✅ by cumulatively fetching the data for old batches\r\ntill current batch `iff a new column has been added`.\r\n- For example, if user has already fetched the 3rd batch, data for\r\n1st,2nd and 3rd will be fetched together when a column has been added,\r\notherwise, data will be fetched incrementally.\r\n\r\n### Issue with Elastic search limit\r\n\r\n- Elastic search has a limit of 10K hits at max but we throw error at\r\n10K which should be allowed.\r\n - Error should be thrown at anything `>10K`. 10001 for example.\r\n - ✅ This PR fixes that just for timeline by allowing 10K hits.\r\n\r\n### Removal of obsolete code\r\n\r\nBelow files related to old Timeline code are removed as well:\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.test.tsx\r\n-\r\nx-pack/plugins/security_solution/public/timelines/components/timeline/footer/index.tsx\r\n\r\n---------\r\n\r\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"088169f446788f9fa8800d77817881524514943e"}},{"branch":"8.16","label":"v8.16.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/205674","number":205674,"state":"OPEN"}]}] BACKPORT--> |
||
Jan Monschke
|
ef7b51d373
|
[8.17] [SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475) (#209971)
# Backport This will backport the following commits from `main` to `8.17`: - [[SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475)](https://github.com/elastic/kibana/pull/209475) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T20:40:17Z","message":"[SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/191767\n\nMultiple IPs are now displayed as individual links, even in the case\nwhere multiple IPs are passed as a single string (e.g.\n`127.0.0.1,127.0.0.2`). Clicking on an individual link will open the\nflyout correctly as well.\n\n\n\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dda538111ed66cb6a36148f07a87068d7de076b6","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:Investigations","backport:prev-minor","backport:prev-major","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings","number":209475,"url":"https://github.com/elastic/kibana/pull/209475","mergeCommit":{"message":"[SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/191767\n\nMultiple IPs are now displayed as individual links, even in the case\nwhere multiple IPs are passed as a single string (e.g.\n`127.0.0.1,127.0.0.2`). Clicking on an individual link will open the\nflyout correctly as well.\n\n\n\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dda538111ed66cb6a36148f07a87068d7de076b6"}},"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/209909","number":209909,"state":"MERGED","mergeCommit":{"sha":"67a7a2fc842fd3e7b3a361d5b080d7a9794c01cf","message":"[9.0] [SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475) (#209909)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[SecuritySolution][Alerts table] Fix issue with multiple ip addresses\nin strings (#209475)](https://github.com/elastic/kibana/pull/209475)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jan\nMonschke\",\"email\":\"jan.monschke@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T20:40:17Z\",\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"backport:prev-major\",\"v9.1.0\"],\"title\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in\nstrings\",\"number\":209475,\"url\":\"https://github.com/elastic/kibana/pull/209475\",\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}},\"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/209475\",\"number\":209475,\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209907","number":209907,"state":"MERGED","mergeCommit":{"sha":"7767ad87599a4d97027757e94abc7b9db1df3cd1","message":"[8.18] [SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475) (#209907)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[SecuritySolution][Alerts table] Fix issue with multiple ip addresses\nin strings (#209475)](https://github.com/elastic/kibana/pull/209475)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jan\nMonschke\",\"email\":\"jan.monschke@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T20:40:17Z\",\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"backport:prev-major\",\"v9.1.0\"],\"title\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in\nstrings\",\"number\":209475,\"url\":\"https://github.com/elastic/kibana/pull/209475\",\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}},\"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/209475\",\"number\":209475,\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209475","number":209475,"mergeCommit":{"message":"[SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475)\n\n## Summary\n\nFixes https://github.com/elastic/kibana/issues/191767\n\nMultiple IPs are now displayed as individual links, even in the case\nwhere multiple IPs are passed as a single string (e.g.\n`127.0.0.1,127.0.0.2`). Clicking on an individual link will open the\nflyout correctly as well.\n\n\n\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\n\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dda538111ed66cb6a36148f07a87068d7de076b6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209908","number":209908,"state":"MERGED","mergeCommit":{"sha":"e62eef171bec5fe025f463b105cbac1fa44a4fff","message":"[8.x] [SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475) (#209908)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[SecuritySolution][Alerts table] Fix issue with multiple ip addresses\nin strings (#209475)](https://github.com/elastic/kibana/pull/209475)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Jan\nMonschke\",\"email\":\"jan.monschke@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T20:40:17Z\",\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"Team:Threat\nHunting:Investigations\",\"backport:prev-minor\",\"backport:prev-major\",\"v9.1.0\"],\"title\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in\nstrings\",\"number\":209475,\"url\":\"https://github.com/elastic/kibana/pull/209475\",\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}},\"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/209475\",\"number\":209475,\"mergeCommit\":{\"message\":\"[SecuritySolution][Alerts\ntable] Fix issue with multiple ip addresses in strings (#209475)\\n\\n##\nSummary\\n\\nFixes\nhttps://github.com/elastic/kibana/issues/191767\\n\\nMultiple IPs are now\ndisplayed as individual links, even in the case\\nwhere multiple IPs are\npassed as a single string (e.g.\\n`127.0.0.1,127.0.0.2`). Clicking on an\nindividual link will open the\\nflyout correctly as\nwell.\\n\\n\\n\\nhttps://github.com/user-attachments/assets/74b05cff-3843-4149-bf27-cd0af07aa558\\n\\n\\n\\n###\nChecklist\\n\\n- [x] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common\nscenarios\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"dda538111ed66cb6a36148f07a87068d7de076b6\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"url":"https://github.com/elastic/kibana/pull/209969","number":209969,"branch":"8.16","state":"OPEN"}]}] BACKPORT--> |
||
Faisal Kanout
|
39457b433d
|
[8.17] [OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263) (#209712)
# Backport This will backport the following commits from `main` to `8.17`: - [[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263)](https://github.com/elastic/kibana/pull/209263) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Faisal Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T12:18:27Z","message":"[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263)\n\n## Summary\r\n\r\nIt fixes #201511\r\n\r\n<img width=\"680\" alt=\"Screenshot 2025-02-03 at 12 51 56\"\r\nsrc=\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\"\r\n/>\r\n\r\n### Release notes:\r\nFix the preview chart in the Custom Threshold rule creation form when\r\nthe field name has slashes","sha":"ed333de757b67bfeb1e68ec33b64bb238ecc21eb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Alerting","v9.0.0","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v8.18.0","v9.1.0","v8.19.0"],"title":"[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes ","number":209263,"url":"https://github.com/elastic/kibana/pull/209263","mergeCommit":{"message":"[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263)\n\n## Summary\r\n\r\nIt fixes #201511\r\n\r\n<img width=\"680\" alt=\"Screenshot 2025-02-03 at 12 51 56\"\r\nsrc=\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\"\r\n/>\r\n\r\n### Release notes:\r\nFix the preview chart in the Custom Threshold rule creation form when\r\nthe field name has slashes","sha":"ed333de757b67bfeb1e68ec33b64bb238ecc21eb"}},"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/209525","number":209525,"state":"MERGED","mergeCommit":{"sha":"e6c252a45321ff691364c5eb024339622c8e70a9","message":"[9.0] [OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263) (#209525)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field\nname has slashes\n(#209263)](https://github.com/elastic/kibana/pull/209263)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Faisal\nKanout\",\"email\":\"faisal.kanout@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-04T12:18:27Z\",\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"Feature:Alerting\",\"backport:prev-minor\",\"backport:prev-major\",\"Team:obs-ux-management\",\"v9.1.0\"],\"title\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n\",\"number\":209263,\"url\":\"https://github.com/elastic/kibana/pull/209263\",\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}},\"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/209263\",\"number\":209263,\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209523","number":209523,"state":"MERGED","mergeCommit":{"sha":"f6e739b19ec45b8f6eba3e9d4935039f5038f797","message":"[8.18] [OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263) (#209523)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field\nname has slashes\n(#209263)](https://github.com/elastic/kibana/pull/209263)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Faisal\nKanout\",\"email\":\"faisal.kanout@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-04T12:18:27Z\",\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"Feature:Alerting\",\"backport:prev-minor\",\"backport:prev-major\",\"Team:obs-ux-management\",\"v9.1.0\"],\"title\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n\",\"number\":209263,\"url\":\"https://github.com/elastic/kibana/pull/209263\",\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}},\"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/209263\",\"number\":209263,\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209263","number":209263,"mergeCommit":{"message":"[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263)\n\n## Summary\r\n\r\nIt fixes #201511\r\n\r\n<img width=\"680\" alt=\"Screenshot 2025-02-03 at 12 51 56\"\r\nsrc=\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\"\r\n/>\r\n\r\n### Release notes:\r\nFix the preview chart in the Custom Threshold rule creation form when\r\nthe field name has slashes","sha":"ed333de757b67bfeb1e68ec33b64bb238ecc21eb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209524","number":209524,"state":"MERGED","mergeCommit":{"sha":"f228a0643970bb9923f7d5f4361ddf123cc2c94e","message":"[8.x] [OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263) (#209524)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field\nname has slashes\n(#209263)](https://github.com/elastic/kibana/pull/209263)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Faisal\nKanout\",\"email\":\"faisal.kanout@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-04T12:18:27Z\",\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"Feature:Alerting\",\"backport:prev-minor\",\"backport:prev-major\",\"Team:obs-ux-management\",\"v9.1.0\"],\"title\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n\",\"number\":209263,\"url\":\"https://github.com/elastic/kibana/pull/209263\",\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}},\"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/209263\",\"number\":209263,\"mergeCommit\":{\"message\":\"[OBX-UX-MGMT][BUG]\nFix chart in Custom Threshold rule when the field name has slashes\n(#209263)\\n\\n## Summary\\r\\n\\r\\nIt fixes #201511\\r\\n\\r\\n<img\nwidth=\\\"680\\\" alt=\\\"Screenshot 2025-02-03 at 12 51\n56\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/fe3fa780-c50d-4906-8c5b-6758fea5fe9c\\\"\\r\\n/>\\r\\n\\r\\n###\nRelease notes:\\r\\nFix the preview chart in the Custom Threshold rule\ncreation form when\\r\\nthe field name has\nslashes\",\"sha\":\"ed333de757b67bfeb1e68ec33b64bb238ecc21eb\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Faisal Kanout <faisal.kanout@elastic.co>"}}]}] BACKPORT--> |
||
|
elastic-vault-github-plugin-prod[bot]
|
484eeeed67
|
[8.17] Sync bundled packages with Package Storage (#209741)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2213 Co-authored-by: elasticmachine <elasticmachine@elastic.co> |
||
|
Yara Tercero
|
50cac192a4
|
[8.17] [Detection Engine][Docs] Added response and request descriptions for API docs (#205822) (#209693)
# Backport This will backport the following commits from `main` to `8.17`: - [[Detection Engine][Docs] Added response and request descriptions for API docs (#205822)](https://github.com/elastic/kibana/pull/205822) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-16T20:14:08Z","message":"[Detection Engine][Docs] Added response and request descriptions for API docs (#205822)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Exception APIs.","sha":"94660cf2f51047e09185f4965f94a34ec80915b2","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","v9.0.0","Team:Detection Engine","backport:version","v8.17.0","v8.18.0"],"title":"[Detection Engine][Docs] Added response and request descriptions for API docs","number":205822,"url":"https://github.com/elastic/kibana/pull/205822","mergeCommit":{"message":"[Detection Engine][Docs] Added response and request descriptions for API docs (#205822)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Exception APIs.","sha":"94660cf2f51047e09185f4965f94a34ec80915b2"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205822","number":205822,"mergeCommit":{"message":"[Detection Engine][Docs] Added response and request descriptions for API docs (#205822)\n\n# Summary\r\n\r\nAs part of the effort to add missing content for Security APIs, this PR\r\nintroduces a few missing request, response, and parameter examples for\r\nDetection Engine Exception APIs.","sha":"94660cf2f51047e09185f4965f94a34ec80915b2"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Patrick Mueller
|
602a0a3c79
|
[8.17] update puppeteer to 24.1.1 (#208477) (#209929)
# Backport This will backport the following commits from `main` to `8.17`: - [update puppeteer to 24.1.1 (#208477)](https://github.com/elastic/kibana/pull/208477) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T19:46:51Z","message":"update puppeteer to 24.1.1 (#208477)\n\n## Summary\r\n\r\nUpdates puppeteer to 24.1.1\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b311acfec43009e5879e42f5025c3f56fa0edde6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","Team:SharedUX","backport:all-open","ci:cloud-deploy","ci:cloud-redeploy","ci:project-deploy-elasticsearch","ci:project-persist-deployment","ci:project-redeploy","backport:version","v8.18.0","v8.15.6","v7.17.28","v8.16.4","v8.17.2","v9.1.0"],"title":"update puppeteer to 24.1.1","number":208477,"url":"https://github.com/elastic/kibana/pull/208477","mergeCommit":{"message":"update puppeteer to 24.1.1 (#208477)\n\n## Summary\r\n\r\nUpdates puppeteer to 24.1.1\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b311acfec43009e5879e42f5025c3f56fa0edde6"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","7.17","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/209898","number":209898,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209896","number":209896,"state":"OPEN"},{"branch":"8.15","label":"v8.15.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.28","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/208477","number":208477,"mergeCommit":{"message":"update puppeteer to 24.1.1 (#208477)\n\n## Summary\r\n\r\nUpdates puppeteer to 24.1.1\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"b311acfec43009e5879e42f5025c3f56fa0edde6"}},{"url":"https://github.com/elastic/kibana/pull/209897","number":209897,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> |
||
Nathan Reese
|
7c1ece4477
|
[8.17] [canvas] fix All embeddables rebuilt on refresh (#209677) (#209858)
# Backport This will backport the following commits from `main` to `8.17`: - [[canvas] fix All embeddables rebuilt on refresh (#209677)](https://github.com/elastic/kibana/pull/209677) <!--- Backport version: 9.6.4 --> ### 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-02-05T17:34:44Z","message":"[canvas] fix All embeddables rebuilt on refresh (#209677)\n\nFixes https://github.com/elastic/kibana/issues/209566\r\n\r\n### Problem\r\nAny input change causes Canvas embeddable's to get re-created. This\r\nmeans that setting a filter control or clicking the refresh button\r\ncauses embeddables to get re-created.\r\n\r\nIn the old embeddable system, the Canvas would only call\r\n`embeddable.updateInput` and `embeddable.reload` on [input\r\nchanges](https://github.com/elastic/kibana/blob/8.13/x-pack/plugins/canvas/canvas_plugin_src/renderers/embeddable/embeddable.tsx#L163).\r\n\r\n### Solution\r\nPR updates embeddable renderer to store embeddable API. Then, on input\r\nchanges, Canvas calls `embeddable.setFilters`.\r\n\r\nThere is no `embeddable.updateInput` equivalent in the new embeddable\r\nsystem. Instead, each state key needs to be updated by a setter. The\r\n[Canvas\r\ndocumentation](https://www.elastic.co/guide/en/kibana/current/canvas-function-reference.html#embeddable_fn)\r\nstates that the embeddable function only accepts `filters`. Therefore,\r\nthe only key that is expected to change from the input is `filters`.\r\nPlease correct me if this is an incorrect assumption.\r\n\r\n### Test instructions\r\n1) install sample web logs\r\n2) install canvas saved object and reload kibana (otherwise canvas is\r\nnot available in the nav menu)\r\n3) open new canvas\r\n4) add map embeddable\r\n5) add filter control. set source to sample web logs and field to\r\n`geo.dest`.\r\n<img width=\"200\" alt=\"Screenshot 2025-02-04 at 2 58 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/6862f0bc-4f61-4f16-aa7c-ea8008cfdbf9\"\r\n/>\r\n6) prefix map element expression with `kibana | selectFilter` so it\r\nlooks like `kibana | selectFilter | embeddable config=...`\r\n7) change filter. Verify map updates but map embeddable is not\r\nre-created.\r\n8) click refresh button, Verify map updates but is not re-created.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fe9023efffc2671cec0597b14950cc2a204e7ade","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","v8.16.4","v8.17.2","v9.1.0","v8.19.0"],"title":"[canvas] fix All embeddables rebuilt on refresh","number":209677,"url":"https://github.com/elastic/kibana/pull/209677","mergeCommit":{"message":"[canvas] fix All embeddables rebuilt on refresh (#209677)\n\nFixes https://github.com/elastic/kibana/issues/209566\r\n\r\n### Problem\r\nAny input change causes Canvas embeddable's to get re-created. This\r\nmeans that setting a filter control or clicking the refresh button\r\ncauses embeddables to get re-created.\r\n\r\nIn the old embeddable system, the Canvas would only call\r\n`embeddable.updateInput` and `embeddable.reload` on [input\r\nchanges](https://github.com/elastic/kibana/blob/8.13/x-pack/plugins/canvas/canvas_plugin_src/renderers/embeddable/embeddable.tsx#L163).\r\n\r\n### Solution\r\nPR updates embeddable renderer to store embeddable API. Then, on input\r\nchanges, Canvas calls `embeddable.setFilters`.\r\n\r\nThere is no `embeddable.updateInput` equivalent in the new embeddable\r\nsystem. Instead, each state key needs to be updated by a setter. The\r\n[Canvas\r\ndocumentation](https://www.elastic.co/guide/en/kibana/current/canvas-function-reference.html#embeddable_fn)\r\nstates that the embeddable function only accepts `filters`. Therefore,\r\nthe only key that is expected to change from the input is `filters`.\r\nPlease correct me if this is an incorrect assumption.\r\n\r\n### Test instructions\r\n1) install sample web logs\r\n2) install canvas saved object and reload kibana (otherwise canvas is\r\nnot available in the nav menu)\r\n3) open new canvas\r\n4) add map embeddable\r\n5) add filter control. set source to sample web logs and field to\r\n`geo.dest`.\r\n<img width=\"200\" alt=\"Screenshot 2025-02-04 at 2 58 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/6862f0bc-4f61-4f16-aa7c-ea8008cfdbf9\"\r\n/>\r\n6) prefix map element expression with `kibana | selectFilter` so it\r\nlooks like `kibana | selectFilter | embeddable config=...`\r\n7) change filter. Verify map updates but map embeddable is not\r\nre-created.\r\n8) click refresh button, Verify map updates but is not re-created.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fe9023efffc2671cec0597b14950cc2a204e7ade"}},"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/209855","number":209855,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209853","number":209853,"state":"OPEN"},{"branch":"8.16","label":"v8.16.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/209677","number":209677,"mergeCommit":{"message":"[canvas] fix All embeddables rebuilt on refresh (#209677)\n\nFixes https://github.com/elastic/kibana/issues/209566\r\n\r\n### Problem\r\nAny input change causes Canvas embeddable's to get re-created. This\r\nmeans that setting a filter control or clicking the refresh button\r\ncauses embeddables to get re-created.\r\n\r\nIn the old embeddable system, the Canvas would only call\r\n`embeddable.updateInput` and `embeddable.reload` on [input\r\nchanges](https://github.com/elastic/kibana/blob/8.13/x-pack/plugins/canvas/canvas_plugin_src/renderers/embeddable/embeddable.tsx#L163).\r\n\r\n### Solution\r\nPR updates embeddable renderer to store embeddable API. Then, on input\r\nchanges, Canvas calls `embeddable.setFilters`.\r\n\r\nThere is no `embeddable.updateInput` equivalent in the new embeddable\r\nsystem. Instead, each state key needs to be updated by a setter. The\r\n[Canvas\r\ndocumentation](https://www.elastic.co/guide/en/kibana/current/canvas-function-reference.html#embeddable_fn)\r\nstates that the embeddable function only accepts `filters`. Therefore,\r\nthe only key that is expected to change from the input is `filters`.\r\nPlease correct me if this is an incorrect assumption.\r\n\r\n### Test instructions\r\n1) install sample web logs\r\n2) install canvas saved object and reload kibana (otherwise canvas is\r\nnot available in the nav menu)\r\n3) open new canvas\r\n4) add map embeddable\r\n5) add filter control. set source to sample web logs and field to\r\n`geo.dest`.\r\n<img width=\"200\" alt=\"Screenshot 2025-02-04 at 2 58 01 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/6862f0bc-4f61-4f16-aa7c-ea8008cfdbf9\"\r\n/>\r\n6) prefix map element expression with `kibana | selectFilter` so it\r\nlooks like `kibana | selectFilter | embeddable config=...`\r\n7) change filter. Verify map updates but map embeddable is not\r\nre-created.\r\n8) click refresh button, Verify map updates but is not re-created.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fe9023efffc2671cec0597b14950cc2a204e7ade"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209854","number":209854,"state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d7985c8064
|
[8.17] [Connectors] depend Sharepoint secret_value on auth_method (#209656) (#209802)
# Backport This will backport the following commits from `main` to `8.17`: - [[Connectors] depend Sharepoint secret_value on auth_method (#209656)](https://github.com/elastic/kibana/pull/209656) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Meghan Murphy","email":"meghan.murphy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T14:55:27Z","message":"[Connectors] depend Sharepoint secret_value on auth_method (#209656)\n\n## Summary\r\n\r\nOnly have secret_value box when configuring a Sharepoint online\r\nconnector when auth_method is 'secret'.\r\n\r\n#### Closes https://github.com/elastic/search-team/issues/9196\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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cac82fdf532f5800c8bca2abc3c44dd443816f4","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","v8.17.2","v9.1.0","v8.19.0"],"title":"[Connectors] depend Sharepoint secret_value on auth_method","number":209656,"url":"https://github.com/elastic/kibana/pull/209656","mergeCommit":{"message":"[Connectors] depend Sharepoint secret_value on auth_method (#209656)\n\n## Summary\r\n\r\nOnly have secret_value box when configuring a Sharepoint online\r\nconnector when auth_method is 'secret'.\r\n\r\n#### Closes https://github.com/elastic/search-team/issues/9196\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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cac82fdf532f5800c8bca2abc3c44dd443816f4"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","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/209796","number":209796,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","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/209656","number":209656,"mergeCommit":{"message":"[Connectors] depend Sharepoint secret_value on auth_method (#209656)\n\n## Summary\r\n\r\nOnly have secret_value box when configuring a Sharepoint online\r\nconnector when auth_method is 'secret'.\r\n\r\n#### Closes https://github.com/elastic/search-team/issues/9196\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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"1cac82fdf532f5800c8bca2abc3c44dd443816f4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Meghan Murphy <meghan.murphy@elastic.co> |
||
|
Kibana Machine
|
ab1cf33278
|
[8.17] [Automatic Import] Fix Structured log template to use single quotes (#209736) (#209781)
# Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix Structured log template to use single quotes (#209736)](https://github.com/elastic/kibana/pull/209736) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-05T12:52:04Z","message":"[Automatic Import] Fix Structured log template to use single quotes (#209736)\n\n## Release Note\r\n\r\nFix Structured log template to use single quotes\r\n\r\n### Summary\r\n\r\nCurrently with a single backslash as escape character the template is\r\nsetting up a double quote surrounding it and it causes YAML Exception\r\n```\r\n 1 | - kv:\r\n 2 | field: message\r\n 3 | field_split: \"\\|\"\r\n--------------------------^\r\n\r\nYAMLException: unknown escape sequence (3:22)\r\n```\r\n\r\nThis PR fixes to use single quotes to not break YAML parsing.","sha":"8181858385efdc099b9ac517afe58ef6d1ba18a6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","backport:8.17","v9.1.0","backport:8.18"],"title":"[Automatic Import] Fix Structured log template to use single quotes","number":209736,"url":"https://github.com/elastic/kibana/pull/209736","mergeCommit":{"message":"[Automatic Import] Fix Structured log template to use single quotes (#209736)\n\n## Release Note\r\n\r\nFix Structured log template to use single quotes\r\n\r\n### Summary\r\n\r\nCurrently with a single backslash as escape character the template is\r\nsetting up a double quote surrounding it and it causes YAML Exception\r\n```\r\n 1 | - kv:\r\n 2 | field: message\r\n 3 | field_split: \"\\|\"\r\n--------------------------^\r\n\r\nYAMLException: unknown escape sequence (3:22)\r\n```\r\n\r\nThis PR fixes to use single quotes to not break YAML parsing.","sha":"8181858385efdc099b9ac517afe58ef6d1ba18a6"}},"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/209736","number":209736,"mergeCommit":{"message":"[Automatic Import] Fix Structured log template to use single quotes (#209736)\n\n## Release Note\r\n\r\nFix Structured log template to use single quotes\r\n\r\n### Summary\r\n\r\nCurrently with a single backslash as escape character the template is\r\nsetting up a double quote surrounding it and it causes YAML Exception\r\n```\r\n 1 | - kv:\r\n 2 | field: message\r\n 3 | field_split: \"\\|\"\r\n--------------------------^\r\n\r\nYAMLException: unknown escape sequence (3:22)\r\n```\r\n\r\nThis PR fixes to use single quotes to not break YAML parsing.","sha":"8181858385efdc099b9ac517afe58ef6d1ba18a6"}},{"url":"https://github.com/elastic/kibana/pull/209757","number":209757,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
Kibana Machine
|
50d18b419a
|
[8.17] [Console] Refactor flaky test (#209516) (#209727)
# Backport This will backport the following commits from `main` to `8.17`: - [[Console] Refactor flaky test (#209516)](https://github.com/elastic/kibana/pull/209516) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-02-05T10:28:46Z","message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-major","v9.1.0","v8.19.0"],"title":"[Console] Refactor flaky test","number":209516,"url":"https://github.com/elastic/kibana/pull/209516","mergeCommit":{"message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209516","number":209516,"mergeCommit":{"message":"[Console] Refactor flaky test (#209516)","sha":"86497d5e7f64816b3fc2a081f84a8e686f262e57"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> |
||
|
elastic-vault-github-plugin-prod[bot]
|
c990c7c5f7
|
[8.17] Sync bundled packages with Package Storage (#209411)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2179 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
d06787d7ee
|
[8.17] [Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561) (#209659)
# Backport This will backport the following commits from `main` to `8.17`: - [[Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561)](https://github.com/elastic/kibana/pull/209561) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bena Kansara","email":"69037875+benakansara@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-04T20:03:48Z","message":"[Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561)\n\nResolves https://github.com/elastic/kibana/issues/196062\r\nFixes https://github.com/elastic/kibana/issues/209515\r\n\r\nDisplays \"Alert when No Data\" in Threshold breached component for no\r\ndata alerts\r\n\r\n- ### Custom threshold alert details page\r\n<img width=\"1643\" alt=\"Screenshot 2025-02-04 at 3 55 32 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5fbf27d2-dcb5-40d1-b466-c8bcc2d700c9\"\r\n/>\r\n\r\n- ### Metric threshold alert details page\r\n<img width=\"1645\" alt=\"Screenshot 2025-02-04 at 3 54 58 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/8968c803-ff73-4f7d-8501-f6a1e7e16e8c\"\r\n/>","sha":"551d31b0ffffd48d221b09acafc740c1d514ac75","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v9.1.0"],"title":"[Custom threshold/Metric threshold] Display No Data in Threshold breached component","number":209561,"url":"https://github.com/elastic/kibana/pull/209561","mergeCommit":{"message":"[Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561)\n\nResolves https://github.com/elastic/kibana/issues/196062\r\nFixes https://github.com/elastic/kibana/issues/209515\r\n\r\nDisplays \"Alert when No Data\" in Threshold breached component for no\r\ndata alerts\r\n\r\n- ### Custom threshold alert details page\r\n<img width=\"1643\" alt=\"Screenshot 2025-02-04 at 3 55 32 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5fbf27d2-dcb5-40d1-b466-c8bcc2d700c9\"\r\n/>\r\n\r\n- ### Metric threshold alert details page\r\n<img width=\"1645\" alt=\"Screenshot 2025-02-04 at 3 54 58 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/8968c803-ff73-4f7d-8501-f6a1e7e16e8c\"\r\n/>","sha":"551d31b0ffffd48d221b09acafc740c1d514ac75"}},"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/209561","number":209561,"mergeCommit":{"message":"[Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561)\n\nResolves https://github.com/elastic/kibana/issues/196062\r\nFixes https://github.com/elastic/kibana/issues/209515\r\n\r\nDisplays \"Alert when No Data\" in Threshold breached component for no\r\ndata alerts\r\n\r\n- ### Custom threshold alert details page\r\n<img width=\"1643\" alt=\"Screenshot 2025-02-04 at 3 55 32 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5fbf27d2-dcb5-40d1-b466-c8bcc2d700c9\"\r\n/>\r\n\r\n- ### Metric threshold alert details page\r\n<img width=\"1645\" alt=\"Screenshot 2025-02-04 at 3 54 58 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/8968c803-ff73-4f7d-8501-f6a1e7e16e8c\"\r\n/>","sha":"551d31b0ffffd48d221b09acafc740c1d514ac75"}}]}] BACKPORT--> Co-authored-by: Bena Kansara <69037875+benakansara@users.noreply.github.com> |
||
|
Kibana Machine
|
a2fe6f3ca5
|
[8.17] Added max_file_size_bytes advanced option to malware for all OSs. (#209541) (#209653)
# Backport This will backport the following commits from `main` to `8.17`: - [Added max_file_size_bytes advanced option to malware for all OSs. (#209541)](https://github.com/elastic/kibana/pull/209541) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthew Scherer","email":"57465354+matthewscherer@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-04T19:49:35Z","message":"Added max_file_size_bytes advanced option to malware for all OSs. (#209541)\n\n## Summary\r\n\r\nThis adds an advanced option \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- [x]\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- [x] 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\nThis is an advanced option. No risks. \r\n\r\n\r\n### Release notes\r\n[os].advanced.malware.max_file_size_bytes key was added to control the\r\nmaximum file size the endpoint will scan for malware.\r\n\r\n---------\r\n\r\nCo-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>","sha":"3d7ccc5544f21f9b470cdd186730182c489c046d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Defend Workflows","release_note:feature","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","backport:8.17","v9.1.0"],"title":"Added max_file_size_bytes advanced option to malware for all OSs.","number":209541,"url":"https://github.com/elastic/kibana/pull/209541","mergeCommit":{"message":"Added max_file_size_bytes advanced option to malware for all OSs. (#209541)\n\n## Summary\r\n\r\nThis adds an advanced option \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- [x]\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- [x] 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\nThis is an advanced option. No risks. \r\n\r\n\r\n### Release notes\r\n[os].advanced.malware.max_file_size_bytes key was added to control the\r\nmaximum file size the endpoint will scan for malware.\r\n\r\n---------\r\n\r\nCo-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>","sha":"3d7ccc5544f21f9b470cdd186730182c489c046d"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209541","number":209541,"mergeCommit":{"message":"Added max_file_size_bytes advanced option to malware for all OSs. (#209541)\n\n## Summary\r\n\r\nThis adds an advanced option \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- [x]\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- [x] 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\nThis is an advanced option. No risks. \r\n\r\n\r\n### Release notes\r\n[os].advanced.malware.max_file_size_bytes key was added to control the\r\nmaximum file size the endpoint will scan for malware.\r\n\r\n---------\r\n\r\nCo-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>","sha":"3d7ccc5544f21f9b470cdd186730182c489c046d"}}]}] BACKPORT--> Co-authored-by: Matthew Scherer <57465354+matthewscherer@users.noreply.github.com> |
||
|
Kibana Machine
|
2d2fe80c3f
|
[8.17] [ObsUX] Skip flaky tests (#209500) (#209601)
# Backport This will backport the following commits from `main` to `8.17`: - [[ObsUX] Skip flaky tests (#209500)](https://github.com/elastic/kibana/pull/209500) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Miriam","email":"31922082+MiriamAparicio@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-04T17:26:10Z","message":"[ObsUX] Skip flaky tests (#209500)\n\n## Summary\r\n\r\nProcesses and Logs tabs test has been flaky for some time, after\r\ndifferent and numerous attempts to fix them we want to consider removing\r\nthem and convert them to component test.\r\n\r\nThis PR skips Processes tab as Logs tab was already skipped, and we\r\nopened an issue make them component tests.\r\nhttps://github.com/elastic/kibana/issues/209497\r\n\r\nCloses: https://github.com/elastic/kibana/issues/192891 &\r\nhttps://github.com/elastic/kibana/issues/203656","sha":"8fee85d84148b6e576c091d215d1c459ac38488d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-failure-flaky","v9.0.0","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[ObsUX] Skip flaky tests","number":209500,"url":"https://github.com/elastic/kibana/pull/209500","mergeCommit":{"message":"[ObsUX] Skip flaky tests (#209500)\n\n## Summary\r\n\r\nProcesses and Logs tabs test has been flaky for some time, after\r\ndifferent and numerous attempts to fix them we want to consider removing\r\nthem and convert them to component test.\r\n\r\nThis PR skips Processes tab as Logs tab was already skipped, and we\r\nopened an issue make them component tests.\r\nhttps://github.com/elastic/kibana/issues/209497\r\n\r\nCloses: https://github.com/elastic/kibana/issues/192891 &\r\nhttps://github.com/elastic/kibana/issues/203656","sha":"8fee85d84148b6e576c091d215d1c459ac38488d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209500","number":209500,"mergeCommit":{"message":"[ObsUX] Skip flaky tests (#209500)\n\n## Summary\r\n\r\nProcesses and Logs tabs test has been flaky for some time, after\r\ndifferent and numerous attempts to fix them we want to consider removing\r\nthem and convert them to component test.\r\n\r\nThis PR skips Processes tab as Logs tab was already skipped, and we\r\nopened an issue make them component tests.\r\nhttps://github.com/elastic/kibana/issues/209497\r\n\r\nCloses: https://github.com/elastic/kibana/issues/192891 &\r\nhttps://github.com/elastic/kibana/issues/203656","sha":"8fee85d84148b6e576c091d215d1c459ac38488d"}}]}] BACKPORT--> Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com> |
||
|
Kibana Machine
|
c16c8f6900
|
[8.17] [Telemetry][Security Solution] Send new Endpoint field (#209149) (#209503)
# Backport This will backport the following commits from `main` to `8.17`: - [[Telemetry][Security Solution] Send new Endpoint field (#209149)](https://github.com/elastic/kibana/pull/209149) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sebastián Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T10:49:25Z","message":"[Telemetry][Security Solution] Send new Endpoint field (#209149)\n\n## Summary\r\n\r\nMake the Security Solution `endpoint-meta-telemetry` task send the new\r\nEndpoint field `Endpoint.metrics.top_process_trees`\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [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\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e15d089b369462cbd9d777a24dcd15582b7cba10","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","backport:prev-major","v8.18.0","v9.1.0","v8.19.0"],"title":"[Telemetry][Security Solution] Send new Endpoint field","number":209149,"url":"https://github.com/elastic/kibana/pull/209149","mergeCommit":{"message":"[Telemetry][Security Solution] Send new Endpoint field (#209149)\n\n## Summary\r\n\r\nMake the Security Solution `endpoint-meta-telemetry` task send the new\r\nEndpoint field `Endpoint.metrics.top_process_trees`\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [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\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e15d089b369462cbd9d777a24dcd15582b7cba10"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"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/209149","number":209149,"mergeCommit":{"message":"[Telemetry][Security Solution] Send new Endpoint field (#209149)\n\n## Summary\r\n\r\nMake the Security Solution `endpoint-meta-telemetry` task send the new\r\nEndpoint field `Endpoint.metrics.top_process_trees`\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [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\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e15d089b369462cbd9d777a24dcd15582b7cba10"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co> |
||
|
Kibana Machine
|
01eecf8a45
|
[8.17] [APM] Fix missing exception stack trace (#208577) (#209494)
# Backport This will backport the following commits from `main` to `8.17`: - [[APM] Fix missing exception stack trace (#208577)](https://github.com/elastic/kibana/pull/208577) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milosz Marcinkowski","email":"38698566+miloszmarcinkowski@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-04T10:19:07Z","message":"[APM] Fix missing exception stack trace (#208577)\n\nCloses #203359\r\n\r\n## Summary\r\n\r\nFix the incorrect condition that prevents an exception stack trace from\r\nbeing displayed.\r\n\r\n| before | after |\r\n|-|-|\r\n| <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 00\"\r\nsrc=\"https://github.com/user-attachments/assets/88656d5e-0964-4686-8a03-a07ab8459709\"\r\n/> | <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 38\"\r\nsrc=\"https://github.com/user-attachments/assets/037cbb98-d7cf-4388-8d94-80c32eb5b17f\"\r\n/> |\r\n\r\n## AC:\r\n\r\n- [x] Exception stack trace is displayed in APM,\r\n- [x] Tested with native Otel collector,\r\n- [x] ~~Wait until data ingestion is fixed and changes can be tested\r\nwith v8.16 and higher~~ (not applicable anymore).","sha":"2fd10dbabe65896ab5031b9edb96654b80606fe7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM] Fix missing exception stack trace ","number":208577,"url":"https://github.com/elastic/kibana/pull/208577","mergeCommit":{"message":"[APM] Fix missing exception stack trace (#208577)\n\nCloses #203359\r\n\r\n## Summary\r\n\r\nFix the incorrect condition that prevents an exception stack trace from\r\nbeing displayed.\r\n\r\n| before | after |\r\n|-|-|\r\n| <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 00\"\r\nsrc=\"https://github.com/user-attachments/assets/88656d5e-0964-4686-8a03-a07ab8459709\"\r\n/> | <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 38\"\r\nsrc=\"https://github.com/user-attachments/assets/037cbb98-d7cf-4388-8d94-80c32eb5b17f\"\r\n/> |\r\n\r\n## AC:\r\n\r\n- [x] Exception stack trace is displayed in APM,\r\n- [x] Tested with native Otel collector,\r\n- [x] ~~Wait until data ingestion is fixed and changes can be tested\r\nwith v8.16 and higher~~ (not applicable anymore).","sha":"2fd10dbabe65896ab5031b9edb96654b80606fe7"}},"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/208577","number":208577,"mergeCommit":{"message":"[APM] Fix missing exception stack trace (#208577)\n\nCloses #203359\r\n\r\n## Summary\r\n\r\nFix the incorrect condition that prevents an exception stack trace from\r\nbeing displayed.\r\n\r\n| before | after |\r\n|-|-|\r\n| <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 00\"\r\nsrc=\"https://github.com/user-attachments/assets/88656d5e-0964-4686-8a03-a07ab8459709\"\r\n/> | <img width=\"2560\" alt=\"Screenshot 2025-01-31 at 10 06 38\"\r\nsrc=\"https://github.com/user-attachments/assets/037cbb98-d7cf-4388-8d94-80c32eb5b17f\"\r\n/> |\r\n\r\n## AC:\r\n\r\n- [x] Exception stack trace is displayed in APM,\r\n- [x] Tested with native Otel collector,\r\n- [x] ~~Wait until data ingestion is fixed and changes can be tested\r\nwith v8.16 and higher~~ (not applicable anymore).","sha":"2fd10dbabe65896ab5031b9edb96654b80606fe7"}}]}] BACKPORT--> Co-authored-by: Milosz Marcinkowski <38698566+miloszmarcinkowski@users.noreply.github.com> |
||
Maryam Saeidi
|
732ea4f84a
|
[8.17] [Custom threshold] Fix using data view runtime fields during rule execution for the custom threshold rule (#209133) (#209280)
# Backport This will backport the following commits from `main` to `8.17`: - [[Custom threshold] Fix using data view runtime fields during rule execution for the custom threshold rule (#209133)](https://github.com/elastic/kibana/pull/209133) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T11:09:29Z","message":"[Custom threshold] Fix using data view runtime fields during rule execution for the custom threshold rule (#209133)\n\nFixes #200772\r\n\r\n## 🐉 Summary\r\n\r\n\r\nThis PR fixes supporting data view runtime fields during rule execution\r\nfor the custom threshold rule.\r\n\r\n## 🧪 How to test\r\n\r\n1. Create a runtime field as shown below:\r\n\r\n |Runtime field| Preview|\r\n |---|---|\r\n\r\n|![Image]( |