Bugsnag vs Crashlytics: 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; Crashlytics: The world's most powerful, yet lightest weight crash reporting solution. Free for everybody. Instead of just showing you the stack trace, Crashlytics performs deep analysis of each and every thread. We de-prioritize lines that don't matter while highlighting the interesting ones. This makes reading stack traces easier, faster, and far more useful! Crashlytics' intelligent grouping can take 50,000 crashes, distill them down to 20 unique issues, and then tell you which 3 are the most important to fix.
Bugsnag can be classified as a tool in the "Exception Monitoring" category, while Crashlytics is grouped under "Mobile Error Monitoring".
Some of the features offered by Bugsnag are:
- Root cause error grouping
- Real-time alerting to chat, email or SMS
On the other hand, Crashlytics provides the following key features:
- Instead of just showing you the stack trace, Crashlytics performs deep analysis of each and every thread. We de-prioritize lines that don't matter while highlighting the interesting ones. This makes reading stack traces easier, faster, and far more useful!
- Crashlytics' intelligent grouping can take 50,000 crashes, distill them down to 20 unique issues, and then tell you which 3 are the most important to fix.
- Now you'll get precise information on the performance of the devices that your apps run on. We'll let you know if the crash only happens on a specific model or generation of a device. We'll even tell you other information, like whether your app only crashes in landscape mode, or whether the proximity sensor is always on.
"Lots of 3rd party integrations" is the primary reason why developers consider Bugsnag over the competitors, whereas "Crash tracking" was stated as the key factor in picking Crashlytics.
According to the StackShare community, Crashlytics has a broader approval, being mentioned in 350 company stacks & 68 developers stacks; compared to Bugsnag, which is listed in 295 company stacks and 47 developer stacks.
What is Bugsnag?
What is Crashlytics?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Bugsnag?
What are the cons of using Crashlytics?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.
I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.
After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.
I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.
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.
Crashlytics is intended to track issues and crashes sent from the test and the distribution application builds.
Bugsnag provides Rails and Sidekiq error tracking with email notifications on exceptions.