Honeybadger vs Sentry: What are the differences?
Honeybadger: Honeybadger is the modern error management service for rails. Honeybadger does more than report errors, it helps you work with your team to fix them. Errors can be assigned. You can comment via email. And a fine-grained permissions system means you control who has access to each specific project; 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.
Honeybadger and Sentry can be primarily classified as "Exception Monitoring" tools.
Some of the features offered by Honeybadger are:
- Collaboration tools for your team
- A blazing-fast error drill-down UI
- Tons of notification options
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.
"Rails integration" is the top reason why over 7 developers like Honeybadger, while over 215 developers mention "Consolidates similar errors and makes resolution easy" as the leading cause for choosing 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.
Airbnb, Uber Technologies, and Instagram are some of the popular companies that use Sentry, whereas Honeybadger is used by ebay, Heroku, and Teespring. Sentry has a broader approval, being mentioned in 1341 company stacks & 434 developers stacks; compared to Honeybadger, which is listed in 34 company stacks and 12 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...