Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(workflows) Brainstorm ideas for waterfall span comparison #1726

Open
Mitan opened this issue Jan 10, 2025 · 0 comments
Open

(workflows) Brainstorm ideas for waterfall span comparison #1726

Mitan opened this issue Jan 10, 2025 · 0 comments
Assignees

Comments

@Mitan
Copy link
Member

Mitan commented Jan 10, 2025

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

  1. 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
    1. Outliers in heat maps/scatter plots
    2. Highlighting a regressed area of a metric chart
    3. From the table results of aggregations
    4. From a particular trace view?
  2. Compare counts and durations of spans in one cohort vs another
    1. Is a specific span being executed more in one group the other
    2. Is a specific span taking longer in one group vs the other (here, it would be so awesome to have exclusive time)
  3. Plot counts/percentiles of these spans
@Mitan Mitan self-assigned this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant