Incident Timeline Builder
A chronological incident timeline ready for the post-mortem — events with timestamps and impact.
More from Business
What you get
A chronological incident timeline in a markdown table format, including time, event, impact, and source.
Who it's for
- DevOps engineers investigating outages
- Incident managers writing post-mortem reports
- IT directors analysing system failures
- Technical writers documenting error timelines
Use cases
- Creating a post-mortem report after a major system outage
- Investigating a security breach and its impact on the system
- Documenting a series of errors that led to a service disruption
- Analysing a spike in errors during a deployment
- Reconstructing a timeline of events after a data loss incident
FAQ
what format is the incident timeline in
The incident timeline is delivered in a markdown table format, with columns for Time, Event, Impact, and Source. This format is easy to read and integrate into your post-mortem reports.
how much does the incident timeline builder cost
The Incident Timeline Builder costs £1.00, providing a cost-effective solution for creating a chronological timeline of events.
what information do i need to provide to get the timeline
You need to provide the incident name and a raw events log, which can include data from sources like Slack, alerts, and deploys, with timestamps.
are the times in the timeline rounded
Yes, the times in the timeline are rounded to the minute, providing a clear and concise view of the events.
Sample output
The incident involved a 5xx spike on payments, which was detected and alerted at 09:14, leading to a series of events to resolve the issue. The issue was eventually resolved after a deploy rollback, with errors clearing at 09:30. | Time (UTC) | Event | Impact | Source | | --- | --- | --- | --- | | 09:14 | 5xx spike on payments | 100% of payment writes failing | PagerDuty alert | | 09:18 | Oncall paged | Notification of incident | PagerDuty | | 09:22 | Deploy 1f4a rolled back | Potential fix for 5xx spike | Deployment logs | | 09:30 | Errors clear | Resolution of 5xx spike | Error monitoring |
Last updated: 2026-06-28