Playing Ahead: Fixing Bugs, Preventing Collapse
summary
Plesk describes building an in-house error-reporting system (their own “Sentry”) to collect and fix PHP errors, detect unexpected cases and environment issues, and embed continuous error analysis into QA. The talk covers preventing errors reaching releases, keeping an error inventory to guide product development, and using monitoring to manage updates and quickly ship fixes.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:12Customer churn problem
- 3:46Fatal error analysis and collapse
- 5:12Error handling workflow issues
- 7:45Error system requirements
- 9:08Custom tracker development
- 10:31Goal: releases without new bugs
- 12:20Error grouping and noise reduction
- 15:11Error monitoring and quarantine
- 16:59Error stats by builds
- 18:27Environment and updates control
- 21:37Dev vs. bugfix balance
- 24:32On-call procedure and inventory
- 26:21Collapse prevention scenarios
- 28:10Results and error reduction
- 30:16Custom tracker architecture and benefits
- 31:03Conclusions and recommendations
- 31:45Q&A
related talks
49mObservability in Practice: How to Become Proactive with Bugs
37mYour Software is Broken — Pay Attention
33mFrom “its broken” to “fix is out”
52mPerformance & Stability Anti patterns
51mVersion Control tips, tricks and good citizenship
13mCatching production errors before our customers
14mTracing: Frontend Issues With Backend Solutions
06mLightning Talk: Keeping the Show Running: Backstage Maintenance from a Platform Eng...