Open bruno-garcia opened 8 months ago
Set to p1 because we're improving onboarding for MPA this quarter
Realistically unlikely we'll tackle this in the next 2 months
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.
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!
Came up on Twitter too:
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!
See: https://www.notion.so/sentry/Replay-for-Server-Side-Rendered-SSR-Applications-a203bcba705a4823a9c5fbaed551c9af (internal document tracking possible implementation paths for this)
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:
replay_id
on the backend so the error includesAlso: