Monitors overview
A monitor is one automated check. Pulse runs it on a schedule, records the result, and rolls it up into your status page and history.
Statuses
| Status | Meaning |
|---|---|
UP |
The check passed. |
DEGRADED |
The service responded but breached a soft threshold (e.g. a certificate nearing expiry). |
DOWN |
The check failed. |
MAINTENANCE |
A maintenance window is active for this monitor. |
NO_DATA |
No result yet (just created, or checks haven't run). |
Monitor types
| Type | Best for |
|---|---|
| HTTP / API | Websites and API endpoints — assert on status code, body or JSON. |
| TCP Port | Databases, mail, game servers — any open TCP port. |
| DNS Record | Verify a DNS record resolves and answers. |
| TLS Certificate | Warn before an HTTPS certificate expires. |
| Domain Expiry | Warn before a domain registration lapses. |
| Heartbeat | Cron jobs and workers that check in to Pulse. |
| Group & Manual | Aggregate other monitors, or set status by hand. |
Common settings
Every monitor shares a few options:
- Name — shown on the status page.
- Product / category — which section it appears under.
- Check interval — how often it runs. See Intervals & regions.
- Region — where the check runs from.
First check
When you create or edit a monitor, Pulse runs a check immediately so your status page shows a data point without waiting for the next scheduled run.
Note
Automated checks run on a background scheduler. Sub-minute intervals are best-effort — see Intervals & regions for the details.