Challenge Accepted: Scoping Errors in “Multi-App” Environment
summary
Explains a concrete solution for noisy multi‑app error streams: introduce arrow boundaries that tag execution scopes, catch sync and promise rejections, and attach scope to reports; route thousands of user‑code errors differently from product errors. Shows implementation details using Sentry and a Raven transport override to capture reports locally and asserts on payloads in tests instead of a proxy server. Describes the Raven test kit, testing strategy, and how this reduces monitoring noise.
AI-written summary · about
chapters (8)
- 0:00Error reporting in multi-app
- 4:09Error reporting and UX
- 7:25User-generated code errors
- 11:45Arrow Boundaries for error scoping
- 14:15Testing Arrow Boundaries with TDD
- 17:07Intercepting error reports
- 21:45Raven Test Kit benefits
- 23:32Q&A
related talks
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications
12mSolve 100% of your errors
36mThe Arcane Art of Error Handling
50mRedemption from Callback Hell
08mMonitoring Errors and Slowdowns Across JS Applications
32mShattering your application into an umbrella project
16mProgressive Delivery with Observability
27mSchrödinger's Error: Living In the grey area of Exceptions