Open maximpn opened 20 hours ago
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
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 likeTry 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.