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!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...