In short
- Headline = the worst metric on the page, made worse (never better) by an open incident or running maintenance.
- A metric is healthy, degraded or unhealthy against your thresholds. Comparisons are strict: exactly on the line does not match.
- Changes wait for a confirmation time, so one bad reading never flips the page.
- History bars judge each hour by how long it was bad. A short blip stays green.
- Uptime % = the share of measured time that was not an outage.
The headline
- Roll up the metrics. The page takes its worst metric: unhealthy, then degraded, then healthy, then no data. Averaging would hide problems.
- Fold in incidents and maintenance. An open incident or running maintenance can make the headline worse, never better. A minor incident reads as degraded; a major or critical one as an outage.
A metric whose agent has gone quiet reads Delayed. Running
maintenance reads Under maintenance.
Per-metric status
Each value is compared against your thresholds:- Matches the healthy rule: healthy.
- Otherwise, matches the unhealthy rule: unhealthy.
- Otherwise: degraded.
Confirmation time
A new status must hold for a confirmation time before the page changes. Getting worse and getting better have separate windows, so you can flag an outage fast and declare recovery carefully. Until then the page keeps the old status. See Thresholds and confirmation.No data
When a check can’t produce a value (the target is unreachable, the query returned nothing), the sample is no data, never a guess. Each metric has a no data treatment: keep it as no data, or count it as healthy, degraded or unhealthy. For example, an error-rate query that returns nothing usually means no errors, so count it as healthy. The treatment applies to the current status and to history, but never colors days before the metric existed or hours that haven’t happened.Delayed
If an agent stops reporting, the page doesn’t keep showing its last verdict. Once the newest sample is older than the staleness cutoff, the metric reads Delayed:History bars
Each metric shows one bar per day in the page’s time zone. A day takes its worst hour. How an hour gets its color. Each stored sample holds its status until the next sample (up to the staleness cutoff). Then:
The threshold is two minutes for each minute of the check’s
interval, at least 2 minutes and at most 30, and never more than the
time the hour was measured.
Examples with the default 1-minute check:
The threshold applies to the colors of the bars, the hourly breakdown
and the uptime calendar only. The uptime percentage counts every minute
of measured time, and the current status, incidents, alerts, SLOs and
SLAs count every sample.

