July Product Updates: Status Pages, Incident Redesign, and more
Fire hydrants usually have a firehose hooked up, and do we have a firehose of updates this July. We’ve been focused on making FireHydrant simpler to use and more deeply integrated with existing workflows to make managing your complex systems easier.
By Robert Ross on 7/17/2020
Fire hydrants usually have a firehose hooked up, and boy do we have a firehose of updates for you. We’ve been focused on making FireHydrant simpler to use and more deeply integrated with existing workflows to make managing your complex systems easier. Let’s dive in!
Status pages are a common tool used in incident communication, by closely coupling our incident response platform to our status pages we have made keeping stakeholders and customers updated on your remediation easier than ever. By running your incident response through FireHydrant the manual work of keeping communications up to date are automated letting you focus on remediation. Read more about the updates Status Page Announcement.
Incident Page Redesign
We have simplified and redesigned the incident page to make it easier than ever to discover information and interact with your incident through our Incident Command Center. Read more about the updates Incident Page Redesign.
PagerDuty Integration Updates
In an effort to make it even faster to spin up an incident in FireHydrant we have upgraded our Alerting integrations to go from detected alert to opened incident in a single click on Slack. Read more about it PagerDuty Integration Updates.
Ticketing - Clubhouse
We’re excited to announce that we are adding support for Clubhouse to our ticketing system. Now you can create an incident ticket that all action items from your incident and retrospective are easily tracked and assigned to. With the Clubhouse integration, tickets created in FireHydrant are created and synced to tickets in Clubhouse. Read more about Ticketing here.
Additional Incident types
As companies continue to expand the scope of what constitutes an incident FireHydrant is following suit. You can now designate incidents in FireHydrant as Unplanned Downtime, Scheduled Maintenance, or Gameday. By running these three types of incidents on FireHydrant you can leverage the automation of runbooks to ensure that your process adheres to your plans every single time.
We were happy to sponsor HashiConf Digital, and our own Rich Burroughs has written up some thoughts on the event.
Our CEO Robert Ross wrote about The Culture of the Codebase, and how we try to keep our code fun at FireHydrant.
Anna Kelly talked with LaunchDarkly about how FireHydrant has helped them improve their incident response.
And Mike Lacsamana explained how you can use FireHydrant Runbooks to stick to your SLAs.
If you missed our previous updates, check out our Product Releases page.
See FireHydrant in action
See how service catalog, incident management, and incident communications come together in a live demo.Get a demo