feat(eap): add span.name field alias
#89254
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
Sentry's new span schema is aligning with OTel, introducing `name` as the top level field by which a span's operation is identified. This effectively replaces `op` in Sentry's current data model. Add `span.name` as a secondary alias for the underlying `sentry.op` field. I considered trying to put this field behind a feature flag, but the blast radius is pretty large since this field is currently a constant that is transformed into several other constants, all of which would have to become dynamic. Adding it as a secondary alias means it shouldn't yet show up anywhere unless a user explicity tries to use it. We might start conditionally using it in the frontend behind a feature flag. Eventually, `span.op` will become the secondary alias, for backwards compatibility.
github-actions
bot
added
the
Scope: Backend
0Calories
approved these changes
Apr 10, 2025
andrewshie-sentry
pushed a commit
that referenced
this pull request
Apr 22, 2025
Sentry's new span schema is aligning with OTel, introducing `name` as the top level field by which a span's operation is identified. This effectively replaces `op` in Sentry's current data model. Add `span.name` as a secondary alias for the underlying `sentry.op` field. I considered trying to put this field behind a feature flag, but the blast radius is pretty large since this field is currently a constant that is transformed into several other constants, all of which would have to become dynamic. Adding it as a secondary alias means it shouldn't yet show up anywhere unless a user explicity tries to use it. We might start conditionally using it in the frontend behind a feature flag. Eventually, `span.op` will become the secondary alias, for backwards compatibility.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
Sentry's new span schema is aligning with OTel, introducing
nameas the top level field by which a span's operation is identified. This effectively replacesopin Sentry's current data model.Add
span.nameas a secondary alias for the underlyingsentry.opfield.I considered trying to put this field behind a feature flag, but the blast radius is pretty large since this field is currently a constant that is transformed into several other constants, all of which would have to become dynamic. Adding it as a secondary alias means it shouldn't yet show up anywhere unless a user explicity tries to use it. We might start conditionally using it in the frontend behind a feature flag.
Eventually,
span.opwill become the secondary alias, for backwards compatibility.