Skip to content

open-telemetry/opentelemetry-specification

This branch is up to date with main.

Folders and files

NameName
Last commit message
Last commit date
Dec 6, 2024
Mar 1, 2023
Feb 10, 2025
May 12, 2023
Feb 10, 2025
May 9, 2023
Feb 13, 2025
Oct 3, 2023
Nov 26, 2020
Oct 9, 2024
Jan 24, 2025
Jul 19, 2021
Mar 4, 2022
Jul 15, 2021
Feb 13, 2025
Dec 17, 2024
May 1, 2019
Jan 6, 2025
May 14, 2024
Nov 23, 2024
Mar 12, 2024
Feb 13, 2025

Repository files navigation

OpenTelemetry Specification

Checks GitHub tag (latest SemVer)

OpenTelemetry Logo

The OpenTelemetry specification describes the cross-language requirements and expectations for all OpenTelemetry implementations.

Change / contribution process

For details, see CONTRIBUTING.md, in particular read Proposing a change before submitting a PR.

Questions

Questions that need additional attention can be brought to the regular specifications meeting. EU and US timezone friendly meeting is held every Tuesday at 8 AM Pacific time. Meeting notes are held in the Google doc. APAC timezone friendly meetings are held on request. See OpenTelemetry calendar.

Escalations to technical committee may be made over the e-mail. Technical committee holds regular meetings, notes are held here.

Specification compliance matrix by language

See Compliance of Implementations with Specification.

Project Timeline

The current project status as well as information on notable past releases is found at the OpenTelemetry project page.

Information about current work and future development plans is found at the specification development milestones.

Versioning the Specification

Changes to the specification are versioned according to Semantic Versioning 2.0 and described in CHANGELOG.md. Layout changes are not versioned. Specific implementations of the specification should specify which version they implement.

Changes to the change process itself are not currently versioned but may be independently versioned in the future.

License

By contributing to OpenTelemetry Specification repository, you agree that your contributions will be licensed under its Apache 2.0 License.