-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(quotas): Always require transaction processing quota #1507
Conversation
mainly this adds a new field in enforcement. i may try a vec next INGEST-1354 INGEST-1587
This is an approach that generically allows multiple data categories for events. The resulting code is fairly reasonable.
The envelope limiter needs to avoid calling redis again and needs to remove items that need to be removed. This does that but it is not hooked up properly as the rate_limited_categories which are passed through the processing are too simplistic and instead I want to pass the enforcement through. That still needs to be hooked up.
Co-authored-by: Iker Barriocanal <32816711+iker-barriocanal@users.noreply.github.com>
We must have processing quota in order to index a transaction.
Instructions and example for changelogFor changes exposed to the Python package, please add an entry to For changes to the Relay server, please add an entry to
To the changelog entry, please add a link to this PR (consider a more descriptive message): - always require processing quota. ([#1507](https://github.com/getsentry/relay/pull/1507)) If none of the above apply, you can opt out by adding #skip-changelog to the PR description. |
This does things like clock drift correction that might still be needed, it is lightweight anyway.
No description provided.