Heartbeat monitoring

Know when the job never ran.

Give scheduled work a private check-in URL, evaluate arrivals against the expected interval, and turn silence into a visible incident.

Start monitoring Read the documentation
Scheduled job
calls
Private heartbeat URL
expected by
PingBeacons
Missed check-in opens an incident

Private endpoint

Each heartbeat receives its own check-in URL.

Expected cadence

Evaluate arrivals against the configured interval.

Missed execution

Silence becomes an explicit operational failure.

Shared workflow

Use incidents, alerts, reports, and maintenance.

01Check-in workflow

Let scheduled work leave evidence.

Call the generated heartbeat endpoint after a cron job, worker, deployment task, or other scheduled process completes.

02Missed arrival

Turn silence into a measurable failure.

PingBeacons compares the last arrival with the expected interval. A missed check-in can open an incident instead of disappearing between application logs.

03History and reports

Read job reliability over time.

Heartbeat results participate in retained monitoring history and the same reporting dimensions used across the workspace.

04Planned work

Keep intentional pauses separate.

Assign heartbeat monitors to a maintenance window when scheduled work will intentionally stop checking in.

Continue the workflow

Related capabilities

Explore every feature
Understand

Incident management

Review missed execution and recovery.

Explore capability Operate

Alerts & notifications

Route missed-check-in events.

Explore capability Understand

Monitoring reports

Analyze heartbeat history.

Explore capability
Start with PingBeacons

Know when scheduled work stops checking in.

Create a private heartbeat, set its expected interval, and make missed execution visible.

Start monitoring Explore features