Business workflow rule configuration behavior and limits

Learn about the configuration behavior and limits of business workflow rules in Splunk APM.

Attention:

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.

Use the following links to navigate between the pages in this alpha release:
On the APM Business Workflow configuration page, the following changes to rules accumulate throughout a single session and are not applied until you select Save changes:

  • Creating rules

  • Editing rules

  • Deleting or disabling rules

The following properties apply to rule creation and configuration:

  • You can have a maximum of 500 rules.

  • Each trace can only belong to one business workflow. When multiple rules can apply to the same trace, the trace is matched to the highest priority rule.

  • Moving a rule up or down in the list changes the rule priority relative to other rules. Rules at the beginning of the list have higher priority than rules at the end of the list.

  • For the service:endpoint naming rule, if a trace contains multiple endpoints of the service, the earliest service endpoint span is used for the workflow name.

  • For the Tag value naming rule, if the service appears in multiple spans within a trace with various values of the selected tag, the earliest occurrence is used for the workflow name.