opentelemetry-ecosystem-explorer

Discovering the OpenTelemetry ecosystem

The OpenTelemetry Ecosystem Explorer is a web application meant to help users discover and explore the various projects that make up the OpenTelemetry ecosystem. OpenTelemetry spans a large set of language SDKs, collectors, exporters, and instrumentation libraries, and the explorer exists to make that spread easier to navigate. The live site is hosted at explorer.opentelemetry.io, and the README ties the work back to a project proposal in the OpenTelemetry community repository. The problem it addresses is practical: a newcomer or even an experienced engineer can struggle to tell which project does what, which is maintained, and how the pieces relate. By centralizing metadata and presenting it through a browseable interface, the explorer reduces the guesswork of picking the right component for a given language or backend. The README keeps the description of the user facing goal brief and points readers to the site itself for the experience. What is notable is that this is not a vendor product but a community owned tool under the OpenTelemetry umbrella, so its purpose is to serve the whole ecosystem rather than promote one part of it. The framing as a discovery and exploration tool sets expectations: it is a map, not a runtime.

Three repository components

The repository is organized into three distinct components. The first is ecosystem-registry, described as a raw data registry that stores metadata from various projects and is updated nightly. That nightly refresh is what keeps the explorer current as new projects appear and old ones change status. The second is ecosystem-automation, the automation pipelines that extract metadata and build the database the site reads from. The third is ecosystem-explorer, the React and Vite web application that users actually interact with to explore the data. Splitting the work this way separates concerns cleanly: one part holds facts, one part gathers them, and one part presents them. The README points to component specific READMEs for the explorer and the automation, and to a general docs folder for project documentation. This structure also helps contributors, because someone who wants to fix a display bug stays in the explorer component while someone improving data collection works in automation. The choice of React with Vite for the front end is consistent with the broader OpenTelemetry web tooling, and the nightly registry update means the public site does not depend on manual edits to stay accurate. Keeping the registry, the automation, and the explorer separate makes each one easier to reason about and to test. A change to how data is gathered does not risk the user interface, and a front end tweak cannot corrupt the nightly data that the public site depends on.

Community and governance

The project runs under the umbrella of the OpenTelemetry Communications SIG, which is the group responsible for outreach and community material in the project. That SIG meets every two weeks on Tuesday at 9:00 AM Pacific Time, and the README points to the OpenTelemetry community calendar for the Zoom link and any schedule changes. Meeting notes are kept in a public Google document, so decisions are visible after the fact. Day to day conversation happens in Slack, specifically the channels for the explorer and for communications, reached through the CNCF Slack. The maintainer list names Jay DeLuca of Grafana Labs, Severin Neumann of Causely, and Vitor Vasconcellos, with Marylia Gutierrez and Luca Cavenaghi listed as approvers, and Pablo Baeyens noted as emeritus. Linking maintainer roles to the OpenTelemetry community membership guide gives contributors a clear picture of how responsibility is assigned and earned. The governance details matter because the explorer aggregates information about other projects, so it helps to know who stewards it and how to reach them. The README closes its people section by pointing to the community repository for the meaning of maintainer and approver roles. Naming the maintainers and their employers gives users a clear point of contact when something is wrong. Because the work sits under a SIG with a public calendar and notes, the explorer's direction is visible to anyone rather than decided in a private channel.

Editorial conclusion

The explorer is an Apache-2.0 licensed TypeScript project run under the OpenTelemetry Communications SIG, with the live site at explorer.opentelemetry.io.