Monitoring Splunk

Configure splunkweb to stop when splunkd crashes

aengelstad
Engager

We've unfortunately had a few instances now where for various reasons the splunkd processes crashes or otherwise stops. Unfortunately the splunkweb process keeps running and presenting a login page HTTP/200 so our load balancer keeps it in the pool.

Ideally there would be a config to have splunkweb shutdown then the splunkd process returns HTTP4XX/5XX or timeouts however I can't see that anywhere.

Worst case I could write a shell script and cron it, but I'm trying to avoid that if I can.

Obviously the easy answer would be to stop splunkd from crashing, but I figure it's better to plan for failure.

Tags (3)
0 Karma

MuS
SplunkTrust
SplunkTrust

Hi aengelstad,

try to use MartinMcNutt's suggestion and have the load balancer also test on port 8089 and if this fails remove port 8000 from the load balancer pool. Other solution would be the script cron job that you suggested.

cheers, MuS

0 Karma

MartinMcNutt
Communicator

What about doing the health check against port 8089 too? Not sure what load balancer you have but I would give high priority to the check on 8089 then 8000.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...