Configure business transactions to track business KPIs
This Splunk APM example describes how to configure APM Business Transactions.
Executives at Buttercup Games set three new business KPIs: the percentage of successful checkout requests, the P90 latency of logins, and Failed Customer Interactions (FCI). To measure these KPIs, Wei, the director of site reliability engineering and an administrator of Splunk APM, wants to configure the KPIs as business transactions.
These are the steps Wei takes to configure business transactions:
Wei creates a business transaction rule for the checkout service
Wei wants to monitor the percentage of successful checkout requests by tracking end-to-end traces that include the checkout service. Using the guided setup in Splunk APM, Wei creates a service rule that targets the checkoutservice. Wei specifies the Source of business transaction name as matched service:endpoint for correlating traces by endpoints.
Wei creates a business transaction rule for the login service
Wei creates another service rule that targets the loginservice for the P90 latency of logins KPI. This time, Wei sets the Source of business transaction name as Tag Value and selects the Operation tag for correlating traces with the login operation.
Wei monitors business KPIs using business transaction dashboards and charts
Now that Wei has created these rules, Splunk APM automatically groups all relevant traces and generates dashboards and charts with Troubleshooting MetricSets for configured business transactions that Wei can monitor to measure relevant business KPIs.
Learn more
For details about rules for configuring business transactions, see Configure business workflow rules.