Added filtering for expected Turnstile errors in Sentry #2573
Conversation
This file contains 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.
https://staff.loc.gov/tasks/browse/CONCD-976
I was unable to get these errors, at least the 600xxx ones, to log in my dev environment even before adding the filter (I was able to get Sentry to capture other messages, so it seems like it doesn't log 600xxx errors by default--I kept the filter to be safe). I was unable to trigger the 300xxx at all, since Turnstile doesn't provide a way to do so. Testing will need to be done in dev/test, to the extent it can be tested at all, since it depends on the user failing Turnstile validation.