OpenTelemetry Ecosystem Explorer

A catalog-and-conformance tool for the opentelemetry instrumentation ecosystem, at explorer.opentelemetry.io (source: github.com/open-telemetry/opentelemetry-ecosystem-explorer). Introduced in exploring-instrumentation-ecosystem. It exists because publishing a semantic convention does not by itself make instrumentation libraries emit it — the Explorer measures the gap instead of assuming it away.

What it does

• Catalogs components. Today: the OpenTelemetry Java agent and the Collector, each with per-version release comparisons; for Java, the telemetry and configuration options a given version actually exposes.
• Runs conformance checks. A companion project, semantic-conventions-conformance (github.com/open-telemetry/semantic-conventions-conformance), executes small scripted scenarios against real instrumentation libraries and validates the telemetry they emit using Weaver's live-check feature (github.com/open-telemetry/weaver). Results publish as JSON; the Explorer's tables read from them.
• Feeds from three sources: generated metadata (code gen off the library's own definitions), maintainer-written descriptions, and the runtime conformance results above. The Java catalog alone took the project "more than a year" to build out to full depth — this is ongoing maintainer labor, not a one-time scrape.

Weaver is a recommendation, not a requirement

Weaver defines telemetry schemas and runs the live-check that grades conformance, but the project's stated position is that other language ecosystems can participate in the Explorer using their own tooling and formats — Weaver is the OTel-native path, not a gate.

Status and edges

• Third-party (non-OTel) projects are a stated goal, not a shipped feature. An earlier attempt at an ecosystem registry found that listing a project's name doesn't say what it does; onboarding and acceptance criteria for a third-party conformance check are still open questions.
• A negative result is ambiguous by design. An attribute the Explorer never observed in a test run may still be one the instrumentation is capable of emitting under different configuration or application behavior — the tool measures observed conformance, not a library's theoretical ceiling.
• Concretely used already: the OTel Java SIG is tracking Explorer-measured HTTP attribute gaps toward a Java agent 3.0 release, gaps that survived the SIG's own 2.0 adoption of the stable HTTP semantic conventions.

Related

opentelemetry · semantic-conventions · exploring-instrumentation-ecosystem · otel-observability-primer · distributed-tracing