Posts Observability with OpenTelemetry Part 6 - Ecosystem

Observability with OpenTelemetry Part 6 - Ecosystem

The past five articles have covered the technical details on how to work with OpenTelemetry to observe your applications. I think there’s a lot of value in finishing up this blog post series with some information on the OTel ecosystem. There is a lot happening with OpenTelemetry, and those that are new to it might be slightly overwhelmed or confused where to find certain things.

As discussed previously, OpenTelemetry is a CNCF project. But, how does it stack up? Measured by pull requests, issues, and commits OpenTelemetry is the second most active CNCF project, behind only Kubernetes:

OTel growth

Image and data source (twitter)

This is a really exciting time to dive into the world of OpenTelemetry. Hopefully it is obvious now, but I believe that OpenTelemetry is here to stay and will serve a significant role in the cloud native ecosystem.

Project site

The first place to start with OpenTelemetry is the project site: Here you’ll find a wealth of information and a good index for a lot of the ecosystem. Here you’ll also find some great “Getting Started” documentation to start familiarizing yourself with OTel and how to implement it in your software.

One part of the OpenTelemetry site worth keeping an eye on is the project blog. Here you’ll find a lot of updates and announcements.

Generally speaking, if you’re new to OpenTelemetry I highly recommend you spend some time poking around the project site.


If there’s one thing that this blog post series has highlighted, OTel has a large featureset. And with these capabilities oftentimes comes with some level of complexity. At some point, you may need assistance from the community. I have found that the best way to chat with members the community (including maintainers!) is through the CNCF Slack workspace. OpenTelemetry has a handful of channels that might interest you. The main one is #opentelemetry, which is the general discussion. There’s a chance you want to be part of more specific conversations, though. Here are some other OTel channels:

  • #otel-collector - All things OpenTelemetry Collector
  • #otel-go - OpenTelemetry Go (API, SDK, implementation)
  • #otel-python - OpenTelemetry Python (API, SDK, implementation)

And a few more! Search for #otel in Slack to see other OpenTelemetry channels.

This could be part of the next section, but it’s worth a callout here. The community repository has a lot of great information, such as: Governance, areas of interest, meetings and calendars, and much more. If you’re looking at getting involved in OTel, this is a great place to start.


I have to admit, one of the more confusing things to me when I was getting started with OpenTelemetry is how the GitHub repositories were organized.

The primary components of OpenTelemetry (not language or collector specific) can be found in these repositories:

OTel Collector repositories are:

A huge part of OTel is the language-specific instrumentation. Here is a sample that explains how they are organized in the project:

This is the general pattern for language implementations, but they can vary. For instance, Java has open-telemetry/opentelemetry-java, but also open-telemetry/opentelemetry-java-contrib for extensions but a separate repo for auto instrumentation with open-telemetry/opentelemetry-java-instrumentation.


The final part of the ecosystem that I think should be noted is the OpenTelemetry Registry. Because of the wide array of implementations and products in the project, this is a great way to search through everything to see what is available for your requirement.


OpenTelemetry is a great project that provides a way to implement a high level of observability within the software that we develop. Through the usage of OTel, we’re able to have maximized insights and answer future questions without having to make any code changes. I highly recommend you dive into the wonderful world of OpenTelemetry! Once you do, you’ll never want to go without it!

This post is licensed under CC BY 4.0 by the author.