Getting Data In

Splunk Health Warning on Search Head

Roy_9
Motivator

Hello,

We are using Splunk cloud and seeing the below error message on SH.

 Search Scheduler Search Lag

  • Root Cause(s):
    • The number of extremely lagged searches (4) over the last hour exceeded the red threshold (1) on this Splunk instance

 

Can someone please help me in fixing this issue?

 

 

Thanks

Labels (3)
Tags (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Use the Cloud Monitoring Console app to see which searches are lagged.  Go to Search->Scheduler Activity and scroll down to the Execution Latency panel.  Group the results by Report Name to find the offending searches.

Try rescheduling the searches to a time when fewer other searches are running.

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

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...