-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
…205878) # Backport This will backport the following commits from `main` to `8.x`: - [[Rules migration] Retry failed translations (#11383) (#204619)](#204619) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-08T12:21:17Z","message":"[Rules migration] Retry failed translations (#11383) (#204619)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThese changes add a functionality which allows user to retry failed\r\nmigration rules.\r\n\r\n### Other tasks and fixes\r\n\r\n* Integrated `MigrationReadyPanel` and `MigrationProgressPanel` to show\r\nmigration's `ready` and `running` states\r\n* Migration stats pooling issue caused by waiting while there are no\r\npending migrations left. If any other operation triggers `startPooling`\r\nduring the waiting it will be ignored and thus latest stats will never\r\ncome back.\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.\r\n\r\n### Testing note\r\n\r\n1. Make sure you have a SIEM migration with failed rules\r\n2. Open that migration via `Security > Rules > SIEM Rules Migrations >\r\n{#MIGRATION_WITH_FAILED_RULES}`\r\n3. You should see a `Reprocess rules (#)` button which triggers failed\r\nrules reprocessing\r\n\r\n## Screen recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d33dc4a0-1791-4869-aa8d-b0322b5f19c3\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"e4586dac809ebfe618223aae33e9723e6cc38384","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:Threat Hunting","Team: SecuritySolution","backport:prev-minor"],"title":"[Rules migration] Retry failed translations (#11383)","number":204619,"url":"https://github.com/elastic/kibana/pull/204619","mergeCommit":{"message":"[Rules migration] Retry failed translations (#11383) (#204619)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThese changes add a functionality which allows user to retry failed\r\nmigration rules.\r\n\r\n### Other tasks and fixes\r\n\r\n* Integrated `MigrationReadyPanel` and `MigrationProgressPanel` to show\r\nmigration's `ready` and `running` states\r\n* Migration stats pooling issue caused by waiting while there are no\r\npending migrations left. If any other operation triggers `startPooling`\r\nduring the waiting it will be ignored and thus latest stats will never\r\ncome back.\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.\r\n\r\n### Testing note\r\n\r\n1. Make sure you have a SIEM migration with failed rules\r\n2. Open that migration via `Security > Rules > SIEM Rules Migrations >\r\n{#MIGRATION_WITH_FAILED_RULES}`\r\n3. You should see a `Reprocess rules (#)` button which triggers failed\r\nrules reprocessing\r\n\r\n## Screen recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d33dc4a0-1791-4869-aa8d-b0322b5f19c3\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"e4586dac809ebfe618223aae33e9723e6cc38384"}},"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/204619","number":204619,"mergeCommit":{"message":"[Rules migration] Retry failed translations (#11383) (#204619)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThese changes add a functionality which allows user to retry failed\r\nmigration rules.\r\n\r\n### Other tasks and fixes\r\n\r\n* Integrated `MigrationReadyPanel` and `MigrationProgressPanel` to show\r\nmigration's `ready` and `running` states\r\n* Migration stats pooling issue caused by waiting while there are no\r\npending migrations left. If any other operation triggers `startPooling`\r\nduring the waiting it will be ignored and thus latest stats will never\r\ncome back.\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.\r\n\r\n### Testing note\r\n\r\n1. Make sure you have a SIEM migration with failed rules\r\n2. Open that migration via `Security > Rules > SIEM Rules Migrations >\r\n{#MIGRATION_WITH_FAILED_RULES}`\r\n3. You should see a `Reprocess rules (#)` button which triggers failed\r\nrules reprocessing\r\n\r\n## Screen recording\r\n\r\n\r\nhttps://github.com/user-attachments/assets/d33dc4a0-1791-4869-aa8d-b0322b5f19c3\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"e4586dac809ebfe618223aae33e9723e6cc38384"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
- Loading branch information
1 parent
874859d
commit 5cffe2e
Showing
28 changed files
with
527 additions
and
123 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.