All features
Cron job monitoringSTARTER+

Cron job monitoring: find out when a job silently stops

Backups, invoices and data syncs fail quietly. With a heartbeat monitor, your job calls a private URL each time it finishes. If the call doesn't arrive on time, Spot Downtime alerts you.

One line to add

Add a curl to the end of your script or crontab entry. No agent or library to install.

Grace periods

Allow for jobs that run long. You're only alerted once the expected time plus the grace period has passed.

Report failures directly

Call the URL with /fail at the end to mark the job down immediately when it errors.

See it in Spot Downtime

The real app, with a demo team's monitors. Part of the Starter and Pro plans.

A heartbeat monitor for a nightly backup, with one missed night
A nightly backup that pings when it finishes. The red bar is the night it didn't.

What is cron job monitoring?

Cron job monitoring, also called heartbeat monitoring, watches for something that should happen on a schedule. Instead of Spot Downtime checking your server, your job checks in: at the end of each run it calls a private ping URL. If the call doesn't arrive within the expected interval plus a grace period, the monitor goes down and your team is alerted.

That catches failures ordinary uptime checks can't see: a crontab entry that was deleted, a server replaced without its scheduled tasks, a job that hangs forever, or a script that has been failing every night for weeks.

Adding a heartbeat to a job

Add one call to the end of the job, for example: /opt/backup.sh && curl -fsS -m 10 followed by your ping URL. The && means the ping only happens when the script succeeds. To report a failure straight away, call the same URL with /fail on the end from your error handling.

Ping with GET, POST or HEAD from anything that can make an HTTP request: curl, wget, PowerShell, Python or Node.js, the last step of a CI pipeline, a Kubernetes CronJob or a scheduled serverless function. There's no agent or library to install.

Choosing the interval and grace period

Set the interval to how often the job runs, from every minute to once a week, and the grace period to how long a run can reasonably take, up to 24 hours. A nightly backup that takes 20 minutes might use 1 day with 30 minutes' grace. You're only alerted once both have passed.

Cron job monitoring is part of the Starter and Pro plans. It sits alongside your website and API monitors in the same workspace, with the same alert channels and incident history.

How to set it up

  1. 1Click Add monitor and choose Heartbeat.
  2. 2Name it and choose how often the job runs, from every minute to once a week, plus a grace period.
  3. 3Copy the ping URL from the monitor's page.
  4. 4Add a call to it at the end of your job.

The details

Expected interval
1 minute to 7 days
Grace period
None up to 24 hours
Ping methods
GET, POST or HEAD to the ping URL; /fail to report a failure
Counts as down
No ping within the interval plus grace, or a /fail call
Plan
Starter and Pro

Questions

Is the ping URL secret?
Yes. It contains a random token, so only someone with the URL can ping it. Treat it like a password.
What if my job pings very often?
Repeated successful pings within a few seconds just move the deadline forward; they don't flood your history.

Set up cron job monitoring in under a minute

Available on Starter and Pro. Start free and upgrade when you need it.

Create a free account