FireHydrant

Manhattan, NY, USA
2017
Jun 10, 2021   |  By Robert Ross
“Mean time to X” is a common term used to describe how long, on average, a particular milestone takes to achieve in incident response. There’s mean time to detect, acknowledge, mitigate, etc. And then there’s the elusive “mean time to recover,” also known as “MTTR.” MTTR, a hotly debated acronym and concept, measures how long it takes to resolve an incident on average. The problem with MTTR, though, is that it doesn’t matter.
May 26, 2021   |  By Daniel Condomitti
When you’re feeling the stress and pain around incidents, making the decision to find an incident management tool is a no-brainer. But how do you choose the one that will work for you, your team, and your business? You might be asking yourself: Where do I start? What do I need to know? What questions do I ask? What are the options? How can I be sure we’re choosing the right tool?
May 21, 2021   |  By FireHydrant
Streamlining your incident management process is what we do best, and one of the ways we do that is by acting as the connective tissue across all of your applications. We’ve partnered with Checkly to bring you a new integration that empowers you to detect problems and resolve incidents faster.
May 21, 2021   |  By Julia Tran
We’re happy to announce our integration with Google Meet to create incident bridges automatically. Using the power of FireHydrant Runbooks, a Google Meet can be added with fully customizable titles and agendas based on your incident details.
May 17, 2021   |  By FireHydrant
That's a wrap! We hosted "WTF is Incident Management" on May 12, 2021. We invited four very knowledgeable panelists to discuss how they define incident management, what changes they'd make if they could start again from scratch, how to manage team stress after an incident, and other subjects. Our panelists were: host Matt Stratton (Staff Developer Advocate at Pulumi), Emily Ruppe (Incident Commander at Twilio), Alina Anderson (Sr.
May 7, 2021   |  By FireHydrant
That’s a wrap! Gremlin hosted Failover Conf 2: Fail Smarter on April 27, 2021. In attendance were over 500 SREs, developers, sales engineers, product managers, DevOps experts, C-level execs, and other reliability pros from around the globe! This year’s conference included discussions around the future of DevOps, strategies for building reliable teams, analyzing human error to create better systems, and more.
Apr 23, 2021   |  By FireHydrant
We're excited to announce the release of two new features this month: customizable Slack incident modals and Incident Tags. Keep reading to more about how they can help your teams manage incidents better!
Apr 15, 2021   |  By FireHydrant
Site Reliability Engineers are expected to know everything that’s happening, all of the time. That’s a lot of things! To help you sift through the noise, we’ve developed a feature that lets you find accurate data about your organization on-demand. You can do this by sending custom-designed commands to FireHydrant directly from your integrated Slack account.
Apr 8, 2021   |  By FireHydrant
We won an award! We're excited to share that we were named the Major Incident Software Innovation of the Year 2020 at the MIM Awards. Our CEO, Robert Ross (better known as Bobby), accepted over video on our behalf (watch the video below). A lot happened for us in 2020 -- not only from winning new business, but growing as a team, and maturing our product. We're excited that MIM felt the same way about us and we're honoured to recieve this award!
Mar 29, 2021   |  By Jon Anderson
FireHydrant uses a CLI for some developer actions, called fhd (FireHydrant developers). Previously, we might have distributed workflows among new developers by having them copy/paste or clone scripts down to their machines--but Crystal lets us encapsulate shared tooling in a compiled binary. This way, we have a CLI that developers can install quickly, and that works seamlessly with our other tools.
Oct 15, 2020   |  By FireHydrant
We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time? In this video, FireHydrant CEO, Robert Ross, will share how FireHydrant customers leverage best practices to break, mitigate, resolve, and fireproof incident processes. We’ll show you how to use chaos engineering philosophies to stress test 3 critical parts of a great process.
Sep 29, 2020   |  By FireHydrant
FireHydrant CEO, Robert Ross, demos the FireHydrant platform during Chaos Conf 2020.
Jun 25, 2020   |  By FireHydrant
How to declare an incident on FireHydrant using our Slack integration.
Jun 25, 2020   |  By FireHydrant
A tutorial on setting up Incident Runbooks within FireHydrant.
Jun 25, 2020   |  By FireHydrant
Apr 29, 2020   |  By FireHydrant
Take a quick tour of our product with me. We'll create an incident, see our SEV1 runbook kick off, and triage and eventually create a retrospective report.
Jan 29, 2020   |  By FireHydrant

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.