Getting Data In

Dispatch Runner: This typically reflects underlying storage performance issues


Hi all.

I would like to know if there is a method to avoid displaying the boring messages,

[INDEXER] Dispatch Runner: Configuration initialization for /opt/splunk/var/run/searchpeers/81F8C272-511D-4FBA-A2EA-F87129051744-1625835689 took longer than expected (3260ms) when dispatching a search (search ID: remote_SH_xxx__xxx__xxx__xxx_1625837471.443922_07316CBA-2692-4C41-B9C4-89500E9141D2); this typically reflects underlying storage performance issues


inside the SearchHead(s) Environment, FROM Indexer(s) Environment.

System is up & running, heavy load, i know, and disks are very sollecitated.
This message is really annoing, i know it's not a blocking-warning (storage is under "stress"), since there are many dashboards with some panels in which the warnings completely break the visual layout.

I tried to search, but seems there's no "solution".

Any idea? I CAN'T upgrade storage and disks!


Labels (1)


If someone else has the same problem, and the same annoying warning icon, it can by bypassed by hiding the corrispective css object,


<html><style>#style, .error-details {display: none !important;}</style></html>


For me, this way, makes the job 👍

0 Karma
Get Updates on the Splunk Community!

Streamline Data Ingestion With Deployment Server Essentials

REGISTER NOW!Every day the list of sources Admins are responsible for gets bigger and bigger, often making the ...

Remediate Threats Faster and Simplify Investigations With Splunk Enterprise Security ...

REGISTER NOW!Join us for a Tech Talk around our latest release of Splunk Enterprise Security 7.2! We’ll walk ...

Introduction to Splunk AI

WATCH NOWHow are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. ...