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

OTLP stability clarifications #1400

Merged
merged 7 commits into from
Feb 5, 2021
Merged

OTLP stability clarifications #1400

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
72600f5
Tiny clarification on OTLP/HTTP Formats status.
carlosalberto Feb 4, 2021
98c4a69
Details about different signals stability.
carlosalberto Feb 4, 2021
8ecfb52
Fix format.
carlosalberto Feb 4, 2021
3ab08d8
Merge branch 'main' into otlp_stability_clarifications
carlosalberto Feb 4, 2021
7f5a31b
Improve.
carlosalberto Feb 4, 2021
2a144cf
Remove unnecesary mention of the gRPC transport.
carlosalberto Feb 5, 2021
47c56fd
Update CHANGELOG.
carlosalberto Feb 5, 2021
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
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,8 @@ Updates:
- Modify OTLP/Zipkin Exporter format variables for 1.0 (allowing further specification post 1.0)
([#1358](https://github.com/open-telemetry/opentelemetry-specification/pull/1358))
- Add `k8s.node` semantic conventions ([#1390](https://github.com/open-telemetry/opentelemetry-specification/pull/1390))
- Clarify stability for both OTLP/HTTP and signals in OTLP.
([#1400](https://github.com/open-telemetry/opentelemetry-specification/pull/1400/files))

## v0.7.0 (11-18-2020)

Expand Down
15 changes: 14 additions & 1 deletion specification/protocol/otlp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ nodes such as collectors and telemetry backends.
Table of Contents
</summary>

- [Signals Maturity Level](#signals-maturity-level)
- [Protocol Details](#protocol-details)
* [OTLP/gRPC](#otlpgrpc)
+ [OTLP/gRPC Concurrent Requests](#otlpgrpc-concurrent-requests)
Expand Down Expand Up @@ -44,6 +45,17 @@ Table of Contents
OTLP is a general-purpose telemetry data delivery protocol designed in the scope
of 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: **Beta**
* Logs: **Alpha**

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 Down Expand Up @@ -301,7 +313,8 @@ The default network port for OTLP/gRPC is 4317.

### OTLP/HTTP

**Status**: [Experimental](../document-status.md)
**Binary Format Status**: [Stable](../document-status.md)
**JSON Format Status**: [Experimental](../document-status.md)
carlosalberto marked this conversation as resolved.
Show resolved Hide resolved

OTLP/HTTP uses Protobuf payloads encoded either in binary format or in JSON
format. The Protobuf schema of the messages is the same for OTLP/HTTP and
Expand Down