FireHydrant

Manhattan, NY, USA
2017
  |  By Robert Ross
TL;DR You deserve a better alerting and on-call tool. So we built Signals. In our early days, we often used the tagline, “You just got paged. Now what?” It encapsulated how FireHydrant solved for all of the messy bits that come after your alert is fired, from incident declaration all the way through to retrospective. At the time, we saw alerting and on-call scheduling as a solved problem.
  |  By Milan Thakker
Analytics are great. We can all agree there. But not all analytics are created equal. FireHydrant has long offered incident analytics dashboards that provide an in-depth look at the entire incident lifecycle. You can see how incidents impact services and teams, understand retrospective participation and completion, and even get insight into follow-ups. But great analytics do more than simply organize data. They help you tell a story.
  |  By The FireHydrant Team
In this article, we will explore how Dock is working to significantly enhance its response time to critical incidents, emphasizing effective integration between tools as key to success. We will address how we challenge the conventional approach by shifting the focus from Mean Time to Acknowledge (MTTA) to Mean Time to Combat (MTTC), a customized metric that measures the time between incident detection and effective communication involving professionals capable of resolving it.
  |  By Robert Ross
Once the unsung heroes of the digital realm, engineers are now caught in a cycle of perpetual interruptions thanks to alerting systems that haven't kept pace with evolving needs. A constant stream of notifications has turned on-call duty into a source of frustration, stress, and poor work-life balance. In 2021, 83% percent of software engineers surveyed reported feelings of burnout from high workloads, inefficient processes, and unclear goals and targets.
  |  By Robert Ross
Although FireHydrant has spent five years focused on what happens after your team (erg, I mean service 🙄) gets paged, the topic of alerting often comes up in discussions with our community. People are tired of paying big bucks for software that’s expensive, bloated, and hasn’t seen much innovation. Clearly, there’s a problem here – and we’re tackling it head on.
  |  By Robert Ross
On-call scheduling is tricky. Like, really tricky. It was one of the scariest parts when we decided to build a modern alerting system earlier this year. We knew we couldn't cut any corners on Day One of our release because it needed to be a fully loaded feature for someone to realistically use our product (and replace an incumbent). This meant including windowed restrictions, coverage requests, and simple to complex rotations.
  |  By Jouhné Scott
Your status page (or lack thereof) has the opportunity to signal a lot about your brand — how transparent you are, how quickly you respond to incidents, how you communicate with your customers — and ultimately, this all seriously impacts your reliability. After all, as our CEO Robert put it in a recent interview on the SRE Path podcast, you don’t get to decide your reliability; your customers do.
  |  By Robert Ross
As engineers, we didn't want to make Signals only a replacement for what the existing incumbents do today. We've had our own gripes for years about the information architecture many old companies still force you to implement today. You should be able to send us any signal from any data source and create an alert based on some conditions. We're no strangers to building features that include conditional logic, but we upped the ante when it came to Signals.
  |  By Robert Ross
Welcome to the first Signals Captain’s Log! My name is Robert, and I’m a recovering on-call engineer and the CEO of FireHydrant. When we started our journey of building Signals, a viable replacement for PagerDuty, OpsGenie, etc, we decided very early that we would tell everyone what makes Signals unique, and what better way than to tell you how we’re building it (without revealing too much 😉). Let’s jump in.
  |  By Joel Smith
October might be a spooky month, but we’re doing our best to make incidents less scary. We released a number of updates this month that focus on two main areas: Let’s jump in.
  |  By FireHydrant
Meet the only all-in-one incident management platform that is there with you from the first alert until you learn from the retrospective.
  |  By FireHydrant
Engineers are bombarded with pages left and right. There's uncertainty about how to escalate. A constant blur exists between what's urgent and what can wait. This never-ending ping-pong game takes a toll. Burnout creeps in, and your engineering culture has taken a nose dive before you know it.
  |  By FireHydrant
In this episode we chat with veteran cloud architect Masaru Hoshi about the challenges of alert fatigue, the importance of effective alerting systems, and fostering ownership in software teams. Masaru shares insights from his 30-year career, emphasizing the need for balance, trust, and collaboration in incident response.
  |  By FireHydrant
In this demo we'll look at how FireHydrant can solve the pains of quickly declaring and managing an incident, all from Slack.
  |  By FireHydrant
See how FireHydrant can help you achieve better reliability, get to resolution, and back to bed quicker.
  |  By FireHydrant
FireHydrant is the only comprehensive reliability platform that allows teams to achieve reliability at scale by creating speed and consistency across the entire incident response lifecycle.

Utilize SRE best practices using FireHydrant’s incident response platform to organize, investigate, and remedy faster.

FireHydrant helps teams respond to service disruptions easily and effectively. By allowing teams to “rally the troops” with only a few clicks and assign incident roles to responders, responsibilities are quickly defined and allow people to focus on what matters: restoring service.

Organize, Investigate, Remedy and Prevent faster with FireHydrant:

  • Teams: Fill out your SRE roles and assign members to instantly delegate responsibility in an incident. Assign who owns what components to get the right people on the job.
  • Slack Integration: If you're using Slack, FireHydrant gets even better. Quickly open incidents, notify other channels, and assemble your team easily all without leaving Slack.
  • The Service Catalog: Keep a catalog of your environments and the things running in them with our service catalog feature. Make it easy to quickly find all of the gears of your product.
  • The Changelog: Fire's typically start when something changes. That's why we offer a one stop shop for you to log all of the change occuring in your stack.
  • Incident Logs: While you're fighting a fire, FireHydrant will transparently keep track of changes and Slack chat in your incident log automatically. You can easily filter notes and chat as well.
  • Post mortem: Easily access all prior incidents with fine grain filtering to help make actionable changes to keep your system robust.