Splunk Search

How to create an alert or a report to track the number of deferred searches?

Abass42
Communicator

I am trying to create an alert or a report to track the number of deferred searches. We had an issue where the cluster captain deferred a massive amount of searches, and it messed up a few things. We are trying to create an alert to maybe mitigate that in the future. In addition to asking the best way to create a alert for this, id also like some more clarification on how to find the deferred searches. 

Through the monitoring console,  either through the DMC or the Cluster Master,  I thought i had seen a panel for deferred searches, but i can not find one now. And when i run the search 

 

 

 

index=_internal earliest=-24h "status=skipped"  sourcetype=scheduler 
| stats  count by host app | sort - count

 

 

 

I get results, but if i change status to deferred, which i assume is a status, I do not get anything.

I was suggested to run 

 

 

 

| rest /services/search/jobs 
| search status=deferred 
| table id, search, app, owner, earliest_time, latest_time, status, sid

 

 

 

but I do not get any status. Status is not a field.

 

The main question I have is How do I access the number of deferred searches? If i can find that, I can run stats count on it. 

 

Thank you. 

Labels (1)
Tags (2)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

if I recall right you should find that information from MC under Search menu. There is scheduler and then you see different options under deployment and instance. The information what you are looking should be there. 
r. Ismo

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk, and empower your SOC to reach new heights! Duration: 1 hour  Prepare to ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...