Skip to content

docs(replay): add Trace Linking section #16199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sfanahata merged 2 commits into from
Feb 2, 2026
+20 −0
Merged

docs(replay): add Trace Linking section #16199

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b81f7fe
docs(replay): add Trace Linking section parallel to Error Linking
Jan 28, 2026
29c29f2
docs(tracing): add Replay Linking section for bidirectional navigation
Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/platforms/javascript/common/session-replay/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,14 @@ Errors that happen on the page while a replay is running will be linked to the r
- The replay was deleted by a member of your org.
- There were network errors and the replay wasn't saved.

## Trace Linking

When [tracing](/product/explore/traces/) is enabled, traces are visible in the Replay timeline. This lets you see performance data in the context of what the user was doing — you can watch a user click a button, then see the corresponding network request and how long it took.

From the Replay Details page, click on any trace span in the timeline to jump directly to the trace view. From there, you can drill into individual spans, see database queries, API calls, and identify performance bottlenecks that affected the user's experience.

This connection works both ways: when viewing a trace, you can jump to the associated replay to see exactly what the user experienced during that operation.

## Verify

While you're testing, we recommend that you set <PlatformIdentifier name="replays-session-sample-rate" /> to `1.0`. This ensures that every user session will be sent to Sentry.
Expand Down
12 changes: 12 additions & 0 deletions docs/platforms/javascript/common/tracing/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,18 @@ You can also manually start spans to instrument specific parts of your code. Thi
- <PlatformLink to="/tracing/span-metrics/">Sending Span Metrics</PlatformLink>:
Learn how to capture metrics on your spans

<PlatformSection notSupported={["javascript.node", "javascript.aws-lambda", "javascript.azure-functions", "javascript.connect", "javascript.express", "javascript.fastify", "javascript.gcp-functions", "javascript.hapi", "javascript.hono", "javascript.koa", "javascript.nestjs", "javascript.bun", "javascript.deno", "javascript.cloudflare", "javascript.cordova", "javascript.wasm"]}>

## Replay Linking

When [Session Replay](/product/explore/session-replay/) is enabled, traces appear in the Replay timeline. This lets you correlate performance data with exactly what the user was seeing and doing.

From any trace, click the replay link to jump directly to the replay and see the user's experience during that operation. From a replay, click any trace span in the timeline to drill into performance details.

This bidirectional linking helps you understand not just *how long* something took, but *what impact* it had on the user's experience.

</PlatformSection>

## Disabling Tracing

If you want to disable tracing, you _should not_ set `tracesSampleRate` at
Expand Down