-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAC][Rule Registry] Rule registry executors skip writing AAD when execution is cancelled #113804
Comments
It looks like there are currently two rule registry executors types: Inside the kibana/x-pack/plugins/rule_registry/server/utils/create_lifecycle_executor.ts Lines 284 to 295 in bbb2e96
to ensure Inside the kibana/x-pack/plugins/rule_registry/server/utils/create_persistence_rule_type_factory.ts Lines 26 to 42 in bbb2e96
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
Blocked on #113804 |
As part of this investigation, we have identified improvements in the way the alerting framework can respond to being cancelled. With this issue, we are planning to (configurably) skip scheduling actions for rules that have been cancelled due to task timeout. With this issue, we are planning to pass a helper function
executionIsCancelled()
that allows executors to check whether or not they should continue execution.In order to be consistent with these framework changes, the rule registry executors should be checking whether or not rule execution is cancelled before writing AAD, otherwise this will lead to inconsistencies. For example, if the rule registry continues to write out AAD documents when the rule execution status is in
error
, with reasontimeout
and no notifications are sent.The text was updated successfully, but these errors were encountered: