Skip to content

Conversation

mjq
Copy link
Member

@mjq mjq commented Oct 8, 2025

If a span name isn't present (e.g. for spans from a transaction), we generate one - the final fallback being to duplicate the span op. In the trace view, rather than show duplicated information when the op and name match, fallback to the description (which typically contains more information).

If a span name isn't present (e.g. for spans from a transaction), we generate
one - the final fallback being to duplicate the span `op`. In the trace view,
rather than show duplicated information when the `op` and `name` match,
fallback to the description (which typically contains more information).
@mjq mjq requested a review from gggritso October 8, 2025 20:46
@mjq mjq requested a review from a team as a code owner October 8, 2025 20:46
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 8, 2025
@mjq mjq requested a review from gggritso October 8, 2025 20:57
@mjq
Copy link
Member Author

mjq commented Oct 8, 2025

@gggritso Thanks George - made one more change so that the More Samples button takes you to the appropriate search. Still looking okay?

@gggritso
Copy link
Member

gggritso commented Oct 8, 2025

@mjq 🚢

@mjq mjq enabled auto-merge (squash) October 8, 2025 21:06
@mjq mjq merged commit eeef3a2 into master Oct 8, 2025
46 checks passed
@mjq mjq deleted the mjq/improve-otlp-spans-in-traces branch October 8, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants