Learn more about Heartbeat monitors in the Heartbeat monitor overview.
Prerequisites
Prerequisites
Before creating heartbeat monitors, ensure you have:
- An initialized Checkly CLI project
- External services, cron jobs, or scripts that can send HTTP POST requests
- Understanding of your scheduled job intervals and expected timing
- Network access from your services to Checkly’s ping endpoints
Configuration
The Heartbeat Monitoring configuration consists of specific heartbeat monitoring options and inherited general monitoring options.- Heartbeat Monitor
- General Monitor
Parameter | Type | Required | Default | Description |
---|---|---|---|---|
period | number | ✅ | - | The expected period between pings (30 seconds to 365 days) |
periodUnit | string | ✅ | - | Time unit: 'seconds' | 'minutes' | 'hours' | 'days' |
grace | number | ✅ | - | Grace period before alerting (0 seconds to 365 days) |
graceUnit | string | ✅ | - | Grace time unit: 'seconds' | 'minutes' | 'hours' | 'days' |
HeartbeatMonitor
Options
The expected period between pings from your external service. This defines how often your job or service should check in.Usage:Examples:Range: 30 seconds to 365 days
- Daily Jobs
- Hourly Tasks
- Frequent Checks
The time unit for the period. Defines whether the period is in seconds, minutes, hours, or days.Usage:Available units:
'seconds'
, 'minutes'
, 'hours'
, 'days'
The grace period to wait before alerting after the expected ping time has passed. This allows for slight delays in job execution.Usage:Examples:Range: 0 seconds to 365 days
- Short Grace Period
- Moderate Grace Period
- Long Grace Period
The time unit for the grace period. Defines whether the grace period is in seconds, minutes, hours, or days.Usage:Available units:
'seconds'
, 'minutes'
, 'hours'
, 'days'
General Monitor Options
Friendly name for your heartbeat monitor that will be displayed in the Checkly dashboard and used in notifications.Usage:
Examples
- Daily Backup Job
- Hourly Data Sync
- CI/CD Pipeline
- Log Processing
- Short Interval Check
Getting the heartbeat Ping URL
After deploying your heartbeat monitor, you can obtain the ping URL in several ways:- CLI Output
- Web UI
The ping URL is unique for each heartbeat monitor and should be kept secure. Anyone with access to this URL can send pings to your monitor.
Heartbeat monitors are passive - they wait for your external services to ping them. Make sure your jobs and services are configured to send HTTP POST requests to the ping URL on successful completion.