Honeybadger

Seattle, WA, USA
2012
May 3, 2021   |  By Julie Kent
Let's face facts. Git is not fun. Git is not friendly. No. It's just infuriatingly useful, so we're stuck with it. But what if you could make git more friendly? More convenient? Would that make your day a little less stressful? In this article, Julie Kent shows us how we can do this with just a few simple tweaks.
Mar 22, 2021   |  By Julie Kent
Without version control systems like git, life as a developer would be very different. It is the center of modern collaborative approaches to development. But how does it work? You know...under the hood? In this piece, Julie Kent gives us a guided tour.
Mar 8, 2021   |  By Diogo Souza
Logging is tricky. You want logs to include enough detail to be useful, but not so much that you're drowning in noise - or violating regulations like GDPR. In this article, Diogo Souza introduces us to Ruby's logging system and the LogRage gem. He shows us how to create custom logs, output the logs in formats like JSON, and reduce the verbosity of default Rails logs.
Feb 8, 2021   |  By Julien Cretel
Management thinks that letting folks from WidgetCo log into widgetco.ourapp.com will really help make the sale. It seems harmless enough. But using a custom subdomain like this can open WidgetCo up to potential security issues. In this article, Julien Cretel introduces us to Subdomain Takeover attacks and discusses ways we can mitigate them.
Jan 21, 2021   |  By Josh Wood
Some devs use JavaScript in the browser; some use JavaScript on the server. What if you do both?
Jan 13, 2021   |  By Milap Neupane
For quick, scalable, highly-available web services, few options compare to AWS Lambda. Just provide your code, add a little configuration, and you're done! In this article, Milap Neupane will introduce us to Lambda, show us how to get it working with Ruby and the Serverless Framework, and discuss reasons to use — or to not use! — Lambda in production.
Dec 16, 2020   |  By Milap Neupane
Every Rails app has a breaking point; a level of activity that it simply cannot handle. Your braking point depends on big architectural decisions, yes — and also on the tiniest changes committed by your most junior developer. That's why it's vital to regularly test your application's performance under load. In this article, Milap Neupane gives us a Rails-centric introduction to load testing with a powerful open-source tool called JMeter.
Dec 2, 2020   |  By Benjamin Curtis
In which we discuss upgrading our quirky billing system.
Sep 8, 2020   |  By Ayooluwa Isaiah
When you're deciding on a technology to use for your project, it helps to have a broad understanding of your options. You may be tempted to build a web service in Go for performance reasons - but what would that code actually look like? How would it compare to languages like Ruby or JS? In this article, Ayooluwa Isaiah gives us a guided tour through the building blocks of go web services so you'll be well-informed.
Aug 17, 2020   |  By Kingsley Silas
Few things are scarier than a database slowly losing integrity over weeks or years. For a while, nobody notices anything. Then users start reporting bugs, yet you can't find any code that's broken. By the time you realize the problem, it may be happening for so long that your backups are unusable. We can avoid problems like these with skillful use of transactions.

Zero-instrumentation, 360 degree coverage of errors, outages and service degradation. Deploy with confidence and be your team's devops hero.

Monitoring — like web development — is complex. Every day we hear about new tools and techniques, but they're usually for big organizations. Ones with dedicated devops teams and so much traffic they care more about “error rates” than individual user experiences. When you're on a smaller team, this doesn't work so well. You know instrumentation doesn’t pay the bills. Customers do. When they encounter a problem you need clear actionable intelligence, not walls of charts and reams of logs.

What if there were a monitoring tool for developers like us? A single tool that could answer at a glance:

  • Are any front-end or back-end systems raising errors?
  • Is the site unreachable or unusually slow?
  • Are scheduled tasks completing as expected?
  • Which customers have been affected by errors today?
That’s Honeybadger. We’re the application health monitoring tool built for you, not Google.

Honeybadger is used by tens of thousands of pragmatic developers in companies of all sizes who want to focus on shipping great, error-free products instead of wasting time building and maintaining a bespoke monitoring stack.