Skip to content

Improve Session Replay integration with server rendered HTML pages #9490

Description

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:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Package: replayIssues related to the Sentry Replay SDK

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions