mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 00:13:52 -04:00
43281 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Jan Monschke
|
87e8b1406d
|
[8.16] [SecuritySolution][Alerts table] Fix issue with multiple ip addresses in strings (#209475) (#209969)
# Backport This will backport the following commits from `main` to `8.16`: - [[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>"}}]}] BACKPORT--> |
||
Faisal Kanout
|
348ee74216
|
[8.16] [OBX-UX-MGMT][BUG] Fix chart in Custom Threshold rule when the field name has slashes (#209263) (#209717)
# Backport This will backport the following commits from `main` to `8.16`: - [[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>"}},{"url":"https://github.com/elastic/kibana/pull/209712","number":209712,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> |
||
Yara Tercero
|
90b568b81a
|
[8.16] [Detection Engine][Docs] Updating examples to meet old ascii docs (#207558) (#209951)
# Backport This will backport the following commits from `main` to `8.16`: - [[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--> |
||
Nathan Reese
|
7bd84beb05
|
[8.16] [canvas] fix All embeddables rebuilt on refresh (#209677) (#209862)
# Backport This will backport the following commits from `main` to `8.16`: - [[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
|
baf44fa969
|
[8.16] [Automatic Import] Fix Structured log template to use single quotes (#209736) (#209780)
# Backport This will backport the following commits from `main` to `8.16`: - [[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
|
7a67721fe1
|
[8.16] [Custom threshold/Metric threshold] Display No Data in Threshold breached component (#209561) (#209657)
# Backport This will backport the following commits from `main` to `8.16`: - [[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
|
0c15d8d741
|
[8.16] Added max_file_size_bytes advanced option to malware for all OSs. (#209541) (#209652)
# Backport This will backport the following commits from `main` to `8.16`: - [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
|
2ee343ebc4
|
[8.16] [ObsUX] Skip flaky tests (#209500) (#209600)
# Backport This will backport the following commits from `main` to `8.16`: - [[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> |
||
Maryam Saeidi
|
d915fd29c4
|
[8.16] [Custom threshold] Fix using data view runtime fields during rule execution for the custom threshold rule (#209133) (#209287)
# Backport This will backport the following commits from `main` to `8.16`: - [[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| (#209493)
# Backport This will backport the following commits from `main` to `8.16`: - [[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> |
||
|
Kibana Machine
|
0cd6dea2c7
|
[8.16] [Telemetry][Security Solution] Send new Endpoint field (#209149) (#209501)
# Backport This will backport the following commits from `main` to `8.16`: - [[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> |
||
Gergő Ábrahám
|
51a908caa8
|
[8.16] [EDR Workflows] Fix invalid event filter for cloud workloads (#208974) (#209330)
# Backport This will backport the following commits from `main` to `8.16`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](https://github.com/elastic/kibana/pull/208974) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","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 invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"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/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},{"url":"https://github.com/elastic/kibana/pull/209284","number":209284,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209285","number":209285,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209288","number":209288,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209290","number":209290,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
jennypavlova
|
f957712a6d
|
[8.16] [Infra] Running processes missing from processes table (#209076) (#209476)
# Backport This will backport the following commits from `main` to `8.16`: - [[Infra] Running processes missing from processes table (#209076)](https://github.com/elastic/kibana/pull/209076) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-04T08:25:36Z","message":"[Infra] Running processes missing from processes table (#209076)\n\nCloses #184582\r\n\r\n## Summary\r\n\r\nThis PR fixes an issue with processes missing from the processes table\r\nand not being searchable.\r\n\r\n- Additional fixes: The chart size was not set correctly and they were\r\nnot visible so it is fixed now:\r\n\r\n| Before | After |\r\n| ---- | ------ |\r\n|\r\n
Alex Szabo
|
b43949ea57 | skip failing suite (#184681) | ||
|
Kibana Machine
|
60477b0824
|
[8.16] [Obs AI Assistant] Fix multiple flyouts (#209158) (#209167)
# Backport This will backport the following commits from `main` to `8.16`: - [[Obs AI Assistant] Fix multiple flyouts (#209158)](https://github.com/elastic/kibana/pull/209158) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-01-31T19:59:01Z","message":"[Obs AI Assistant] Fix multiple flyouts (#209158)","sha":"50b8776b1fb6e7e6e2a96a8b61edc499579bf260","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:Obs AI Assistant","backport:version","v8.18.0","v8.16.4","v8.17.2","v9.1.0"],"title":"[Obs AI Assistant] Fix multiple flyouts","number":209158,"url":"https://github.com/elastic/kibana/pull/209158","mergeCommit":{"message":"[Obs AI Assistant] Fix multiple flyouts (#209158)","sha":"50b8776b1fb6e7e6e2a96a8b61edc499579bf260"}},"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/209158","number":209158,"mergeCommit":{"message":"[Obs AI Assistant] Fix multiple flyouts (#209158)","sha":"50b8776b1fb6e7e6e2a96a8b61edc499579bf260"}}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
c2c4490204
|
[8.16] [ResponseOps] Fix connector test (#208754) (#209058)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps] Fix connector test (#208754)](https://github.com/elastic/kibana/pull/208754) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-31T08:11:15Z","message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","backport:prev-major","v9.1.0"],"title":"[ResponseOps] Fix connector test","number":208754,"url":"https://github.com/elastic/kibana/pull/208754","mergeCommit":{"message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5"}},"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/208754","number":208754,"mergeCommit":{"message":"[ResponseOps] Fix connector test (#208754)\n\n## Summary\r\n\r\nThis PR fixes a test introduced in\r\nhttps://github.com/elastic/kibana/pull/208033","sha":"5a57f40f6708fbb74b5929e7cd3856524825c8b5"}}]}] BACKPORT--> Co-authored-by: Antonio <antonio.coelho@elastic.co> |
||
|
Kibana Machine
|
a702e9c82c
|
[8.16] Increase maximum Osquery timeout to 24 hours (#207276) (#209035)
# Backport This will backport the following commits from `main` to `8.16`: - [Increase maximum Osquery timeout to 24 hours (#207276)](https://github.com/elastic/kibana/pull/207276) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Michael Wolf","email":"michael.wolf@elastic.co"},"sourceCommit":{"committedDate":"2025-01-31T00:18:47Z","message":"Increase maximum Osquery timeout to 24 hours (#207276)\n\nSome Osquery queries are expected to be long running. To accommodate\r\nthis, increase the maximum timeout in the query creation UI to 24 hours\r\n(86400 seconds).\r\n\r\n24 hours should allow most long-running queries, while still having a\r\nlimit that ensures misbehaving queries do not block others for an\r\nextremely long time.\r\n\r\nRelates to https://github.com/elastic/beats/issues/42352. Osquerybeat\r\nwill also increase its timeout limit to 24h, this change will allow the\r\nhigher timeout to be set by users in Kibana.","sha":"81a57e005ed0a6b72a254056813b1c6ee633da1f","branchLabelMapping":{"^v9.0.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:prev-major"],"title":"Increase maximum Osquery timeout to 24 hours","number":207276,"url":"https://github.com/elastic/kibana/pull/207276","mergeCommit":{"message":"Increase maximum Osquery timeout to 24 hours (#207276)\n\nSome Osquery queries are expected to be long running. To accommodate\r\nthis, increase the maximum timeout in the query creation UI to 24 hours\r\n(86400 seconds).\r\n\r\n24 hours should allow most long-running queries, while still having a\r\nlimit that ensures misbehaving queries do not block others for an\r\nextremely long time.\r\n\r\nRelates to https://github.com/elastic/beats/issues/42352. Osquerybeat\r\nwill also increase its timeout limit to 24h, this change will allow the\r\nhigher timeout to be set by users in Kibana.","sha":"81a57e005ed0a6b72a254056813b1c6ee633da1f"}},"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/207276","number":207276,"mergeCommit":{"message":"Increase maximum Osquery timeout to 24 hours (#207276)\n\nSome Osquery queries are expected to be long running. To accommodate\r\nthis, increase the maximum timeout in the query creation UI to 24 hours\r\n(86400 seconds).\r\n\r\n24 hours should allow most long-running queries, while still having a\r\nlimit that ensures misbehaving queries do not block others for an\r\nextremely long time.\r\n\r\nRelates to https://github.com/elastic/beats/issues/42352. Osquerybeat\r\nwill also increase its timeout limit to 24h, this change will allow the\r\nhigher timeout to be set by users in Kibana.","sha":"81a57e005ed0a6b72a254056813b1c6ee633da1f"}}]}] BACKPORT--> Co-authored-by: Michael Wolf <michael.wolf@elastic.co> |
||
|
Kibana Machine
|
310514fd16
|
[8.16] [Security GenAI] "Select a Connector" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969) (#208989)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] "Select a Connector" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)](https://github.com/elastic/kibana/pull/208969) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T16:53:36Z","message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a","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: SecuritySolution","backport:prev-major","Team:Security Generative AI"],"title":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907)","number":208969,"url":"https://github.com/elastic/kibana/pull/208969","mergeCommit":{"message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a"}},"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/208969","number":208969,"mergeCommit":{"message":"[Security GenAI] \"Select a Connector\" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights. (#208907) (#208969)\n\n## Summary\r\n\r\nBUG: https://github.com/elastic/kibana/issues/208907\r\n\r\nThis PR fixes the issue where user cannot select a different connector\r\ntype after mistakenly selecting a wrong one.\r\n\r\n### Steps to reproduce without required endpoint installation:\r\n\r\n1. Make sure there are no connectors\r\n2. Open \"AI Assistant\" on one of the security solution pages\r\n3. Press \"(+) Add connector\" button\r\n4. Connector type selection modal is visible\r\n5. Select \"Amazon Bedrock\" type (or any other connector type)\r\n6. Cancel the modal\r\n7. Press \"(+) Add connector\" button again\r\n\r\n**ISSUE**: previously selected connector type is being displayed and\r\nthere is no way to switch between types\r\n**EXPECTED**: we should show connector type selection modal once\r\nprevious one was closed\r\n\r\n### Issue recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48052bf1-4e00-43b7-a63e-f8a7969b9dbf\r\n\r\n### Fixed state recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48be1cc4-0326-43a1-bd57-bb82fc1f19eb","sha":"b28036a2e0f13358b4da614761d32667612ac03a"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
88d8fef550
|
[8.16] [Synthetics] Fix ping heatmap regression when Inspect flag is turned off !! (#208726) (#208794)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fix ping heatmap regression when Inspect flag is turned off !! (#208726)](https://github.com/elastic/kibana/pull/208726) <!--- 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":"2025-01-29T16:35:52Z","message":"[Synthetics] Fix ping heatmap regression when Inspect flag is turned off !! (#208726)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/208304 !!\r\n\r\nFix ping heatmap regression when Inspect flag is turned off !!\r\n\r\nThis flag is turned on auto in dev which caused an issue !!\r\n\r\nTo reproduce the step, you can turn off the inspect flag in dev mode by\r\nremoving `this.isDev `from this condition\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/synthetics/server/lib.ts#L93\r\n\r\n### After\r\n\r\n<img width=\"1726\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ad786351-37e4-4c18-b68e-695880d836e9\"\r\n/>","sha":"557cac273c70bced82f961148c4f4f86ccda0580","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:obs-ux-management","backport:version"],"title":"[Synthetics] Fix ping heatmap regression when Inspect flag is turned off !!","number":208726,"url":"https://github.com/elastic/kibana/pull/208726","mergeCommit":{"message":"[Synthetics] Fix ping heatmap regression when Inspect flag is turned off !! (#208726)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/208304 !!\r\n\r\nFix ping heatmap regression when Inspect flag is turned off !!\r\n\r\nThis flag is turned on auto in dev which caused an issue !!\r\n\r\nTo reproduce the step, you can turn off the inspect flag in dev mode by\r\nremoving `this.isDev `from this condition\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/synthetics/server/lib.ts#L93\r\n\r\n### After\r\n\r\n<img width=\"1726\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ad786351-37e4-4c18-b68e-695880d836e9\"\r\n/>","sha":"557cac273c70bced82f961148c4f4f86ccda0580"}},"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/208726","number":208726,"mergeCommit":{"message":"[Synthetics] Fix ping heatmap regression when Inspect flag is turned off !! (#208726)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/208304 !!\r\n\r\nFix ping heatmap regression when Inspect flag is turned off !!\r\n\r\nThis flag is turned on auto in dev which caused an issue !!\r\n\r\nTo reproduce the step, you can turn off the inspect flag in dev mode by\r\nremoving `this.isDev `from this condition\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/synthetics/server/lib.ts#L93\r\n\r\n### After\r\n\r\n<img width=\"1726\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ad786351-37e4-4c18-b68e-695880d836e9\"\r\n/>","sha":"557cac273c70bced82f961148c4f4f86ccda0580"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
a249734364
|
[8.16] [Automatic Import] Add missing fields to input manifest templates (#208768) (#208800)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import] Add missing fields to input manifest templates (#208768)](https://github.com/elastic/kibana/pull/208768) <!--- 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-01-29T16:59:58Z","message":"[Automatic Import] Add missing fields to input manifest templates (#208768)\n\n## Summary\r\n\r\nAdds missing fields to input manifest templates.","sha":"45131838005d033a41be0fb23bcaf4d45db5ebd1","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic Import] Add missing fields to input manifest templates","number":208768,"url":"https://github.com/elastic/kibana/pull/208768","mergeCommit":{"message":"[Automatic Import] Add missing fields to input manifest templates (#208768)\n\n## Summary\r\n\r\nAdds missing fields to input manifest templates.","sha":"45131838005d033a41be0fb23bcaf4d45db5ebd1"}},"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/208768","number":208768,"mergeCommit":{"message":"[Automatic Import] Add missing fields to input manifest templates (#208768)\n\n## Summary\r\n\r\nAdds missing fields to input manifest templates.","sha":"45131838005d033a41be0fb23bcaf4d45db5ebd1"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Matthew Kime
|
c386042452
|
[8.16] [search profiler] Move profile button inline with index field (#202253) (#208480)
# Backport This will backport the following commits from `main` to `8.16`: - [[search profiler] Move profile button inline with index field (#202253)](https://github.com/elastic/kibana/pull/202253) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-01-22T04:01:43Z","message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","Feature:Search Profiler","v9.0.0","backport:prev-major","v8.18.0"],"title":"[search profiler] Move profile button inline with index field","number":202253,"url":"https://github.com/elastic/kibana/pull/202253","mergeCommit":{"message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3"}},"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/202253","number":202253,"mergeCommit":{"message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207648","number":207648,"state":"MERGED","mergeCommit":{"sha":"5db51893984383cfd76eeb91a63ec23cfaa32f50","message":"[8.x] [search profiler] Move profile button inline with index field (#202253) (#207648)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[search profiler] Move profile button inline with index field\n(#202253)](https://github.com/elastic/kibana/pull/202253)\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\":\"Matthew\nKime\",\"email\":\"matt@mattki.me\"},\"sourceCommit\":{\"committedDate\":\"2025-01-22T04:01:43Z\",\"message\":\"[search\nprofiler] Move profile button inline with index field (#202253)\\n\\n##\nSummary\\r\\n\\r\\nAt smaller window sizes, the `Profile` button disappears\nbeneath the\\r\\ncode editor. Lets move it to the top and shrink\nit.\\r\\n\\r\\n<img width=\\\"1051\\\" alt=\\\"Screenshot 2024-11-30 at 11 47\n27 PM\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\\\">\",\"sha\":\"c12c88d243840d498b767a5f9b29f2748d4b2ff3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Kibana\nManagement\",\"release_note:skip\",\"Feature:Search\nProfiler\",\"v9.0.0\",\"backport:prev-major\"],\"title\":\"[search profiler]\nMove profile button inline with index\nfield\",\"number\":202253,\"url\":\"https://github.com/elastic/kibana/pull/202253\",\"mergeCommit\":{\"message\":\"[search\nprofiler] Move profile button inline with index field (#202253)\\n\\n##\nSummary\\r\\n\\r\\nAt smaller window sizes, the `Profile` button disappears\nbeneath the\\r\\ncode editor. Lets move it to the top and shrink\nit.\\r\\n\\r\\n<img width=\\\"1051\\\" alt=\\\"Screenshot 2024-11-30 at 11 47\n27 PM\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\\\">\",\"sha\":\"c12c88d243840d498b767a5f9b29f2748d4b2ff3\"}},\"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/202253\",\"number\":202253,\"mergeCommit\":{\"message\":\"[search\nprofiler] Move profile button inline with index field (#202253)\\n\\n##\nSummary\\r\\n\\r\\nAt smaller window sizes, the `Profile` button disappears\nbeneath the\\r\\ncode editor. Lets move it to the top and shrink\nit.\\r\\n\\r\\n<img width=\\\"1051\\\" alt=\\\"Screenshot 2024-11-30 at 11 47\n27 PM\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\\\">\",\"sha\":\"c12c88d243840d498b767a5f9b29f2748d4b2ff3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Matthew Kime <matt@mattki.me>"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3512420dbf
|
[8.16] [ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API (#208033) (#208658)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API (#208033)](https://github.com/elastic/kibana/pull/208033) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-29T00:37:12Z","message":"[ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API (#208033)\n\nCloses #207188\r\n\r\n## Summary\r\n\r\nThis is a freak scenario that is hard to reproduce. That is why I did\r\nnot add a test in\r\n`x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/actions/delete.ts`.\r\nWe cannot create a connector with an unregistered type so there is no\r\nway to test deletion in the functional tests.\r\n\r\nI added a unit test and there are steps below to test manually too.\r\n\r\n### How to reproduce\r\n\r\n1. Create a connector, let's say `Pagerduty`.\r\n2. Stop Kibana.\r\n3. Change the connector type id in\r\n`stack_connectors/server/connector_types/pagerduty/index.ts`\r\n - `'.pagerduty'` -> `'.pagerduty-foobar'`.\r\n- This will mean that when you restart Kibana a new connector ID will be\r\nregistered and the existing connector you created will be invalid/not\r\nsupported.\r\n4. Restart Kibana.\r\n5. Try to delete the connector.\r\n\r\nIf this PR works, you can delete the connector, and an error should be\r\nlogged in the Kibana console.\r\n\r\nOn main the deletion would have failed.","sha":"e5d38af58bbd6bd62c2869516c383383245a3d0d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Actions/ConnectorsManagement","backport:prev-major"],"title":"[ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API","number":208033,"url":"https://github.com/elastic/kibana/pull/208033","mergeCommit":{"message":"[ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API (#208033)\n\nCloses #207188\r\n\r\n## Summary\r\n\r\nThis is a freak scenario that is hard to reproduce. That is why I did\r\nnot add a test in\r\n`x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/actions/delete.ts`.\r\nWe cannot create a connector with an unregistered type so there is no\r\nway to test deletion in the functional tests.\r\n\r\nI added a unit test and there are steps below to test manually too.\r\n\r\n### How to reproduce\r\n\r\n1. Create a connector, let's say `Pagerduty`.\r\n2. Stop Kibana.\r\n3. Change the connector type id in\r\n`stack_connectors/server/connector_types/pagerduty/index.ts`\r\n - `'.pagerduty'` -> `'.pagerduty-foobar'`.\r\n- This will mean that when you restart Kibana a new connector ID will be\r\nregistered and the existing connector you created will be invalid/not\r\nsupported.\r\n4. Restart Kibana.\r\n5. Try to delete the connector.\r\n\r\nIf this PR works, you can delete the connector, and an error should be\r\nlogged in the Kibana console.\r\n\r\nOn main the deletion would have failed.","sha":"e5d38af58bbd6bd62c2869516c383383245a3d0d"}},"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/208033","number":208033,"mergeCommit":{"message":"[ResponseOps][Actions] Allow to delete connectors with unsupported connector type using the API (#208033)\n\nCloses #207188\r\n\r\n## Summary\r\n\r\nThis is a freak scenario that is hard to reproduce. That is why I did\r\nnot add a test in\r\n`x-pack/test/alerting_api_integration/security_and_spaces/group2/tests/actions/delete.ts`.\r\nWe cannot create a connector with an unregistered type so there is no\r\nway to test deletion in the functional tests.\r\n\r\nI added a unit test and there are steps below to test manually too.\r\n\r\n### How to reproduce\r\n\r\n1. Create a connector, let's say `Pagerduty`.\r\n2. Stop Kibana.\r\n3. Change the connector type id in\r\n`stack_connectors/server/connector_types/pagerduty/index.ts`\r\n - `'.pagerduty'` -> `'.pagerduty-foobar'`.\r\n- This will mean that when you restart Kibana a new connector ID will be\r\nregistered and the existing connector you created will be invalid/not\r\nsupported.\r\n4. Restart Kibana.\r\n5. Try to delete the connector.\r\n\r\nIf this PR works, you can delete the connector, and an error should be\r\nlogged in the Kibana console.\r\n\r\nOn main the deletion would have failed.","sha":"e5d38af58bbd6bd62c2869516c383383245a3d0d"}}]}] BACKPORT--> Co-authored-by: Antonio <antonio.coelho@elastic.co> |
||
Christos Nasikas
|
f81c0edb27
|
[8.16] [ResponseOps][Rules] Validate timezone in rule routes (#201508) (#208300)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][Rules] Validate timezone in rule routes (#201508)](https://github.com/elastic/kibana/pull/201508) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-01-24T17:46:24Z","message":"[ResponseOps][Rules] Validate timezone in rule routes (#201508)\n\n## Summary\r\n\r\nThis PR adds validation only for internal routes that use the `rRule`\r\nschema.\r\n\r\n## Testing\r\n\r\n1. Create a rule in main.\r\n2. Snooze the rule by using the API as\r\n\r\n```\r\nPOST /internal/alerting/rule/<ruleId>/_snooze\r\n{\r\n \"snooze_schedule\": {\r\n \"id\": \"e58e2340-dba6-454c-8308-b2ca66a7cf7b\",\r\n \"duration\": 86400000,\r\n \"rRule\": {\r\n \"dtstart\": \"2024-09-04T09:27:37.011Z\",\r\n \"tzid\": \"invalid\",\r\n \"freq\": 2,\r\n \"interval\": 1,\r\n \"byweekday\": [\r\n \"invalid\"\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n\r\n4. Go to the rules page and verify that the rules are not loaded.\r\n5. Switch to my PR.\r\n6. Go to the rules page and verify that the rules load.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a3fc89629e1a6cec2f5200bb75099fcab866701","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesFramework","backport:prev-major","v8.18.0","v8.16.4","v8.17.2"],"title":"[ResponseOps][Rules] Validate timezone in rule routes","number":201508,"url":"https://github.com/elastic/kibana/pull/201508","mergeCommit":{"message":"[ResponseOps][Rules] Validate timezone in rule routes (#201508)\n\n## Summary\r\n\r\nThis PR adds validation only for internal routes that use the `rRule`\r\nschema.\r\n\r\n## Testing\r\n\r\n1. Create a rule in main.\r\n2. Snooze the rule by using the API as\r\n\r\n```\r\nPOST /internal/alerting/rule/<ruleId>/_snooze\r\n{\r\n \"snooze_schedule\": {\r\n \"id\": \"e58e2340-dba6-454c-8308-b2ca66a7cf7b\",\r\n \"duration\": 86400000,\r\n \"rRule\": {\r\n \"dtstart\": \"2024-09-04T09:27:37.011Z\",\r\n \"tzid\": \"invalid\",\r\n \"freq\": 2,\r\n \"interval\": 1,\r\n \"byweekday\": [\r\n \"invalid\"\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n\r\n4. Go to the rules page and verify that the rules are not loaded.\r\n5. Switch to my PR.\r\n6. Go to the rules page and verify that the rules load.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a3fc89629e1a6cec2f5200bb75099fcab866701"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201508","number":201508,"mergeCommit":{"message":"[ResponseOps][Rules] Validate timezone in rule routes (#201508)\n\n## Summary\r\n\r\nThis PR adds validation only for internal routes that use the `rRule`\r\nschema.\r\n\r\n## Testing\r\n\r\n1. Create a rule in main.\r\n2. Snooze the rule by using the API as\r\n\r\n```\r\nPOST /internal/alerting/rule/<ruleId>/_snooze\r\n{\r\n \"snooze_schedule\": {\r\n \"id\": \"e58e2340-dba6-454c-8308-b2ca66a7cf7b\",\r\n \"duration\": 86400000,\r\n \"rRule\": {\r\n \"dtstart\": \"2024-09-04T09:27:37.011Z\",\r\n \"tzid\": \"invalid\",\r\n \"freq\": 2,\r\n \"interval\": 1,\r\n \"byweekday\": [\r\n \"invalid\"\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n\r\n4. Go to the rules page and verify that the rules are not loaded.\r\n5. Switch to my PR.\r\n6. Go to the rules page and verify that the rules load.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a3fc89629e1a6cec2f5200bb75099fcab866701"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/208252","number":208252,"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"}]}] BACKPORT--> |
||
|
Kibana Machine
|
e1e83a47fb
|
[8.16] [Dashboard/Lens] Fix scroll jumping when editing from flyout (#207429) (#208407)
# Backport This will backport the following commits from `main` to `8.16`: - [[Dashboard/Lens] Fix scroll jumping when editing from flyout (#207429)](https://github.com/elastic/kibana/pull/207429) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nick Partridge","email":"nicholas.partridge@elastic.co"},"sourceCommit":{"committedDate":"2025-01-27T16:30:02Z","message":"[Dashboard/Lens] Fix scroll jumping when editing from flyout (#207429)\n\n## Summary\r\n\r\nFixes an issue that caused the body scroll to jump when clicking options\r\nin the Lens inline editor flyout.\r\n\r\nFixes #201544\r\n\r\nThis issue was created when we added the `autoFocus` option to the\r\n`EuiSelectable` for the dataview picker and the chart type picker.\r\n\r\nThis appears to be an issue with how eui is handling the `autoFocus`,\r\nsee https://github.com/elastic/eui/issues/8287.\r\n\r\nIn the meantime this is a workaround to prevent this scroll jumping\r\nwhile also keeping the auto focus behavior.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/94256fa7-f6bd-4943-91f6-42201ce4ab74\r\n\r\n### Checklist\r\n\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## Release note\r\n\r\nFixes and issue in Dashboards with the Lens inline editor where the\r\ndashboard would scroll to the top when interacting with the Lens editor\r\nflyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"a4089b1dbd2a4b2727a7b47a4bc83bd843e1777a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","release_note:fix","Team:Presentation","loe:small","Team:Visualizations","Feature:Lens","impact:high","v9.0.0","backport:prev-major"],"title":"[Dashboard/Lens] Fix scroll jumping when editing from flyout","number":207429,"url":"https://github.com/elastic/kibana/pull/207429","mergeCommit":{"message":"[Dashboard/Lens] Fix scroll jumping when editing from flyout (#207429)\n\n## Summary\r\n\r\nFixes an issue that caused the body scroll to jump when clicking options\r\nin the Lens inline editor flyout.\r\n\r\nFixes #201544\r\n\r\nThis issue was created when we added the `autoFocus` option to the\r\n`EuiSelectable` for the dataview picker and the chart type picker.\r\n\r\nThis appears to be an issue with how eui is handling the `autoFocus`,\r\nsee https://github.com/elastic/eui/issues/8287.\r\n\r\nIn the meantime this is a workaround to prevent this scroll jumping\r\nwhile also keeping the auto focus behavior.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/94256fa7-f6bd-4943-91f6-42201ce4ab74\r\n\r\n### Checklist\r\n\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## Release note\r\n\r\nFixes and issue in Dashboards with the Lens inline editor where the\r\ndashboard would scroll to the top when interacting with the Lens editor\r\nflyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"a4089b1dbd2a4b2727a7b47a4bc83bd843e1777a"}},"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/207429","number":207429,"mergeCommit":{"message":"[Dashboard/Lens] Fix scroll jumping when editing from flyout (#207429)\n\n## Summary\r\n\r\nFixes an issue that caused the body scroll to jump when clicking options\r\nin the Lens inline editor flyout.\r\n\r\nFixes #201544\r\n\r\nThis issue was created when we added the `autoFocus` option to the\r\n`EuiSelectable` for the dataview picker and the chart type picker.\r\n\r\nThis appears to be an issue with how eui is handling the `autoFocus`,\r\nsee https://github.com/elastic/eui/issues/8287.\r\n\r\nIn the meantime this is a workaround to prevent this scroll jumping\r\nwhile also keeping the auto focus behavior.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/94256fa7-f6bd-4943-91f6-42201ce4ab74\r\n\r\n### Checklist\r\n\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## Release note\r\n\r\nFixes and issue in Dashboards with the Lens inline editor where the\r\ndashboard would scroll to the top when interacting with the Lens editor\r\nflyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com>","sha":"a4089b1dbd2a4b2727a7b47a4bc83bd843e1777a"}}]}] BACKPORT--> Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co> |
||
Antonio
|
33063e343a
|
[8.16] [Response Ops] Fix maintenance window custom schedule create and update error (#192649) (#208334)
# Backport This will backport the following commits from `main` to `8.16`: - [[Response Ops] Fix maintenance window custom schedule create and update error (#192649)](https://github.com/elastic/kibana/pull/192649) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jiawei Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-16T23:52:00Z","message":"[Response Ops] Fix maintenance window custom schedule create and update error (#192649)\n\n## Summary\r\nFixes a bug where the backend would throw an error if we tried to create\r\nor update a maintenance window with a custom schedule. This was due to\r\nthe `form-lib` converting everything `frequency`, `interval`, and\r\n`customFrequency` field to a string and our logic assumed it was a\r\nnumber so the `===` comparisons were failing.\r\n\r\n### How to test:\r\n1. Navigate to the create maintenance window form\r\n2. Attempt to create a maintenance window with a custom schedule\r\n3. Assert the maintenance window was created successfully\r\n4. Attempt to edit the maintenance window with a different custom\r\nschedule\r\n5. Assert the maintenance window was edited successfully \r\n\r\nFixes: https://github.com/elastic/kibana/issues/192601\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"134b81572c4234e9c813aa5ed5dda286a99ffc32","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","backport:skip","Team:ResponseOps","v9.0.0","v8.16.0"],"title":"[Response Ops] Fix maintenance window custom schedule create and update error","number":192649,"url":"https://github.com/elastic/kibana/pull/192649","mergeCommit":{"message":"[Response Ops] Fix maintenance window custom schedule create and update error (#192649)\n\n## Summary\r\nFixes a bug where the backend would throw an error if we tried to create\r\nor update a maintenance window with a custom schedule. This was due to\r\nthe `form-lib` converting everything `frequency`, `interval`, and\r\n`customFrequency` field to a string and our logic assumed it was a\r\nnumber so the `===` comparisons were failing.\r\n\r\n### How to test:\r\n1. Navigate to the create maintenance window form\r\n2. Attempt to create a maintenance window with a custom schedule\r\n3. Assert the maintenance window was created successfully\r\n4. Attempt to edit the maintenance window with a different custom\r\nschedule\r\n5. Assert the maintenance window was edited successfully \r\n\r\nFixes: https://github.com/elastic/kibana/issues/192601\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"134b81572c4234e9c813aa5ed5dda286a99ffc32"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192649","number":192649,"mergeCommit":{"message":"[Response Ops] Fix maintenance window custom schedule create and update error (#192649)\n\n## Summary\r\nFixes a bug where the backend would throw an error if we tried to create\r\nor update a maintenance window with a custom schedule. This was due to\r\nthe `form-lib` converting everything `frequency`, `interval`, and\r\n`customFrequency` field to a string and our logic assumed it was a\r\nnumber so the `===` comparisons were failing.\r\n\r\n### How to test:\r\n1. Navigate to the create maintenance window form\r\n2. Attempt to create a maintenance window with a custom schedule\r\n3. Assert the maintenance window was created successfully\r\n4. Attempt to edit the maintenance window with a different custom\r\nschedule\r\n5. Assert the maintenance window was edited successfully \r\n\r\nFixes: https://github.com/elastic/kibana/issues/192601\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"134b81572c4234e9c813aa5ed5dda286a99ffc32"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com> |
||
|
Antonio
|
5a6b240dfd
|
[8.16] [ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084) (#208313)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084)](https://github.com/elastic/kibana/pull/207084) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-24T11:40:25Z","message":"[ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084)\n\nCloses #198774\r\n\r\n## Summary\r\n\r\n- There was a bug when submitting `rrule` with a `byweekday` I fixed\r\nthat validation to use a more inclusive regex. `byweekday` can be the\r\nexpected `MO`, `TU`, etc but also `-1FR` or `+3SA` where the number\r\ncorresponds to the week in a month.\r\n- The model version for the maintenance window was incorrect so when\r\nsaving the SO the validation was failing. I fixed that and now we are\r\nallowed to save `number[]` as expected.\r\n- I removed some duplicated code and we now use the `rrule` schema from\r\nthe `common` folder","sha":"0df78e629b429f6007f559aca339b4323b71e4c0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-major","v8.18.0"],"title":"[ResponseOps][MW] Fix bug when creating repeating Maintenance Window","number":207084,"url":"https://github.com/elastic/kibana/pull/207084","mergeCommit":{"message":"[ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084)\n\nCloses #198774\r\n\r\n## Summary\r\n\r\n- There was a bug when submitting `rrule` with a `byweekday` I fixed\r\nthat validation to use a more inclusive regex. `byweekday` can be the\r\nexpected `MO`, `TU`, etc but also `-1FR` or `+3SA` where the number\r\ncorresponds to the week in a month.\r\n- The model version for the maintenance window was incorrect so when\r\nsaving the SO the validation was failing. I fixed that and now we are\r\nallowed to save `number[]` as expected.\r\n- I removed some duplicated code and we now use the `rrule` schema from\r\nthe `common` folder","sha":"0df78e629b429f6007f559aca339b4323b71e4c0"}},"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/207084","number":207084,"mergeCommit":{"message":"[ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084)\n\nCloses #198774\r\n\r\n## Summary\r\n\r\n- There was a bug when submitting `rrule` with a `byweekday` I fixed\r\nthat validation to use a more inclusive regex. `byweekday` can be the\r\nexpected `MO`, `TU`, etc but also `-1FR` or `+3SA` where the number\r\ncorresponds to the week in a month.\r\n- The model version for the maintenance window was incorrect so when\r\nsaving the SO the validation was failing. I fixed that and now we are\r\nallowed to save `number[]` as expected.\r\n- I removed some duplicated code and we now use the `rrule` schema from\r\nthe `common` folder","sha":"0df78e629b429f6007f559aca339b4323b71e4c0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/208181","number":208181,"state":"MERGED","mergeCommit":{"sha":"8759f0286675744937e4ed8f5ad4880e35f6547e","message":"[8.x] [ResponseOps][MW] Fix bug when creating repeating Maintenance Window (#207084) (#208181)\n\n# Backport\r\n\r\nThis will backport the following commits from `main` to `8.x`:\r\n- [[ResponseOps][MW] Fix bug when creating repeating Maintenance Window\r\n(#207084)](https://github.com/elastic/kibana/pull/207084)\r\n\r\n<!--- Backport version: 9.6.4 -->\r\n\r\n### Questions ?\r\nPlease refer to the [Backport tool\r\ndocumentation](https://github.com/sorenlouv/backport)\r\n\r\n<!--BACKPORT\r\n[{\"author\":{\"name\":\"Antonio\",\"email\":\"antonio.coelho@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-24T11:40:25Z\",\"message\":\"[ResponseOps][MW]\r\nFix bug when creating repeating Maintenance Window (#207084)\\n\\nCloses\r\n#198774\\r\\n\\r\\n## Summary\\r\\n\\r\\n- There was a bug when submitting\r\n`rrule` with a `byweekday` I fixed\\r\\nthat validation to use a more\r\ninclusive regex. `byweekday` can be the\\r\\nexpected `MO`, `TU`, etc but\r\nalso `-1FR` or `+3SA` where the number\\r\\ncorresponds to the week in a\r\nmonth.\\r\\n- The model version for the maintenance window was incorrect\r\nso when\\r\\nsaving the SO the validation was failing. I fixed that and\r\nnow we are\\r\\nallowed to save `number[]` as expected.\\r\\n- I removed\r\nsome duplicated code and we now use the `rrule` schema from\\r\\nthe\r\n`common`\r\nfolder\",\"sha\":\"0df78e629b429f6007f559aca339b4323b71e4c0\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Feature:Alerting\",\"release_note:skip\",\"Team:ResponseOps\",\"v9.0.0\",\"backport:prev-major\"],\"title\":\"[ResponseOps][MW]\r\nFix bug when creating repeating Maintenance\r\nWindow\",\"number\":207084,\"url\":\"https://github.com/elastic/kibana/pull/207084\",\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\r\nFix bug when creating repeating Maintenance Window (#207084)\\n\\nCloses\r\n#198774\\r\\n\\r\\n## Summary\\r\\n\\r\\n- There was a bug when submitting\r\n`rrule` with a `byweekday` I fixed\\r\\nthat validation to use a more\r\ninclusive regex. `byweekday` can be the\\r\\nexpected `MO`, `TU`, etc but\r\nalso `-1FR` or `+3SA` where the number\\r\\ncorresponds to the week in a\r\nmonth.\\r\\n- The model version for the maintenance window was incorrect\r\nso when\\r\\nsaving the SO the validation was failing. I fixed that and\r\nnow we are\\r\\nallowed to save `number[]` as expected.\\r\\n- I removed\r\nsome duplicated code and we now use the `rrule` schema from\\r\\nthe\r\n`common`\r\nfolder\",\"sha\":\"0df78e629b429f6007f559aca339b4323b71e4c0\"}},\"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/207084\",\"number\":207084,\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\r\nFix bug when creating repeating Maintenance Window (#207084)\\n\\nCloses\r\n#198774\\r\\n\\r\\n## Summary\\r\\n\\r\\n- There was a bug when submitting\r\n`rrule` with a `byweekday` I fixed\\r\\nthat validation to use a more\r\ninclusive regex. `byweekday` can be the\\r\\nexpected `MO`, `TU`, etc but\r\nalso `-1FR` or `+3SA` where the number\\r\\ncorresponds to the week in a\r\nmonth.\\r\\n- The model version for the maintenance window was incorrect\r\nso when\\r\\nsaving the SO the validation was failing. I fixed that and\r\nnow we are\\r\\nallowed to save `number[]` as expected.\\r\\n- I removed\r\nsome duplicated code and we now use the `rrule` schema from\\r\\nthe\r\n`common` folder\",\"sha\":\"0df78e629b429f6007f559aca339b4323b71e4c0\"}}]}]\r\nBACKPORT-->"}},{"url":"https://github.com/elastic/kibana/pull/208312","number":208312,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ea8f4acba1
|
[8.16] [Lens] add an accessible label to range slider (#205308) (#208306)
# Backport This will backport the following commits from `main` to `8.16`: - [[Lens] add an accessible label to range slider (#205308)](https://github.com/elastic/kibana/pull/205308) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marta Bondyra","email":"4283304+mbondyra@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-25T22:11:46Z","message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","v9.0.0","backport:prev-major"],"title":"[Lens] add an accessible label to range slider","number":205308,"url":"https://github.com/elastic/kibana/pull/205308","mergeCommit":{"message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e"}},"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/205308","number":205308,"mergeCommit":{"message":"[Lens] add an accessible label to range slider (#205308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/182765 (with the solution\r\nsuggested by @1Copenut)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ed5728302a3063af325ea862f64c019bd67cbb5e"}}]}] BACKPORT--> Co-authored-by: Marta Bondyra <4283304+mbondyra@users.noreply.github.com> |
||
Mark Hopkin
|
fae7f204bd
|
[8.16] Added examples for necessary Entity Analytics OpenAPI docs (#205439) (#208232)
# Backport This will backport the following commits from `main` to `8.16`: - [Added examples for necessary Entity Analytics OpenAPI docs (#205439)](https://github.com/elastic/kibana/pull/205439) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jared Burgett","email":"147995946+jaredburgettelastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-15T23:17:19Z","message":"Added examples for necessary Entity Analytics OpenAPI docs (#205439)\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\nSecurity Entity Analytics APIs.\r\n\r\nAll of the affected APIs are the Asset Criticality APIs.\r\n\r\n# How to Test\r\n\r\nUntil the docs are deployed, this can be tested by navigating to\r\nhttps://editor.swagger.io/ and pasting in the fully bundled file, which\r\ncan be found\r\n[here]( |
||
|
Kibana Machine
|
6c64d5bf0f
|
[8.16] [Automatic Import]Add missing fields into AWS S3 manifest (#208080) (#208102)
# Backport This will backport the following commits from `main` to `8.16`: - [[Automatic Import]Add missing fields into AWS S3 manifest (#208080)](https://github.com/elastic/kibana/pull/208080) <!--- 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-01-23T17:08:48Z","message":"[Automatic Import]Add missing fields into AWS S3 manifest (#208080)\n\n## Summary\r\n\r\nThis PR adds missing fields in `aws-s3-manifest.yml` generated for\r\ndatastream to be able to add the right data into the agent input.\r\n\r\n### Checklist\r\n\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)","sha":"28885a762f66ba4719dcff445171000888898a83","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic Import]Add missing fields into AWS S3 manifest","number":208080,"url":"https://github.com/elastic/kibana/pull/208080","mergeCommit":{"message":"[Automatic Import]Add missing fields into AWS S3 manifest (#208080)\n\n## Summary\r\n\r\nThis PR adds missing fields in `aws-s3-manifest.yml` generated for\r\ndatastream to be able to add the right data into the agent input.\r\n\r\n### Checklist\r\n\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)","sha":"28885a762f66ba4719dcff445171000888898a83"}},"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/208080","number":208080,"mergeCommit":{"message":"[Automatic Import]Add missing fields into AWS S3 manifest (#208080)\n\n## Summary\r\n\r\nThis PR adds missing fields in `aws-s3-manifest.yml` generated for\r\ndatastream to be able to add the right data into the agent input.\r\n\r\n### Checklist\r\n\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)","sha":"28885a762f66ba4719dcff445171000888898a83"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
|
Antonio
|
159f89cb9f
|
[8.16] Fixed an error with missing uids in the cases detail page (#207228) (#208057)
# Backport This will backport the following commits from `main` to `8.16`: - [Fixed an error with missing uids in the cases detail page (#207228)](https://github.com/elastic/kibana/pull/207228) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:15:43Z","message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-major","v8.18.0","v8.16.4","v8.17.2"],"title":"Fixed an error with missing uids in the cases detail page","number":207228,"url":"https://github.com/elastic/kibana/pull/207228","mergeCommit":{"message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207228","number":207228,"mergeCommit":{"message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207873","number":207873,"state":"MERGED","mergeCommit":{"sha":"06af0cf9a340eee1f5678af8797c442834c173e7","message":"[8.x] Fixed an error with missing uids in the cases detail page (#207228) (#207873)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [Fixed an error with missing uids in the cases detail page\n(#207228)](https://github.com/elastic/kibana/pull/207228)\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\":\"Antonio\",\"email\":\"antonio.coelho@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-22T16:15:43Z\",\"message\":\"Fixed\nan error with missing uids in the cases detail page (#207228)\\n\\nFixes\n#206801\\r\\n\\r\\n## Summary\\r\\n\\r\\nWhen opening the case detail page we\nretrieve user profile info for the\\r\\ndifferent case user\nactions.\\r\\n\\r\\nIf the uid stored in ES is an empty string for any of\nthese user\\r\\nactions, we get an error that looks like\nthis:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n###\nSteps to reproduce/test (thanks @jcger )\\r\\n\\r\\n1. Create a user with\nthe `system_indices_superuser` role\\r\\n2. Create a case and assign a\nuser to it\\r\\n3. Get the ID of the assignment user action from the case\nabove\\r\\n```\\r\\nGET .kibana_alerting_cases/_search\\r\\n{\\r\\n \\\"query\\\":\n{\\r\\n \\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n \\\"type\\\":\n\\\"cases-user-actions\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"cases-user-actions.type\\\": \\\"assignees\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n\n\\\"nested\\\": {\\r\\n \\\"path\\\": \\\"references\\\",\\r\\n \\\"query\\\": {\\r\\n\n\\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.type\\\": \\\"cases\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.id\\\": \\\"<case_id>\\\"\\r\\n }\\r\\n }\\r\\n ]\\r\\n }\\r\\n }\\r\\n }\\r\\n\n}\\r\\n ]\\r\\n }\\r\\n }\\r\\n}\\r\\n```\\r\\n4. Manually set the `uid` of the\nassignee to `\\\"\\\"`\\r\\n```\\r\\nPOST\n.kibana_alerting_cases/_update/<cases-user-actions-id>\\r\\n{\\r\\n\n\\\"script\\\": {\\r\\n \\\"source\\\": \\\"\\\"\\\"\\r\\n\nctx._source[\\\"cases-user-actions\\\"].payload.assignees[0].uid = \\\"\\\";\\r\\n\n\\\"\\\"\\\"\\r\\n }\\r\\n}\\r\\n```\\r\\n\\r\\nAfter this PR the popup should **not**\nappear\nanymore.\",\"sha\":\"d8e5cbf67f2bae859a18f956c22205b78d3da5aa\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:skip\",\"Team:ResponseOps\",\"v9.0.0\",\"Feature:Cases\",\"backport:prev-minor\"],\"title\":\"Fixed\nan error with missing uids in the cases detail\npage\",\"number\":207228,\"url\":\"https://github.com/elastic/kibana/pull/207228\",\"mergeCommit\":{\"message\":\"Fixed\nan error with missing uids in the cases detail page (#207228)\\n\\nFixes\n#206801\\r\\n\\r\\n## Summary\\r\\n\\r\\nWhen opening the case detail page we\nretrieve user profile info for the\\r\\ndifferent case user\nactions.\\r\\n\\r\\nIf the uid stored in ES is an empty string for any of\nthese user\\r\\nactions, we get an error that looks like\nthis:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n###\nSteps to reproduce/test (thanks @jcger )\\r\\n\\r\\n1. Create a user with\nthe `system_indices_superuser` role\\r\\n2. Create a case and assign a\nuser to it\\r\\n3. Get the ID of the assignment user action from the case\nabove\\r\\n```\\r\\nGET .kibana_alerting_cases/_search\\r\\n{\\r\\n \\\"query\\\":\n{\\r\\n \\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n \\\"type\\\":\n\\\"cases-user-actions\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"cases-user-actions.type\\\": \\\"assignees\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n\n\\\"nested\\\": {\\r\\n \\\"path\\\": \\\"references\\\",\\r\\n \\\"query\\\": {\\r\\n\n\\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.type\\\": \\\"cases\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.id\\\": \\\"<case_id>\\\"\\r\\n }\\r\\n }\\r\\n ]\\r\\n }\\r\\n }\\r\\n }\\r\\n\n}\\r\\n ]\\r\\n }\\r\\n }\\r\\n}\\r\\n```\\r\\n4. Manually set the `uid` of the\nassignee to `\\\"\\\"`\\r\\n```\\r\\nPOST\n.kibana_alerting_cases/_update/<cases-user-actions-id>\\r\\n{\\r\\n\n\\\"script\\\": {\\r\\n \\\"source\\\": \\\"\\\"\\\"\\r\\n\nctx._source[\\\"cases-user-actions\\\"].payload.assignees[0].uid = \\\"\\\";\\r\\n\n\\\"\\\"\\\"\\r\\n }\\r\\n}\\r\\n```\\r\\n\\r\\nAfter this PR the popup should **not**\nappear\nanymore.\",\"sha\":\"d8e5cbf67f2bae859a18f956c22205b78d3da5aa\"}},\"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/207228\",\"number\":207228,\"mergeCommit\":{\"message\":\"Fixed\nan error with missing uids in the cases detail page (#207228)\\n\\nFixes\n#206801\\r\\n\\r\\n## Summary\\r\\n\\r\\nWhen opening the case detail page we\nretrieve user profile info for the\\r\\ndifferent case user\nactions.\\r\\n\\r\\nIf the uid stored in ES is an empty string for any of\nthese user\\r\\nactions, we get an error that looks like\nthis:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n###\nSteps to reproduce/test (thanks @jcger )\\r\\n\\r\\n1. Create a user with\nthe `system_indices_superuser` role\\r\\n2. Create a case and assign a\nuser to it\\r\\n3. Get the ID of the assignment user action from the case\nabove\\r\\n```\\r\\nGET .kibana_alerting_cases/_search\\r\\n{\\r\\n \\\"query\\\":\n{\\r\\n \\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n \\\"type\\\":\n\\\"cases-user-actions\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"cases-user-actions.type\\\": \\\"assignees\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n\n\\\"nested\\\": {\\r\\n \\\"path\\\": \\\"references\\\",\\r\\n \\\"query\\\": {\\r\\n\n\\\"bool\\\": {\\r\\n \\\"filter\\\": [\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.type\\\": \\\"cases\\\"\\r\\n }\\r\\n },\\r\\n {\\r\\n \\\"term\\\": {\\r\\n\n\\\"references.id\\\": \\\"<case_id>\\\"\\r\\n }\\r\\n }\\r\\n ]\\r\\n }\\r\\n }\\r\\n }\\r\\n\n}\\r\\n ]\\r\\n }\\r\\n }\\r\\n}\\r\\n```\\r\\n4. Manually set the `uid` of the\nassignee to `\\\"\\\"`\\r\\n```\\r\\nPOST\n.kibana_alerting_cases/_update/<cases-user-actions-id>\\r\\n{\\r\\n\n\\\"script\\\": {\\r\\n \\\"source\\\": \\\"\\\"\\\"\\r\\n\nctx._source[\\\"cases-user-actions\\\"].payload.assignees[0].uid = \\\"\\\";\\r\\n\n\\\"\\\"\\\"\\r\\n }\\r\\n}\\r\\n```\\r\\n\\r\\nAfter this PR the popup should **not**\nappear anymore.\",\"sha\":\"d8e5cbf67f2bae859a18f956c22205b78d3da5aa\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Antonio <antonio.coelho@elastic.co>"}},{"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"}]}] BACKPORT--> |
||
|
Kibana Machine
|
b09bca4439
|
[8.16] [ResponseOps] Do not change time field when edit (#206858) (#208029)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps] Do not change time field when edit (#206858)](https://github.com/elastic/kibana/pull/206858) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-23T11:38:15Z","message":"[ResponseOps] Do not change time field when edit (#206858)\n\nFixed: https://github.com/elastic/kibana/issues/204432\r\n\r\nHow to test:\r\nGo to rules creation. Create ESquery rule. Set some `@timestamp` time\r\nfield. Try to edit rule. Check if it's save previous value of time\r\nfield.\r\n\r\nCheck the PR satisfies following conditions. \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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"993392bc4f6a96391644578a77bc2c4406581d05","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-major","v8.18.0"],"title":"[ResponseOps] Do not change time field when edit","number":206858,"url":"https://github.com/elastic/kibana/pull/206858","mergeCommit":{"message":"[ResponseOps] Do not change time field when edit (#206858)\n\nFixed: https://github.com/elastic/kibana/issues/204432\r\n\r\nHow to test:\r\nGo to rules creation. Create ESquery rule. Set some `@timestamp` time\r\nfield. Try to edit rule. Check if it's save previous value of time\r\nfield.\r\n\r\nCheck the PR satisfies following conditions. \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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"993392bc4f6a96391644578a77bc2c4406581d05"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206858","number":206858,"mergeCommit":{"message":"[ResponseOps] Do not change time field when edit (#206858)\n\nFixed: https://github.com/elastic/kibana/issues/204432\r\n\r\nHow to test:\r\nGo to rules creation. Create ESquery rule. Set some `@timestamp` time\r\nfield. Try to edit rule. Check if it's save previous value of time\r\nfield.\r\n\r\nCheck the PR satisfies following conditions. \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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"993392bc4f6a96391644578a77bc2c4406581d05"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia <iuliia.guskova@elastic.co> |
||
Tiago Costa
|
72f891c415
|
skip flaky suite (#196199) | ||
Candace Park
|
9c25cb8cc2
|
[8.16] [AVC Banner] Updates the AVC Banner for 2025 (#205467) (#205819)
# Backport This will backport the following commits from `main` to `8.16`: - [[AVC Banner] Updates the AVC Banner for 2025 (#205467)](https://github.com/elastic/kibana/pull/205467) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Candace Park","email":"56409205+parkiino@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-07T18:30:27Z","message":"[AVC Banner] Updates the AVC Banner for 2025 (#205467)\n\n## Summary\r\n\r\n- [x] Updates the AVC banner title and blog link\r\n- [x] Banner will remain visible until EOY 2025 \r\n- [x] Confirm that the original AVC banner code (not the part that hides\r\nit EOY of 2024) is present in 8.16, 8.17 and 8.x branches\r\n\r\n# Screenshots\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"08535f54a0d9b172f8cd695a5330bcd87f896d7c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:Defend Workflows","backport:prev-major","v8.17.0","v8.18.0","v8.16.3","v8.17.1"],"number":205467,"url":"https://github.com/elastic/kibana/pull/205467","mergeCommit":{"message":"[AVC Banner] Updates the AVC Banner for 2025 (#205467)\n\n## Summary\r\n\r\n- [x] Updates the AVC banner title and blog link\r\n- [x] Banner will remain visible until EOY 2025 \r\n- [x] Confirm that the original AVC banner code (not the part that hides\r\nit EOY of 2024) is present in 8.16, 8.17 and 8.x branches\r\n\r\n# Screenshots\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"08535f54a0d9b172f8cd695a5330bcd87f896d7c"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205467","number":205467,"mergeCommit":{"message":"[AVC Banner] Updates the AVC Banner for 2025 (#205467)\n\n## Summary\r\n\r\n- [x] Updates the AVC banner title and blog link\r\n- [x] Banner will remain visible until EOY 2025 \r\n- [x] Confirm that the original AVC banner code (not the part that hides\r\nit EOY of 2024) is present in 8.16, 8.17 and 8.x branches\r\n\r\n# Screenshots\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"08535f54a0d9b172f8cd695a5330bcd87f896d7c"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
45ba3694c7
|
[8.16] Upgrade Node.js to 20.18.2 (#207431) (#207892)
# Backport This will backport the following commits from `main` to `8.16`: - [Upgrade Node.js to 20.18.2 (#207431)](https://github.com/elastic/kibana/pull/207431) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T18:00:14Z","message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open"],"title":"Upgrade Node.js to 20.18.2","number":207431,"url":"https://github.com/elastic/kibana/pull/207431","mergeCommit":{"message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba"}},"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/207431","number":207431,"mergeCommit":{"message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
Walter Rafelsberger
|
30f212a3e4
|
[8.16] Update @elastic/ml-ui dependencies (main) (#204210) (#207798)
# Backport This will backport the following commits from `main` to `8.16`: - [Update @elastic/ml-ui dependencies (main) (#204210)](https://github.com/elastic/kibana/pull/204210) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Ignacio Rivas
|
c445484f41
|
[8.16] [Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764) (#207835)
# Backport This will backport the following commits from `main` to `8.16`: - [[Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764)](https://github.com/elastic/kibana/pull/206764) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2025-01-16T08:27:12Z","message":"[Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764)","sha":"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","Feature:Search Profiler","v9.0.0","backport:prev-minor","v8.16.0","v8.17.0","v8.18.0"],"title":"[Searchprofiler] Fix CTA not being shown when screen is not tall enough","number":206764,"url":"https://github.com/elastic/kibana/pull/206764","mergeCommit":{"message":"[Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764)","sha":"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206764","number":206764,"mergeCommit":{"message":"[Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764)","sha":"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9"}},{"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.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/206896","number":206896,"state":"MERGED","mergeCommit":{"sha":"d824cd242abbb8e4c31ade640445640a59357e43","message":"[8.x] [Searchprofiler] Fix CTA not being shown when screen is not tall enough (#206764) (#206896)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Searchprofiler] Fix CTA not being shown when screen is not tall\nenough (#206764)](https://github.com/elastic/kibana/pull/206764)\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\":\"Ignacio\nRivas\",\"email\":\"rivasign@gmail.com\"},\"sourceCommit\":{\"committedDate\":\"2025-01-16T08:27:12Z\",\"message\":\"[Searchprofiler]\nFix CTA not being shown when screen is not tall enough\n(#206764)\",\"sha\":\"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Kibana\nManagement\",\"release_note:skip\",\"Feature:Search\nProfiler\",\"v9.0.0\",\"backport:prev-minor\"],\"title\":\"[Searchprofiler] Fix\nCTA not being shown when screen is not tall\nenough\",\"number\":206764,\"url\":\"https://github.com/elastic/kibana/pull/206764\",\"mergeCommit\":{\"message\":\"[Searchprofiler]\nFix CTA not being shown when screen is not tall enough\n(#206764)\",\"sha\":\"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9\"}},\"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/206764\",\"number\":206764,\"mergeCommit\":{\"message\":\"[Searchprofiler]\nFix CTA not being shown when screen is not tall enough\n(#206764)\",\"sha\":\"c3b9466de6b3bc03a74fc433ee77aec8c3f291a9\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Ignacio Rivas <rivasign@gmail.com>"}}]}] BACKPORT--> |
||
Jeramy Soucy
|
68dcc12bac
|
[8.16] Update platform security modules (main) (#206227) (#207320)
# Backport This will backport the following commits from `main` to `8.16`: - [Update platform security modules (main) (#206227)](https://github.com/elastic/kibana/pull/206227) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-17T15:46:36Z","message":"Update platform security modules (main) (#206227)\n\n### Manual update 2025-01-14:\nuuid v11 contains breaking changes. uuid will be bumped to v10 instead.\n\n### This PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n|\n[@types/js-yaml](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/js-yaml)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/js-yaml))\n| devDependencies | patch | [`^4.0.5` ->\n`^4.0.9`](https://renovatebot.com/diffs/npm/@types%2fjs-yaml/4.0.5/4.0.9)\n| |\n|\n[@types/lodash](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/lodash)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash))\n| devDependencies | patch | [`^4.17.13` ->\n`^4.17.14`](https://renovatebot.com/diffs/npm/@types%2flodash/4.17.13/4.17.14)\n| |\n|\n[@types/object-hash](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/object-hash)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/object-hash))\n| devDependencies | major | [`^1.3.0` ->\n`^3.0.6`](https://renovatebot.com/diffs/npm/@types%2fobject-hash/1.3.0/3.0.6)\n| |\n|\n[@types/uuid](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/uuid)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/uuid))\n| devDependencies | major | [`^9.0.0` ->\n`^10.0.0`](https://renovatebot.com/diffs/npm/@types%2fuuid/9.0.0/10.0.0)\n| |\n| [dependency-cruiser](https://togithub.com/sverweij/dependency-cruiser)\n| devDependencies | minor | [`^16.4.2` ->\n`^16.8.0`](https://renovatebot.com/diffs/npm/dependency-cruiser/16.4.2/16.8.0)\n| `16.9.0` |\n| [fast-deep-equal](https://togithub.com/epoberezkin/fast-deep-equal) |\ndependencies | patch | [`^3.1.1` ->\n`^3.1.3`](https://renovatebot.com/diffs/npm/fast-deep-equal/3.1.3/3.1.3)\n| |\n| [minimist](https://togithub.com/minimistjs/minimist) | devDependencies\n| patch | [`^1.2.6` ->\n`^1.2.8`](https://renovatebot.com/diffs/npm/minimist/1.2.8/1.2.8) | |\n| [object-hash](https://togithub.com/puleos/object-hash) | dependencies\n| major | [`^1.3.1` ->\n`^3.0.0`](https://renovatebot.com/diffs/npm/object-hash/1.3.1/3.0.0) | |\n| [uuid](https://togithub.com/uuidjs/uuid) | dependencies | major |\n[~~`9.0.0` ->\n`11.0.3`~~](https://renovatebot.com/diffs/npm/uuid/9.0.0/11.0.3)`9.0.0`\n-> `10.0.0` | ~~`11.0.5` (+1)~~ |\n\n---\n\n### Release Notes\n\n<details>\n<summary>sverweij/dependency-cruiser (dependency-cruiser)</summary>\n\n###\n[`v16.8.0`](https://togithub.com/sverweij/dependency-cruiser/releases/tag/v16.8.0)\n\n[Compare\nSource](https://togithub.com/sverweij/dependency-cruiser/compare/v16.7.0...v16.8.0)\n\n#### ✨ features\n\n-\n[`dd81580`]( |
||
|
Tiago Costa
|
018a377629
|
chore(NA): bump version to 8.16.4 (#207409)
Usually bump from 8.16.3 to 8.16.4 |
||
Gonçalo Rica Pais da Silva
|
030bac4924
|
[8.16] [APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651) (#207224)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)](https://github.com/elastic/kibana/pull/206651) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T13:36:22Z","message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5","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:all-open","Team:obs-ux-infra_services"],"title":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues","number":206651,"url":"https://github.com/elastic/kibana/pull/206651","mergeCommit":{"message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5"}},"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/206651","number":206651,"mergeCommit":{"message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5"}}]}] BACKPORT--> |
||
|
Maryam Saeidi
|
0f5fe605ac
|
[8.16] [Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615) (#207037)
# Backport This will backport the following commits from `main` to `8.16`: - [[Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615)](https://github.com/elastic/kibana/pull/206615) <!--- 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-01-16T08:01:31Z","message":"[Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615)\n\nFixes #206588\r\n\r\n## Summary\r\n\r\nThis PR fixes the `Unable to load page` error on the alert details page\r\nwhen the query has a leading wildcard by passing the uiSetting config to\r\nthe buildEsQuery helper in the LogRateAnalysis component.\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"362f2dd9b06cbbd10f0746e5138509bd0e595b8d","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","backport:prev-major","Team:obs-ux-management","v8.18.0"],"title":"[Custom threshold] Fix leading wildcard issue on the custom threshold alert details page","number":206615,"url":"https://github.com/elastic/kibana/pull/206615","mergeCommit":{"message":"[Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615)\n\nFixes #206588\r\n\r\n## Summary\r\n\r\nThis PR fixes the `Unable to load page` error on the alert details page\r\nwhen the query has a leading wildcard by passing the uiSetting config to\r\nthe buildEsQuery helper in the LogRateAnalysis component.\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"362f2dd9b06cbbd10f0746e5138509bd0e595b8d"}},"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/206615","number":206615,"mergeCommit":{"message":"[Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615)\n\nFixes #206588\r\n\r\n## Summary\r\n\r\nThis PR fixes the `Unable to load page` error on the alert details page\r\nwhen the query has a leading wildcard by passing the uiSetting config to\r\nthe buildEsQuery helper in the LogRateAnalysis component.\r\n\r\n\r\n\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"362f2dd9b06cbbd10f0746e5138509bd0e595b8d"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/206892","number":206892,"state":"MERGED","mergeCommit":{"sha":"58b4af3cd1194c3ea809533c081b5dc8553825c9","message":"[8.x] [Custom threshold] Fix leading wildcard issue on the custom threshold alert details page (#206615) (#206892)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Custom threshold] Fix leading wildcard issue on the custom threshold\nalert details page\n(#206615)](https://github.com/elastic/kibana/pull/206615)\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\":\"Maryam\nSaeidi\",\"email\":\"maryam.saeidi@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-01-16T08:01:31Z\",\"message\":\"[Custom\nthreshold] Fix leading wildcard issue on the custom threshold alert\ndetails page (#206615)\\n\\nFixes #206588\\r\\n\\r\\n## Summary\\r\\n\\r\\nThis PR\nfixes the `Unable to load page` error on the alert details page\\r\\nwhen\nthe query has a leading wildcard by passing the uiSetting config\nto\\r\\nthe buildEsQuery helper in the LogRateAnalysis\ncomponent.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"362f2dd9b06cbbd10f0746e5138509bd0e595b8d\",\"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\",\"backport:prev-major\",\"Team:obs-ux-management\"],\"title\":\"[Custom\nthreshold] Fix leading wildcard issue on the custom threshold alert\ndetails\npage\",\"number\":206615,\"url\":\"https://github.com/elastic/kibana/pull/206615\",\"mergeCommit\":{\"message\":\"[Custom\nthreshold] Fix leading wildcard issue on the custom threshold alert\ndetails page (#206615)\\n\\nFixes #206588\\r\\n\\r\\n## Summary\\r\\n\\r\\nThis PR\nfixes the `Unable to load page` error on the alert details page\\r\\nwhen\nthe query has a leading wildcard by passing the uiSetting config\nto\\r\\nthe buildEsQuery helper in the LogRateAnalysis\ncomponent.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"362f2dd9b06cbbd10f0746e5138509bd0e595b8d\"}},\"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/206615\",\"number\":206615,\"mergeCommit\":{\"message\":\"[Custom\nthreshold] Fix leading wildcard issue on the custom threshold alert\ndetails page (#206615)\\n\\nFixes #206588\\r\\n\\r\\n## Summary\\r\\n\\r\\nThis PR\nfixes the `Unable to load page` error on the alert details page\\r\\nwhen\nthe query has a leading wildcard by passing the uiSetting config\nto\\r\\nthe buildEsQuery helper in the LogRateAnalysis\ncomponent.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"362f2dd9b06cbbd10f0746e5138509bd0e595b8d\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>"}},{"url":"https://github.com/elastic/kibana/pull/206966","number":206966,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
jennypavlova
|
e3d35f9bb7
|
[8.16] [APM] Fix: Add tracing sample missing fields in the overview (#206932) (#206983)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM] Fix: Add tracing sample missing fields in the overview (#206932)](https://github.com/elastic/kibana/pull/206932) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-16T16:45:06Z","message":"[APM] Fix: Add tracing sample missing fields in the overview (#206932)\n\nCloses #200474\r\n\r\n## Summary\r\n\r\nThis PR fixes the issue with tracing sample missing URL/Status Code/User\r\nAgent fields in the overview\r\n\r\n## Testing\r\n- Open the APM UI and find APM traces that contains `url.full` /\r\n`transaction.page.url`, `http.request.method` and\r\n`http.response.status_code`\r\n- One should be ingested using an otel collector the other should use an\r\napm-server\r\n- if using oblt cluster you can check transactions from `loadgenerator`\r\nand `opbeans-python` for example\r\n - check the trace summary:\r\n - Otel:\r\n \r\n\r\n\r\n\r\n - APM server:\r\n \r\n\r\n","sha":"1d493c0a8df778ca8bfd86dbf11d59c8aa3d548c","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-major","Team:obs-ux-infra_services"],"title":"[APM] Fix: Add tracing sample missing fields in the overview","number":206932,"url":"https://github.com/elastic/kibana/pull/206932","mergeCommit":{"message":"[APM] Fix: Add tracing sample missing fields in the overview (#206932)\n\nCloses #200474\r\n\r\n## Summary\r\n\r\nThis PR fixes the issue with tracing sample missing URL/Status Code/User\r\nAgent fields in the overview\r\n\r\n## Testing\r\n- Open the APM UI and find APM traces that contains `url.full` /\r\n`transaction.page.url`, `http.request.method` and\r\n`http.response.status_code`\r\n- One should be ingested using an otel collector the other should use an\r\napm-server\r\n- if using oblt cluster you can check transactions from `loadgenerator`\r\nand `opbeans-python` for example\r\n - check the trace summary:\r\n - Otel:\r\n \r\n\r\n\r\n\r\n - APM server:\r\n \r\n\r\n","sha":"1d493c0a8df778ca8bfd86dbf11d59c8aa3d548c"}},"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/206932","number":206932,"mergeCommit":{"message":"[APM] Fix: Add tracing sample missing fields in the overview (#206932)\n\nCloses #200474\r\n\r\n## Summary\r\n\r\nThis PR fixes the issue with tracing sample missing URL/Status Code/User\r\nAgent fields in the overview\r\n\r\n## Testing\r\n- Open the APM UI and find APM traces that contains `url.full` /\r\n`transaction.page.url`, `http.request.method` and\r\n`http.response.status_code`\r\n- One should be ingested using an otel collector the other should use an\r\napm-server\r\n- if using oblt cluster you can check transactions from `loadgenerator`\r\nand `opbeans-python` for example\r\n - check the trace summary:\r\n - Otel:\r\n \r\n\r\n\r\n\r\n - APM server:\r\n \r\n\r\n","sha":"1d493c0a8df778ca8bfd86dbf11d59c8aa3d548c"}},{"url":"https://github.com/elastic/kibana/pull/206978","number":206978,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> |
||
Steph Milovic
|
00ffc91bce
|
[8.16] [Security assistant] Update conversations api improvement (#206828) (#206865)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security assistant] Update conversations api improvement (#206828)](https://github.com/elastic/kibana/pull/206828) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-01-15T20:36:33Z","message":"[Security assistant] Update conversations api improvement (#206828)","sha":"56ce5d45c02436fc2cc31b20f1ccf29823bacf59","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:all-open","Team:Security Generative AI"],"title":"[Security assistant] Update conversations api improvement","number":206828,"url":"https://github.com/elastic/kibana/pull/206828","mergeCommit":{"message":"[Security assistant] Update conversations api improvement (#206828)","sha":"56ce5d45c02436fc2cc31b20f1ccf29823bacf59"}},"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/206828","number":206828,"mergeCommit":{"message":"[Security assistant] Update conversations api improvement (#206828)","sha":"56ce5d45c02436fc2cc31b20f1ccf29823bacf59"}},{"url":"https://github.com/elastic/kibana/pull/206861","number":206861,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/206862","number":206862,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c96baea737
|
[8.16] [Fleet] Fix output id when using default output as integration output (#206286) (#206676)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] Fix output id when using default output as integration output (#206286)](https://github.com/elastic/kibana/pull/206286) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-01-10T16:31:24Z","message":"[Fleet] Fix output id when using default output as integration output (#206286)","sha":"9cda1a83a6e5b48b88a326a67a185bc8a6a703fa","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v9.0.0","backport:prev-major"],"title":"[Fleet] Fix output id when using default output as integration output","number":206286,"url":"https://github.com/elastic/kibana/pull/206286","mergeCommit":{"message":"[Fleet] Fix output id when using default output as integration output (#206286)","sha":"9cda1a83a6e5b48b88a326a67a185bc8a6a703fa"}},"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/206286","number":206286,"mergeCommit":{"message":"[Fleet] Fix output id when using default output as integration output (#206286)","sha":"9cda1a83a6e5b48b88a326a67a185bc8a6a703fa"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
Sebastián Zaffarano
|
3f4c7f6227
|
[8.16] [8.x] [Telemetry][Security Solution] Index metadata collector (#194004) (#204311) (#204629)
# Backport This will backport the following commits from `8.x` to `8.16`: - [[8.x] [Telemetry][Security Solution] Index metadata collector (#194004) (#204311)](https://github.com/elastic/kibana/pull/204311) <!--- Backport version: 8.9.8 --> ### 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":"2024-12-16T16:05:02Z","message":"[8.x] [Telemetry][Security Solution] Index metadata collector (#194004) (#204311)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Telemetry][Security Solution] Index metadata collector\n(#194004)](https://github.com/elastic/kibana/pull/194004)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Sebastián\nZaffarano\",\"email\":\"sebastian.zaffarano@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-13T18:31:03Z\",\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:\nSecuritySolution\",\"backport:all-open\",\"ci:cloud-deploy\"],\"number\":194004,\"url\":\"https://github.com/elastic/kibana/pull/194004\",\"mergeCommit\":{\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\"}},\"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/194004\",\"number\":194004,\"mergeCommit\":{\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7a3de72bbe94a87bd972602b29212764f2619951","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport"],"number":204311,"url":"https://github.com/elastic/kibana/pull/204311","mergeCommit":{"message":"[8.x] [Telemetry][Security Solution] Index metadata collector (#194004) (#204311)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Telemetry][Security Solution] Index metadata collector\n(#194004)](https://github.com/elastic/kibana/pull/194004)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Sebastián\nZaffarano\",\"email\":\"sebastian.zaffarano@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-12-13T18:31:03Z\",\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:\nSecuritySolution\",\"backport:all-open\",\"ci:cloud-deploy\"],\"number\":194004,\"url\":\"https://github.com/elastic/kibana/pull/194004\",\"mergeCommit\":{\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\"}},\"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/194004\",\"number\":194004,\"mergeCommit\":{\"message\":\"[Telemetry][Security\nSolution] Index metadata collector (#194004)\\n\\n##\nSummary\\r\\n\\r\\nImplements a security_solution task scheduled to run once\na day to\\r\\ncollect the following information:\\r\\n\\r\\n1. Datastreams\nstats\\r\\n2. Indices stats\\r\\n3. ILMs stats\\r\\n4. ILM configs\\r\\n\\r\\nThe\ntask allows a runtime configuration to limit the number of\nindices\\r\\nand data streams to analyze or event to disable the feature\nentirely.\\r\\n\\r\\nOnce the data is gathered, the task sends it as EBT\nevents.\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nElastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"36b344a4c58a3d78a892288e0eef71e9ff163b9d\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7a3de72bbe94a87bd972602b29212764f2619951"}},"sourceBranch":"8.x","suggestedTargetBranches":[],"targetPullRequestStates":[{"url":"https://github.com/elastic/kibana/pull/204628","number":204628,"branch":"8.17","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
8acffa7873
|
[8.16] [Security Solution] List all policies to display integrations properly (#205103) (#205889)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] List all policies to display integrations properly (#205103)](https://github.com/elastic/kibana/pull/205103) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T13:26:32Z","message":"[Security Solution] List all policies to display integrations properly (#205103)\n\n**Resolves: #200167**\n\n## Summary\n\nIncrease number of fetched package policies to the maximum. Currently\nonly the first 20 policies (the first page) are returned, which results\nin treating all remaining ones as disabled.\nI am proposing the simplest change of increasing the limit here to the\nmaximum. There shouldn't be too many policies there, e.g. in the\nreproduction I am running there are 23 instead of 20.\nIf that is not enough, however, the alternative would be to discover\nthat there are more policies than the specified limit and the next\npage(s) would have to be collected and the results added to the final\nlist.\n\n#BEFORE\n\n\n\n#AFTER \n\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"6d49348db89302cf658637e8e8bd9e33760a2cad","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:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v8.16.3","v8.17.1"],"title":"[Security Solution] List all policies to display integrations properly","number":205103,"url":"https://github.com/elastic/kibana/pull/205103","mergeCommit":{"message":"[Security Solution] List all policies to display integrations properly (#205103)\n\n**Resolves: #200167**\n\n## Summary\n\nIncrease number of fetched package policies to the maximum. Currently\nonly the first 20 policies (the first page) are returned, which results\nin treating all remaining ones as disabled.\nI am proposing the simplest change of increasing the limit here to the\nmaximum. There shouldn't be too many policies there, e.g. in the\nreproduction I am running there are 23 instead of 20.\nIf that is not enough, however, the alternative would be to discover\nthat there are more policies than the specified limit and the next\npage(s) would have to be collected and the results added to the final\nlist.\n\n#BEFORE\n\n\n\n#AFTER \n\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"6d49348db89302cf658637e8e8bd9e33760a2cad"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205103","number":205103,"mergeCommit":{"message":"[Security Solution] List all policies to display integrations properly (#205103)\n\n**Resolves: #200167**\n\n## Summary\n\nIncrease number of fetched package policies to the maximum. Currently\nonly the first 20 policies (the first page) are returned, which results\nin treating all remaining ones as disabled.\nI am proposing the simplest change of increasing the limit here to the\nmaximum. There shouldn't be too many policies there, e.g. in the\nreproduction I am running there are 23 instead of 20.\nIf that is not enough, however, the alternative would be to discover\nthat there are more policies than the specified limit and the next\npage(s) would have to be collected and the results added to the final\nlist.\n\n#BEFORE\n\n\n\n#AFTER \n\n\n\n### Checklist\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"6d49348db89302cf658637e8e8bd9e33760a2cad"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co> |
||
Kenneth Kreindler
|
56aebad97e
|
[8.16] [Security Assistant] Move security AI assistant button into global nav bar (#203060) (#205886)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Assistant] Move security AI assistant button into global nav bar (#203060)](https://github.com/elastic/kibana/pull/203060) <!--- Backport version: 8.9.8 --> ### 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-01-08T10:03:54Z","message":"[Security Assistant] Move security AI assistant button into global nav bar (#203060)\n\n## Summary\r\n\r\nMore changes are needed within the observability and search solution to\r\nclose the issue fully.\r\n\r\nSummarise your PR. If it involves visual changes include a screenshot or\r\ngif.\r\n\r\nMove the security AI assistant button from the solution header bar into\r\nthe global nav bar. This is part of the AI assistant unification\r\ninitiative.\r\n\r\n### How to Test\r\n- Start kibana\r\n- Go to one of the security solution pages (e.g. attack discovery)\r\n- AI assistant button should be in the global nav bar. Clicking it opens\r\nthe assistant.\r\n\r\n- The button can also be tested for security serverless deployment. It\r\nshould look like the screenshot bellow.\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\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\nClassic:\r\n\r\n (#205903)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Implement refactoring remark from PR #201731 (#204022)](https://github.com/elastic/kibana/pull/204022) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T14:01:47Z","message":"[Security Solution] Implement refactoring remark from PR #201731 (#204022)\n\n## Summary\n\nIn the PR #201731 for ticket #180660 @banderror advised to refactor code\nin that PR to better separate the concerns (business logic from\ncomponents). This is the implementation of that review\n[remark]( |
||
|
Gonçalo Rica Pais da Silva
|
2e63133937
|
[8.16] [ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726) (#205854)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)](https://github.com/elastic/kibana/pull/205726) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T09:16:17Z","message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69","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:all-open","Team:obs-ux-infra_services"],"title":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions","number":205726,"url":"https://github.com/elastic/kibana/pull/205726","mergeCommit":{"message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69"}},"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/205726","number":205726,"mergeCommit":{"message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69"}}]}] BACKPORT--> |
||
Mike Côté
|
98100987d6
|
[8.16] [ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650) (#205831)
# Backport This will backport the following commits from `main` to `8.16`: - [[ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650)](https://github.com/elastic/kibana/pull/205650) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Zacqary Adam Xeper","email":"Zacqary@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-07T19:32:43Z","message":"[ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205558\r\n\r\nUpdates the RRule library to correctly handle some scenarios with\r\ninvalid parameters that would either cause it to return strange\r\nrecurrence data or to infinitely loop. Specifically:\r\n\r\n- On `RRule` object creation, removes and ignores any `bymonth`,\r\n`bymonthday`, `byweekday`, or `byyearday` value that's out of bounds,\r\ne.g. less than 0 or greater than the number of possible months, days,\r\nweekdays, etc.\r\n- Successfully ignores cases of `BYMONTH=2, BYMONTHDAY=30` (February\r\n30th), an input that's complicated to invalidate but still won't ever\r\noccur\r\n\r\nAllowing these values to go unhandled led to unpredictable behavior. The\r\nRRule library uses Moment.js to compare dates, but Moment.js months,\r\ndays, and other values generally start at `0` while RRule values start\r\nat `1`. That led to several circumstances where we passed Moment.js a\r\nvalue of `-1`, which Moment.js interpreted as moving to the\r\n***previous*** year, month, or other period of time.\r\n\r\nAt worst, this could cause an infinite loop because the RRule library\r\nwas constantly iterating through the wrong year, never reaching the date\r\nit was supposed to end on.\r\n\r\nIn addition to making the RRule library more able to handle these cases,\r\nthis PR also gives it a hard 100,000 iteration limit to prevent any\r\npossible infinite loops we've missed.\r\n\r\nLastly, the Snooze Schedule APIs also come with additional validation to\r\nhopefully prevent out of bounds dates from ever being set.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <jankigaurav.salvi@elastic.co>\r\nCo-authored-by: adcoelho <antonio.coelho@elastic.co>","sha":"b30210929be0824f684f0b7d9d13bc936c1cbd22","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesFramework","backport:version","v8.18.0","v8.16.3","v8.17.1"],"number":205650,"url":"https://github.com/elastic/kibana/pull/205650","mergeCommit":{"message":"[ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205558\r\n\r\nUpdates the RRule library to correctly handle some scenarios with\r\ninvalid parameters that would either cause it to return strange\r\nrecurrence data or to infinitely loop. Specifically:\r\n\r\n- On `RRule` object creation, removes and ignores any `bymonth`,\r\n`bymonthday`, `byweekday`, or `byyearday` value that's out of bounds,\r\ne.g. less than 0 or greater than the number of possible months, days,\r\nweekdays, etc.\r\n- Successfully ignores cases of `BYMONTH=2, BYMONTHDAY=30` (February\r\n30th), an input that's complicated to invalidate but still won't ever\r\noccur\r\n\r\nAllowing these values to go unhandled led to unpredictable behavior. The\r\nRRule library uses Moment.js to compare dates, but Moment.js months,\r\ndays, and other values generally start at `0` while RRule values start\r\nat `1`. That led to several circumstances where we passed Moment.js a\r\nvalue of `-1`, which Moment.js interpreted as moving to the\r\n***previous*** year, month, or other period of time.\r\n\r\nAt worst, this could cause an infinite loop because the RRule library\r\nwas constantly iterating through the wrong year, never reaching the date\r\nit was supposed to end on.\r\n\r\nIn addition to making the RRule library more able to handle these cases,\r\nthis PR also gives it a hard 100,000 iteration limit to prevent any\r\npossible infinite loops we've missed.\r\n\r\nLastly, the Snooze Schedule APIs also come with additional validation to\r\nhopefully prevent out of bounds dates from ever being set.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <jankigaurav.salvi@elastic.co>\r\nCo-authored-by: adcoelho <antonio.coelho@elastic.co>","sha":"b30210929be0824f684f0b7d9d13bc936c1cbd22"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205650","number":205650,"mergeCommit":{"message":"[ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205558\r\n\r\nUpdates the RRule library to correctly handle some scenarios with\r\ninvalid parameters that would either cause it to return strange\r\nrecurrence data or to infinitely loop. Specifically:\r\n\r\n- On `RRule` object creation, removes and ignores any `bymonth`,\r\n`bymonthday`, `byweekday`, or `byyearday` value that's out of bounds,\r\ne.g. less than 0 or greater than the number of possible months, days,\r\nweekdays, etc.\r\n- Successfully ignores cases of `BYMONTH=2, BYMONTHDAY=30` (February\r\n30th), an input that's complicated to invalidate but still won't ever\r\noccur\r\n\r\nAllowing these values to go unhandled led to unpredictable behavior. The\r\nRRule library uses Moment.js to compare dates, but Moment.js months,\r\ndays, and other values generally start at `0` while RRule values start\r\nat `1`. That led to several circumstances where we passed Moment.js a\r\nvalue of `-1`, which Moment.js interpreted as moving to the\r\n***previous*** year, month, or other period of time.\r\n\r\nAt worst, this could cause an infinite loop because the RRule library\r\nwas constantly iterating through the wrong year, never reaching the date\r\nit was supposed to end on.\r\n\r\nIn addition to making the RRule library more able to handle these cases,\r\nthis PR also gives it a hard 100,000 iteration limit to prevent any\r\npossible infinite loops we've missed.\r\n\r\nLastly, the Snooze Schedule APIs also come with additional validation to\r\nhopefully prevent out of bounds dates from ever being set.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com>\r\nCo-authored-by: Janki Salvi <jankigaurav.salvi@elastic.co>\r\nCo-authored-by: adcoelho <antonio.coelho@elastic.co>","sha":"b30210929be0824f684f0b7d9d13bc936c1cbd22"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/205803","number":205803,"state":"MERGED","mergeCommit":{"sha":"a02fcb232faed2f385ce9b97fbdb323ccbf8ca45","message":"[8.x] [ResponseOps] [Alerting] Handle invalid RRule params and prevent infinite looping (#205650) (#205803)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ResponseOps] [Alerting] Handle invalid RRule params and prevent\ninfinite looping\n(#205650)](https://github.com/elastic/kibana/pull/205650)\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\":\"Zacqary Adam\nXeper\",\"email\":\"Zacqary@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-01-07T19:32:43Z\",\"message\":\"[ResponseOps]\n[Alerting] Handle invalid RRule params and prevent infinite looping\n(#205650)\\n\\n## Summary\\r\\n\\r\\nCloses\nhttps://github.com/elastic/kibana/issues/205558\\r\\n\\r\\nUpdates the RRule\nlibrary to correctly handle some scenarios with\\r\\ninvalid parameters\nthat would either cause it to return strange\\r\\nrecurrence data or to\ninfinitely loop. Specifically:\\r\\n\\r\\n- On `RRule` object creation,\nremoves and ignores any `bymonth`,\\r\\n`bymonthday`, `byweekday`, or\n`byyearday` value that's out of bounds,\\r\\ne.g. less than 0 or greater\nthan the number of possible months, days,\\r\\nweekdays, etc.\\r\\n-\nSuccessfully ignores cases of `BYMONTH=2, BYMONTHDAY=30`\n(February\\r\\n30th), an input that's complicated to invalidate but still\nwon't ever\\r\\noccur\\r\\n\\r\\nAllowing these values to go unhandled led to\nunpredictable behavior. The\\r\\nRRule library uses Moment.js to compare\ndates, but Moment.js months,\\r\\ndays, and other values generally start\nat `0` while RRule values start\\r\\nat `1`. That led to several\ncircumstances where we passed Moment.js a\\r\\nvalue of `-1`, which\nMoment.js interpreted as moving to the\\r\\n***previous*** year, month, or\nother period of time.\\r\\n\\r\\nAt worst, this could cause an infinite loop\nbecause the RRule library\\r\\nwas constantly iterating through the wrong\nyear, never reaching the date\\r\\nit was supposed to end on.\\r\\n\\r\\nIn\naddition to making the RRule library more able to handle these\ncases,\\r\\nthis PR also gives it a hard 100,000 iteration limit to\nprevent any\\r\\npossible infinite loops we've missed.\\r\\n\\r\\nLastly, the\nSnooze Schedule APIs also come with additional validation\nto\\r\\nhopefully prevent out of bounds dates from ever being\nset.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi\n<117571355+js-jankisalvi@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi <jankigaurav.salvi@elastic.co>\\r\\nCo-authored-by: adcoelho\n<antonio.coelho@elastic.co>\",\"sha\":\"b30210929be0824f684f0b7d9d13bc936c1cbd22\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"Team:ResponseOps\",\"v9.0.0\",\"Feature:Alerting/RulesFramework\",\"backport:version\",\"v8.18.0\",\"v8.16.3\",\"v8.17.1\"],\"title\":\"[ResponseOps]\n[Alerting] Handle invalid RRule params and prevent infinite\nlooping\",\"number\":205650,\"url\":\"https://github.com/elastic/kibana/pull/205650\",\"mergeCommit\":{\"message\":\"[ResponseOps]\n[Alerting] Handle invalid RRule params and prevent infinite looping\n(#205650)\\n\\n## Summary\\r\\n\\r\\nCloses\nhttps://github.com/elastic/kibana/issues/205558\\r\\n\\r\\nUpdates the RRule\nlibrary to correctly handle some scenarios with\\r\\ninvalid parameters\nthat would either cause it to return strange\\r\\nrecurrence data or to\ninfinitely loop. Specifically:\\r\\n\\r\\n- On `RRule` object creation,\nremoves and ignores any `bymonth`,\\r\\n`bymonthday`, `byweekday`, or\n`byyearday` value that's out of bounds,\\r\\ne.g. less than 0 or greater\nthan the number of possible months, days,\\r\\nweekdays, etc.\\r\\n-\nSuccessfully ignores cases of `BYMONTH=2, BYMONTHDAY=30`\n(February\\r\\n30th), an input that's complicated to invalidate but still\nwon't ever\\r\\noccur\\r\\n\\r\\nAllowing these values to go unhandled led to\nunpredictable behavior. The\\r\\nRRule library uses Moment.js to compare\ndates, but Moment.js months,\\r\\ndays, and other values generally start\nat `0` while RRule values start\\r\\nat `1`. That led to several\ncircumstances where we passed Moment.js a\\r\\nvalue of `-1`, which\nMoment.js interpreted as moving to the\\r\\n***previous*** year, month, or\nother period of time.\\r\\n\\r\\nAt worst, this could cause an infinite loop\nbecause the RRule library\\r\\nwas constantly iterating through the wrong\nyear, never reaching the date\\r\\nit was supposed to end on.\\r\\n\\r\\nIn\naddition to making the RRule library more able to handle these\ncases,\\r\\nthis PR also gives it a hard 100,000 iteration limit to\nprevent any\\r\\npossible infinite loops we've missed.\\r\\n\\r\\nLastly, the\nSnooze Schedule APIs also come with additional validation\nto\\r\\nhopefully prevent out of bounds dates from ever being\nset.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi\n<117571355+js-jankisalvi@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi <jankigaurav.salvi@elastic.co>\\r\\nCo-authored-by: adcoelho\n<antonio.coelho@elastic.co>\",\"sha\":\"b30210929be0824f684f0b7d9d13bc936c1cbd22\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\",\"8.16\",\"8.17\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/205650\",\"number\":205650,\"mergeCommit\":{\"message\":\"[ResponseOps]\n[Alerting] Handle invalid RRule params and prevent infinite looping\n(#205650)\\n\\n## Summary\\r\\n\\r\\nCloses\nhttps://github.com/elastic/kibana/issues/205558\\r\\n\\r\\nUpdates the RRule\nlibrary to correctly handle some scenarios with\\r\\ninvalid parameters\nthat would either cause it to return strange\\r\\nrecurrence data or to\ninfinitely loop. Specifically:\\r\\n\\r\\n- On `RRule` object creation,\nremoves and ignores any `bymonth`,\\r\\n`bymonthday`, `byweekday`, or\n`byyearday` value that's out of bounds,\\r\\ne.g. less than 0 or greater\nthan the number of possible months, days,\\r\\nweekdays, etc.\\r\\n-\nSuccessfully ignores cases of `BYMONTH=2, BYMONTHDAY=30`\n(February\\r\\n30th), an input that's complicated to invalidate but still\nwon't ever\\r\\noccur\\r\\n\\r\\nAllowing these values to go unhandled led to\nunpredictable behavior. The\\r\\nRRule library uses Moment.js to compare\ndates, but Moment.js months,\\r\\ndays, and other values generally start\nat `0` while RRule values start\\r\\nat `1`. That led to several\ncircumstances where we passed Moment.js a\\r\\nvalue of `-1`, which\nMoment.js interpreted as moving to the\\r\\n***previous*** year, month, or\nother period of time.\\r\\n\\r\\nAt worst, this could cause an infinite loop\nbecause the RRule library\\r\\nwas constantly iterating through the wrong\nyear, never reaching the date\\r\\nit was supposed to end on.\\r\\n\\r\\nIn\naddition to making the RRule library more able to handle these\ncases,\\r\\nthis PR also gives it a hard 100,000 iteration limit to\nprevent any\\r\\npossible infinite loops we've missed.\\r\\n\\r\\nLastly, the\nSnooze Schedule APIs also come with additional validation\nto\\r\\nhopefully prevent out of bounds dates from ever being\nset.\\r\\n\\r\\n### Checklist\\r\\n\\r\\n- [x] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common\nscenarios\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi\n<117571355+js-jankisalvi@users.noreply.github.com>\\r\\nCo-authored-by:\nJanki Salvi <jankigaurav.salvi@elastic.co>\\r\\nCo-authored-by: adcoelho\n<antonio.coelho@elastic.co>\",\"sha\":\"b30210929be0824f684f0b7d9d13bc936c1cbd22\"}},{\"branch\":\"8.x\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v8.18.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.3\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.1\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Zacqary Adam Xeper <Zacqary@users.noreply.github.com>"}},{"branch":"8.16","label":"v8.16.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Zacqary Adam Xeper <Zacqary@users.noreply.github.com> |
||
Jon
|
d57842ab23
|
[8.16][ci] Use daily promoted EPR distribution (#205221) (#205653)
#205221 |