fix: remove unnecessary sentry capture for expected user input errors #642
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.
Summary
Removes
sentry_sdk.capture_exception()calls forReportEmptyErrorandReportExpiredException- these are expected user input validation issues that don't need to be tracked as errors in Sentry.Problem
These exceptions were being sent to Sentry creating ~150K+ error events per week:
ReportEmptyError: ~129K events/week (customer uploaded empty/invalid report)ReportExpiredException: ~24K events/week (customer uploaded expired report)These are already:
Solution
Remove the unnecessary
capture_exception()calls while keeping all logging and error handling intact.Impact
Note
Removes Sentry exception capture for expected user-input errors in report processing, keeping logging and error handling intact.
build_report_from_raw_content, removedsentry_sdk.capture_exception()forReportExpiredExceptionandReportEmptyErrorlog.info/log.warningmessages and returns appropriateProcessingErrorresults for these casesWritten by Cursor Bugbot for commit 295d1d6. This will update automatically on new commits. Configure here.