Service Graph

Introduction#

Modern technical architectures are complex, with lots of layers and interdependencies. Because of this complexity, it can be hard for teams to fully understand the impact of an incident on a single service.

Service Graph gives your teams a holistic view of your ecosystem without you having to draw it on the whiteboard.

Connect services to other resources they consume, and the resources that consume them. Build out the full system diagram using dependency relationships so all of your stakeholders can see how one service impacts the entire product.

Business Services place semantic meaning to your ecosystem. Your users don't need to know which backend isn't behaving correctly; they only know which "front door" application they can't access. By creating Business Services and assigning them in the Service Graph, everyone in your organization can quickly see the impact of an incident, no matter how much they know about the architecture of the services.

Learn More#

Read more about what Service Graph provides#

• In our blog

Watch the product demos:#

• Technical Service Dependencies and Suggested Service Dependencies
• Suggested Technical Service Dependencies - Impact Tab

Check out the training modules on PDU:#

• Business Services
• Service Graph

Watch the click-through tutorial (need one recorded for this)#

Find the product documenation in our Knowledge Base:#

• Service Dependencies
• Service Graph

Using the API?#

The endpoints are:

• Business Services
• Service Dependencies
• need to check deep-linking on apis

Managing PagerDuty with Terraform?#

• Find the latest PagerDuty Terraform Provider docs here
• pagerduty_business_service
• pagerduty_service_dependency

Service Ownership#

Interested in how PagerDuty thinks about services and service ownership? Check out our Service Ownership Ops Guide.

Related Features#

• Business Service Subscriptions