About the default business transaction rule
Learn about the default rule, when to use it, and how to turn it off.
Splunk APM includes a default system-generated business transaction rule: all traces will be associated with business transactions that are identified by the initiating endpoints of those traces. You can’t edit the default rule, but you can turn it off.
When to use the default business transaction rule
If the initiating endpoint of a trace is granular enough to capture meaningful business transactions, for example with API calls, then the default rule is useful because it groups related traces by their initiating endpoint, which is different from other initiating endpoints. To influence which business transactions are discovered by the default rule, you can create endpoint rules to group related requests.
In systems where many traces have the same initiating endpoints, for example because there is a gateway in place, then you may want to extract the business transaction name from a service other than the initiating endpoint. In this case, you can create a business transaction rule that names the business transaction based on theservice:endpoint or a specified tag value.Turn off the default business transaction rule
How to turn off the default business transaction rule.
- From the Splunk Observability Cloud main menu, select Settings, then APM business transactions.
- In the Business Transaction Rules table, locate the Default rule. Select the toggle to turn off the rule.
- Select Save Changes.