Bugsnag vs Sentry: What are the differences?
Bugsnag: Bugsnag provides production error monitoring and management for front-end, mobile and back-end applications. Bugsnag captures errors from your web, mobile and back-end applications, providing instant visibility into user impact. Diagnostic data and tools are included to help your team prioritize, debug and fix exceptions fast; Sentry: Cut time to resolution for app errors from five hours to five minutes. Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time. 500K developers use Sentry to get the code-level context they need to resolve issues at every stage of the app lifecycle.
Bugsnag and Sentry can be categorized as "Exception Monitoring" tools.
Some of the features offered by Bugsnag are:
- Root cause error grouping
- Real-time alerting to chat, email or SMS
On the other hand, Sentry provides the following key features:
- Real-Time Updates: For the first time, developers can fix code-level issues anywhere in the stack well before users even encounter an error.
- Complete Context: Spend more time where it matters, rather than investing in low-impact issues.
"Lots of 3rd party integrations" is the primary reason why developers consider Bugsnag over the competitors, whereas "Consolidates similar errors and makes resolution easy" was stated as the key factor in picking Sentry.
Sentry is an open source tool with 21.4K GitHub stars and 2.44K GitHub forks. Here's a link to Sentry's open source repository on GitHub.
According to the StackShare community, Sentry has a broader approval, being mentioned in 1341 company stacks & 434 developers stacks; compared to Bugsnag, which is listed in 295 company stacks and 49 developer stacks.
I essentially inherited a Shopify theme that was originally created by an agency. After discovering a number of errors being thrown in the Dev Console just by scrolling through the website, I needed more visibility over any errors happening in the field. Having used both Sentry and TrackJS, I always got lost in the TrackJS interface, so I felt more comfortable introducing Sentry. The Sentry free tier is also very generous, although it turns out the theme threw over 15k errors in less than a week.
I highly recommend setting up error tracking from day one. Theoretically, you should never need to upgrade from the free tier if you're keeping on top of the errors...