What noisy errors should Sentry filter out next?

[rachrwang]

Not all errors are created equal - some point to critical problems in code while others are pure noise. We built Inbound Filters to automatically discard noisy errors, and hopefully make your Sentry experience more actionable.

Here's the current set of filters that Sentry provides out of the box:

Despite our best efforts to update this list of filters when we identify new errors, we know new ones crop up all the time and our lists aren't exhaustive.

This is where we'd like to ask for your help: what other errors should Sentry be filtering out? Please be as specific as possible, and link out to examples where possible.

We'll use the ideas we crowdsource to inform our next sets of updates. Thank you!

[smeubank]

We are considering a solution in the JavaScript SDK which could help detect what might be noise from browser extensions, for example, and prevent this noise from appearing in the issues feed.

getsentry/sentry-javascript#10882 (comment)

[smeubank]

while this can be done in the JS SDK, we could also consider server side implementations which similar detects events which have these signs of being from extensions and kicking them out

[collectedmind]

We tend to get a ton of errors from third party initializations (like ad marketplaces) that end up flooding our logs. Curious if that qualifies, or if that is already handled in a way I haven't found yet.

[smeubank]

Yes this counts. So there are some existing ways, but they are not full proof. The following changelog, covers some existing methods, and a new one which you can use with one of our bundler plugins.

https://sentry.io/changelog/ignore-errors-that-dont-come-from-your-code/