List view
Get the metrics data model and protocol (OTLP) to [“Stable”](https://github.com/open-telemetry/opentelemetry-specification/blob/1afab39e5658f807315abf2f3256809293bfd421/specification/versioning-and-stability.md#stable). This means people can use OTLP as an exchange format for metrics.
Due by March 31, 2021•1/3 issues closedMetrics API/SDK specification reaches [“Stable”](https://github.com/open-telemetry/opentelemetry-specification/blob/9047c91412d3d4b7f28b0f7346d8c5034b509849/specification/versioning-and-stability.md#stable). Together with the stable version of the specification, we should expect release candidates from multiple language clients, similar to what we had for tracing. Depending on the actual progress, the API specification might reach Stable earlier than the SDK. **11/09/2021** * Metrics API specification reaches Stable. * Language clients can release RC or stable versions of the API package depending on their progress. **11/30/2021** * Metrics SDK specification reaches Stable. * Language clients can release RC or stable versions of the SDK package depending on their progress.
Due by November 30, 2021•39/39 issues closedMetrics API/SDK specification reaches [“Feature-freeze”](https://github.com/open-telemetry/opentelemetry-specification/blob/1afab39e5658f807315abf2f3256809293bfd421/specification/document-status.md#feature-freeze). After feature-freeze, we will focus on bug fixes or editorial changes. **7/31/2021** * Metrics API specification reaches Feature-freeze. * Expect prerelease API and SDK packages from several language clients (e.g. Golang, Java, .NET, Python). **10/31/2021** * Metrics SDK specification reaches Feature-freeze.
Due by October 30, 2021•40/40 issues closedMetrics API [“Experimental”](https://github.com/open-telemetry/opentelemetry-specification/blob/1afab39e5658f807315abf2f3256809293bfd421/specification/versioning-and-stability.md#experimental) version is already released as part of the [Specification 1.4 release](https://github.com/open-telemetry/opentelemetry-specification/releases/tag/v1.4.0). The Metrics SDK specification Experimental version is targeting **8/31/2021**, the actual release happened on **9/14/2021**. Language clients are expected to start working on the API implementation. We recommend language client maintainers to start the implement the SDK once the SDK specification reaches Experimental.
Due by September 14, 2021•19/19 issues closed- Due by July 31, 2020•1/1 issues closed
- Due by July 1, 2020•34/43 issues closed
Move the date because we want to make the metrics in.
Due by May 12, 2020•26/26 issues closed- Due by June 1, 2020•15/15 issues closed
The spirit of v0.3 release is to deliver a product with the stable, almost the release candidate level of APIs and interfaces. After the v0.3 release of language SDKs we do expect that languages public surface may change, but we do not expect any major changes in conceptual level in specifications.
Due by February 8, 2020•65/65 issues closedThe spirit of this release is to have a demo-able product that anybody can start playing with and start implementing instrumentation adaptors and data collectors for various scenarios. As part of this release we ask to implement Tracing and Metrics exporters so it will be easy to visualize the scenarios. For Tracing - either Jaeger or Zipkin can be selected, for Metrics - Prometheus.
Due by October 4, 2019•21/21 issues closed- Due by October 8, 2020•8/12 issues closed
First draft of the OpenTelemetry API specification, based on the first version of OpenTelemetry-Java.
Due by June 21, 2019•27/27 issues closed