incident-timeline-formatter
Turns rough incident notes into a stable Markdown timeline with impact and handoff shape intact.
What it does
The first useful run is a stable Markdown timeline that lets the team agree on sequence, impact changes, and handoffs before the deeper analysis starts. That alone removes a lot of review drag.
Try it locally
python3 incident_timeline_formatter.py sample_incident.jsonExample output
# Incident Timeline
- Events: 4
- Window: 2026-04-17 08:04 UTC to 2026-04-17 08:43 UTC
- Impact updates: 2
## Timeline
- 2026-04-17 08:04 UTC | API Gateway | Webhook retries start spiking for partner ingest. | status: signal | impact: Delayed order intake for one region.
- 2026-04-17 08:11 UTC | On-call | Confirms queue backlog and starts incident thread. | status: investigatingWhere it helps
Use this before an incident review, before sharing rough notes with another team, or anywhere the real blocker is that the event sequence still is not trustworthy enough to discuss cleanly.