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

Jump to bottom

Clarify that 64 bit integer numbers are decimal strings in OTLP/JSON #1637

Merged
merged 3 commits into from
Apr 27, 2021
Merged

Clarify that 64 bit integer numbers are decimal strings in OTLP/JSON #1637

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
61d7643
Clarify that 64 bit integer numbers are decimal strings in OTLP/JSON
tigrannajaryan Apr 22, 2021
bf02c7d
Merge branch 'main' into feature/tigran/otlp-json
bogdandrutu Apr 27, 2021
0b48250
Merge branch 'main' into feature/tigran/otlp-json
tigrannajaryan Apr 27, 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
5 changes: 5 additions & 0 deletions specification/protocol/otlp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,6 +363,11 @@ they are not base64-encoded like it is defined in the standard
The hex encoding is used for `trace_id` and `span_id` fields in all OTLP
Protobuf messages, e.g. the `Span`, `Link`, `LogRecord`, etc. messages.

Note that according to [Protobuf specs](
https://developers.google.com/protocol-buffers/docs/proto3#json) 64-bit integer
numbers in JSON-encoded payloads are encoded as decimal strings, and either
numbers or strings are accepted when decoding.

#### OTLP/HTTP Response

Response body MUST be the appropriate serialized Protobuf message (see below for
Expand Down