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
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 ...
Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...
Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...
Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...
If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...
In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...