System Check
System Check is the continuous half of HealthCheck. It runs scheduled probes against your endpoints, opens incidents when they fail, tells the right people, and keeps the uptime record that SLOs, reports, and status pages are built on.
The screens
| Screen | Path | What it holds |
|---|---|---|
| Dashboard | /healthcheck/dashboard | Overview, SLOs, Saved Layouts |
| Monitors | /healthcheck/monitors | The monitor list and the new-monitor form |
| Incidents | /healthcheck/incidents | Incidents and Runbooks |
| Status Pages | /healthcheck/status-pages | Public status pages and their components |
| Alerting | /healthcheck/alerting | Channels, Silences, Maintenance, Escalation |
| Observability | /healthcheck/observability | Traces, RUM Sites, Forecast |
| Agents | /healthcheck/agents | Where checks are executed from |
How a check becomes an incident
- A scheduler picks up monitors that are due and dispatches their work.
- The work runs locally or on an agent, depending on the check type and the location you chose.
- A failing result opens an incident for that monitor.
- The incident notifies the channels attached to the monitor, unless a silence or maintenance window is suppressing it.
- Uptime and response-time history accumulate for the monitor report and any SLO that tracks the monitor.
Permissions
Every write in System Check gates on a single backend resource, healthcheck:monitor.
That means creating a monitor, an SLO, a runbook, a saved dashboard, a status page, or a scheduled report all require the same create permission, and editing or deleting them require the corresponding update and delete permissions. There are no per-screen permission keys today.
A read-only role can browse every screen and open saved results but cannot start work.
API surface without a screen
The System Check backend also exposes capabilities that have no user interface in this release. They are reachable through the API only:
- API keys and IP rules
- Crawler schedules
- Post-mortems
- On-call schedules
They are listed here so their absence from the navigation is not mistaken for a gap in the product. Do not expect a screen for them yet.
