Monitoring Splunk

Skipped Search

VijaySrrie
Builder

Hi Team,

An alert is scheduled to run for every 2 hours 
It is getting skipped
per day the alert will run - 12 times
For a week 12*7 = 84 times a week

We could see in the skipped search result that the alert is skipped for 3000 times in last 7 days
How is it possible?

Below search is used to find the skipped search

splunk_server=*prod1-heavy  index="_internal" sourcetype="scheduler" host=*-prod1-heavy
| eval scheduled=strftime(scheduled_time, "%Y-%m-%d %H:%M:%S")
| lookup search_env_mapping host AS host OUTPUT tenant
| stats count values(scheduled) as scheduled values(savedsearch_name) as search_name values(status) as status values(reason) as reason values(run_time) as run_time values(dm_node) as dm_node values(sid) as sid by savedsearch_name tenant
| sort -count
| search status!=success
| table scheduled, savedsearch_name, status, reason,count,tenant
Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Perhaps the alert is not configured as expected.  Please share the savedsearches.conf stanza for the alert so we can check for errors.

---
If this reply helps you, Karma would be appreciated.
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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...