The mission of OpenTelemetry is to enable effective observability by making high-quality, portable telemetry ubiquitous. In other words, observability should be built in into the software you develop.
While external instrumentation through zero code instrumentation solutions and instrumentation libraries provide a convenient way to make your application observable, we believe that ultimately all applications should either integrate the OpenTelemetry APIs and SDKs directly for native telemetry, or provide a first-party plugin that fits into the ecosystem of the given software.
This page contains a sample of libraries, services, and apps providing native instrumentation or first class plugins.
Native library instrumentation with OpenTelemetry provides better observability and developer experience for users, removing the need for libraries to expose and document hooks. Below you will find a list of libraries that use the OpenTelemetry API to provide out of the box observability.
The following list contains a sample of libraries, services, and apps that have either integrated OpenTelemetry APIs and SDKs directly for native telemetry or provide a first-party plugin that fits into their own extensibility ecosystem.
Open source projects (OSS) are at the beginning of the list, and commercial projects follow. Projects which are part of the CNCF have a CNCF logo beside their name.
To have your library, service, or app listed, submit a PR with an entry added to the registry. The entry should include the following:
If you provide external integration of OpenTelemetry for any kind of library, service, or app, then consider adding it to the registry.
If you adopt OpenTelemetry for Observability as an end user and do not provide any kind of services around OpenTelemetry, see Adopters.
If you provide a solution that consumes OpenTelemetry to offer observability to end users, see Vendors.
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!