Solve 100% of your errors
summary
Sentry shows how to actually fix every error by pairing session replay with stack traces, network captures and traces so a 500 response becomes reproducible: a replay reveals a cart with four Pokémon and an invalid ID that caused simultaneous front‑ and back‑end errors. Default privacy‑by‑default scrubbing runs in the browser but opt‑in request/response bodies let engineers see the failing payload. A webpack plugin surfaces React‑aware breadcrumbs and produces hydration diffs and DOM inspect snapshots so visual and textual regressions are identified and traced to code locations.
AI-written summary · about
chapters (6)
- 0:00Introduction to debugging
- 1:07Debugging a network error
- 4:40Privacy and data scrubbing
- 5:41React-aware debugging
- 8:52Solving hydration errors
- 11:21Summary and call to action
related talks
26mVisualizing the Unseen to Fix Errors Faster with Sentry’s Session Replay Live
14mSpeed up fixing app issues using Sentry
48mProper Error Handling with React/Redux
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications
08mTrack Slowdowns and Crashes in your React apps
08mMonitoring Errors and Slowdowns Across JS Applications
15mInside Mobile Session Replay: Smarter Debugging
14mTracing: Frontend Issues With Backend Solutions