Seattle, WA, USA

Latest News

Sep 19, 2019   |  By Ben Findley
Here at Honeybadger, we want to do our part to help student developers keep their apps free from errors. That’s why we are excited to offer our error monitoring, uptime and check-in monitoring tool free of charge to students that take advantage of the GitHub Student Developer Pack.
Sep 16, 2019   |  By Ben Findley
Palantir orbs, the Globe of Peace, Thief Raid, Trine, Prophecy Records, Ood Translators — the list of important orbs throughout history is quite long. However, the Honeybadger orb for CircleCI gives you deployment super powers. Do those other “important” orbs offer this feature? I didn’t think so!
Aug 5, 2019   |  By Joshua Wood
At Honeybadger, we use Redis a lot. It's our Swiss Army Knife; it's a cache, a single source of truth, it stores background jobs, and more. Basically, Redis is one of those services that should never fail. I was pondering the DevOps apocalypse recently, as one does (could Redis be one of the four horsemen?), which led me to jump into our #ops channel to ask Ben a simple question: what are the risks if someone executed flushall on our redis instances?
Jul 25, 2019   |  By Kevin Webster
Have you ever dealt with an error in production, and no matter what you try, you can't replicate the issue on your development or staging environments? Often the next step is to gather more data by tossing a debug log at production. If you don't have a good way to correlate logs with a request it can be frustrating, especially during an incident. We added a feature to help, and it's called Breadcrumbs.
Jul 17, 2019   |  By Starr Horne
It's 2019, so we decided it was time to take a more modern approach to the Honeybadger front end. We implemented Turbolinks! This is only the first step on an ambitious roadmap. In 2025 we plan to migrate to Angular 1, and we'll finish out the decade on React unless we run into any roadblocks! But let's get real. Honeybadger isn't a single page app, and it probably won't ever be. SPAs just don't make sense for our technical requirements.