Service Graph
Interact with the topology of all technical and business service dependencies in your account
The Service Graph is an interactive mapping of all technical and business service dependencies in your PagerDuty account. View the health of the full service topology at a glance, identify gaps in relationships and seamlessly create dependencies in the graph itself. This feature allows users to easily understand how services combine to deliver customer-facing or business capabilities. During incident response, understand the full blast radius of an issue, zero in on the probable cause, and facilitate cross-team collaboration.
![image6.png Service Graph](https://files.readme.io/49f804b-image6.png)
Service Graph
View the Service Graph
Requirements
- Users with permission to view each service in a dependency relationship will be able to see that relationship in the service graph. If a user does not have permission to view a service, that service and relationship will not display in the graph.
- The Service Graph is available as soon as one or more technical or business services is configured. No further configuration is necessary.
- If you would like to configure dependencies in bulk, you can do so via the REST API, Terraform, or by provisioning them from ServiceNow.
Navigate to Services Service Graph. The Service Graph will only display services that have one or more dependency relationships. Any services that do not yet have dependency relationships will be listed in the right panel under Services without Dependencies, which is broken into two tabs for Technical Services and Business Services.
Service Cards
Each service in the graph is represented by a service card. Service cards contain the following critical information about a service:
- Service Name
- Team: Only available on accounts with Teams, and when the view is sufficiently zoomed in.
- Operational Status of the Service: Operational technical services and business services will be denoted by a green checkmark. Impacted technical services will be denoted by a red exclamation. Impacted business services will display the priority of the most-impacting incident.
Service Display Actions
Users can zoom in and out, hover, and select to display more or fewer services:
- Zoomed out view: Business services are square and technical services are circular.
- Zoomed in view: Business services are rectangular and technical services have rounded edges.
- Hover: Hovering over a service card will highlight the selected service, as well as one level of relationship from that service in both the Uses and Used By directions.
- Select: Clicking on a service will highlight the selected service as well as one level of relationship from that service in both the Uses and Used By directions. It will also display a right panel with service and incident information.
Right Panel
The information displayed in the right panel includes:
- Service Name
- Service Description
- Status
- On-Call Now: Technical services only.
- Escalation Policy: Technical services only.
- Owner: Business services only.
- Team
- Open Incidents: Up to three of the most recent incidents with priority, as applicable. If there are more than three incidents impacting the service, there will also be a link to View All Incidents.
- View Service Profile: A link to view the service profile page.
- Manage Service Dependencies: A link to manage dependencies in the service profile page.
Click in the top right corner of the panel, or on the graph’s background, to close the panel.
![image1.png Service details in the right panel](https://files.readme.io/1119dc2-image1.png)
Service details in the right panel
In the case that the graph has many relationships or services, the top-most or root nodes will be displayed as well as two levels of relationships below that. If there are too many relationships or services to load an optimal view of the service graph, we require users to select a business or technical service to focus the graph. The filtered view will display the selected service as well as the two levels of relationships from that service in both the Uses and Used By directions.
![image4.png Select a service](https://files.readme.io/4729f6b-image4.png)
Select a service
Additional service relationships will be aggregated into grouped nodes. You can click on a grouped node to expand additional relationships.
![image5.png Additional service relationships](https://files.readme.io/d304261-image5.png)
Additional service relationships
Create Service Dependencies
Required User Permissions
Only users with permission to create dependency relationships between services will be able to draw connections between nodes in the graph.
- Navigate to Services Service Graph.
- Search or scroll for your desired technical or business service in the right panel drag and drop the service into the service graph.
- Hover over a service in the graph to display two gray nodes which can be used to draw relationships between two services.
- The arrow denotes the direction of the relationship. For example, drawing a line from Service A to Service B would denote that Service B is dependent on Service A.
![image3.png Service cards with draggable nodes](https://files.readme.io/20629fe-image3.png)
Service cards with draggable nodes
- Draw an arrow between the services by selecting a node and dragging it in your desired direction to denote the dependency relationship.
Disconnect Dependency Relationships
You can disconnect a relationship from the graph by clicking on the line between two services and selecting Disconnect in the prompt that appears.
![image2.png Disconnect dependency relationship](https://files.readme.io/410a634-image2.png)
Disconnect dependency relationship
Updated 3 months ago