Skip to content
Go to dashboard

9.5Incidents

An incident opens when a monitor reaches its failure threshold, outside the cooldown. While it is open, it is firing. When the monitor passes again, it is resolved and obsrvly sends the resolved message. You cannot close an incident by hand.

  1. Select alerting, then incidents.
  2. Use all, firing or resolved to filter the list. The page shows how many incidents are firing now.
  3. Select an incident to open its monitor.

Each incident shows:

  • firing with a live timer, or resolved with when it closed,
  • the monitor's name, or (monitor deleted),
  • the last error message,
  • when it fired and when it was resolved, or not yet resolved,
  • how many checks had failed in a row,
  • who acknowledged it and when, if anyone did.

The list updates every 30 seconds. It shows the newest 200 incidents, plus up to 200 firing ones. If nothing has ever fired, it shows No incidents.

The resolved message#

  • It is sent even if the monitor was muted when it went down. It then says: No alert was sent when it went down, because the monitor was muted or in a maintenance window.
  • If the incident opened and closed inside a maintenance window, no resolved message is sent.

Your status page can also show incidents (see chapter 12).

Through the API#

Call ListIncidents. Use status (firing, resolved, or empty for all), limit (default 50, at most 200) and cursor for the next page.

List firing incidents
bash
curl -s "$API/alert/obsrvly.v1.AlertService/ListIncidents" \
  -H "Authorization: Bearer $OBSRVLY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "firing", "limit": 50}'

Each incident has alertId, monitorId, monitorName, firedAt, resolvedAt, durationSeconds, consecutiveFailures, lastError, status, acknowledgedAt and acknowledgedBy. resolvedAt is empty while it is open. To get the next page, send back the nextCursor from the reply.

Last updated