To identify business transactions using particular parts of the HTTP request, click Name Transactions dynamically using part of the request and configure the option that makes sense for your application.

Carefully consider your naming configuration choices. If you use a value such as the request originating address and you have many clients accessing your application, it's likely that you would quickly reach the maximum number of registered business transactions. See "About the "All Other Traffic" Business Transaction" in Business Transactions for information about this event.

The following provides sample results based on the configuration options:

• To name transactions based upon the parameter name, click Use a parameter value in Transaction names and enter the Parameter Name.For example, when you name the following transaction using the parameter name "category": http://example.com/Store/Inventory?category=electronics, Splunk AppDynamics names the transaction to include the category parameter value: /Store/Inventory.electronics.
• To use a header value in transaction names, click Use header value in transaction names and enter a Header Name. For example, if you name the transaction using a header such as "Version", Splunk AppDynamics names transactions with the header value as follows: /Store/Inventory.v2.5.
• To use a cookie value in transaction names, click Use a cookie value in Transaction names and enter the Cookie Name.For example, for a website that tracks a user's loyalty status in a cookie. Set the Cookie Name to "loyalty". Splunk AppDynamics names transactions for the loyalty cookie value: /Store/Inventory.Status=Gold.
• To Use a session attribute value in transaction names, Click Use a session attribute in Transaction names and enter the Session Attribute Key.For example, a website stores a customer's region in the session property. Set the Session Attribute name to "region". Splunk AppDynamics names transactions for the region session attribute value: /Store/Inventory.NorthAmerica.
• To use the request method in Transaction names, click Use the request method (GET/POST/PUT) in Transaction names.For example: /Store/Inventory.GET.
• To use the request host in Transaction names, click Use the request host in Transaction names. For example: /Store/Inventory.192.0.2.0
• To use the request originating address in Transaction names, clickUse the request originating address in Transaction names.Splunk AppDynamics names transactions for the IP address of the request client. For example: /Store/Inventory.192.0.2.10 .
• To use a regular expression on the URI to name the transaction, clickApply a custom regular expression on the transaction name. Splunk AppDynamics uses the following rules to name the transaction:
  • The Apache Agent uses Perl style regular expressions.
  • Splunk AppDynamics tests the regular expression against the segments specified in the configuration.
  • Splunk AppDynamics names the business transaction for the substring match.
  • If the regular expression pattern isn't found, the business transaction name follows the URI rules.
  • If you use groups in the regular expression, Splunk AppDynamics names the business transaction for the first matching group. If no matching groups are found in the pattern match, Splunk AppDynamics names the transaction for the fully matched substring.For example consider the following URL: http://mywebapp.example.com/abc/;jsessionid=12345008;mykey=mytransaction;anotherkey=foo .Use the first two segments of the URI with the following regular expression to name the transaction for the value ofmykey: .*mykey.(\w+).* .In this instance Splunk AppDynamics names the transactionmytransaction.