Replay
Watch what led to a ticket, across all the services of its project.
A ticket says what failed. A replay shows how the system got there: your stored log lines arrive in order, service by service, up to the moment the error appeared. It shows the evidence and leaves the conclusion to you. Nothing is filtered, summarized or interpreted.
Open a replay
On a ticket's page, choose Replay. The replay opens 15 minutes before the ticket, in the ticket's environment. 5 min earlier moves back in steps, up to 24 hours before the ticket and never past your plan's retention. Up to 5 minutes after the ticket can be read; playback stops at the ticket first, and Play goes on.
The timeline
Each service has one row on a shared time axis. Bars show how many lines arrived, and the strip under a bar shows the worst level of that moment. Services with warnings or errors come first; the rest fold under N quiet services. The dashed line is the ticket, and diamonds are the project's other tickets. A stretch of a row with no bars means no lines arrived. Hatching means the lines cannot be there: time that was not stored, lines that were lost, or lines still being written.
Click or drag on the timeline to move. Click a service to keep only its lines. Space plays or pauses, and the arrow keys move the cursor.
What a replay can show
Replay shows only what was stored:
- Being written. Lines are written every 5 minutes on Free and every 2 minutes on paid plans, so the last minutes of a new ticket arrive shortly after it.
- History starts here. Time before a project's first stored line was not stored. It is not silence.
- Some lines are missing here. If lines could not be stored, the replay says how many and when.
- Context lines only. A ticket from before the history started, or whose lines are past retention, offers the lines stored with the ticket instead.
Lines are stored after redaction, so IP addresses appear as <ip>, and each message is cut at 2 KiB. trace and debug lines appear only if you send them: SDKs default to minLevel: info.
Turn it off
Admins can turn off Keep log history per project: see Projects and API keys.
API
Read the same data with GET /v1/tickets/{ticket_id}/replay, .../replay/timeline and .../replay/lines. Requests may answer 422 replay-window, 429 replay-busy or 503 archive-unavailable.