Embrace announced that the donation of its Kotlin implementation and SDK to OpenTelemetry has been accepted.
This contribution expands vendor-neutral observability support across client and server-side applications written in Kotlin.
OpenTelemetry is an incubating Cloud Native Computing Foundation (CNCF) project developed by end users, open source contributors, and vendors to advance interoperable, portable observability standards. Kotlin is the default language for modern Android development, and Kotlin Multiplatform (KMP) is increasingly used to share code across Android, iOS, web, and server-side applications. This contribution enhances OpenTelemetry’s reach to Kotlin and KMP use cases, enabling teams to capture telemetry in a way that better aligns with user-facing applications.
“OpenTelemetry is becoming the global foundation for observability, and meaningful contributions to that foundation matter,” said Andrew Tunall, President and Chief Product Officer at Embrace. “With Kotlin now central to mobile, frontend, and backend development, and with growing community investment in client-side observability, this is an exciting moment for the ecosystem. We’re proud to donate a Kotlin Multiplatform implementation that supports production-ready, real-world engineering workflows.”
Enabling client-side observability for Kotlin and KMP
The implementation can be used for backend development needs, and it also introduces new support for client-side environments like mobile and web. Client-side environments present unique observability challenges, requiring teams to understand not just whether an application is functioning, but how end-users experience workflows and why outcomes change in production.
While Kotlin applications running on the Java Virtual Machine (JVM) can use OpenTelemetry through Java interoperability, teams building shared logic with Kotlin Multiplatform often require a solution that operates without JVM dependencies. The contributed implementation addresses these needs while remaining aligned with OpenTelemetry’s specification-driven approach. It supports two modes of operation:
- Compatibility mode, which interoperates with the OpenTelemetry Java SDK for Android and JVM targets. This enables engineering teams to leverage existing instrumentation built by the JVM community.
- Regular mode, which is a re-write of the OTel spec in Kotlin. This can be used for both JVM and non-JVM targets.
At the time of contribution, the project includes tracing and logging APIs, providing a foundation for modeling user workflows and correlating events across platforms.
Community stewardship and ecosystem impact
Embrace will continue to contribute and maintain the implementation alongside the broader OpenTelemetry community and encourages additional contributors to participate.
“The real power of OpenTelemetry is the standard itself – a shared contract that allows many implementations to evolve and serve different environments,” said Jamie Lynch, Senior Software Engineer at Embrace and a Maintainer of the OpenTelemetry Kotlin project. “By contributing a Kotlin Multiplatform implementation, we’re investing in a future where frontend teams can build observability on the same open foundations as the backend, while meeting the realities of modern app development.”
Developers interested in using or contributing to the OpenTelemetry Kotlin Multiplatform implementation can:
- Access the project on GitHub: https://github.com/open-telemetry/opentelemetry-kotlin
- Learn more about the Kotlin SIG: https://opentelemetry.io/community
- Join the conversation in the #otel-kotlin channel in the CNCF Slack: https://slack.cncf.io/
- Read more about the process and rationale for this contribution on the official CNCF blog
Hot Topic
The Latest
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...
40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...
Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...
Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...
Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...
Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...