Silence is the signal
Give a heartbeat an expected period and a grace period. One line at the end of your job pings the URL. Miss the window and an incident opens on its own.
Cron & Heartbeats
The job that quietly stopped running.
Nothing fails louder than a backup you find out was never running. Heartbeats invert the check: your job pings us, and silence is the alert.
Included on every plan. Nothing here is an add-on.
Heartbeats · last 23 runs
1 incident open- nightly-backup every 24 h
- invoice-run every 1 h
- search-reindex every 15 min
- queue-worker every 5 min
On time Late, inside grace Missed
Cron & Heartbeats, in detail.
Report failure explicitly
A /fail endpoint lets a job report that it ran and went wrong. That is a different problem from not running at all, and worth telling apart at three in the morning.
Anything on a schedule
Nightly backups, billing runs, queue workers, ETL jobs, certificate renewals, data exports. If it should have happened by now and didn’t, that’s worth knowing.
Checkout API is down
- Monitor
- Checkout API
- Target
- https://api.acme.com/checkout
- Reason
- HTTP 503 on 3 consecutive checks
- Confirmed by
- NYC, Frankfurt
- Since
- 09:12:04 UTC
Sent once, per channel
- Phone call Delivered
- SMS Delivered
- Slack Delivered
- Webhook Signed · 200
The specifics
Heartbeat options
Written out in full, because “monitoring” means something different at every vendor.
- Expected period
- How often the job should check in
- Grace period
- How late is still acceptable before an incident opens
- Endpoints
- A ping URL, plus /fail to report an explicit failure
- Alerts
- Dedicated webhook event for missed heartbeats
Works with
Every part of StatusCheck is on every plan. These are the pieces this one talks to most.
Try it on your own endpoints.
StatusCheck opens in batches. Join the waitlist and we’ll email you once, when it’s your turn. The free plan needs no card.