Recorded events
How to read the timeline
- Names, not identifiers. The timeline is written for humans: it records the name of the person involved.
- Action source. Actions performed by people can record where they came from — web dashboard, email, Slack or Microsoft Teams.
- System actions have no author. Automatic escalation, auto-resolution and automatic closure show up as system actions.
Notification audit
Next to the timeline, the Audit tab lists every notification sent for the incident: channel, status, attempts, time and the transition that originated it (trigger, acknowledgement, assignment, escalation or resolution). Sends to shared channels (Slack, Teams, Discord and Telegram) appear in the Organization channels section. When the on-screen alert shows up in someone’s open dashboard, the audit records Alert shown.A push delivery means the provider accepted the message, not that it was read. Email and chat channels do not confirm reading either.
What it is for day to day
Shift handover
Whoever takes over on-call reads the timeline and understands the state without asking.
Post-mortem
Time to first acknowledgement and time to resolution come straight out of the record.
Configuration diagnosis
Frequent escalations or recurring fallbacks point at a short schedule or a service with no team.
Audit
Who acknowledged, who took it, who resolved it — with date and time.
Older incidents may show timeline messages using legacy wording. Operational history is never rewritten — that is expected, not a bug.