Use monitoring when you want to ensure that a background job is running regularly.

Monitors work on a recurring schedule and wait for a check-in from your background job. If no check-in occurs within the predefined schedule, then an alert will be triggered.

Monitor check-ins are done by a call to an HTTP endpoint (e.g. (where my-token is a unique token for each monitor).

An example might be sending a check-in using curl after a cron job has successfully completed.

0 * * * * /path/to/ && curl

Sitesure supports two types of monitors: schedule and heartbeat monitors

Scheduled monitors

Scheduled monitors are for jobs that run on a schedule and only check-in once per period.

This type of monitor is good for monitoring cron jobs or any other job that runs on a repeat schedule whether once every minute or once a month.

Scheduled monitors can be set with an expected run time. If a job hasn’t checked-in within the expected run-time after its scheduled start, then you will be notified. This helps with jobs that might run as infrequently as daily (or a monthly invoice run) but you want to be notified as soon as possible if it fails to check-in.

Heartbeat monitors

Heartbeat monitors are for jobs that run on an ad-hoc basis and check-in multiple times per period.

This type of monitor is good for background events that might not fit a schedule but you want to know if nothing has happened within a specific window.

Heartbeat monitors will alert you if no check-in occurs within the specified period.