Within the SDK you can reduce the data volume you’re sending. All SDKs provide some mechanism to override if an event should send. Please consult the documentation for your SDK for more information on how to configure this. Use the beforeSend function (or its equivalent in your SDK) as a specific example of such a mechanism to filter out known, non-actionable, or bursty errors before they are sent to Sentry.

Turn on inbound data filters for legacy browsers, browser extensions, localhost, and web crawlers. Any filtered events will not count towards your quota. This ensures that events are dropped earlier in the pipeline, preventing them from being counted toward DSN rate limits.

Set DSN-Level Rate Limits: Configure rate limits to cap the number of events a key can send within a defined period. This helps control event ingestion and prevents overages.- Adjust Sampling Rates: Configure the sampleRate option (and related settings) to control the proportion of events sent to Sentry. This allows you to reduce the overall volume of events while preserving the most critical data.

Create Metric Alerts: Set up alerts to notify you when event volume exceeds a predefined threshold, allowing you to take timely action. For example, you can set up a rule to notify you if an error occurs more than a specified number of times within an hour.

Use Delete and Discard Rules: Stop noisy issues from counting against your quota by discarding or deleting them. This is particularly useful for managing recurring issues.

Delete and Discard is only available on Business Plans.