Add configurable rate limiting for sentry events#183
Merged
Conversation
8521019 to
8706670
Compare
fisherdarling
approved these changes
Mar 26, 2026
8706670 to
7f902b1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
install_hookmethod is replaced byinstall_hook_with_settingsso users can express their rate limiting settings. The default is no rate limiting at all, which means the hook behaves the same as before.install_hookuses those defaults, but is marked deprecated to encourage users to supply explicit settings.The rate limit is applied per-fingerprint. If the event does not have an explicit fingerprint, we fall back to the event's message, exception value, exception type, or level in that order.