Filter out browser extension errors

[chadwhitacre]

Originally requested by @mikemaccana via Twitter:

Sentry is reporting errors for our web app that are actually from user's Chrome extensions.
We've ignored it, but can I suggest this be disabled by default?

Beyond ignoring in-app, another workaround is to set allowUrls.

---

[kamilogorek]

Browser extensions can be filtered directly in the UI:

[chadwhitacre]

Easy as that. 😁 Go team!

[mikemaccana]

Thanks! Just switched this on now. May I suggest it (or something similar) be enabled by default in future? It took us a little moment to realise error was caused was an extension and I'm sure we're not the only ones.

[chadwhitacre]

@kamilogorek Do you have any insight into why this option is disabled by default? Do we not trust it enough to enable it? 😁

[kamilogorek]

To quote one of our engineers: "We've purposefully disabled these filters by default some while ago because it was impossible to debug missing events reported by customers"

[chadwhitacre]

Thanks @kamilogorek, sounds about right. False positives can be difficult to debug as @mikemaccana has discovered, but false negatives are even more difficult. :-/

[gnapse]

I have both the allowUrls option set, and the browser extensions filter enabled in the settings. But we still get an error that's coming from a browser extension:

The browser extension, according to the highlighted extension ID in the following screenshot, is the Rabby Wallet Chrome extension.

Any suggestions of what else can be done?

[gndelia]

@gnapse Were you able to filter these issues? I'm having the same problem

[gnapse]

I haven't checked again, but I believe we have not figured this out in my team. It's a small nuisance, that we only found out while trying to reach sentry-zero in our product. But we have not spent a lot of time figuring this out after I noticed it.