A short guide to Incident Timeline Generator
Turn scattered facts into a useful handoff.
Turn timestamped notes and logs into a clean incident timeline with gaps called out. Here is the practical way to prepare the input, read the output, and decide what to check next.
01
When to reach for it
Parses ISO timestamped event lines, sorts the accepted events by time, and reports the resulting timeline. It is most useful when you are dealing with unclear incident or missing timeline. Start with the smallest example that still shows the behavior.
- Look for unclear incident, missing timeline, postmortem prep.
- Reduce the example until one observation can change the result.
02
How to prepare the input
Paste a focused example in one timestamped event per line. Leave out unrelated noise so the result stays easy to verify.
- Use the accepted format: one timestamped event per line.
- Keep the facts that make the behavior reproducible.
- Do not treat missing context as a reason to invent an answer.
Example input
Safe sample
2026-08-04T10:00:00Z deploy started 2026-08-04T10:04:00Z error rate increased 2026-08-04T10:12:00Z rollback completed
Run this first to see the shape of the result. Then change one meaningful fact and confirm that the output changes with it.
03
How to read the result
Returns the accepted events in chronological order with a next check. Read the finding beside the evidence that produced it. The result narrows the next check; it does not claim to have changed your system.
- Separate the observed fact from the suggested next check.
- Prefer the smallest reversible experiment that can confirm or reject the finding.
- Save the output when it belongs in an incident note, review, or handoff.
04
Know the boundary
The report organizes the facts you provide; it does not execute a rollback, deployment, or incident action.