Interval-based alerting
Tell us how often the job should ping, any interval from one minute up, and a missed run is detected within a minute. An optional grace period covers jobs that run a little late.
Heartbeat monitoring for cron jobs, backups and ETL pipelines. Each job pings its own URL when it runs, and your team is alerted when it fails or the pings stop.
Uptime checks work by making HTTP requests. Scheduled jobs work the other way round. They call home when they succeed. Site Qwality gives each job a unique ping URL; silence means something went wrong.
Tell us how often the job should ping, any interval from one minute up, and a missed run is detected within a minute. An optional grace period covers jobs that run a little late.
Ping when a run starts, when it succeeds, or when it fails with its exit code. A reported failure alerts right away.
Each ping is stored with its time, source address and headers, so you can see which host called in, how long the run took and how it ended.
Failures and recoveries go to the notification groups you choose. A failed job can also open an incident that resolves itself when pings resume.
A plain HTTPS request to your ping URL, with no SDK and no agent. Works from bash, Python, Node, Ruby, Go, or anywhere else you can make a request.
Every failure window is recorded with an uptime percentage per check, and a status page component can follow the job.
Traditional monitoring checks that your service responds. Cron monitoring inverts that: your job reports each successful run, and a missing report is itself the alert. There is no agent to maintain.
Nothing to install. Copy the ping URL from your dashboard and append a curl call to your existing script, after the work has succeeded.
line of code to integrate any scheduled job
shortest expected interval between pings
cron monitors free, unlimited on any paid plan
free tier, no credit card needed to start
Each monitor gets a unique ping URL. Your job calls it when a run finishes successfully. If no ping arrives within the interval you set, plus any grace period, the check fails within a minute and your notification groups are alerted.
Set the interval to the time between scheduled runs, not the run time, and ping at the end of the job. Add a grace period as long as a healthy run can be late, and a late run that pings inside it does not alert.
Yes. Add /start to the ping URL when a run begins, and /fail or the exit code when it ends. The recent pings list shows each run’s result, exit code and run time, and a reported failure takes the check down right away instead of waiting for a missed ping.
No. The integration is a single HTTPS request: a curl command, a fetch() call, or the equivalent in any language. No daemon, no agent, no code dependency to maintain.
Yes. Any interval from one minute up works. You set the time between pings rather than a cron expression.
The cron job monitoring tools guide compares nine tools from their own pricing and documentation pages.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.