Core Concepts / Monitors
Monitors
A monitor represents a single scheduled task or cron job. It holds the configuration for when the job should run and who should be notified if it fails.
Monitor Fields
Name
A human-readable name for your monitor, such as "Daily Database Backup" or "Weekly Invoice Generation".
Slug
A URL-safe identifier automatically generated from the name. Used in the ping URL if you are using auto-provisioning with Project Ping Keys.
Schedule
Defines when HealthyCron expects to receive a ping. Can be either a simple interval (e.g. every 5 minutes) or a traditional cron expression (e.g.
0 * * * *).
Grace Period
The additional "leeway" time allowed before a late job triggers an alert.
Project
The logical group or environment this monitor belongs to (e.g. Production vs Staging).
Understanding Grace Periods
If your job runs at 9:00am and has a 5 minute grace period, an alert fires at 9:05am if no ping is received. It is highly recommended to set a grace period of at least 20% of the job's duration to avoid false positives due to server load or network lag.
Monitor States
| State | Description |
|---|---|
| Healthy | Pings are arriving on time. No action required. |
| Late | The ping is overdue, but the grace period has not fully elapsed. |
| Failed | The grace period has elapsed. Alerts have been sent. |
| Paused | Alerts are temporarily suppressed. Pings will be ignored until unpaused. |
| New | The monitor was just created and has not received its first ping yet. |
Maintenance Windows
If you are performing planned maintenance and expect jobs to fail, you can manually toggle a monitor into the PAUSED state from the dashboard. This prevents false alarms from waking up your team.
Previous
← How Monitoring Works
Next
Pinging API →