This post is about monitoring cron jobs on shared hosting. Cron jobs fail silently on shared hosting. I explain how I monitor, alert, and recover when scheduled tasks stop running.
Assume Cron Will Fail Eventually
Cron jobs fail silently on shared hosting. I explain how I monitor, alert, and recover when scheduled tasks stop running.
- crontab logs — applied directly to monitoring cron jobs on shared hosting.
- heartbeat files — applied directly to monitoring cron jobs on shared hosting.
- email alerts — applied directly to monitoring cron jobs on shared hosting.
- failure recovery scripts — applied directly to monitoring cron jobs on shared hosting.
The Working Approach
For Cron Job Monitoring on Shared Hosting, I kept the implementation narrow: crontab logs, heartbeat files, email alerts, and failure recovery scripts. Every decision tied back to that scope instead of expanding into unrelated admin features.
Make Failures Visible Quickly
Representative code from the implementation — simplified for readability, but structurally what I deploy.
Cron heartbeat file for job monitoring
<?php
file_put_contents('/var/www/app/storage/cron-heartbeat.txt', time());
$last = (int) @file_get_contents('/var/www/app/storage/cron-heartbeat.txt');
if (time() - $last > 90000) {
mail('ops@example.com', 'Cron failed', 'Nightly job did not run.');
}Where This Approach Paid Off
Shipping monitoring cron jobs on shared hosting cleanly meant the next developer could extend it without untangling hidden coupling.
The part worth copying is the scope discipline: solve the stated problem fully before adding adjacent nice-to-haves.
Before You Start Your Version
- Start with the exact problem statement for monitoring cron jobs on shared hosting — one sentence, no buzzwords.
- Prioritise crontab logs before polishing secondary UI details.
- Validate heartbeat files under realistic data volume, not demo rows.
