Monitoring Errors and Slowdowns Across JS Applications
summary
Sentry ties frontend and backend traces together with the Sentry SDK and shows human readable stack traces because of uploaded source maps the system fires a Slack alert for a 500 error that happens 160 occurrences affecting 60 users and surfaces a performance issue with LCP 10.6s (total transaction 11.1s) pointing to a 10.5s HTTP client step and sequential DB queries; release health shows 84% crash free with 7% adoption so teams can assign ownership and fix the concrete failure modes.
AI-written summary · about
chapters (4)
related talks
08mMonitoring Errors and Slowdowns with a JS Frontend and Node Backend
07mIdentify Issues and Prevent Slowdowns in your Vue.JS Apps
08mTrack Slowdowns and Crashes in your React apps
14mTracing: Frontend Issues With Backend Solutions
14mSpeed up fixing app issues using Sentry
33mFrom “its broken” to “fix is out”
12mSolve 100% of your errors
41mTroubleshooting Spring Boot applications with Sentry