open-telemetry/opentelemetry-specification

Specifications for OpenTelemetry

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on March 6th, 2022
Created on May 1st, 2019
Open Issues & Pull Requests: 478 (+0)
Number of forks: 996
Total Stargazers: 4,322 (+0)
Total Subscribers: 151 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 hours
Mean response time: 165.6 days
90th percentile: 635.7 days
Tracked items: 934

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 54% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "area:sdk" is answered fastest, typically in under an hour, while "release:after-ga" waits about 4 days. 34% of tracked open issues have had no activity in three months. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 452
New in 7 days: 1
Closed in 7 days: 94
Avg open age: 1,279 days
Stale 30+ days: 133
Stale 90+ days: 68

Recent activity

Opened in 7 days: 0
Closed in 7 days: 94
Comments in 7 days: 115
Events in 7 days: 520

Top labels

  • spec:trace (407)
  • spec:metrics (381)
  • Stale (283)
  • spec:miscellaneous (251)
  • area:semantic-conventions (242)
  • area:sdk (199)
  • area:api (171)
  • sig-issue (160)

Detailed Description

The OpenTelemetry Specification repository serves as the authoritative cross-language specification document for all OpenTelemetry implementations. Hosted at opentelemetry.io/docs/specs/otel with Markdown sources maintained in the specification directory, this repository defines the requirements and expectations that guide how observability tools and libraries should implement OpenTelemetry across different programming languages and platforms. The specification covers critical areas including distributed tracing, metrics collection, logging, and the APIs and SDKs that enable these capabilities.

The repository is classified across multiple observability and standardization domains, including instrumentation, metrics, logging, APIs, telemetry, observability frameworks, distributed systems, performance monitoring, and distributed tracing. This broad classification reflects the specification's role as a foundational document that touches nearly every aspect of the OpenTelemetry ecosystem. The primary language used in the repository is Makefile, indicating that the specification is built and maintained through automated processes rather than being a traditional code repository.

This interconnection demonstrates how the specification serves as a central reference point for multiple implementation projects across the ecosystem.

The specification follows Semantic Versioning 2.0 for changes, with versions and descriptions documented in CHANGELOG.md. The repository includes a specification compliance matrix that tracks how different language implementations conform to the specification requirements. Development is organized through regular meetings held every Tuesday at 8 AM Pacific time for EU and US timezones, with additional APAC-friendly meetings available on request. Technical escalations are handled through the OpenTelemetry Technical Committee, which maintains meeting notes and oversees major specification decisions.

The project is governed by a Technical Committee that includes maintainers from major organizations, with Robert Pająk from Splunk and Josh Suereth from Google listed as primary maintainers. A broader set of specification sponsors from companies including Honeycomb, Dynatrace, Microsoft, Google, Oracle, and Grafana Labs serve as approvers. All contributions are licensed under the Apache 2.0 License, and the repository maintains detailed contribution guidelines in CONTRIBUTING.md that outline the process for proposing changes to the specification.