Alerting

My alert keeps getting auto disabled

delgendy
Explorer

I have an alert that keeps getting auto disabled, how can I identify this from the internal logs.
I want to run a search on the internal logs to know when this alert got disabled and to alert off .

Tags (1)
0 Karma

p_gurav
Champion

You can try this search to get last run of that alert before it disabled:

index=_internal sourcetype=scheduler  | stats latest(_time) as last_event by savedsearch_name | eval last_run=tostring(now()-last_event,"duration") | eval last_event=strftime(last_event, "%Y-%m-%d %H:%M:%S")
0 Karma

delgendy
Explorer

Is there any log level as Warning or Error in the internal logs that would tell me it is disabled? This is what I was leaning towards this more than getting the time difference.
However still your answer is helpful and i will try that thanks

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!

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...