Service dependencies

Service dependencies maps let you visualize the relationships between the application and technical services defined in your Service Catalog. The direction of arrows on the map indicates what a service depends on. For example, in the image below, 'Service A' depends on 'Service B' and 'Service C' (and conversely, 'Service A' is depended on by 'Service 1' and 'Service 2').

The icon for each service lets you see at a glance if the service is impacted by any active incidents, and the highest severity level of those incidents. While the map displays a focused view by default, you can expand the map to view additional upstream and downstream services. The icon to indicate if a branch of the map can be extended is color-coded by the highest severity of any active incidents impacting services in the hidden branch.

You can access the dependencies map for a service to view that service's direct dependencies, explore how that service relates to other services in your architecture, and manually define the dependencies between your services. You can also access the dependencies map for an incident to view which services are impacted, investigate which other services may be affected or had recent changes, identify potential root causes, and run automations for impacted services.

Getting around the map

By default, the dependency map for a service displays a focused view of that service's direct dependencies, while the dependencies map for an incident displays services impacted by the incident and paths to any identified potential root causes or recent changes. You can extend that view by expanding and collapsing branches of the map to view or hide additional upstream or downstream services, as well as search for specific services.

Dependencies map for a service

You can use the dependencies map for a service to view and define the relationships between the services in your architecture.

Dependencies map for an incident

You can view a service dependencies map for an incident to explore which services are impacted or potentially impacted, identify root causes and recently changed services, engage service owners as resolvers, and run service-specific automations.