OpenTelemetry spec implementation offering both a native implementation and a compatibility façade over the Java SDK, with tracing, logging, and API/noop instrumentation modules.
An implementation of the OpenTelemetry specification as a Kotlin Multiplatform Library.
Please read the docs to get started.
| Platform | Tier | Tests run in CI | Example app | Production use | Notes |
|---|---|---|---|---|---|
| JVM | 1 | ✅ | ✅ | ✅ | Heavily tested and supported for production use. |
| Android (API 21+) | 1 | ✅ | ✅ | ✅ | Heavily tested and supported for production use. |
| iOS | 2 | ❌ | ✅ | ❌ | Compiles. |
| tvOS | 2 | ❌ | ❌ | ❌ | Compiles. |
| JS | 2 | ✅ | ✅ | ❌ | Compiles. |
| Linux (x64 and ARM64) | 2 | ✅ | ❌ | ❌ | Compiles. |
Tier 1 targets are best-supported for production use. Tier 2 targets compile and pass shared tests, but have received limited real-world testing. Support may be dropped for targets if their maintenance burden becomes too great.
Interested in adding support for another platform? See adding a new target.
Example usage of the library can be found here.
Got feedback or found a bug? Please open a GitHub issue and we'll get back to you.
Read our roadmap here.
We are currently resource constrained and are actively seeking new contributors interested in working towards approver / maintainer roles. In addition to the documentation for approver / maintainer roles and the contributing guide, here are some additional notes on engaging:
The SIG meeting is open for all to join. We invite everyone to join our meeting, regardless of your experience level. Whether you're a seasoned OpenTelemetry contributor, just starting your journey, or simply curious about the work we do, you're more than welcome to participate!
Ongoing contributions are formally acknowledged via OpenTelemetry's membership levels. Generally the maintainers will reach out and offer a specific role after seeing evidence of continued contributions that match a given role. However, do feel free to contact the maintainers if you think you already meet the requirements, or if you want guidance on doing so.
For more information about the maintainer role, see the community repository.
For more information about the approver role, see the community repository.
For more information about the triager role, see the community repository.
An implementation of the OpenTelemetry specification as a Kotlin Multiplatform Library.
Please read the docs to get started.
| Platform | Tier | Tests run in CI | Example app | Production use | Notes |
|---|---|---|---|---|---|
| JVM | 1 | ✅ | ✅ | ✅ | Heavily tested and supported for production use. |
| Android (API 21+) | 1 | ✅ | ✅ | ✅ | Heavily tested and supported for production use. |
| iOS | 2 | ❌ | ✅ | ❌ | Compiles. |
| tvOS | 2 | ❌ | ❌ | ❌ | Compiles. |
| JS | 2 | ✅ | ✅ | ❌ | Compiles. |
| Linux (x64 and ARM64) | 2 | ✅ | ❌ | ❌ | Compiles. |
Tier 1 targets are best-supported for production use. Tier 2 targets compile and pass shared tests, but have received limited real-world testing. Support may be dropped for targets if their maintenance burden becomes too great.
Interested in adding support for another platform? See adding a new target.
Example usage of the library can be found here.
Got feedback or found a bug? Please open a GitHub issue and we'll get back to you.
Read our roadmap here.
We are currently resource constrained and are actively seeking new contributors interested in working towards approver / maintainer roles. In addition to the documentation for approver / maintainer roles and the contributing guide, here are some additional notes on engaging:
The SIG meeting is open for all to join. We invite everyone to join our meeting, regardless of your experience level. Whether you're a seasoned OpenTelemetry contributor, just starting your journey, or simply curious about the work we do, you're more than welcome to participate!
Ongoing contributions are formally acknowledged via OpenTelemetry's membership levels. Generally the maintainers will reach out and offer a specific role after seeing evidence of continued contributions that match a given role. However, do feel free to contact the maintainers if you think you already meet the requirements, or if you want guidance on doing so.
For more information about the maintainer role, see the community repository.
For more information about the approver role, see the community repository.
For more information about the triager role, see the community repository.
