Cron Job Monitoring: Never Wake Up to a Silent Failure Again
Your cron jobs do not complain when they fail. PingWatchdog does.
Cron jobs and scheduled tasks fail silently. Your database backup script errors out on a Tuesday. You find out on Friday when you need the backup. PingWatchdog heartbeat monitoring catches cron job failures the moment they happen, so silent failures do not turn into emergencies.
The problem
Cron jobs fail silently by default. The server is running, the cron daemon is working, but your script exited with an error and nobody knows.
You discover backup failures, stale data, or missed emails days or weeks after they happened. Recovery is harder the longer the gap.
Your monitoring tool says your server is up, but your critical nightly jobs have been failing for a week. Uptime monitoring does not catch this.
You have cron jobs running on different servers, containers, and platforms. There is no single place to see if all scheduled tasks ran successfully.
How PingWatchdog solves it
Create a heartbeat monitor for each cron job. You get a unique URL. Add a curl request to the end of your cron script.
Set the expected interval. If your job runs every hour, PingWatchdog expects a ping every 60 minutes. If a ping does not arrive, we alert you.
Configure grace periods so irregularly spaced jobs still work. If your job runs every 5 minutes but sometimes takes 7, set an 8-minute grace period.
Monitor cron jobs, Kubernetes CronJobs, systemd timers, and cloud scheduler events all from a single heartbeat dashboard.
How to set up in 2 minutes
Create a heartbeat monitor in PingWatchdog and copy the unique URL
Add `curl -s https://pingwatchdog.com/api/v1/heartbeat/hw_YOURTOKEN` to the end of your cron script
Set the expected interval (e.g., every 60 minutes) and grace period (e.g., 10 minutes)
Add the same curl line to all your scheduled tasks: Kubernetes CronJobs, systemd timers, AWS EventBridge rules
How teams use it
A SaaS team runs nightly database backups and data export jobs. With PingWatchdog heartbeat monitoring, they catch a backup failure within 15 minutes — instead of discovering it when they try to restore a backup three weeks later. The fix is a disk space issue that takes 5 minutes to resolve.
Frequently asked questions
How is heartbeat monitoring different from uptime monitoring?
Uptime monitoring checks if your server responds to requests. Heartbeat monitoring checks if your scheduled tasks actually ran. Your server can be healthy while your backup script has been failing for a month. Heartbeat monitoring catches what uptime monitoring cannot.
What if my cron job runs at irregular intervals?
Set a generous grace period. If your job runs between 55 and 65 minutes, set a 70-minute grace period. PingWatchdog only alerts if no heartbeat arrives within that window. You can also use cron schedules that ping at fixed intervals for more reliable monitoring.
How many heartbeat monitors can I have?
3 on Free, 10 on Solo, and 25 on Team plans. Heartbeat monitors have a separate limit from uptime monitors, so they do not compete with your website and API checks.