[Security Solution] Failed rule execution shows 0 for index duration even though alerts were written #155672
Labels
bug
Fixes for quality problems that affect the customer experience
consider-next
Feature:Rule Monitoring
Security Solution Detection Rule Monitoring area
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
Team:Detection Engine
Security Solution Detection Engine Area
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Summary
First identified in
8.8
/main
(in testing #155384), the Rule Execution Results table can show0
forIndex Duration
even though alerts were written. This is problematic as we don't currently show how many alerts were created per execution, so users must use theIndex Duration
column to determine if alerts were created.Steps to recreate
host.name:*
)Rule Execution Results
table and verify a0
Index Duration
, then click theFilter alerts by execution id
action and verify alerts indeed were writtenAdditionally, in recreating this issue it looks like
Index Duration
can sometimes be non-zero even when alerts weren't created (i.e. the inverse of the above):Index Duration shows non 0 value, however no alerts were indexed:
Resulting documents
Rule Execution Results API response:
Event Log docs for execution 4c6fee0e-3c8a-4e3b-b9d1-c7a04869918f (gap failure, but alerts generated)
Event Log docs for execution a18e1a68-a143-4bf8-8983-94d49e132ff1 (successful execution w/ 2 index duration but no alerts)
The text was updated successfully, but these errors were encountered: