ref(traces): Prefer transaction over span.name for trace naming#110708
Open
ref(traces): Prefer transaction over span.name for trace naming#110708
Conversation
Query the transaction column in the EAP enrichment query and use it as the trace name when present, falling back to span.name. This provides more accurate names for Sentry SDK transaction spans while preserving OTel span naming. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Backend
Member
Author
|
@sentry review |
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.
#107543 addressed issues with OTel spans in Explore's Trace Samples tab, but it caused a worse experience for some Sentry SDK spans (see #109629).
This PR additionally queries
transactionin the trace samples query and uses it as the trace name when present, falling back tospan.name. This should give us the best of both worlds, bringing back the more descriptivetransactionvalues for Sentry SDK users while falling back for OTel span wheretransactionis blank.Fixes #109629.