Your Cron Job Didn't Hurt You. It Hurt Everyone Else.
The person who owns the cron job is usually the last to notice it stopped running. The pain lands on everyone downstream — support, finance, customers, partners.
Blog
What we're building and what keeps breaking.
Your Cron Job Isn't Running. Here's How to Find Out Why.
A debugging checklist for when the schedule said it should have fired and your inbox is suspiciously quiet. Daemon, crontab, syntax, timezone, environment, output, SELinux, disk inodes, and the silent-success failure mode.
I Kept Getting Alerted for a Job That Was Fine
CronDoctor's own internal monitors were alerting me 2-3 times an hour on perfectly normal runs. Averages were the problem. Here's how I found P95 and why it's how CronDoctor handles all cron job monitoring now.
CronDoctor Caught Its Own Bug After I Went to Bed
I woke up to 5 emails from my own product. Here's what happened when CronDoctor monitored itself and found a real problem.