Quick Start Guide

By now, you probably already understand what FireHydrant is all about. For a refresher, check out What is FireHydrant?

This article outlines the most critical things you should do to improve your incident response process with FireHydrant. We recommend keeping it simple to start--for example, configuring one integration and creating one Runbook--and then scaling from there. 

1. Set up Slack integration

Slack and FireHydrant are a powerful duo. The Slack integration unlocks a lot of powerful workflows for your incident response team, making those previous steps a lot more efficient. You can use FireHyrant without Slack, but you'll miss out on a lot of the capabilities and value we offer.

2. Create your first Runbook

Runbooks are our bread and butter. They remove the stress and toil from incident response processes by automating the manual tasks your team is used to doing. Runbooks can do things like create a dedicated Slack channel for your incidents, spin up a Zoom bridge, send emails, generate customized Slack messages, and much more.

3. Invite your teammates

A good incident response process involves a team. Bring any key players into FireHydrant to help manage incidents. Remember, anyone can declare an incident from Slack--without being a FireHydrant user--but to have access to all other actions in Slack, you must be a FireHydrant user. Invite on-call engineers, SREs, DevOps teams, and anyone else close to the incident management process.

Note: Once you've accomplished these first three steps, you can start using FireHydrant to automate some of your incident management process. But don't stop there, continue reading this guide for tips and tricks to really level up your incident management process and prepare for your first FireDrill.

4. Configure additional integrations

Now that Slack is integrated, you're off to a great start! Next, we recommend setting up the Zoom integration so that your Runbooks can automatically spin up a conference bridge for you and your team to use during incidents. You might also want to integrate Jira or Clubhouse so your Runbooks can automatically create tickets for incidents, and follow up tasks during Retrospectives.

 

5. Add your Infrastructure properties to FireHydrant

In FireHydrant, when we refer to "Infrastructure", we're referring to your Services, Functionalities, and Environments. By adding these pieces of infrastructure to FireHyrant, you can do things like automatically assign Incidents to a team based on the Infrastructure that's impacted. Or you can automatically set the severity based on the Infrastructure, and much more. You can import your infrastructure from PagerDuty or Opsgenie, using our API, or using our Terraform provider.

 

6. Create teams

Teams help you get the right people involved in an incident quickly. Depending on the type of incident, you may want to assign a specific team. You can automatically assign teams based on impacted infrastructure, or you can dynamically assign teams based on the current on-call schedules from your alerting provider.

 

7. Prepare for a FireDrill

FireDrills are a great way to practice your incident response process. We recommend running FireDrills often so that you can iron out any kinks and make sure you have the right things in place for your incident response process to go smoothly. Before running your first FireDrill, make sure you've configured some of the more critical pieces of FireHydrant.

 

8. Run your first FireDrill

Now that your FireHydrant implementation is in a good spot, it's time to run your first FireDrill. Remember, these are practice scenarios. Your first FireDrill will probably uncover a lot of learnings and maybe raise some questions on how to improve your FireHydrant implementation. We're always here to help, just reach out to support@firehydrant.io!

 

 

 

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section