What the heck is FounderQuest and what is it doing on the Honeybadger blog? FounderQuest is a weekly podcast recorded and produced by the founders of Honeybadger, Ben, Starr, and Josh (these guys). It covers a wide range of topics centered around...
Introducing the pg_partition_manager gem: It helps you easily maintain PostgreSQL partitioned tables that need to be created and dropped over time as you add and expire time-based data in your application.
Configuring your Rails app via environment variables works well, but sometimes you want to be able to update your configuration on the fly. Here's a way to update your app's environment using SSM Parameter Store. Why would you want to do this? Well...
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.
Using Honeybadger’s orb allows your team to easily track deployments as part of your workflow. Our orb will automatically include the SHA of the revision that was deployed, which we link in the Honeybadger UI to GitHub, GitLab, or Bitbucket, so you can see at a glance what got deployed and when.
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...
We added a useful debugging tool called Breadcrumbs. Check them out, and perhaps you will never need a random debug log in production ever again.
Most people consider timeouts to be a kind of error, so it'd be nice to have them reported by Honeybadger like any other errors. This article will show you how to set that up.
Now you can use PagerDuty's event rules feature to suppress an event or change its severity based on data sent from Honeybadger. For instance, when an exception is sent to PagerDuty, you could set the severity to "critical" for a specific environment when fault.environment equals "production".