Scaling End to End Reliability Tracking Across Large Scale, Multiplexed Products and Services
summary
A vertical, product-centered reliability system federates metric ownership to product teams and measures user-facing failures by HTTP response code and error rate per endpoint instead of top-volume errors. Responsibility-based triage assigns regressions to endpoint (client) owners to evaluate user impact; many root causes trace to the web tier. Results include a ~300% alert threshold change that detects incidents about one day earlier, a 0.215% lift in iOS monthly engaged business, 9% fewer Android requests, and >90% faster Android photo/video data paths.
AI-written summary · about
chapters (8)
- 0:00End-to-end reliability at Meta
- 3:15User issue categorization
- 6:49Mobile to web Federation
- 8:17Web Federation principles
- 11:27Improvements and user experience optimizations
- 12:34Horizontal vs vertical reliability
- 14:43Bug report reduction
- 15:26Future Federation challenges
related talks
18mProduct Reliability in
13mBeyond observability: Using reliability scores to drive results
45mMobile App Reliability: What It Is and How to Achieve It
17m“How’s the App Doing?” Bringing Mobile Into Your Reliability Picture
35mMobile Observability at scale
40mWhy Is My App SLOw? Defining Reliability in Platform Engineering
15mShit, our Site is Down! Let's build a culture of reliability
49mScaling Reliability: So You Want to Add a 9