Open cseas opened 1 year ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-stats for triage ⏲️
Hi @cseas - Thanks a lot for this feedback. This is in our backlog. Your solution suggestion is helpful as well, I wanted to ask if you care about seeing the full breakdown of these transaction numbers.
For e.g. Do you want to see how many transactions were sampled away due to your sampling rate or any filtering in the SDK?
Do you want to see how many transactions were sampled away due to your sampling rate or any filtering in the SDK?
@Dhrumil-Sentry That'd be helpful, yes. But the immediate requirement is just to confirm whether our sampling is even working or not. The current numbers make it look like it's not. Can you confirm that the numbers shown right now are the ones after sampling?
@cseas - The stats we show in-app are the numbers Sentry is ingesting after being sampled on the client side. The total does not include transactions that are being discarded due to client-side sampling.
Problem Statement
We have set
tracesSampleRate: 0.2
in our Sentry init config but when we check the Stats page for our project, we can see that the "Total Transactions" and "Accepted Transactions" are roughly the same number.Does this mean that the sampling isn't working?
Solution Brainstorm
Please add a tooltip on the "Total Transactions" widget on Stats page that clarifies whether the number shown is only sampled transactions or actually all transactions before sampling.
Product Area
Stats