Missed runs
Detect when scheduled processes fail to report completion.
Monitor Type
Heartbeat Monitoring
Ensure scheduled jobs and background workers report in on time.
What this monitor checks
Delay windows
Alert when jobs finish outside expected timing windows.
Reliability trend
Track consistency of recurring tasks over time.
Common use cases
Cron monitoring
Validate hourly and daily jobs complete as expected.
Batch pipelines
Catch stalled ETL and asynchronous processing workflows quickly.
Sync verification
Confirm background sync processes continue sending heartbeats.
Implementation blueprint
1. Define critical targets
Start with services and workflows that create direct customer or revenue impact.
2. Tune alert thresholds
Use warning and critical layers so on-call responders get signal without alert fatigue.
3. Validate escalation flow
Simulate failures and verify acknowledgement, assignment, and recovery behavior end-to-end.
Suggested thresholds
| Signal | Recommended baseline | Escalate when |
|---|---|---|
| Expected heartbeat interval | Within schedule window | Missed 1 full interval |
| Completion delay | < 2 minutes | > 5 minutes over baseline |
| Consecutive misses | 0 | >= 2 consecutive misses |
FAQ
When should I use heartbeat monitoring?
Use it for jobs that should report completion on a predictable schedule.
How strict should missed-run alerts be?
Start with warning at one missed run and critical at two consecutive misses.
Can heartbeat checks reduce silent failures?
Yes. They catch hidden background failures where user-facing endpoints still appear healthy.
Related monitor types
Custom Metrics Monitoring
Pair this monitor to increase coverage and improve incident triage confidence.
Database Monitoring
Use together to reduce blind spots and catch degradation before customer impact.
Choose your preferred alert channels
Notify the right responders instantly across channels your team already uses.
Email and SMS
Deliver rapid alerts with fallback channels for critical incidents.
Slack and Teams
Route monitor events directly into team collaboration channels.
Webhooks and integrations
Trigger downstream workflows in PagerDuty, Opsgenie, and internal tools.
Advanced capabilities included
Multi-location monitoring
Run checks from multiple regions to isolate local routing issues from global outages.
Maintenance windows
Pause checks during planned maintenance to keep alert noise low and signal clear.
Recurring notifications
Keep stakeholders informed when incidents remain open for longer durations.
Status communication
Coordinate internal and customer updates with status page friendly incident workflows.
What teams value most
"We moved from delayed outage discovery to immediate, actionable alerts with clear ownership."
Deploy Heartbeat Monitoring checks quickly
Create your monitor, define escalation policy, and start getting reliable signal in minutes.