Open sentryadam0000345 opened 4 months ago
Routing to @getsentry/product-owners-performance for triage ⏲️
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-performance for triage ⏲️
Discussion in Jira for now.
Closing! See discussion in Jira and Notion 👍🏻
We'll keep this ticket open. We want to build the ability to aggregate on top of spans which would solve this ultimately but we don't have a timeline yet
The Aggregate Spans view also doesn't show span description, making it hard to determine which span shows up when and at what percent
This is cardinality issue - if the particular span has too many variations issues/123, issues/234 etc across transactions - that view is aggregating only by the span.op
We will add this to our backlog but we won't be addressing this in the next few months
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Please look at this JIRA for more info related to the customer specifically: https://getsentry.atlassian.net/browse/UP-225
Expected Result
There should be more details then what is shown in Span Description column.
Actual Result
"-" is shown in the Span Description column.
Product Area
Performance
Link
No response
DSN
No response
Version
No response