Glossary

Every term the dashboard uses, in one place.

Monitor — one thing being watched, with its own type, schedule and settings.

Check — one attempt to look at that thing. Runs on the interval, from each selected region.

Result — what one check produced: up or down, how long it took, and the error if there was one.

Interval — how often a check runs. Your plan sets the minimum; see the settings article.

Timeout — how long one check waits before giving up and calling it a failure.

Failure threshold — how many consecutive failed results open an incident. Counted across all regions in arrival order, not per region.

Region — where a check runs from. New York is always on; the rest depend on your plan.

Incident — the record of something being down, from the moment the failure was confirmed until it recovered.

Maintenance window — a planned period when checks still run and results are still recorded, but nothing alerts and no incident opens.

Uptime % — the share of checks that passed over a period. Checks during a maintenance window are excluded.

Response time — how long a check took, in milliseconds. Not applicable to every type: a heartbeat has none, and a server check reports a measurement instead.

Latency alert — notifies you when responses get slow, without marking the monitor down. It never changes status.

Notification channel — where alerts go. One of Email, Slack, Microsoft Teams, Discord, Webhook.

Status page — a public page showing your customers which of your services are healthy.

Component — one line on a status page, backed by one or more monitors.

Heartbeat — a monitor that waits to be pinged, rather than going out to look. For jobs that run on a schedule.

Enrollment token — the credential that lets a server join your account. It can create a server and nothing else.

Server (or host) — a machine running our agent, reporting its own CPU, memory and disk.

Check catalog — the list of measurements the agent knows how to take.

Team — the account everything belongs to. Monitors, status pages and servers belong to a team, not to a person.

API key — a credential for the API, scoped and shown once.

Last updated 4 October 2026

Still stuck?

If this did not answer your question, tell us and we will fix the page as well as answer you.