Deployment Architecture

The percentage of non high priority searches lagged (100%) over the last 24 hours is very high and exceeded the yellow thresholds (40%) on this Splunk instance. Total Searches that were part of this percentage=1. Total lagged Searches=1

kalilinux0011
New Member

what does it mean please?

The percentage of non high priority searches lagged (100%) over the last 24 hours is very high and exceeded the yellow thresholds (40%) on this Splunk instance. Total Searches that were part of this percentage=1. Total lagged Searches=1

how to solve it?

Thanks a lot

][1]

Tags (1)
0 Karma

aberkow
Builder

My interpretation of this is that your scheduled searches are being hung for some reason. I would typically assume this means the necessary resources are being consumed by other searches, but you only have one lagged search, which is interesting. Additionally, it is "non high priority", so hopefully that means this isn't an enormous issue.

EIther way, you should be able to investigate this (assuming you're a Splunk admin on your instance) by going into Settings -> Monitoring Console -> Search -> Scheduler Activity: Instance, and inputing the timeframe when this occurred. Hopefully the information under "historical charts" can point you in the direction of what caused this to occur (perhaps the machine blipped, etc), or at least narrow down the timeframe/options so you can continue debugging.

Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...