rfc(decision): Make Sentry Semantic Conversions Mandatory in SDKs#147
Closed
antonpirker wants to merge 3 commits into
Closed
rfc(decision): Make Sentry Semantic Conversions Mandatory in SDKs#147antonpirker wants to merge 3 commits into
antonpirker wants to merge 3 commits into
Conversation
antonpirker
force-pushed
the
rfc/make-sentry-semantic-conversions-mandatory-in-sd-ks
branch
from
ab2f81c to
4e0ed42
Compare
Contributor
Author
|
As |
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
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.
We should make sure, that it is hard to add span attributes that are not listed in our Semantic Conversions.
This should make it impossible to just randomly add attributes that are not documented anywhere.
Rendered RFC