Session replay overview

Session replay gives responders a timeline of user activity around an error or incident. Use it when stack traces and logs explain what failed but not what the user did before the failure.

What replay is for

• Confirm the user path that led to a frontend or request error.
• See clicks, navigation, console events, and timing around the failure.
• Attach user-experience evidence to incident investigation.
• Separate one-off user behavior from repeatable product defects.

Enable replay

Open project settings and review the Session Replay panel. Enable capture only after the project has appropriate privacy rules and the team understands what replay evidence may include.

Find replays

Replays appear from error groups and incidents when session evidence is linked to the failure. Open the replay section from the error or incident detail, then select a session to inspect the timeline.

Read a session

Start at the moment nearest the error. Look backward for the user's path and forward for retries, reloads, or recovery. Combine replay observations with stack traces, logs, and deploy context before assigning root cause.

Privacy controls

Replay evidence can be sensitive. Review redaction and MCP exposure settings before making replay data available broadly.

• Disable session exposure for repair agents unless replay evidence is needed.
• Redact fields and values that can appear in captured context.
• Limit project access to teams that need to investigate user sessions.

Triage with replay

1. Open the error group or incident with linked sessions.
2. Review the stack trace and event time first.
3. Open the matching replay and inspect the user actions before the error.
4. Add replay findings to the incident summary or linked issue.
5. Resolve the group only after the replay path no longer reproduces the failure.