Manhattan, NY, USA
Oct 28, 2018 | By Bobby Tables
FireHydrant has been around for a few months and after feedback and self reflection there was a lot missing from it that needed to be addressed. The experience of using the tool was lacking and needed some love to better serve the needs of its users. A lot of work has been done since I formally announced FireHydrant, so I want to share some of it here.
Aug 28, 2018 | By Bobby Tables
Distributed systems are difficult to keep in their entirety in your head. There’s web applications, queue processors, cron jobs, and a myriad of other gears churning to make your product offering function. So when a gear stops turning, how do you know what that gear does? This is where having a service catalog comes in.
Aug 12, 2018 | By Bobby Tables
If you’re deploying to Kubernetes, you may have come across the problem of knowing what changed and when. If you’re manually applying YAML files to a Kubernetes cluster you may forget to log that action or do it later with an estimate of when you did it. This introduces a challenge when things break and you’re blissfully unaware something was deployed to your environment. Most of the time when your site experiences a disruption, it’s because something changed.
Jun 21, 2018 | By Bobby Tables
Slack is arguably one of the best tools that companies are using lately. It has an incredible ecosystem of integrations, native applications for every platform, and flawless chat at its core. Slack was an obvious choice when building FireHydrant to integrate with as a first class citizen. In this post we’ll give some simple tips on how to utilize the FireHydrant bot to make sure you don’t drop a beat during the fray of an incident.
Jun 20, 2018 | By Bobby Tables
If you work at a software company, odds are you have dealt with an outage of some kind. The alarms go off, people start asking “Is the site down?” in chat, and you start responding to mean tweets of angry customers. Throughout all of the sudden chaos that comes with an incident in your system, it can be difficult to keep track of time. When did you discover something? Did you apply that patch 5 minutes ago or 50 minutes ago? Who applied it?