What Is Heartbeat Monitoring?

Reviewed by Ionut Caval · Updated June 2026

Heartbeat monitoring solves a problem that ordinary external checks cannot. A nightly backup script, a queue worker, or a scheduled data sync has no endpoint a monitor can request, and worse, when one of these silently fails to run, nothing errors and nobody notices until the missing output causes a problem days later. With heartbeat monitoring, the job itself sends a small signal (typically an HTTP request to a unique URL) every time it finishes successfully. The monitor expects that signal on a schedule, and if it does not arrive within a grace period, it alerts. The absence of a heartbeat is the alert.

How heartbeat monitoring works

You configure two values per check: the expected interval and a grace period. The interval matches the job's schedule, and the grace period absorbs normal variation in run time so a job that takes a little longer than usual does not trigger a false alarm. A concrete example: a backup that runs every 24 hours might be set to a 24-hour interval with a 1-hour grace period, so the monitor only alerts if more than 25 hours pass with no ping. The flow is simple:

• The job runs and, on success, sends a request to its unique heartbeat URL.
• The monitor records the timestamp and resets its countdown to (interval + grace).
• If the next ping arrives in time, nothing happens and the check stays healthy.
• If the countdown expires with no ping, the job is presumed failed and an alert fires.

More advanced setups send a signal at both the start and the end of a run, which lets the monitor also catch a job that started but hung or crashed midway, and measure how long each run took. Because the signal is sent from inside the job, heartbeat monitoring is sometimes called passive or push monitoring, in contrast to the active, "pull" model of synthetic monitoring.

Heartbeat vs health-check and synthetic monitoring

The distinction is who initiates the contact. A health check and synthetic monitoring are pull-based: the monitor calls the service on a schedule and judges the response. Heartbeat monitoring is push-based: the service calls the monitor, and silence is failure. This is exactly what makes it suited to work that has no inbound URL. The two models are complementary, and many teams run both: synthetic checks confirm the user-facing site stays up and feeds the uptime metric, while heartbeats confirm the invisible scheduled work behind it actually ran. Pulsetic's cron job monitoring provides heartbeat URLs for your scheduled tasks, and for a broader look at active checks see the comparison of synthetic monitoring versus real user monitoring.

See also: Cron job monitoring