Issue
Some of our users have custom chrome extensions that prevent sentry API envelope calls from going through. We'd like to inform/prompt the users that these APIs are not going through.
Applies To
- All SaaS Customers
Resolution
Unfortunately there is nothing in the error event that could easily be flagged as a chrome extension as far as the Sentry SDK's capabilities go.
We recommend taking a look at our Dealing with Ad-Blockers and Using the `tunnel` Option troubleshooting sections here. As written, it is possible to work around ad blockers by using our NPM packages and tunnelling. Alternatively, you can set up a Relay which can act as a proxy that will send your events to your custom domain name first before Sending them to Sentry, which should not trigger chrome extensions.
Lastly, you also have the option to implement something custom with your own code. It could be error handling that detects when Sentry API calls fail and creates a user-friendly message explaining that their ad-blocker or security extension might be interfering with error reporting functionality. You can then provide instructions on how to whitelist your domain and Sentry's IP ranges and domains or disable the ad-blocker for your site if they want to ensure full functionality. Please note that while you can inform users about these issues, ultimately it's their choice whether to modify their browser settings or extensions.