Incident Management

Fyren provides a full incident lifecycle — from the moment an issue is detected through investigation, identification, monitoring, and resolution. Each step is communicated to your subscribers and displayed on the public status page.

Incident Lifecycle

Incidents progress through the following statuses:

Severity Levels

Timeline Updates

Each incident has a timeline of updates. When you add an update, you set the new status and a message explaining what happened:

{
  "status": "identified",
  "message": "Root cause identified. A fix is being deployed."
}

Updates are displayed chronologically on the public status page incident detail view. Each update records the user who created it for audit purposes.

Affected Components

Incidents are linked to one or more components via a junction table. When an incident is active, the affected components are highlighted on the status page.

{
  "title": "API Latency Issues",
  "status": "investigating",
  "severity": "major",
  "message": "We are investigating increased response times.",
  "componentIds": ["abc123", "def456"]
}

Incident Templates

For recurring incident types, create templates to speed up incident creation. A template stores:

• Name — Template identifier (e.g., "Database failover")
• Title — Default incident title
• Severity — Default severity level
• Initial message — Pre-written first update
• Default components — Components typically affected

Create an incident from a template:

POST /api/v1/admin/incident-templates/:id/create-incident

You can override any field at creation time:

{
  "title": "Custom title override",
  "componentIds": ["specific-component"]
}

Auto-Incidents

Monitors can be configured to automatically create and resolve incidents:

• Create on failure — When the monitor's failure threshold is breached, an incident is created automatically with the monitor linked via triggeredByMonitorId
• Auto-resolve — When the monitor recovers, the auto-created incident is resolved automatically

Enable these per-monitor:

{
  "createIncidentOnFailure": true,
  "autoResolveIncident": true
}

See Uptime Monitoring for details on failure thresholds and recovery.

API Reference

See Admin Endpoints — Incidents for the full API.