[Security Solution] Improve waitForRuleStatus verboseness #202562
Open
Description
Summary
waitForRuleStatus requires verboseness improvements to make failure reason much more prominent. Existing logging doesn't include the current rule execution status.
Details
waitForRuleStatus waits for rule execution with specified status. It prints messages like Try number 117 out of 1600 for function waitForRuleStatus while waiting. In case of failed tests waiting might take long time and lead to test timeout like here. In that case there is not event a clue on what went wrong.
Ideally we should print some debugging information with the current existing status.
Metadata
Assignees
Labels
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Security Detection Rule Management TeamSecurity Detection Response TeamNew value added to drive a business resultAddressing this issue will have a medium level of impact on the quality/strength of our product.Issues related to tests.