As is the experience for most B2B SaaS engineering teams, one question we get asked often is, “Do you use Bugsnag yourself?” The answer is, “We do”. Additionally, we at Bugsnag believe that in order to provide the best error monitoring and stability management solution, we must also be the pioneers and thought leaders when it comes to technical debt, application health, and efficient debugging workflows.
In Bugsnag, we automatically ignore errors with browser extension files in the stacktrace, so there’s zero configuration needed to deal with browser extensions in most cases.
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 for crashes in older browser versions, you can focus on fixing errors impacting the majority of users.
Stepping back from the lens of a single error and considering the overall health of your app, you will want to consider user stability, which is one of the two ways you can measure application stability. Spoiler alert: Bugsnag measures both! Stability can be calculated as a percentage of successful sessions over a period of time (session stability) or as a percentage of users who’ve experienced successful sessions over a period of time (user stability). You can easily view these scores in the Stability Center and toggle between which calculation of stability you prefer to view by default.
Bot traffic describes any non-human traffic to a website or an app. While some bot traffic is beneficial, abusive bot traffic can be very disruptive. Distinguishing between bots and real users is important when it comes to error monitoring. For instance, if your website is seeing a huge spike in errors coming from real users, this likely requires immediate attention. On the other hand, if a spike in errors is attributed to bots, attention should go towards managing bot traffic. This can save your team a significant amount of time wasted on debugging.
It’s common for JS teams to have tools in place to identify bot traffic. Using Bugsnag’s custom filters, you can get an understanding of the impact that bots have on your application stability. With the help of custom metadata, your team can leverage bot diagnostics to identify if a user is a bot.
You can even create a bookmark to conveniently access errors excluding bot traffic.