Issue
I want to know why a high-volume transaction, API, or URL (for example hundreds of requests per minute) only appears as a small sample in Sentry.
Applies To
All SaaS Customers
Performance Monitoring
Filtering / Sampling
Resolution
That pattern usually means your trace sample rate is doing its job. Sentry doesn’t keep every occurrence of a busy transaction. With a uniform tracesSampleRate, each transaction has the same probability of being sent, so a frequently used endpoint can show up far less often than it actually runs in production.
To see more of that traffic, you have a couple of options:
Raise the uniform rate - increase
tracesSampleRateso more transactions of every kind are kept.Use a sampler - set
tracesSamplerto apply a higher rate (or1) to that transaction name/route and a lower rate elsewhere.
See Configure Sampling for your SDK.
If the volume still looks wrong after changing the sampling, check distributed-trace inheritance and related behavior in Why changing my traces sample rate does not affect the amount of transactions sent to Sentry? and How does transaction sampling work?
To confirm whether the SDK is creating or dropping transactions, enable the SDK’s debug option and watch the console or process logs while the app is running.