0
More details on the Requests page
Source: getsentry/sentry#72628 · opened by @jboulter11
Problem Statement
I want the Requests page to break down the requests by route, not just by domain.
Basically, it's cool that you can see each domain's high level stats but it's not that useful, really, until I can see it broken down by url.
I also wanna be able to setup alerts based off these things to catch outages or server/client regressions.
If you need screenshots here ping us in Slack, I can't post them publicly.
Solution Brainstorm
I want to see that the /2/log_timing route is seeing 10% 500 responses 90% 200 responses. I want to see exact error codes, so if a route is getting 422 vs 401s I wanna see that.
Product Area
Performance
I want the Requests page to break down the requests by route, not just by domain.
Basically, it's cool that you can see each domain's high level stats but it's not that useful, really, until I can see it broken down by url.
I also wanna be able to setup alerts based off these things to catch outages or server/client regressions.
If you need screenshots here ping us in Slack, I can't post them publicly.
Solution Brainstorm
I want to see that the /2/log_timing route is seeing 10% 500 responses 90% 200 responses. I want to see exact error codes, so if a route is getting 422 vs 401s I wanna see that.
Product Area
Performance
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow Customization of Custom Details Section in PagerDuty Incidents and Alerts
0 votes · 0 comments
Add explanation to lifetime event count on issue details
0 votes · 0 comments
Add hyperlink from a Message in Issue Details page to code base
0 votes · 0 comments
Add a "Show Less" button to issue details stack trace
0 votes · 0 comments
Error occurrence count details in filters/discarded-groups/ view
0 votes · 0 comments
No comments yet.