Refactor OTLP/HTTP section #2756
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make Binary and JSON encodings their own sections. This makes the spec easier to understand and also makes adding further clarifications to JSON easier. There are no functional changes. OTLP protocol behavior remains exactly the same. This is purely editorial change.
carlosalberto
approved these changes
Aug 30, 2022
jack-berg
approved these changes
Aug 30, 2022
|
Editorial, merging. |
MSNev
pushed a commit
to MSNev/opentelemetry-specification
that referenced
this pull request
Sep 6, 2022
Make Binary and JSON encodings their own sections. This makes the spec easier to understand and also makes adding further clarifications to JSON easier. There are no functional changes. OTLP protocol behavior remains exactly the same. This is purely editorial change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make Binary and JSON encodings their own sections.
This makes the spec easier to understand and also
makes adding further clarifications to JSON easier.
There are no functional changes. OTLP protocol behavior
remains exactly the same. This is purely editorial change.