Improve Session Replay integration with server rendered HTML pages

[bruno-garcia]

We're working on onboarding for backend project to include browser support. Similar to how we have NextJS, Remix, we want to onboarding for Laravel, ASP.NET, Django, Express, Spring, etc to include a snippet to be added to their html template. Enabling an experience to a single framework such as NextJS:

I was talking to @mydea and a few ideas came up:

• Tracing end to end
• Release from trace baggage (to make it easier to onboard with the loader, uses same release version as backend)
• If exception happens on the backend, we want to replay to sample.
  • Pass event_Id to the frontend so replay can send it. We could also define the replay_id on the backend so the error includes
    • Could be done by setting the replay_id on the baggage given by the BE to the FE when rendering
  • but for that to make sense we need the buffer to persist page loads
  • Needs: remove minFlushDelay
  • Keep last 30 seconds buffer for on error somehow?
    • Shared worker?
    • In the compression worker have an opt-in to store data in the worker in indexDB.

Also:

• sentry-replay_id= baggage header is not present when trace starts in the backend with SSR app #9756

[mydea]

ref: #9468

[bruno-garcia]

Set to p1 because we're improving onboarding for MPA this quarter

[bruno-garcia]

Realistically unlikely we'll tackle this in the next 2 months

[souredoutlook]

Something I think we can tackle now without adding features is maybe making a guide with Laravel (or similar) about how to wring the most out of Replay by re-throwing back end errors on the front end or cooking the baggage headers to get the traces tab to conform with the framework.

[ericemmrich]

Something I think we can tackle now without adding features is maybe making a guide with Laravel (or similar) about how to wring the most out of Replay by re-throwing back end errors on the front end or cooking the baggage headers to get the traces tab to conform with the framework.

That would already help a lot - thank you in advance!

[bruno-garcia]

Came up on Twitter too:

[mydea]

Side note, you can try setting up replay with this config:

replayIntegration({
  minReplayDuration: 0,
  flushMinDelay: 200,
  flushMaxDelay: 250,
})

To get an experience that is better suited for MPAs!

[mydea]

See: https://www.notion.so/sentry/Replay-for-Server-Side-Rendered-SSR-Applications-a203bcba705a4823a9c5fbaed551c9af (internal document tracking possible implementation paths for this)