Move API exception logging to DRF handler#2167
Merged
Merged
Conversation
alastair
force-pushed
the
429-api-exception-handler
branch
2 times, most recently
from
July 21, 2026 08:11
8991011 to
5d0d87d
Compare
alastair
force-pushed
the
429-api-exception-handler
branch
from
July 21, 2026 08:18
5d0d87d to
36a9e25
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
1 participant
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.
our API exceptions had side effects when you initialized them, sending logging events and metrics.
Instead, make the exceptions themselves pure, and only log events in a custom DRF error handler
Issue(s)
Description
Deployment steps: