Skip to main content

How do I link Session Replay to backend errors?

Issue

I want to know how to set up Session Replay so backend errors show up with my frontend replays.

Applies To

  • All SaaS Customers

  • Session Replay

  • Distributed Tracing

Resolution

Session Replay is still recorded in the browser. “Replays for backend errors” doesn’t record anything on the backend, it lets Sentry connect a frontend replay to a backend error when they’re part of the same distributed trace.

To set it up:

  1. Enable Session Replay on your frontend - the defaults are often replaysSessionSampleRate: 0.1 and replaysOnErrorSampleRate: 1.
    ​
    Keep in mind that replaysOnErrorSampleRate only kicks in for frontend errors, so you may want to adjust these rates in your frontend config. See Session Replay setup.
    ​

  2. Make sure your frontend and backend SDKs are up to date. Backend error linking requires specific minimum SDK versions, listed in Replays for Backend Errors. For example, JavaScript requires 7.51.0+ and Python requires 1.26.0+.
    ​

  3. Enable tracing on both the frontend and backend and make sure trace propagation is configured so API calls carry the trace across. On the frontend, this typically means setting tracePropagationTargets to include your API URLs.

Once that’s set up, you can find the linked replay in Replay Details or in the backend issue’s Replays tab.

If you’re still not seeing any replays linked to backend errors, please check I am not seeing Replays for my backend.

Related Articles
Did this answer your question?