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!

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