search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.25k stars 4.21k forks source link

Separate Rate Limits for Transactions and Errors #79880

Open chaitanyadeorukhkar opened 3 weeks ago

chaitanyadeorukhkar commented 3 weeks ago

Problem Statement

Separate Rate Limits for Transactions and Errors

We would like the ability to set distinct rate limits for transactions and errors. Our goal is to allow errors to flow seamlessly, while imposing stricter rate limits on transactions. Currently, rate limits are applied per DSN, which limits flexibility. Although we recognize that a sampling rate for transactions exists, it is not always feasible to adjust it through code, especially in cases where a complex rollout process is required. Therefore, our request is for a feature that enables separate rate limits specifically for transactions and errors.

Solution Brainstorm

No response

Product Area

Settings - Projects

getsantry[bot] commented 3 weeks ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 3 weeks ago

Routing to @getsentry/product-owners-settings-projects for triage ⏲️

getsantry[bot] commented 3 weeks ago

Routing to @getsentry/product-owners-ingestion-and-filtering for triage ⏲️

jjbayer commented 3 weeks ago

Internally, error and transaction limits are already separate entities, so this could be a UI + API change as far as I can tell. @matejminar if it makes sense from a product perspective, is this something your team could take on?