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.
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...