Know before your users do.
Generate a scheduled health-endpoint monitor with Slack, Discord or webhook alerts after repeated failures and on recovery, plus a systemd timer.
Don't learn it from a customer
The worst way to find out your service is down is a message from a user — it means it was down long enough for someone to notice and care, and you had no idea. A monitor closes that gap to minutes: it watches the same health endpoint your supervisor and load balancer use, and the moment it's been failing long enough to be real, you get a ping. Self-hosting is no excuse to be the last to know.
An alert is the start of the story, not the end. What you do with it — whether the service already tried to recover itself, whether there's a known-good version to fail over to, whether anyone has to wake up at all — is the difference between a blip and an incident. Automating that response, across the hosts you own, is what a control plane is for.
An alert tells you. A control plane handles it.
Infraveil can report configured health evidence and perform bounded restart or recovery actions for managed services. Cached fallback requires intact compatible material and local dependencies; escalation, failover, evidence completeness, and recovery success are not guaranteed.
See how it works