Monitoring Errors and Slowdowns with a JS Frontend and Node Backend
summary
Demo shows a JS frontend talking to a Node (Express.js) backend with Sentry set up end to end: it surfaces a 500 error happening 45 times to 22 users, a separate inventory error recorded ~87,000 times, and a product endpoint slowdown where a backend HTTP call takes ~7.2s of a 7.8s transaction. The workflow includes Sentry SDK init, uploaded source maps and suspect commits, cross-project tracing from frontend to backend, and Slack alerts so the root cause gets found and fixed.
AI-written summary · about
related talks
08mMonitoring Errors and Slowdowns Across JS Applications
08mTrack Slowdowns and Crashes in your React apps
14mTracing: Frontend Issues With Backend Solutions
07mIdentify Issues and Prevent Slowdowns in your Vue.JS Apps
14mSpeed up fixing app issues using Sentry
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications
33mFrom “its broken” to “fix is out”
12mSolve 100% of your errors