Alerting

How to solve Red Health threshold in Splunk Cloud instances?

GoliSH
Engager

Searches Delayed

  • Root Cause(s):
    • The percentage of non high priority searches delayed (22%) over the last 24 hours is very high and exceeded the red thresholds (20%) on this Splunk instance. Total Searches that were part of this percentage=147626. Total delayed Searches=32735

How we can permanently solve this issue

0 Karma

gcusello
SplunkTrust
SplunkTrust

hi @GoliSH,

you should analyze your scheduled searches and change their scheduling to distribute executions.

Ciao.

Giuseppe

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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...