Define ignore_errors & ignore_transactions #884
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| To further simplfiy ignoring certain events from being sent to sentry, it is also sugggested to provide `ignoreTransactions` and `ignoreErrors` (or exception, choose terminology which is best for the platform). This option should provide a simple way to allow users to discard events (ignore) from before they are sent to sentry. Prevents sending data which is is undesired and may consume quota or resources on the Sentry server. | ||
|
|
||
| ```python | ||
| ignore_transactions = ['GET /api/health','/api/v1/*'] |
There was a problem hiding this comment.
Please specify that this list refers to transaction names.
|
@smeubank might be worth pointing out to https://develop.sentry.dev/sdk/client-reports/ as well since events are dropped on the client. |
Co-authored-by: Philipp Hofmann <[email protected]>
will merge this as is. @jjbayer is there anything we need to consider on relay to send a new item type client reports for these 2 new discard reasons? |
Background
With improved server side sampling Sentry attempts to already remove some transactions which do not provide value to the user. However this is a known case for many users for a long time. There is the traces sampler function, but the UX for this is bulky when you have a simple use case.
Use case: There transcations and errors which a users never wants sent to sentry, to appear in a feed or count against their quota.
Proposal: provide simple options which is a list of errors/exceptions and transactions, respectively, which the SDK will then always discard and never send to Sentry
Preview: Event Sampling
Similar implementations:
getsentry/sentry-php#1503
JS
ignoreErrors: Manage Your Error Quota