Splunk ITSI

Normal/Clearing event getting same timestamp as original event

FeatureCreeep
Path Finder

I have an alert that can clear in the same minute that it originally fired.  When the correlation search runs, both events are in it, the alert and the clearing alert.  The correlation search creates notable events for each but uses the current time for the _time for the notable events and not the _time from the original alerts.  Since both alerts are converted into notable events during the same correlation search run, they get the exact same timestamp.  This causes ITSI to not definitely know the correct order of the events and it sometimes thinks the Normal/Clear event came BEFORE the original alert.

This seems odd to me.  I would have imagined that ITSI would use the original event time as the _time for the notable event but it doesn't.

Any ideas on how to address?   

Labels (3)
0 Karma
1 Solution

KendallW
Contributor

Hi @FeatureCreeep try setting the 'param.is_use_event_time' in alert_actions.conf as discussed in this doc:
https://lantern.splunk.com/Observability/Product_Tips/IT_Service_Intelligence/Configuring_notable_ev... 

View solution in original post

0 Karma

KendallW
Contributor

Hi @FeatureCreeep try setting the 'param.is_use_event_time' in alert_actions.conf as discussed in this doc:
https://lantern.splunk.com/Observability/Product_Tips/IT_Service_Intelligence/Configuring_notable_ev... 

0 Karma

FeatureCreeep
Path Finder

Exactly what I needed!  Thanks!

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...