Splunk Search

Is there a way to set trigger conditions using SPL

sm1tty
Loves-to-Learn Lots

I am coming across an interesting problem where notables are being generated for each event in Splunk with unique notable IDs, despite trigger conditions being set and notables being set to "Trigger Once".

For example, if we are looking for 5 or more failed user login events over the span of 10 minutes, we will receive 5 notable alerts in our queue for each event, despite having counts  set to >=5 and other trigger conditions set, and having trigger set to "once" as opposed to "for each result". It seems like even when the trigger is set to "once", it is still behaving as if it is set to "for each result"

sm1tty_0-1643897484105.png

Is there a way to set trigger conditions using SPL itself so that only one notable event is generated for a query that yields multiple results so we will only receive one notable?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...