About the default business workflow rule
Learn about the default business workflow rule in Splunk APM.
Alpha features described in this document are provided by Splunk to you "as is" without any warranties, maintenance and support, or service-level commitments. Splunk makes this alpha feature available in its sole discretion and may discontinue it at any time. These documents are not yet publicly available and we ask that you keep such information confidential. Use of alpha features is subject to the Splunk Pre-Release Agreement for Hosted Services.
Service map
- Business workflows
Call Graph Profiling
When to use the default business workflow rule
Learn when to use the default business workflow rule in Splunk APM.
If the initiating endpoint of a trace is granular enough to capture meaningful business workflows, 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 workflows are discovered by the default rule, you can create operation and 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 workflow name from a service other than the initiating endpoint. In this case, you can create a business workflow rule that names the business workflow based on the service:endpoint or a specified tag value.
Turn off the default business workflow rule
Learn how to turn off the default business workflow rule in Splunk APM.
- From the Splunk Observability Cloud main menu, select Settings.
- Select APM Business Workflow configuration.
- In the Business workflow rules table, locate the Default rule. Switch the Status toggle to Inactive.