!
Reliability
Incident Management
Lightweight incidents: open, acknowledge, resolve, with timeline + comments.
▸ How it works
Incidents are first-class. Alerts can auto-open one and link the firing alert event. Manual incidents can be opened from any chart or finding. Each incident has assignees, severity, status, comments, attached artefacts (logs, traces, screenshots), and an immutable timeline of actions. On resolution, MTTR is computed and rolled into per-service SLO scores.
▸ What this lets you do
- ✓ One place to coordinate during a fire — chat, evidence, action items
- ✓ Auto-link alerts to incidents so the postmortem writes itself
- ✓ MTTR / MTBF tracked per service automatically
- ✓ Public-facing status page (optional) reads from `severity≥major` incidents
▸ Get it running
- 1 Open `Incidents` → `+ New incident`, or let an alert auto-open one
- 2 Assign, comment, attach evidence
- 3 Resolve when fixed — timeline export to PDF for postmortems
▸ Code examples
curl -X POST https://funnel.example.com/v1/incidents \
-H "Authorization: Bearer st_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Checkout latency spike",
"severity": "major",
"service": "checkout",
"summary": "p95 > 1s for 5 min",
"assignees": ["[email protected]"]
}'
Where to find it
/app/p/:org/:project/incidents