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.
Easily define dependencies between services
As your service catalog becomes more complex, so does the burden of defining your service relationships. After connecting dependencies, service owners can add extra value to this service definition with the use of dependency notes. These notes can provide crucial insight for determining if dependencies should be brought into the impacted scope of an active incident. Identifying important subtleties between services can help inform engineers on which areas to execute their next steps, improving their service downtime.