Getting Data In

Best Practice for monitoring indexer health

sfmandmdev
Path Finder

Currently we ping the HTTP, SplunkTCP, and MgmtHostPorts to provide us with status of the splunk indexers. At busy times we report a lot of failures primarily on the SplunkTCP port. Most times, these errors can be ignored as the indexer will start to accept connections again as soon as some of the queues have cleared. Is there a better method to monitoring the health of the indexers?

Thanks Noel

Tags (3)

dwaddle
SplunkTrust
SplunkTrust
0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

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

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...