Sentry as a way not to be afraid
summary
Shows how Sentry captures real exceptions from a tiny Flask+SQLite app, reveals that a TypeError came from lists-of-lists via expanded stack-frame local variables, and demos a running self-hosted Sentry on my laptop using the official Docker image plus provided docker-compose and ansible files. Compares cloud vs self-hosted (reports can lag ~2–6 minutes on sentry.io), covers JavaScript breadcrumbs, grouped events, rate limits and notifications, and gives concrete examples where logs fail but Sentry pinpoints user input and third‑party failures.
AI-written summary · about
chapters (9)
- 0:00Introduction to Sentry
- 2:30Demonstrating application errors
- 6:10Analyzing errors with Sentry
- 10:01Debugging user-input issues
- 15:16Logs vs. Sentry monitoring
- 18:21Managing error notifications
- 22:10Deployment and installation
- 25:16Advanced usage cases
- 31:34Frontend integration and conclusion
related talks
14mSpeed up fixing app issues using Sentry
41mTroubleshooting Spring Boot applications with Sentry
13mCatching production errors before our customers
23mObserving your applications with Sentry and Prometheus
08mMonitoring Errors and Slowdowns Across JS Applications
26mVisualizing the Unseen to Fix Errors Faster with Sentry’s Session Replay Live
26mWhat's Next? The past, present, and future (All Dev, No Ops)
33mFrom “its broken” to “fix is out”