Docs » Use cases: Troubleshoot errors and monitor application performance using Splunk APM » Track how services impact Business Workflows

Track how services impact Business Workflows 🔗

Kai, a site reliability engineer at Buttercup Games, wants to know how the application’s microservices contribute errors or latency to Business Workflows, which track business KPIs at Buttercup Games.

Kai first wants to know if any Business Workflows have errors. Kai opens the APM Overview, which generates charts of all services and Business Workflows by error rate or latency and highlights the top services and Business Workflows:

This screenshot shows the APM Overview page, which has charts of latency and requests/errors of all Business Workflows.


Kai finds that two workflows have abnormal error rates. Kai selects the Explore window to open the service map. Kai clicks nodes with red dots that indicate services with root cause error rates. In this case, paymentservice and checkoutservice nodes are having issues. Kai uses the Breakdown menu to break down each service by Workflow and selects each workflow node to see charts that provide error and latency details:

This screenshot shows charts and numerical data of the requests, errors, and root causes in the Business Workflow node.

Kai discovers that the paymentservice contributes the errors for PaymentService/Charge and frontend/chart/checkout workflows, and the checkoutservice doesn’t impact any Business Workflows. Kai sends this information to the payment service owner to resolve the errors impacting overall business KPIs.

Learn more

For details about business workflows, see Correlate traces to track Business Workflows.