Deployment Architecture

Search Head Pooling - How to configure load balancer health monitor

zindain24
Path Finder

Hello,

We are using an F5-Bigip load balancer to host splunk.company.com for a pool of search heads.

Our internet services team is looking for a way to perform a health check on each pool member. Normally, they place a small html file in the document root and have the load balancer read it periodically. Has anyone had Splunk experience with this? Does anyone have any better idea for a health-check?

Also where is the web server "document root" in Splunk? We are running our servers on Linux.

Thanks!

1 Solution

zindain24
Path Finder

From the F5-Bigip perspective we just check for a tcp connection for each pool member. If a tcp connection fails on a pool member, it is removed from the global pool until availability is restored. We also robotically monitor Splunks response time and availability using an IBM product called ITCAM.http://www-03.ibm.com/software/products/en/compositeapplicationmanagerfortransactions

View solution in original post

zindain24
Path Finder

From the F5-Bigip perspective we just check for a tcp connection for each pool member. If a tcp connection fails on a pool member, it is removed from the global pool until availability is restored. We also robotically monitor Splunks response time and availability using an IBM product called ITCAM.http://www-03.ibm.com/software/products/en/compositeapplicationmanagerfortransactions

zindain24
Path Finder

From the F5-Bigip perspective we just check for a tcp connection for each pool member. If a tcp connection fails on a pool member, it is removed from the global pool until availability is restored. We also robotically monitor Splunks response time and availability using an IBM product called ITCAM.

http://www-03.ibm.com/software/products/en/compositeapplicationmanagerfortransactions

0 Karma

pwmcity
Path Finder

Can I ask if you found an answer to this? I'm about to set up the exact same thing

0 Karma
Get Updates on the Splunk Community!

Message Parsing in SOCK

Introduction This blog post is part of an ongoing series on SOCK enablement. In this blog post, I will write ...

Exploring the OpenTelemetry Collector’s Kubernetes annotation-based discovery

We’ve already explored a few topics around observability in a Kubernetes environment -- Common Failures in a ...

Use ‘em or lose ‘em | Splunk training units do expire

Whether it’s hummus, a ham sandwich, or a human, almost everything in this world has an expiration date. And, ...