Solving the Drag of Technical Debt with Error Monitoring
summary
Company uses Bugsnag error monitoring to turn raw errors into a single stability score defined as the inverse of error rate (percentage of crash‑free user sessions), measured per release and per platform. Combines dynamic monitoring with static analysis and SLO/SLA thresholds (examples cited like “three nines” stability) so product work pauses when stability dips below the agreed line. Customers and the vendor use an on‑prem and cloud Bugsnag dashboard to delay shipping a board‑committed feature until stability improves.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:21Technical debt basics
- 6:53Emotional impact of tech debt
- 9:43Aligning teams on debt
- 12:14Measuring stability scores
- 16:34Using stability targets
- 19:44Key takeaways and Q&A
related talks
37mYour Software is Broken — Pay Attention
30mReliable Observability at Scale: Error Budgets for 1,000+
49mObservability in Practice: How to Become Proactive with Bugs
37mDriving App Reliability with Real Time Monitoring and SLIs
21mImprove quality by monitoring and observing
30mTechniques for SLOs and Error Budgets at Scale
28mProduction Testing Through Monitoring
13mBeyond observability: Using reliability scores to drive results