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!

Database Performance Sidebar Panel Now on APM Database Query Performance & Service ...

We’ve streamlined the troubleshooting experience for database-related service issues by adding a database ...

IM Landing Page Filter - Now Available

We’ve added the capability for you to filter across the summary details on the main Infrastructure Monitoring ...

Dynamic Links from Alerts to IM Navigators - New in Observability Cloud

Splunk continues to improve the troubleshooting experience in Observability Cloud with this latest enhancement ...