Your Cron Jobs Are Failing Silently — Here's How to Catch Them

The problem nobody talks about Your monitoring catches errors. It catches high latency, 500s, disk full, OOM kills. But what about the things that simply don't happen ? A cron job that should run every hour... just stops. No error. No log. Nothing. A nightly ETL that should finish by 4am... never starts. A data sync that usually happens every ~15 minutes... goes silent. You find out days later when someone asks "why is this data stale?" This is the dead man's switch problem. The term comes from train operators — a switch that must be actively held down, triggering an alarm if released. The same concept applies to software: if an expected signal stops arriving, something is wrong. Why existing tools don't solve this Log-based alerts trigger on patterns they see . Error-rate alerts need errors to count. If a process doesn't run at all, there's nothing to alert on. You could write a custom check for each job — "query the DB for last run timestamp, compare to now, alert if stale." But that