Skip to content
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

Closed
wants to merge 29 commits into from

Conversation

flub
Copy link
Contributor

@flub flub commented Sep 30, 2022

No description provided.

Floris Bruynooghe and others added 23 commits September 14, 2022 15:53
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.
@github-actions
Copy link

github-actions bot commented Sep 30, 2022

Fails
🚫 Please consider adding a changelog entry for the next release.
Instructions and example for changelog

For changes exposed to the Python package, please add an entry to py/CHANGELOG.md. This includes, but is not limited to event normalization, PII scrubbing, and the protocol.

For changes to the Relay server, please add an entry to CHANGELOG.md under the following heading:

  1. Features: For new user-visible functionality.
  2. Bug Fixes: For user-visible bug fixes.
  3. Internal: For features and bug fixes in internal operation, especially processing mode.

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.

Generated by 🚫 dangerJS against d69570d

Floris Bruynooghe added 3 commits September 30, 2022 14:26
This does things like clock drift correction that might still be
needed, it is lightweight anyway.
@jan-auer jan-auer changed the title feat(txprocessing): always require processing quota feat(quotas): Always require transaction processing quota Oct 13, 2022
@flub flub closed this Oct 13, 2022
@flub
Copy link
Contributor Author

flub commented Oct 13, 2022

replaced by #1515 and #1517

@jan-auer jan-auer deleted the flub/billing-processing-rules branch October 25, 2022 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant