Skip to content

Commit

Permalink
Declare OTLP stable (open-telemetry#3274)
Browse files Browse the repository at this point in the history
  • Loading branch information
jonatan-ivanov authored and lmolkova committed Mar 8, 2023
1 parent 7208924 commit 9f5c94b
Showing 1 changed file with 1 addition and 19 deletions.
20 changes: 1 addition & 19 deletions specification/protocol/otlp.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# OpenTelemetry Protocol Specification

**Status**: [Mixed](../document-status.md)
**Status**: [Stable](../document-status.md)

The OpenTelemetry Protocol (OTLP) specification describes the encoding, transport,
and delivery mechanism of telemetry data between telemetry sources, intermediate
Expand All @@ -11,7 +11,6 @@ nodes such as collectors and telemetry backends.

<!-- toc -->

- [Signals Maturity Level](#signals-maturity-level)
- [Protocol Details](#protocol-details)
* [OTLP/gRPC](#otlpgrpc)
+ [OTLP/gRPC Concurrent Requests](#otlpgrpc-concurrent-requests)
Expand Down Expand Up @@ -52,17 +51,6 @@ nodes such as collectors and telemetry backends.
OTLP is a general-purpose telemetry data delivery protocol designed in the scope
of the OpenTelemetry project.

## Signals Maturity Level

Each signal has different support and stability in OTLP, described through its
own maturity level, which in turn applies to **all** the OTLP Transports listed below.

* Tracing: **Stable**
* Metrics: **Stable**
* Logs: **Stable**

See [OTLP Maturity Level](https://github.com/open-telemetry/opentelemetry-proto#maturity-level).

## Protocol Details

OTLP defines the encoding of telemetry data and the protocol used to exchange
Expand All @@ -84,8 +72,6 @@ All server components MUST support the following transport compression options:

### OTLP/gRPC

**Status**: [Stable](../document-status.md)

After establishing the underlying gRPC transport, the client starts sending
telemetry data using unary requests using
[Export*ServiceRequest](https://github.com/open-telemetry/opentelemetry-proto)
Expand Down Expand Up @@ -391,8 +377,6 @@ connection cannot be established.

#### Binary Protobuf Encoding

**Status**: [Stable](../document-status.md)

Binary Protobuf encoded payloads use proto3
[encoding standard](https://developers.google.com/protocol-buffers/docs/encoding).

Expand All @@ -401,8 +385,6 @@ request and response headers when sending binary Protobuf encoded payload.

#### JSON Protobuf Encoding

**Status**: [Stable](../document-status.md)

JSON Protobuf encoded payloads use proto3 standard defined
[JSON Mapping](https://developers.google.com/protocol-buffers/docs/proto3#json)
for mapping between Protobuf and JSON, with the following deviations from that mapping:
Expand Down

0 comments on commit 9f5c94b

Please sign in to comment.