open-telemetry/community

OpenTelemetry community content

Hosted by OpenTelemetry · part of Cloud Native Computing Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

open-telemetry/community has 1k+ stars and 300+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Curated List / Learning ResourceCategory(s):Observability & MonitoringLogging & TracingDevOps & Observability
Added to GitGenius on October 12th, 2026
Created on May 2nd, 2019
Open Issues & Pull Requests: 158 (+0)
GitHub issues: Enabled
Number of forks: 323
Total Stargazers: 1,151 (+0)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.0 hours
Mean response time: 7.6 days
90th percentile: 6.1 days
Tracked items: 879

Maintainer activity

17 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. Only 26% of open issues come from outside the core team — the tracker reads mainly as internal planning. Work labelled "area/github-membership" is answered fastest, typically in under an hour, while "triage:accepted" waits about 35 hours. 45% of tracked open issues have had no activity in three months. 84% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 119
New in 7 days: 12
Closed in 7 days: 12
Avg open age: 423 days
Stale 30+ days: 95
Stale 90+ days: 72

Recent activity

Opened in 7 days: 12
Closed in 7 days: 12
Comments in 7 days: 23
Events in 7 days: 95

Top labels

  • area/github-membership (347)
  • area/repo-maintenance (158)
  • area/project-infra (50)
  • triage:accepted (39)
  • area/gc-election (21)
  • triage:deciding (17)
  • area/donation (12)
  • Stale (11)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OpenTelemetry community is a community governance and coordination hub for an open-source observability project.

The project addresses the need for organized collaboration across a distributed community working on standardized observability instrumentation and tooling. It provides structure through governing bodies, special interest groups organized by specification, implementation, and cross-cutting concerns, and communication channels that enable contributors to coordinate work and make decisions transparently.

Developers should engage with this repository if they want to contribute to OpenTelemetry's core specifications, language implementations, or ecosystem tools. It suits organizations building observability solutions that need to align with community standards or those seeking to influence the direction of distributed tracing and metrics standards. The project explicitly welcomes new contributors through dedicated Slack channels and a contributor guide, making it accessible to those unfamiliar with the community's processes.

The project maintains active governance through two committees with publicly available meeting notes and recordings. Special interest groups operate across multiple technical domains with documented membership and areas of interest. Communication infrastructure includes dedicated Slack channels, a published calendar of meetings, and mailing lists to support asynchronous participation across time zones.