Skip to content

Heartbeat monitoring for cron jobs, backups and scheduled tasks.

Some failures are silent. Give your scheduled task a private check-in URL and know when the expected signal stops arriving.

Illustrative example · Demo data
/heartbeat/••••••••

Regular signals → missed signal → recovery

  1. 01Check-in received
  2. 02Expected signal missing
  3. 03Signals resumed

Fictional sequence. Animation timing is not check cadence or a performance promise.

01

Your job sends the signal

Connect the private heartbeat URL to your job and configure its expected interval. Keep that URL secret: possession of it allows a check-in to be sent for the monitor.

02

A missing pulse has meaning

The last check-in shows when your job most recently reported. If the next expected signal does not arrive within the configured window, the monitor can detect the missed heartbeat and record an incident.

03

Recovery when the signal resumes

When check-ins resume, recovery is recorded and can produce an email notification. Place the signal at the point in your job that represents the outcome you want to observe; a check-in alone does not validate a backup file.

In practice

Where this signal earns its place.

  • Nightly backup completion signals.
  • Scheduled imports and synchronization jobs.
  • Recurring reports and background maintenance.

A closer look

Does UpDownTracker run my cron job?

No. Your environment runs the task and sends the check-in. UpDownTracker observes whether the expected signal arrives.

Can I share the heartbeat URL?

Treat it as a secret and keep it out of screenshots, public repositories and support messages. The example on this page is masked and cannot receive signals.

Connect the context

Related signals

All features

Start monitoring

Know about downtime before your customers do.

Add your first monitor and keep website availability, performance and incident history in one clear place.

7-day Starter trial · No credit card required · Starts with your first monitor