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.
What is Bugsnag?
What is Sentry?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Bugsnag?
BugSnag's customer support has gone above and beyond for me! They got me a free shirt, and I am veyr impressed by thier error management system. Easy to work with, and makes location errors I may have missed quick and easy!
It is really fine if you do not mind paying a bit. Much more reliable and better designed than the competition. Open source code for iOS tracker, helps a lot. Excellent online support.
Lots of companies I respect were using it + open-source + great features and UI. Went for the hosted version, since it plays nice with Heroku. I like how they group together similar errors, give you the ability to mute events or mark them as solved. P.S. check out the Founder Stories feature we did on Sentry if you want to know how they started, its an awesome story.
The error and event tracking in Sentry is superb. Being able to assign the raw error to people along with all information at the time the event occurred means that we're tracking and fixing problems before they become apparent to customers. We use the self-hosted instance of Sentry.
Sentry is a very powerful error reporting tool. We use it both on front-end and back-end of Ataccama One. It proved to be invaluable in providing insights on our errors - what caused it, what user did before the error occured, stack trace, release tracking and more.
We use Sentry to gather our thrown non-checked exceptions in one place, so we don't have to crawl through all our logs manually. All standalone-applications, our website aswell as our game-servers are linked into sentry.
Sentry is amazing, most of our systems send their exceptions to sentry. We couldn't live without it and get a much better understanding of how our code is behaving in the wild. Plus it integrates with Github.
Bugsnag provides Rails and Sidekiq error tracking with email notifications on exceptions.