Lazy Robots: Telemetry Buffering on Android
summary
OpenTelemetry Android adds a disk-buffering layer that serializes telemetry to internal storage as Protobuf files, creating per-signal folders and honoring FIFO via timestamped filenames. A pair of exporters — to-disk exporters and from-disk exporters — write every ~10 seconds and retry upload when app runs, sending to backends like Jaeger. Demo shows traces buffered during airplane mode and fully ingested afterward with no gaps; feature is young and needs tuning for throttling and adaptive cache.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Client-side observability challenges
- 3:37Telemetry buffering solution
- 7:56Disk storage and reads
- 10:44Battery and data balance
- 11:06Live demo
- 16:24Results and benefits
- 17:07Future features and call to action
related talks
42mOpenTelemetry on Android: From black box to X‑Ray
18mOpenTelemetry for Mobile Apps: Challenges and Opportunities in Data Mob...
40mDebugging Android Performance at Scale: Lessons from Building Datadog's Mobile Profiler
26mBuild-Time Auto-Instrumentation in Android
40mAndroid high performance baby
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
39mDeep-Diving Android Performance with Perfetto
38mA Busy Android App Developers' Guide to Perfetto