open-telemetry/semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains

Hosted by OpenTelemetry · part of Cloud Native Computing Foundation

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

open-telemetry/semantic-conventions has 650+ stars and 400+ forks on GitHub, is written in Jinja, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 37 minutes ago
Type:Documentation / SpecificationCategory(s):Observability & MonitoringLogging & TracingDevOps & Observability
Added to GitGenius on October 12th, 2026
Created on May 9th, 2023
Open Issues & Pull Requests: 765 (+0)
GitHub issues: Enabled
Number of forks: 400
Total Stargazers: 672 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.2 hours
Mean response time: 30.3 days
90th percentile: 71.1 days
Tracked items: 951

Maintainer activity

29 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

Roughly one issue in three opened in the past year never receives a reply. 63% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "tooling" is answered fastest, typically in under an hour, while "area:rpc" waits about 13 days. 60% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 49% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 599
New in 7 days: 13
Closed in 7 days: 5
Avg open age: 544 days
Stale 30+ days: 530
Stale 90+ days: 455

Recent activity

Opened in 7 days: 10
Closed in 7 days: 4
Comments in 7 days: 19
Events in 7 days: 67

Top labels

  • triage:needs-triage (515)
  • enhancement (283)
  • experts needed (131)
  • area:k8s (87)
  • triage:accepted:ready (83)
  • bug (78)
  • triage:accepted:ready-with-sig (62)
  • area:db (60)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OpenTelemetry Semantic Conventions is a standards specification that defines a common set of attributes for generating consistent, accessible telemetry across a variety of domains.

The project addresses the problem of inconsistent naming and meaning of telemetry data across different systems and instrumentation libraries. It solves this by establishing a shared vocabulary of semantic attributes that provide meaning to observability data when collecting, producing, and consuming it. The conventions are defined in YAML files within a model directory, and human-readable documentation is generated from these definitions and maintained in a docs folder.

Teams building observability solutions, instrumentation libraries, or telemetry collection systems should adopt these conventions to ensure their data is interoperable with the broader OpenTelemetry ecosystem. The project suits any organization instrumenting applications or infrastructure that wants to follow established standards rather than inventing custom attribute naming schemes. This is particularly valuable for vendors and tool builders who need their telemetry to work seamlessly across different platforms and consumers.

The project operates with explicit prioritization of roadmap initiatives, and contributions outside those areas may experience delays or rejection unless formally added through the project proposal process. Development activity is structured around special interest groups organized by domain areas, with a defined governance model including maintainers, approvers, and a community contribution process documented in the repository.