Client-side observability is a different ocean than backend. Unlike servers, mobile and web apps must account for OS kills, crashes, long-running user sessions, asynchronous telemetry, flaky networking connectivity, activity that spans multiple tabs and lifecycle boundaries, device fragmentation, and so much more.
In this panel discussion with key members of the Android, Kotlin, Java, and Browser SIGs, we’ll check the surf on client-side support in OpenTelemetry. Topics include:
- Today's conditions: Why client-side apps break OTel's backend assumptions, and why that impacts the data model and semantic conventions for mobile and web.
- Current wave: What's actually shipped across Android, Kotlin, and the browser, and where they are in terms of stability.
- Rip currents: What the key challenges are, including modeling sessions and crashes, async telemetry, client-side metrics, and data modeling differences between mobile and browser.
- Next swell: Where Android, Kotlin, and browser OTel are headed over the next year.
We want to hear from you! Send us your questions about OpenTelemetry for mobile and web, including the improvements you want to see, and we’ll dive into them in the panel discussion or during our Q&A section.
