Status reference

What the colored pills around the app mean. Three primitives — Issues, Incidents, Monitors — each with its own status vocabulary.

Nightlamp uses three status vocabularies. Issues describe a fingerprinted group of events (open, acknowledged, resolved, ignored). Incidents describe a customer-facing outage (open, resolved). Monitors describe a recurring probe's lifecycle (active, paused, deleted) — not the most recent probe outcome, which lives in last_check_status. The sections below define each value.

What does each Issue status mean?

An Issue is a fingerprinted group of events with the same root cause. Statuses describe what the Issue is doing right now:

openNew events arriving. Has not been triaged or resolved.

acknowledgedAn ops engineer has claimed it; events still arriving.

resolvedMarked fixed, and it stays that way. New events on the same fingerprint keep aggregating and raise a regression alert once, without pulling the issue back into the default queue.

ignoredMarked not actionable. New events on the same fingerprint stay out of the default queue.

What does each Incident status mean?

An Incident is a customer-facing event ledger — what to email about, what to show on the status page. One Incident can roll up many Issues; one Issue can trigger multiple Incidents over time.

openActive outage. Notifications fired; on-call paged.

resolvedUnderlying issue confirmed fixed. Resolve email sent to ops + customer.

What does each Monitor status mean?

A Monitor is a recurring probe (HTTP, keyword, SSL, TCP) running on a schedule. Statuses describe the monitor itself, not the most recent probe outcome — that lives in last_check_status.

activeProbing on schedule.

pausedManually paused (e.g. during a planned maintenance window). Probe runner skips it.

deletedSoft-deleted. Records retained for audit; not visible in lists.

Confirmation rule: a single failed probe doesn't open an incident — the runner re-probes twice with a 5 s delay. An incident only opens when all three attempts fail. This catches transient network blips without paging on every flap.