Splitting Matches into Separate Business Transactions

With only transaction matching configured, all requests matched by the match rule belong to the custom business transaction. Alternatively, you can create a match rule that generates multiple named business transaction based on criteria in the request.

For example, the following configuration defines a custom match rule that matches by superclass. In the example, the entry point matches the process() method defined in classes that extend the com.acme.AbstractProcessor superclass. In our example, the superclass is extended by the subclasses SalesProcessor, InventoryProcessor, BacklogProcessor.

  1. Create A custom rule that matches the superclass matches all of those subclasses.
  2. Split the transaction on class name, you can have separate business transactions created for the respective subclasses. Splunk AppDynamics names the transactions with the class name, prepending the match rule name to the class name. For example, Process.SalesProcessor, Process.InventoryProcessor, and Process.BacklogProcessor.

t's possible that parameter values carry what would be meaningful identifiers for business transactions in your application. For example, say the jobType parameter in the following method may have the values of Sales, Inventory or Backlog.

public void process(String jobType,String otherParameters...)

You can split the transaction based on parameter value by indicating the zero-based position of the parameter in the method signature, 0 in the example:

The toString() Using Getter Chains for more information. As indicated in the dialog, you can use other transaction splitting criteria as well, including thread ID, method name, class name, and so on.

The name of the rule is prepended to the dynamically-generated name to form the business transaction name.