Resources

We've got your back. We write no-bs content so you can do awesome work.

JUMP TOAll

Featured resources

Blog

Reliability Guide

Incident Management Buyer's Guide

Customer Stories

Events

Featured resources

ruby rails integrations ruby on rails programming

Integrations on Rails: How we build and deploy integrations at FireHydrant

This post explores how we built FireHydrant in a way that allows us to rapidly build and deploy integrations to help our product fit into responders’ workflows and not vice versa.

3 questions to ask in the build vs buy debate for incident response tooling

In many cases, there are components that go into building and running an incident management tool that aren’t considered. These are the three most common ones.

Getting started with severity levels

Incidents can take many forms. How you respond to the incident will vary based on the impact of the incident. And that’s where severity comes into play.

FireHydrant is now more powerful across the entire incident lifecycle

Sweeping platform improvements give you more power, configurability, and insights across every phase of an incident – even when it’s over. Discover what’s new in Status Pages, Retrospectives, and Analytics.

Blog View all

Read the latest from our engineering team, hear from our community, and get quick tips and tricks on how to better manage incidents.

ruby rails integrations ruby on rails programming

Integrations on Rails: How we build and deploy integrations at FireHydrant

This post explores how we built FireHydrant in a way that allows us to rapidly build and deploy integrations to help our product fit into responders’ workflows and not vice versa.

3 questions to ask in the build vs buy debate for incident response tooling

In many cases, there are components that go into building and running an incident management tool that aren’t considered. These are the three most common ones.

Getting started with severity levels

Incidents can take many forms. How you respond to the incident will vary based on the impact of the incident. And that’s where severity comes into play.

Reliability Guide View all

Read on for reliability best practices, definitions, and POVs from the FireHydrant team.

How To Getting Started Incident Response SRE

How To Categorize the Impact of an Incident

Everything is going well until you get an alert that there has been a system outage. In this article, we define an incident and share how to categorize an incident's impact.

SRE 101 Getting Started

What is SRE?

Site Reliability Engineering (SRE) is a practice for managing the reliability of systems. Google originally developed SRE in the early-2000s when Ben Treynor Sloss started the first SRE team, coined the name, and set the tone for the industry.

Culture Team Building How To

How to Cultivate an Open Culture

In an organization with an open culture, everyone should be able to receive and provide critical feedback in a meaningful manner with transparency and respect.