Product Updates: Conditions in FireHydrant Runbooks, CSV Exports, and much more

A lot can happen in a month. Not only did all the leaves suddenly change colors in the Northeast, we also released conditions in FireHydrant Runbooks (a great new feature that lets you build custom logic into your automation that you should definitely check out), premiered a fun video at Chaos Conf, filmed 5 episodes of Throughput Thursdays on Twitch (where our CEO, Robert, is building a Terraform provider), and hosted a webinar on how to use chaos engineering philosophies to test your incident process. But wait, there’s more!

Fresh product releases to try

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!

Some content to catch up on

Be Incident Ready

Have you tested your incident response process? Learn how to use chaos engineering philosophies to stress test 3 critical parts of a great process in our latest on demand webinar “Incident Ready: How to Chaos Engineer Your Incident Response Process.”

API’s, new codebases, and Throughput Thursdays

There’s a lot of new content on the blog, but the highlights include a post about building your API first where we talk about the early decisions FireHydrant made for our platform and one about 7 Ways to Get Acquainted With a New Codebase that our junior developer, Tori Crawford (formerly Fluharty), wrote about how she’s getting used to working with our code.

And of course, if you haven’t caught up yet, you can find previous episodes of Throughput Thursday here and don’t miss it on Twitch, live every Thursday at 5pm on twitch.tv/bobbytables.

ICYMI

If you missed our previous updates, check out our Product Releases page.