Sentry event quota limits and inbound filter behavior

Managing costs for low-traffic workloads in Sentry requires a precise understanding of how different filtering mechanisms impact the billed event quota. While SDK-level sampling reduces the volume of data transmitted from the client, server-side Inbound Filters are designed to exclude specific events after they reach the Sentry platform.

There is uncertainty regarding the exact sequence of event processing when combining client-side sampleRate configurations with server-side Inbound Filters. Specifically, it is unclear if events discarded by Inbound Filters are still counted against the monthly quota before the filter is applied, or if they are excluded from the billing total entirely.

• Does the Inbound Filter mechanism prevent an event from counting toward the quota?
• How does the quota consumption differ between SDK-level sampling and server-side filtering?