Skip to content

Conversation

@gggritso
Copy link
Member

@gggritso gggritso commented Aug 12, 2025

If the user has OTel-friendly UI enabled, update the logic that figures out which sibling spans should be collapsed. Since the labels for the spans use the op and name, the collapsing logic also needs to use op and name, rather than op and description.

Unfortunately, in order to check the feature flag, I had to pass organization through everywhere in the TraceTree class. There are so many call sites, and passing an organization in the options is pattern that already exists, so I followed it here, too.

One alternative is to do a shenanigan, and to fill the description field of a span with the name, and let everything else work the same, but that feels like it'll just cause more confusion.

More parts of the trace waterfall need access to the organization.
@linear
Copy link

linear bot commented Aug 12, 2025

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 12, 2025
@gggritso gggritso requested a review from Abdkhan14 August 12, 2025 20:01
@gggritso gggritso marked this pull request as ready for review August 12, 2025 20:01
@gggritso gggritso requested review from a team August 12, 2025 20:01
cursor[bot]

This comment was marked as outdated.

Copy link
Contributor

@Abdkhan14 Abdkhan14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets try this out, the organization thing is a bit icky but it's for a flag and we'll get rid of it eventually so it doesn't hurt as much

cursor[bot]

This comment was marked as outdated.

@gggritso gggritso merged commit 72f80ae into master Aug 15, 2025
46 checks passed
@gggritso gggritso deleted the georgegritsouk/ope-63-collapse-sibling-spans-based-on-spanname branch August 15, 2025 15:56
priscilawebdev pushed a commit that referenced this pull request Aug 25, 2025
If the user has OTel-friendly UI enabled, update the logic that figures
out which sibling spans should be collapsed. Since the _labels_ for the
spans use the op and name, the collapsing logic also needs to use op and
name, rather than op and description.

Unfortunately, in order to check the feature flag, I had to pass
`organization` through _everywhere_ in the `TraceTree` class. There are
so many call sites, and passing an `organization` in the options is
pattern that already exists, so I followed it here, too.

One alternative is to do a shenanigan, and to fill the `description`
field of a span with the name, and let everything else work the same,
but that feels like it'll just cause more confusion.
andrewshie-sentry pushed a commit that referenced this pull request Aug 26, 2025
If the user has OTel-friendly UI enabled, update the logic that figures
out which sibling spans should be collapsed. Since the _labels_ for the
spans use the op and name, the collapsing logic also needs to use op and
name, rather than op and description.

Unfortunately, in order to check the feature flag, I had to pass
`organization` through _everywhere_ in the `TraceTree` class. There are
so many call sites, and passing an `organization` in the options is
pattern that already exists, so I followed it here, too.

One alternative is to do a shenanigan, and to fill the `description`
field of a span with the name, and let everything else work the same,
but that feels like it'll just cause more confusion.
@github-actions github-actions bot locked and limited conversation to collaborators Aug 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants