October 19, 2020

Conditions in FireHydrant Runbooks, CSV Exports, and many small improvements

ICYMI: Try conditions in FireHydrant Runbooks

FireHydrant Runbooks have consistently been the most powerful and popular way of implementing your automated incident response process. However, after receiving a lot of great feedback, we extended the ability to create automation beyond the start of your incident. With conditions, you can now add automation to any point of your incident response lifecycle.

You can find our announcement post here, but try out these 2 easy ways for you to get started: how to build automated stakeholder email notifications and how to archive your Slack channel after an incident has ended.

Get reporting how you want it: CSV export of analytics data

FireHydrant captures some of the most full featured incident metrics, but we know that these metrics are extremely valuable in other places outside of the FireHydrant platform. Now you can quickly export your quarterly SEV1 incident data as CSV to populate charts for your next board meeting or capacity planning. Visit Analytics to export some data.

A few little things to take note

We’re always making small, but mighty, improvements to the platform to increase how easy things are to use. This month we added support for searching for incidents based off of their number on the incidents list, dynamic title tags for easier history browsing, updates to the responders algorithm to more correctly show who interacted on an incident, and displaying who opened an incident on the incidents list. Go to the platform to check them out!

See FireHydrant in action

See how service catalog, incident management, and incident communications come together in a live demo.

Get a demo