You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current rate limiting code has become hard to maintain because of the many different data types and categories and the relationships between them:
One envelope item can match multiple data categories
Some envelope items have a parent-child relationship which is not reflected in the envelope itself.
Introduce a structured data type to make rate limiting more declarative and less error prone. These types can then be used throughout processing, not just in rate limiting. This draft might be a good starting point, but figuring out the design details is part of the epic.
The content you are editing has changed. Please copy your edits and refresh the page.
Implement the quota enforcement as described in https://develop.sentry.dev/ingestion/relay/transaction-span-ratelimits/.
The current rate limiting code has become hard to maintain because of the many different data types and categories and the relationships between them:
Introduce a structured data type to make rate limiting more declarative and less error prone. These types can then be used throughout processing, not just in rate limiting. This draft might be a good starting point, but figuring out the design details is part of the epic.
Tasks
The text was updated successfully, but these errors were encountered: