1. Domain whitelisting
2. Strip out exceptions from browser extensions
In Bugsnag, we automatically ignore errors with browser extension files in the stack trace, so there’s zero configuration needed to deal with browser extensions in most cases.
3. Ignore old browsers
Older versions of browsers are much harder to deal with since they’re more prone to crashing, and many don’t even give you stacktraces with error reports. Since fewer users still run these older versions they may be less important to support. By silencing notifications about crashes in older versions of browsers, you can focus on fixing the errors that impact the majority of your users.
4. Use sourcemaps
5. Correlate errors to user or IP address
You can sort errors by event and user counts in Bugsnag which is really helpful for understanding the overall impact of an error. You can even save these filter settings as a default to see user counts automatically every time you look at your Dashboard.
6. Assign version numbers to your JS to track with each error