Alerting

Realtime alert: How can I either write my search or throttle my alert triggers to only alert the first time Splunk sees one alert per unique field value?

xxkenta
Explorer

Hello

I am currently trying to write an alert for some Windows Event Log data on client machine BSODs. The problem here is that after the initial BSOD, windows will continue to create and log the same events again and again, just with a different "EventID" and "RecordNumber". However, I only care about the first time one of these events is logged with a unique field value for the field "Report_Id".

Is there a way I can either write my search or throttle my alert triggers to only alert the first time Splunk sees a new "Report_Id" value?

Will it work by doing a real-time search and just doing a dedup on the unique field?

Thanks

0 Karma
1 Solution

dflodstrom
Builder

You can throttle alerts so that events with the same EventID, RecordNumber, and host value do not trigger future alerts for a timespan that you specify: https://docs.splunk.com/Documentation/Splunk/7.1.0/Alert/ThrottleAlerts

You'd just have to specify the amount of time to throttle and the field names.

View solution in original post

dflodstrom
Builder

You can throttle alerts so that events with the same EventID, RecordNumber, and host value do not trigger future alerts for a timespan that you specify: https://docs.splunk.com/Documentation/Splunk/7.1.0/Alert/ThrottleAlerts

You'd just have to specify the amount of time to throttle and the field names.

Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...