Honeybadger for Go (golang) v0.0.3 released

Last week we released some improvements to our Go client, which reports panics and errors from Go applications. You can now configure the client to ignore errors in development/test mode.

Last week we released some improvements to our Go client, which reports panics and errors from Go applications. Check out the package on GitHub, and read on to learn about the update!

Development mode

Adding a test/development mode is something we've been wanting to do since we first released Honeybadger for Go, and now it's possible by using the NewNullBackend() method.

In the honeybadger package a backend is an interface which responds to the method Notify():

// The Backend interface is implemented by the server type by default, but a
// custom implementation may be configured by the user.
type Backend interface {
    Notify(feature Feature, payload Payload) error

The backend Honeybadger uses to report data can be configured using the honeybadger.Configure() method. Making the backend configurable allows the user to decide how the data should be handled after our package collects it; the default backend is the server backend, which sends the data to Honeybadger servers via HTTP.

NewNullBackend() creates a backend which swallows all errors and does not send them to Honeybadger. This is useful for development and testing to disable sending unnecessary errors. To stop reporting live data, just configure the backend option to use the null backend:

honeybadger.Configure(honeybadger.Configuration{Backend: honeybadger.NewNullBackend()})

Updated CI build

Now that Go 1.6 is out, we updated our TravisCI build matrix to test 1.4-1.6 so that we can be sure that we support the latest versions of Go and do not create regressions.


One of the packages we depend on, shirou/gopsutil released a breaking change to their API which forced us to update our usage. Be sure to update both honeybadger and gopsutil to the latest versions when you upgrade (and always vendor your dependencies!)

We also fixed an issue with an unexported field name on the Fingerprint type, which was added in v0.0.2.

Thanks to our contributors

This release was made possible by our awesome customers. Thank you to Chris Gaffney, Stephen Meriwether and Kostiantyn Stepaniuk for your contributions. Let me know if you ever visit Portland, OR so that I can buy you a beer. :beers: :)

For a full history of the changes we make to the honeybadger package for Go, check out the CHANGELOG.

I hope that these improvements will help you exterminate errors and panics in your Go applications faster. If you haven't tried Honeybadger for Go yet, sign up for a free trial!

Honeybadger has your back when it counts.

We combine error tracking, uptime monitoring, and cron & heartbeat monitoring into a simple, easy-to-use platform. Our mission: to tame production and make you a better, more productive developer.

Learn more
author photo

Joshua Wood

Josh is Honeybadger's resident bug hunter and technical debt collector. Once enthusiastically referred to as a "human exception tracker", he spends his days crafting the middleware, plugins, and gems which keep the 'badger fat and happy through a steady diet of fresh data.

More articles by Joshua Wood
“We've looked at a lot of error management systems. Honeybadger is head and shoulders above the rest and somehow gets better with every new release.” 
Michael Smith
Try Honeybadger Free for 15 Days