Visualizing the Unseen to Fix Errors Faster with Sentry’s Session Replay Live
summary
Sentry’s Session Replay records DOM diffs (a fork of rrweb) and ties each recording to tracing IDs so you see the front end UI and the backend trace together, including breadcrumbs, web vitals, console and network (request bodies stripped by default). Recording has two modes — 100% error sampling plus configurable regular sampling (e.g. 10%) — and the hosted free plan gives 50 free replays. Mobile replays use screenshots, text and images are masked by default, and self‑hosting removes quotas.
AI-written summary · about
chapters (16)
- 0:00Sentry and session replay intro
- 1:48Session replay setup
- 3:58Linking replay to errors
- 5:01Human element in replays
- 7:58Mobile replay privacy
- 9:22Privacy controls
- 10:26Self-hosting Sentry
- 12:30Replay performance impact
- 13:58DOM inspection in replays
- 14:41Replay limits
- 15:44Sentry vs OpenTelemetry
- 18:59Maintaining self-hosted Sentry
- 21:26Tracing in modern architectures
- 23:33Monitoring React Native & Flutter
- 24:15Frontend vs backend errors
- 25:19Closing & Q&A
related talks
15mInside Mobile Session Replay: Smarter Debugging
19mSolve your Mobile Bugs with Session Replay
12mSolve 100% of your errors
09mSession Replay
26mLogging, and Errors, and Metrics Oh My!
33mFrom “its broken” to “fix is out”
08mMonitoring Errors and Slowdowns Across JS Applications
14mTracing: Frontend Issues With Backend Solutions