← statichum.studio

Self-hosted monitoring stack that actually monitors itself (built-in dead-man's-switch)

dev tool real project •• multiple requests

Self-hosters running lightweight observability stacks keep naming the one failure mode monitoring exists to prevent: the monitor (or its host) dies silently and never tells you. They want a stack with a native external heartbeat / dead-man's-switch, pointing out that Zabbix ships self-checks while the Prometheus ecosystem leaves it as the operator's external homework.

builder note

Don't build another dashboard... build the watchdog primitive: a tiny redundant component that pushes a heartbeat to an independent channel (SMS, a second host, a hosted ping) and screams when the monitor itself goes quiet, shippable as a drop-in companion to existing Prometheus/Kuma setups.

landscape (4 existing solutions)

The simple-self-hosted-observability lane is crowded (Netdata, Uptime Kuma, Grafana stacks), but the specific, repeatedly-named gap is self-monitoring: a lightweight stack that pushes an external heartbeat so you hear about its own death. Zabbix has it but is too heavy; nobody lightweight does it cleanly.

Prometheus + Alertmanager No native self-monitoring or HA; a dead-man's-switch is a manual external pattern most operators never wire up.
Uptime Kuma Great simple uptime monitoring, but it is itself a single instance that can fail silently, with no self-HA or external heartbeat.
Zabbix Has the native HA and self-checks people want, but it is the heavyweight, dated tool homelabbers are actively fleeing.
Healthchecks.io (self-hostable) A dead-man's-switch for cron jobs, but it is yet another service you must also keep alive and does not watch the whole stack holistically.

sources (1)

hn https://news.ycombinator.com/item?id=48091898 "monitoring system not alerting me when the systems it runs on are failing" 2026-05-11
self-hostedmonitoringobservabilitydead-mans-switchhomelab