Mobile Observability at scale
summary
Focuses on real time mobile observability (not post hoc analytics) and shows concrete practices: report response parsing errors with endpoint URL and exception attributes, alert when spikes exceed 50 errors in 15 minutes, use a lightweight proxy collector to drop noisy floods, and set clear SLOs like 99.9% sessions zero crashes with owned alerts via codeowners. Scales to 10–20+ teams by standardizing metrics, aligning with backend events and enforcing single-team ownership for each endpoint.
AI-written summary · about
chapters (8)
- 0:00Introduction to mobile observability
- 3:57Why mobile observability matters
- 9:19Choosing what to measure
- 15:56Alerting and automation
- 19:24Handling incidents effectively
- 25:18Scaling observability across teams
- 30:50Future of mobile observability
- 33:16Next steps and key takeaways
related talks
33mEffective observability in microservice architectures
29mObservability; a gentle introduction
20mIntroduction to Observability on Mobile
17m“How’s the App Doing?” Bringing Mobile Into Your Reliability Picture
38mThe Murphy's Laws of Observability
48mAPI Observability by Design: Building Systems That Tell Their Own Stories
39mActionable Observability
40mSurvivability of Observability: Taking your DIY system to success