You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Brainstorm ideas on how the Cohort comparison approach can be extended to waterfall comparison. From PRD:
Milestone 2 - Span Waterfall Comparison
User Story
As a developer, I want to quickly identify if the p95 duration of my checkout page is longer due to code paths taking longer or due to additional processing taking place compared to the p50 so that I can quickly identify areas of improvement
As a developer, I want to identify what code paths are causing my server API calls to take longer for EU compared to the US region
Acceptance Criteria
The user should be able to specify an outlier and a baseline cohort explicitly or implicitly via the design. This could be done in several ways
Outliers in heat maps/scatter plots
Highlighting a regressed area of a metric chart
From the table results of aggregations
From a particular trace view?
Compare counts and durations of spans in one cohort vs another
Is a specific span being executed more in one group the other
Is a specific span taking longer in one group vs the other (here, it would be so awesome to have exclusive time)
Plot counts/percentiles of these spans
The text was updated successfully, but these errors were encountered:
Brainstorm ideas on how the Cohort comparison approach can be extended to waterfall comparison. From PRD:
Milestone 2 - Span Waterfall Comparison
User Story
Acceptance Criteria
The text was updated successfully, but these errors were encountered: