open-telemetry/opentelemetry.io

The OpenTelemetry website and documentation

Hosted by OpenTelemetry · part of Cloud Native Computing Foundation

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

open-telemetry/opentelemetry.io has 950+ stars and 1.5k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Documentation / SpecificationCategory(s):Logging & TracingDocumentation ToolsDevOps & Observability
Added to GitGenius on October 12th, 2026
Created on April 29th, 2019
Open Issues & Pull Requests: 472 (+0)
GitHub issues: Enabled
Number of forks: 1,977
Total Stargazers: 984 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.9 hours
Mean response time: 35.3 days
90th percentile: 39.2 days
Tracked items: 1,173

Maintainer activity

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

At least 11% of opentelemetry.io's 45 maintainers work at Grafana Labs. 33 say where they work, and 5 of those are Grafana Labs.

OpenTelemetry owns this repository. 2 of its people did this work here, and are not included above.

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

About 5% of issues opened in the past year have never received a reply. 72% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "i18n" is answered fastest, typically in about 3 hours, while "lang:pt" waits about 29 hours. 54% of tracked open issues have had no activity in three months. 66% 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: 342
New in 7 days: 13
Closed in 7 days: 6
Avg open age: 458 days
Stale 30+ days: 288
Stale 90+ days: 255

Recent activity

Opened in 7 days: 13
Closed in 7 days: 6
Comments in 7 days: 32
Events in 7 days: 149

Top labels

  • CI/infra (249)
  • triage:accepted (242)
  • help wanted (152)
  • sig:collector (88)
  • docs (86)
  • lang:pt (76)
  • i18n (71)
  • good first issue (69)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OpenTelemetry.io is a documentation and website repository that serves as the central hub for the OpenTelemetry project.

The repository hosts the official OpenTelemetry website, project documentation, and blog content. It is built using Hugo and deployed on Netlify. The site functions as the primary entry point for users learning about OpenTelemetry, providing guides, API documentation, and community resources. The documentation is structured to help both newcomers and experienced users understand and implement OpenTelemetry's observability standards.

Developers should use this repository if they are contributing to OpenTelemetry's documentation or maintaining the project's web presence. The site is particularly valuable for those new to OpenTelemetry, as it serves as the first touchpoint for understanding the project's capabilities and getting started. The repository welcomes contributions from community members, especially from newcomers who can identify gaps or unclear sections in the documentation. Contributors can submit blog posts, fix documentation issues, and improve content clarity through the established contribution process.

The project maintains active community engagement through regular meetings held every two weeks, with notes documented publicly. The development activity shows structured governance with defined maintainer, approver, and triager roles across the community. The project operates with a formal contribution review process and maintains a security policy for handling vulnerabilities. Documentation contributions are guided by a style guide and contributor's guide to ensure consistency and quality across the site.