Dashboards & Visualizations

Splunk alert configuration based on dynamic log error/exception patterns

saro0710
New Member

Hi,

We are using splunk for log managment and as well as alert configuration based on Exceptions/Errors threshold which works very well for static log contents.

But if a new exception or error is introduced due to a new release or patch, there is no way to find out the new pattern of errors/exceptions with splunk alerting system.

Is there any way that we can configure dynamic alerts based on dynamic nature of log pattern changes in terms of exceptions and erros with the help of REST API framework ?

Please let me know the detail

Thanks,
Saravanan

Tags (2)
0 Karma

Ayn
Legend

This sounds like something you could do with the anomalies operator. It applies to a sliding window of events for which it monitors a field you define, and then assign an "unexpectedness" score to each value of that field.

So if you have a windows containing 10000 events and 9000 of them have the value "foo", 999 have the value "obnoxious ozelot" and the 10000th event arrives with the value "preposterous panda", Splunk will assign a very high unexpectedness score to that since it's never been seen before in the sliding window of events. You could then use the unexpectedness in your alert conditions to trigger alerts on events that don't match any of the expected values.

More information on the anomalies command is available here: http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Anomalies

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...