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!

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...