Monitors
Monitors overview
The six monitor types StatusCheck supports, and the settings they share.
A monitor watches one target with one kind of check. Choose the type that most directly proves the thing you care about is working: if customers use an HTTPS API, an HTTP monitor with a status assertion says more than a ping ever will.
Monitor types
Section titled “Monitor types”| Type | What it proves | Typical target |
|---|---|---|
| HTTP | The endpoint answers with the status code and content you expect, within your latency budget. | Websites, APIs, health endpoints |
| TCP | A port accepts connections. | Databases, mail servers, game servers, anything not HTTP |
| DNS | A name resolves to the records you expect, from the resolver you choose. | Your domain, your CDN’s CNAME, MX records |
| ICMP | The host is reachable and packet loss is within bounds. | Servers, routers, office links |
| SSL | The certificate is valid, trusted, complete, and not about to expire. | Any TLS endpoint |
| Heartbeat | A job that runs on your side checked in on schedule. | Cron jobs, queues, backups, ETL |
Settings every monitor shares
Section titled “Settings every monitor shares”Interval. How often each selected region runs the check. From 30 seconds to 24 hours depending on plan. Shorter intervals detect problems sooner and use more of your monitor quota’s check budget; 60 seconds is a good default for anything customer-facing.
Regions. Where checks run from. Pick at least two so failures can be confirmed. Pick regions close to your customers for representative latency.
Timeout. How long a single check may take before it counts as a failure. Default 10 seconds; the maximum is 30 seconds.
Response-time threshold. Optional. When the confirmed response time exceeds this value the monitor is marked Degraded rather than down, so slowness is visible without paging anyone.
Alerting. Which channels receive alerts for this monitor, and how many consecutive confirmed failures to require before the first alert (default 1). Set this higher for flaky third-party dependencies you can’t fix at 3 a.m.
Groups. Optional folders on the monitors board. Groups are for you; status-page components are for your customers.
Pausing
Section titled “Pausing”Pausing a monitor stops its checks and freezes its uptime history; it doesn’t count toward your monitor quota while paused. Use pauses for planned decommissioning. For planned downtime, schedule a maintenance window instead so the history stays honest.