OpenTelemetry is vast. The Java agent alone includes over 240 different auto-instrumentations. The Collector has hundreds of components. Python, JavaScript, Go, and .NET each have their own ecosystems of instrumentation libraries, each with its own patterns and conventions.
In our 2025 Developer Experience Survey, users said that “documentation is difficult to navigate, requiring users to switch between the OpenTelemetry website and GitHub repositories” and that they often have to “piece together information from various sources.” Only about half of users rely on opentelemetry.io as their primary resource; the rest turn to GitHub, vendor documentation, or wherever they can find answers.

OpenTelemetry's platform is an observability framework, offering insights into distributed tracing, metrics collection, and log management for cloud-native applications. Through documentation, tutorials, and community contributions, OpenTelemetry provides insights into instrumenting applications to monitor performance and troubleshoot issues. Developers and DevOps teams can learn about distributed tracing standards, telemetry data formats, and integration with observability tools to gain visibility into complex distributed systems.

OpenTelemetry

OpenTelemetry has launched the Ecosystem Explorer, a new site at explorer.opentelemetry.io that maps what telemetry signals (spans, metrics, attributes) each instrumentation library actually emits. The Java agent ecosystem is the first fully mapped area, with over 240 auto-instrumentations indexed, searchable, and tracked across versions with nightly automation. Future plans include Collector components, Python, JavaScript, and GenAI/LLM instrumentation. The project is open for contributors across research, Python data pipelines, React/TypeScript frontend work, and UX design.

Introducing the Ecosystem Explorer Project

<p>OpenTelemetry: the only tool where you need observability… to observe your observability.</p>
