-
Notifications
You must be signed in to change notification settings - Fork 897
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.
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
Fix examples and the link in experimental JSON file format #2886
Merged
tigrannajaryan
merged 2 commits into
open-telemetry:main
from
tigrannajaryan:feature/tigran/fix-json-file
Nov 3, 2022
Merged
Fix examples and the link in experimental JSON file format #2886
tigrannajaryan
merged 2 commits into
open-telemetry:main
from
tigrannajaryan:feature/tigran/fix-json-file
Nov 3, 2022
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
Member
tigrannajaryan
commented
Oct 17, 2022
- The severityNumber field is an enum and must use a numeric value according this: Prohibit usage of enum value name strings in OTLP/JSON #2758
- Link to a more appropriate section of otlp.md doc.
reyang
approved these changes
Oct 17, 2022
carlosalberto
approved these changes
Oct 24, 2022
bogdandrutu
approved these changes
Oct 25, 2022
jack-berg
approved these changes
Oct 25, 2022
Good to go @tigrannajaryan but we need a rebase ;) |
@tigrannajaryan please rebase |
bogdandrutu
reviewed
Nov 1, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also fix "AGGREGATION_TEMPORALITY_*" and probably span status/kind.
tigrannajaryan
force-pushed
the
feature/tigran/fix-json-file
branch
from
November 2, 2022 20:37
2124d24
to
f2d03d2
Compare
- The severityNumber field is an enum and must use a numeric value according this: open-telemetry#2758 - Link to a more appropriate section of otlp.md doc.
- Remove deprecatedCode - Use numeric value for status code
tigrannajaryan
force-pushed
the
feature/tigran/fix-json-file
branch
from
November 2, 2022 21:21
1eefa48
to
d9ca31b
Compare
Done. |
lmolkova
pushed a commit
to lmolkova/opentelemetry-specification
that referenced
this pull request
Nov 3, 2022
…metry#2886) - The severityNumber field is an enum and must use a numeric value according this: open-telemetry#2758 - Link to a more appropriate section of otlp.md doc. - Remove deprecatedCode - Use numeric value for status code
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
…metry#2886) - The severityNumber field is an enum and must use a numeric value according this: open-telemetry#2758 - Link to a more appropriate section of otlp.md doc. - Remove deprecatedCode - Use numeric value for status code
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.