If your system has hundreds of business transactions, you can leverage the rule system to fine-tune which transactions you want to detect and monitor. Creating rules provides you specific transaction visibility. For example, you can create rules to:

• Detect transactions that are not automatically detected.
• Prioritize monitoring some transactions over others.
• Remain under the transaction limit. When you combine multiple transactions in a rule, the individual transactions no longer count towards the transaction limit; the rule is counted as a single transaction.
• Exclude transactions from monitoring.

For example, Val is creating transaction detection rules for an ECommerce application. Val discovers that the most critical transaction, user-checkout, is grouped into All Other Traffic, which obscures its visibility. To ensure that Splunk AppDynamics collects detailed metrics for user-checkout, Val creates a rule that detects user-checkout, and sets the rule priority to a high value, 50. For less critical transactions, Val creates a rule that detects multiple transactions: createaccount, billing, and delivery-options. Val sets the rule priority to a lower value, 15. Combining multiple transactions into one rule helps Val stay within the transaction limit. See Transaction Detection Rules.