[Rules migration] Retry failed translations (#11383)

[e40pud]

Summary

Internal link to the feature details

These changes add a functionality which allows user to retry failed migration rules.

Other tasks and fixes

• Integrated MigrationReadyPanel and MigrationProgressPanel to show migration's ready and running states
• Migration stats pooling issue caused by waiting while there are no pending migrations left. If any other operation triggers startPooling during the waiting it will be ignored and thus latest stats will never come back.

Note

This feature needs siemMigrationsEnabled experimental flag enabled to work.

Testing note

1. Make sure you have a SIEM migration with failed rules
2. Open that migration via Security > Rules > SIEM Rules Migrations > {#MIGRATION_WITH_FAILED_RULES}
3. You should see a Reprocess rules (#) button which triggers failed rules reprocessing

Screen recording

Screen.Recording.2024-12-17.at.17.53.37.mov

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[semd]

LGTM!
Thanks @e40pud, good work 💯

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8cb7438

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	6483	6484	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	21.4MB	21.4MB	+5.4KB

History

• 💚 Build #262700 succeeded 0e7794c
• 💚 Build #262450 succeeded 9740874
• 💔 Build #262372 failed 5cfc84e
• 💛 Build #261988 was flaky 0c7f37c
• 💔 Build #261519 failed 7f45eca

cc @e40pud