Home
Pricing
Platform Blog About Contact FAQ Partners
Sign in Start free
Cron Job Monitoring

Know when a job
fails or goes quiet.

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.

Free tier included No credit card 2-minute setup
app.siteqwality.com / heartbeats / nightly-backup
nightly-backup HealthyLIVE
LAST PING02:01 UTC
INTERVAL24h
LAST CHECKED02:30 UTC
Monping
Tueping
Wedping
Thuping
Friping

Monitoring for the jobs that never make a request.

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.

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.

Start, success and failure

Ping when a run starts, when it succeeds, or when it fails with its exit code. A reported failure alerts right away.

Every ping recorded

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.

Alerts and incidents

Failures and recoveries go to the notification groups you choose. A failed job can also open an incident that resolves itself when pings resume.

One-line integration for any stack

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.

Failure history and uptime

Every failure window is recorded with an uptime percentage per check, and a status page component can follow the job.

Dead-man's switch pattern

No ping means
something broke.

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.

  • Each check gets a unique ping URL your job calls when a run finishes
  • A missed ping fails the check
  • The next ping flips it back to healthy and closes the failure window
app.siteqwality.com / heartbeats / daily-report-etl
daily-report-etl FailedLIVE
EXPECTEDevery 24h
LAST PINGyesterday 06:00
STATUSFailed
Monping
Tueping
Wedping
Thuping
Frino ping
One-line integration

Add a ping.
That's the whole job.

Nothing to install. Copy the ping URL from your dashboard and append a curl call to your existing script, after the work has succeeded.

  • Works from any language or shell that can make an HTTP request
  • Any HTTP method is accepted, and POST is the convention
  • Send a custom header such as the hostname to see which runner pinged
wrap any script#!/bin/bash
set -euo pipefail

# your job
python /opt/etl/run.py

# ping Site Qwality, only reached on success
curl -fsS -X POST "https://ping.siteqwality.com/<account-id>/<cron-job-id>"
✓ ping received · recorded
1

line of code to integrate any scheduled job

60s

shortest expected interval between pings

25

cron monitors free, unlimited on any paid plan

$0

free tier, no credit card needed to start

FAQ

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.

Start free. No credit card.

Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.