Skip to main content

Incident Lifecycle

Incidents in isthisthing.online track service disruptions from detection to resolution. They can be created automatically by monitors or manually by your team.

Incident sources​

SourceDescription
MonitorCreated automatically when a monitor fails enough consecutive checks.
ManualCreated by a team member from the dashboard.

How auto-detection works​

  1. A monitor runs a check at its configured interval.
  2. If the check fails, it counts toward the confirmation threshold (default: 2 consecutive failures).
  3. When the threshold is met, an incident is created automatically.
  4. Notifications are sent to your configured integration channels.

If you enable the Mission Critical option on a monitor, an incident is created immediately on the first failure — the confirmation threshold is bypassed. Use this for services where any downtime must be flagged instantly.

The confirmation threshold prevents false alerts from transient network blips. You can adjust it per monitor in the monitor settings.

Incident statuses​

StatusMeaning
OpenNewly created, actively affecting services.
InvestigatingTeam is looking into the root cause.
MonitoringFix is deployed, monitoring for stability before resolving.
ResolvedIssue is confirmed fixed. Notifications sent to subscribers.
Under MaintenanceScheduled maintenance window active (manual only).

Creating a manual incident​

  1. Go to Incidents in the sidebar.
  2. Click Create Incident.
  3. Enter a title and description.
  4. Optionally link it to a monitor.
  5. Click Create.

Manual incidents are useful for planned maintenance, known issues, or incidents on unmonitored services.

The incident timeline​

Every incident has a timeline that records all activity:

Event typeWhen it appears
CreatedIncident is first created.
Status changedStatus transitions (e.g., Open → Investigating).
Details updatedTitle or description is edited.
Monitor updateSystem posts an update based on check results.
ResolvedIncident is marked as resolved.
NoteA team member adds a free-form update for context.

Adding a timeline note​

  1. Open the incident detail page.
  2. Scroll to the timeline section.
  3. Type your update and click Add.

Use notes to communicate with your team or document investigation steps.

Resolving an incident​

  1. Open the incident.
  2. Click Resolve.
  3. Optionally add a final note describing the fix.
  4. Confirm.

Resolution sends notifications to all configured channels and updates your status page.

Bulk actions​

From the incidents list, you can select multiple incidents and:

  • Resolve — resolve all selected at once.
  • Delete — remove all selected permanently.

AI features (Pro/Enterprise)​

Pro and Enterprise plans include AI-powered assistance:

  • Refine description — AI rewrites incident descriptions for clarity.
  • Technical analysis — AI generates a root cause analysis based on monitor data. Available from the incident detail page. Not shown on public status pages.

See also​