GuardYak Docs

How to monitor a cron job with a heartbeat in GuardYak

Backups and scheduled jobs fail silently: nothing crashes, the job just doesn't run. A heartbeat check gives the job a URL to request every time it finishes, and alerts you when a request doesn't arrive on schedule.

Before you start

  • A GuardYak account (every check type is available on the free plan)

Plays silently with captions; the narrated version is on its way.

Transcript

Find out when a backup or scheduled job quietly stops running. Here's how to monitor a cron job with a heartbeat in GuardYak.

Start a new check and choose Heartbeat. Instead of GuardYak calling your server, your job calls GuardYak.

Name the check after the job, and set the interval to how often it runs. A nightly backup runs every day.

Select Next, then add the email address that should hear about problems.

Select Review and create the check.

Copy the ping URL from the Target column. Add a request to it at the end of your job, and if a run is missed, GuardYak alerts you.

Steps

  1. Choose the check type ▶ 0:10

    In Checks, select + New check, then select Heartbeat.

    New check page with the Heartbeat check type highlighted
  2. Name it and set how often it runs ▶ 0:18

    Enter a Check name, then set Check interval to how often the job runs, for example Every day.

    Configure step for a Heartbeat check with the interval set to every day
  3. Choose who gets alerts ▶ 0:26

    Select Next. Under Address, enter the email that should receive alerts.

    Notify step with an email address entered for alerts
  4. Create the check ▶ 0:31

    Select Review, check the summary, then select Create check. The new check appears on Checks.

    Checks list showing the new Nightly database backup check
  5. Copy the ping URL into your job ▶ 0:34

    On Checks, select Copy ping URL in the new check's Target column. Make the last line of your job request it, for example curl -fsS <ping URL>.

    Checks list with the heartbeat check's ping URL and its copy button
ResultThe check appears on Checks with its ping URL as the target. It goes down when a ping is overdue.

Next steps

Updated 2026-11-03