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

Group throughput chart data by span action #71118

Open
gggritso opened this issue May 17, 2024 · 2 comments
Open

Group throughput chart data by span action #71118

gggritso opened this issue May 17, 2024 · 2 comments

Comments

@gggritso
Copy link
Member

gggritso commented May 17, 2024

tl;dr

  • the "Requests Per Minute" chart on the Requests landing page (and domain summary page?) should be split up by HTTP operation. i.e., 5 lines, for HTTP GET, HTTP POST, etc.
  • the "Queries Per Minute" chart on the Queries landing page (and the queries summary page?) should be split by database operation. i.e., 5 lines for SELECT, INSERT, etc.

A few notes:

  • we've gotten this request from a few people now, and it makes a lot of sense
  • a "Top 5" chart also shows an "Other" category, so we don't need to worry about showing too many lines
  • this should probably be a toggle, and maybe a filter, so people can select the exact action they're interested in
  • if splitting up by all actions is too granular, we can split up by "theme" e.g., in Databases, read vs. write operations rather than every possible operation
@getsantry
Copy link
Contributor

getsantry bot commented May 17, 2024

Routing to @getsentry/product-owners-performance-queries for triage ⏲️

@gggritso gggritso changed the title Group throughput chart data by span domain Group throughput chart data by span action May 17, 2024
@getsantry
Copy link
Contributor

getsantry bot commented May 21, 2024

Routing to @getsentry/product-owners-insights for triage ⏲️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant