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
