API Endpoints — Incidents¶

Incident management for tracking and resolving issues.

List Incidents¶

GET /api/incidents

Query: status (open/acknowledged/resolved), severity, application_id, limit, cursor

Create Incident¶

POST /api/incidents

Body:

{
  "title": "Database connection pool exhausted",
  "application_id": "uuid",
  "severity": "P1",
  "template_id": "42",
  "root_cause": "Database connection pool exhaustion"
}

Auto-creation: AI Insights engine auto-creates pending incidents for P1 templates.

Update Incident¶

PATCH /api/incidents/{incident_id}

Body:

{
  "status": "acknowledged",
  "assignee_id": "uuid",
  "resolution_notes": "Increased max_connections to 200"
}

Status Flow: open → acknowledged → resolved → closed

Incident Fields¶

Field	Type	Description
`id`	UUID	Primary key
`title`	str	Human-readable title
`application_id`	UUID	FK → applications
`severity`	str	P1–P4
`status`	str	open/acknowledged/resolved/closed
`opened_at`	datetime	Creation time
`acknowledged_at`	datetime	When acknowledged
`resolved_at`	datetime	When resolved
`mttd_seconds`	int	Mean Time To Detect
`mtta_seconds`	int	Mean Time To Acknowledge
`mttr_seconds`	int	Mean Time To Resolve
`template_id`	str	Link to Drain3 template
`ai_insight_id`	UUID	Link to generating insight