Splunk Cloud Platform

Alerts are triggered late

DineshElumalai
Engager

Hello

I have an alert that runs every 2 minutes for the last 40 hours of data. I use five different logs to retrieve the result I need using the join command. The throttle is set on, suppressing the results for 40 hours in order to suppress the repeating alert.

My alert runs perfectly and triggers on time. But every three to four months once, I get the delayed alert for some hours. This issue was repeating for every three to four months, So I had an alternative alert running. Now one of the alert gets delayed for 4 hours and an other one was on time. It makes the alert less reliable.

I started to monitor the triggered alerts in Triggered alerts section. Note: It's a very big query takes 30 seconds.

 May I know the possible reason for this and best practices to avoid this error in future? How to identify the issue? 

Labels (1)
Tags (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

it’s hard to help you without more information about your environment and queries.

You could try to look if this helps https://conf.splunk.com/files/2020/slides/TRU1761C.pdf

There are many more presentations which could help too?

r. Ismo

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 ...