Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Declare OTLP stable #3274

Merged
merged 3 commits into from
Mar 8, 2023
Merged

Declare OTLP stable #3274

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
63abbc5
Declare OTLP stable
jonatan-ivanov Mar 2, 2023
89dea51
Merge branch 'main' into declare-otlp-stable
reyang Mar 7, 2023
6c92be7
Merge branch 'main' into declare-otlp-stable
reyang Mar 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 1 addition & 19 deletions specification/protocol/otlp.md
View file
Open in desktop
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