Heartbeat and cron monitoring
Know when cron jobs, workers, or service clusters stop reporting.
Give every job or service a heartbeat URL, define when it should report, and alert only when the expected signal is late or a cluster no longer has enough healthy sources.
Heartbeat monitoring is available on paid plans starting at $29/month.
Free includes up to 50 Ping, Port, or HTTP monitors with unlimited executions at a five-minute minimum interval, but it does not include heartbeat monitoring.
- node-01 heartbeat18 sec ago
- node-02 heartbeat21 sec ago
- node-03 heartbeat24 sec ago
- Healthy quorum4 of 4
Trusted by
What this monitor proves
A silent job should not become a silent failure.
Heartbeat monitoring reverses the check: the job or service reports successful activity, and Testable detects when the expected signal does not arrive.
- 01
Scheduled jobs
Confirm backups, billing runs, reports, imports, and other cron jobs finish on schedule.
- 02
Long-running workers
Expect recurring heartbeats from queue consumers, daemons, and background services.
- 03
Service clusters
Track sources independently and define the minimum healthy quorum for the group.
curl -fsS -X POST \
'https://heartbeat.testable.io/your-monitor?source=worker-01'Setup
Add one lightweight call to the successful path.
Create the heartbeat, choose its expected interval and grace period, then call the generated URL from the job, worker, or service.
- Create the heartbeat Name the workload and choose a schedule or recurring interval.
- Add sources Use one source per node when you need cluster-level visibility.
- Send the signal Call the generated URL only from the point that proves useful work completed.
- Handle missed beats Confirm the failure, notify responders, and open an incident when appropriate.
When a check fails
Get evidence your team can act on.
Testable connects the failed check to investigation, alerting, incident response, and customer communication.
Last-seen history
See when each workload or cluster source most recently reported.
Quorum-aware health
Avoid treating one unavailable node as a total outage when enough sources remain healthy.
Escalation and status
Route confirmed misses to the right channel and expose only the components customers need to see.
Common questions
What teams ask before they start.
Can one monitor track multiple nodes?
Yes. Give each node its own source value and set the minimum number of active sources required for health.
Can I monitor both fixed schedules and continuous workers?
Yes. Configure a scheduled deadline for jobs or a recurring expected interval for workers and services.
What should trigger the heartbeat?
Call it from the successful completion path or from the point that proves the workload is healthy and making progress.
Make silent job and worker failures visible.
Create a heartbeat, add the generated call, and let Testable watch the deadline and response workflow.