Push (Heartbeat) Monitor

The Push monitor in updu is a passive monitoring tool. Instead of updu actively checking service endpoints, this monitor waits to receive a "ping" or "heartbeat" from your scripts, cron jobs, backups, or external services within a specified interval.

Configuration Options

When setting up a Push monitor, you can configure the following options:

Basic Settings

• Name: A descriptive name for your monitor.
• Group: Optional group assignment for organizing monitors.
• Expected Interval (seconds): How frequently updu expects to receive a heartbeat before marking the monitor down.
• Grace Period (seconds): Additional allowable delay time on top of the interval before triggering a down incident.

Push Specific Settings

• Push Token: A randomly generated API key automatically created when the monitor is saved. This token must be included in the URL of the HTTP requests made to updu.

Example Use Cases

• Cron Job Monitoring: Appending a curl https://updu.yourdomain.com/api/v1/push?token=YOUR_TOKEN command directly to the end of a scheduled bash backup script to alert you if the backup fails to run.
• Long-running Process Health: Embedding an HTTP request snippet within a worker daemon to signal it's alive and processing events every few minutes.