Product Reliability in
summary
Shift from server signals to instrumentation of UI journeys, tracing with Proto on Android, and automated availability/latency/data quality checks tied into change supervision (pauses rollouts and blocks bad feature ramps). Built assertions on anonymized visual-element logs and preprod AI-generated tests, added near‑real‑time alerts, and ran a code yellow that stopped recurring annual zero‑results outages. Result: earlier detection, fewer users hit, lower cost to fix, and measurable ties to engagement and retention.
AI-written summary · about
chapters (17)
- 0:00User impact in reliability
- 1:08Speaker background and team context
- 2:12Server-side monitoring limits
- 3:15Business impact of outages
- 4:38User-centric reliability journey
- 5:21Gaps in change supervision and alerts
- 6:48Measuring user experience with 3 signals
- 7:53Monitoring availability visually
- 8:57Tracking latency with traces
- 10:03Data quality in microservices
- 11:08Change supervision for user feedback
- 12:52Real-time monitoring beyond rollouts
- 13:15Case study: preventing search outages
- 14:41Integration with feature delivery
- 15:44Scaling user-centric reliability
- 16:46Future of AI-powered reliability
- 17:27Call to action for user-centric reliability
related talks
17mScaling End to End Reliability Tracking Across Large Scale, Multiplexed Products and Services
13mBeyond observability: Using reliability scores to drive results
25mElevating Android App Resilience: Incident Management Strategies
27mContinuous Reliability. How?
25mProduct Reliability for Google Maps
31mObservability driven development
48mBuild Trust with Your Users Workshop
24mBeyond Regression Testing: Observability for QA