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
Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...