Prevent capture of errors coming from /go/* urls on Cloud environment.
Created by: jhchabran
Those errors are polluting our Sentry backlog and are extremely numerous due to Google having indexed those pages.
These changes introduce a new type of errors, "Muted" which prevents capture when they reach the Sentry error reporting code.
A convenient function has been added to errorutil
to enable to
mute errors at the router level.
For example, in the last 48 hours, we have seen +1000 errors in total and are down to 56 after filtering out "/go/*" legacy urls.
Questions
- Is the
Mute
terminology clear enough? - And if we're okay to silence that whole route itself obviously.