Zero Error Policy: Discovering Errors Faster Than Users
summary
Covers the Zero Error Policy for web apps: a process where every runtime error is detected by monitoring, analyzed by the team, and fixed when needed. Explains practical steps for frontend projects to reduce monitoring noise, improve error handling in code, and configure effective notifications so monitoring actually helps detect new post-release bugs and respond to user issues.
AI-written summary · about
chapters (19)
- 0:00Zero Error Policy intro
- 5:24Monitoring errors problem
- 6:31What is Zero Error Policy
- 8:37Error noise in streams
- 10:25Software vs operational errors
- 13:37Tagging network errors
- 16:29Filtering extension errors
- 18:17Unsupported browser errors
- 20:25Diagnosable error messages
- 21:48Missing stack traces
- 24:17Script Error fixes
- 26:49Source Map debugging
- 28:14Debugging online scripts
- 31:03Error logging completeness
- 32:06Linting error handling
- 33:10Logging library errors
- 34:13Alert setup
- 39:08Zero Error Policy results
- 40:12Q&A
related talks
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications
38mThe Design of Error
28mHow to get to zero unhandled exceptions in production
39mZero Touch Prod: Towards Safer and More Secure Production Environments
45mZero-Sales Lost — Incident Management
53mObservable Web Applications
52mPerformance & Stability Anti patterns
30mReliable Observability at Scale: Error Budgets for 1,000+