[Prototype] How to support complex attributes in logs/events? (Option B) #6959
Conversation
This file contains hidden or 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
trask
commented
Dec 16, 2024
| // TODO(jack-berg): Should this be a JSON encoding? | ||
| String asString(); | ||
|
|
||
| static ValueBuilder builder() { |
There was a problem hiding this comment.
this is specifically for building "maps"
another option is in #6761 that has separate map and list builders:
|
Closing in favor of #6983 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prototype for open-telemetry/opentelemetry-specification#4334
See also
Looking for feedback from @open-telemetry/java-approvers on whether evolving in this way seems reasonable, or if there is a different approach you would prefer in order to support complex attributes on logs/events.