Airbrake vs Bugsnag: What are the differences?
Developers describe Airbrake as "Airbrake captures and groups errors in Ruby, iOS, Django, PHP & more". Airbrake collects errors for your applications in all major languages and frameworks. We alert you to new errors and give you critical context, trends and details needed to find and fix errors fast. On the other hand, Bugsnag is detailed as "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.
Airbrake and Bugsnag can be primarily classified as "Exception Monitoring" tools.
Some of the features offered by Airbrake are:
- Dupe Detection- Developers will only receive an email once when an error occurs — rather than getting buried under an error email avalanche.
- Auto Resolve- An action on each application deployment — that way developers can focus on the problems that exist today, not the ones from last month.
- Github Aware- Airbrake is github-aware, and can link code in your Airbrake error stack traces to the corresponding locations on github.
On the other hand, Bugsnag provides the following key features:
- Root cause error grouping
- Real-time alerting to chat, email or SMS
"Reliable" is the top reason why over 26 developers like Airbrake, while over 46 developers mention "Lots of 3rd party integrations" as the leading cause for choosing Bugsnag.
LinkedIn, Square, and Coinbase are some of the popular companies that use Bugsnag, whereas Airbrake is used by Stack Exchange, thoughtbot, and Mailgun. Bugsnag has a broader approval, being mentioned in 295 company stacks & 49 developers stacks; compared to Airbrake, which is listed in 91 company stacks and 22 developer stacks.
What is Airbrake?
What is Bugsnag?
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?
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.
Efficiently trace and detect errors in the stack without having to explicitly setup error tracking for each action.
Bugsnag provides Rails and Sidekiq error tracking with email notifications on exceptions.