Allow complex attributes on spans #2588
Merged
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
approved these changes
Aug 4, 2025
beeme1mr
approved these changes
Aug 4, 2025
github-project-automation
bot
moved this from Untriaged
to Needs More Approval
in Semantic Conventions Triage
lmolkova
moved this from Needs More Approval
to Ready to be Merged
in Semantic Conventions Triage
joaopgrassi
pushed a commit
to dynatrace-oss-contrib/semantic-conventions
that referenced
this pull request
Aug 18, 2025
ShipraJain01
pushed a commit
to ShipraJain01/semantic-conventions
that referenced
this pull request
Aug 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Following up on open-telemetry/opentelemetry-specification#4485, this PR relaxes
anyattribute usage on spans.We're actively experimenting with complex attributes in GenAI SIG #2179 where we have chat history recorded on spans or events.
While OTel implementations don't allow complex attributes on spans, we suggest to record them as JSON strings as a temporary workaround in unstable instrumentations.