1 hour ago · Tech · hide · 0 comments

In this post I share the third and most recent iteration on the uptime monitoring for all my homelab services. The main job of this subsystem is to alert me when some web service is down. I have two different systems that detect and alert uptime issues on my homelab services: cloud-status and uptime. Both are small pieces of Rust code that I've written for my use case. They both read my Caddyfile to know which hosts I have and probe them one by one. The main difference is that cloud-status probe from the point of view of the outside, using an hourly job that runs on some cloud provider. While uptime probes from the inside of the homelab, every fifteen seconds. Cloud status This is a job that will run on a cloud server every hour to check that: my private services that only answer to private IPs are not available on the Internet my protected services that require knock protection redirect to the login page my public services answer with 200 In case of any problem, it will notify me by…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.