Health Monitoring

* Scheduling Guide

Health monitoring schedules power the heartbeat checks, uptime pings, and synthetic monitors that detect service degradation before users notice. Intervals of one to five minutes are typical for public-facing services; internal services can often tolerate a longer polling window. The key design decision is where the check runs: a cron job on the same host as the service it monitors will go silent when that host fails, so health checks should run from a separate machine or a managed monitoring platform. For distributed systems, stagger health checks across different regions to detect geographic routing failures. Certificate expiry checks are a common edge case — add a scheduled check that alerts 30 days before expiry, not just when the certificate has already expired.