April 20, 2022
Runbook Ownership + Service Dependancies
When an incident happens, most organizations have a way of identifying all affected services. The trouble is, it’s often a human-centered process that depends on the knowledge of key individuals or manually updated documentation. There might be a version in your alerting tool, a version in your corporate Wiki, and a different version still in your team’s head. This means that during incidents, responders spend valuable time determining the full impact that could be spent remediating core issues. With the addition of service dependencies to FireHydrant Service Catalog, responders can immediately identify the full scope of service and customer impact across an incident with a comprehensive view of downstream and upstream dependencies. And since Service Catalog documents service ownership, they can quickly pull in the needed responding teams.
Learn more at our blog post here
Feature - Users can define task lists for incidents, assign them to an incident as part of a runbook step, and add them to an active incident in slack Feature - Updated /fh help experience in an incident channel to include guidance for tasks and task lists Feature - Runbook Ownership now available to lock down Runbook editing to Owning Teams
Notice - Tasks will not be assigned tickets even if there is a default ticketing integration in the organization
See FireHydrant in action
See how service catalog, incident management, and incident communications come together in a live demo.Get a demo