Observability of your app in production
summary
Advocates setting up observability as soon as the app hits users, arguing that Crashlytics, Performance Monitoring, Analytics from Firebase get you running free and fast, and that ticking the export to Play Store vitals to BigQuery lets you query historical crashes and events. Emphasizes structured logs with metadata like structured logs with commit hashes so you can tie a crash to an exact build. Cites a Play Services outage that left teams blind without device logs and describes a graceful-degrade system that switches to a webview during backend failures.
AI-written summary · about
chapters (10)
- 0:00Introduction to observability
- 1:14What is observability?
- 3:18Bread and butter of observability
- 8:54Unstructured vs structured logging
- 13:04Feature flags and graceful degradation
- 14:28When to implement observability
- 17:58Firebase for observability
- 21:27Advanced observability tools
- 23:50Now what with observability data
- 24:53SRE practices for mobile apps
related talks
44mEfficient Android app monitoring
27mBuilding Observability into Your iOS App Platform
20mHow is your app actually doing in production
29mObservability for Developers: How to Get From Here to There
53mCheck your app's vitals
30mImprove app performance and stability with Firebase
55mBuilding Quality with Firebase
29mCrash-reporting taken to next-level