Honeybadger Pricing Overview

The business value that Honeybadger provides is fairly simple: it aggregates error reports and collects additional context about those errors in an easy-to-consume web interface. It provides tools for unobtrusive integration with codebases, and features to manage the complexity of a firehose of automated error reports (merging duplicate errors, searching for specific occurrences within a particular fault, linking to Github issues etc. ). It does all of this well, without getting in the way.

The *best* thing about honeybadger, however, is their team. On at least 3 separate occasions, I've contacted their support with an issue that seems fairly specific to my own workflow (mostly hoping for advice), and within a day or two they've deployed a change to the product to better support those needs (or fix an edge case bug that I happened to trip over). I've never felt more valued as a customer in my professional life, and each time it's ended up saving me a huge amount of time in the long run. Even if another error aggregator offered more features, I'd still choose honeybadger for that reason alone. They're in it to help, and that shows up in their actions.

o7 Honeybadger team! Review collected by and hosted on G2.com.

The one complaint I have about Honeybadger is that the way they group error reports can result in a lot of duplicate reports for parts of a code base under frequent change. It's largely based on the file name and line number of the first stack frame in the stack trace, so any time a change pushes a line of code up or down in it's source file, any existing errors from that line of code will show up as a new issue in Honeybadger. There are ways to solve this, with custom 'fingerprinting' logic for errors, to be implemented in your codebase with the SDK provided, and there are tools for merging duplicate reports, but it's the one thing I'd consider as a trade-off for the all the benefits that Honeybadger provides Review collected by and hosted on G2.com.