OSS TanbouSign in with GitHub

Review the shared API and SDK contracts used across telemetry languages

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
4,346
Primary language
Makefile
License
Apache-2.0
Repository last updated
Oct 5, 2026
On this page

Overview

OpenTelemetry Specification is the documentation repository for language-neutral traces, metrics, logs, and related contracts. Implementers can review MUST versus SHOULD requirements, stability, and compatibility at a fixed release.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Define API and SDK responsibilities with normative terms

The Trace API defines the roles and required or recommended behavior of TracerProvider, Tracer, SpanContext, and Span. For example, a Tracer MUST provide creation of a new Span.

Sources: [1][2]

Best fit

Fit SDK implementation and instrumentation design review

It serves as a baseline when implementing a language SDK or reviewing whether an instrumentation API follows the common contract.

Sources: [1]

Before adoption

Pin the document release and per-signal stability

This repository is not an executable SDK. Record the adopted release, each document Status, and the meaning of MUST and SHOULD instead of following main implicitly.

Sources: [1][3]

Official sources

  1. [1]Specification README at v1.61.0(2026-10-05)
  2. [2]Trace API specification at v1.61.0(2026-10-05)
  3. [3]Specification LICENSE at v1.61.0(2026-10-05)
  4. [4]Specification v1.61.0 release(2026-10-05)
Supplemental curator note

Pin a release during implementation review and separate the Tracer MUST requirement from the Enabled SHOULD requirement to define the required surface accurately.

Try it in 3 steps

  1. 1

    Fetch specification v1.61.0

    Use Git to pin the implementation baseline at v1.61.0 and continue in otel-spec-review. This does not install an SDK.

    git clone --branch v1.61.0 --depth 1 https://github.com/open-telemetry/opentelemetry-specification.git otel-spec-review && cd otel-spec-review
  2. 2

    Extract the Tracer contract

    Extract the Tracer operations section from the Trace API document into tracer-contract.txt and require nonempty output.

    sed -n '/^### Tracer operations/,/^## SpanContext/p' specification/trace/api.md > tracer-contract.txt && test -s tracer-contract.txt
  3. 3

    Distinguish required and recommended behavior

    Assert separately that creating a new Span is MUST behavior while reporting Enabled is SHOULD behavior.

    grep -F 'The `Tracer` MUST provide functions to:' tracer-contract.txt && grep -F 'Create a new `Span`' tracer-contract.txt && grep -F 'The `Tracer` SHOULD provide functions to:' tracer-contract.txt && grep -F 'Report if `Tracer` is `Enabled`' tracer-contract.txt
Check the official README

Growth

Growth trends · Last 30 days

4,346 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
34
Open PRs
26
Issues opened
28
Issues closed
385
PRs opened
114
PRs merged
100

Issues

28 / 385

Jul 8Oct 5
Issues openedIssues closed

Pull requests

114 / 100

Jul 8Oct 5
PRs openedPRs merged

Maintenance

Median first response
27 hr
Issue response rate
33.3% (5/15)

Based on up to the 100 newest issues opened by external users in the last 90 days. A first comment from an OWNER, MEMBER, or COLLABORATOR counts as a response; issues whose full comment history cannot be checked are excluded. The median and response rate update weekly.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • opentelemetry
Stars
4,346
Forks
1,005
Watchers
151
Open issues
253
Contributors
318
Owner type
Organization
Primary language
Makefile
License
Apache-2.0
Repository last updated
Oct 5, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?