Skip to content

Heartbeat & Cron Monitoring

Your services ping a unique URL on schedule. If a ping is missed, you get alerted. Perfect for cron jobs, CI/CD pipelines, and background workers.

Everything You Need for Heartbeat Monitoring

Unique Heartbeat URLs
Each heartbeat monitor gets a unique URL. Just send a GET or POST request from your cron job, CI pipeline, or background worker — no agents to install.
Configurable Expected Intervals
Set the expected ping frequency from 1 minute to 24 hours. Define exactly how often your job should check in so we know when something is wrong.
Grace Periods
Add a grace period for tasks that occasionally run a few seconds late. Avoid false positives from minor scheduling drift.
Cron Expression Support
Define schedules using standard cron expressions. Webalert calculates expected ping times automatically from your crontab syntax.
Multi-timezone
Configure each heartbeat in its own timezone. No more mental UTC conversions — schedules display in the timezone your job actually runs in.
Dashboard Integration
See all heartbeat monitors alongside your HTTP, TCP, and DNS monitors in one unified dashboard with ping history and status timeline.

How Heartbeat Monitoring Works

1

Create a Monitor

Create a heartbeat monitor and get a unique URL. Choose the expected interval and grace period.

2

Ping from Your Code

Add an HTTP call to that URL at the end of your job or script. One line of code is all it takes.

3

Get Alerted on Missed Pings

If the ping doesn't arrive on time, we alert you instantly via your preferred channels.

Never Miss a Failed Cron Job Again

Free forever plan with 3 monitors. No credit card required. Set up in under 2 minutes.