Heartbeat monitoring for backups, cron jobs, and private services

Create a heartbeat checker

In Add checker, choose Heartbeat, then enter a display name, an optional group, the expected interval, and a grace period. The form uses whole minutes. Intervals can range from one minute to 30 days; grace can range from zero to 24 hours. Save the checker and copy the reporting command while its token is shown.

Arm it with the first success report

A new heartbeat waits without generating DOWN alerts until the first valid report. Each report restarts the interval plus grace. When the deadline passes, the regular consecutive-down threshold applies during the scheduled checker runs. A new success report allows the worker to record recovery. The dashboard refreshes the last report time and state.

Report only after a successful backup

For a daily backup, choose 1440 minutes plus a grace period that covers normal completion-time variation. Run the reporting command only if the backup command succeeds. Replace both placeholders below. Keep the token in a protected script or secret store.

your-backup-command && curl --fail --request POST \
  --header 'Authorization: Bearer YOUR_HEARTBEAT_TOKEN' \
  https://simple-ping.com/heartbeat

API documentation for heartbeat management

Monitor private systems through an outbound report

A script behind a VPN can perform a local health check, then report success over outbound HTTPS. The heartbeat proves that the reporting condition ran successfully; it does not independently inspect the private application. The token can submit success reports only and cannot access your account. Resetting it immediately invalidates the old token, so update every reporting script. Avoid placing it in a URL or a public repository.