How Timers are Matched with Business Transactions

HTTP requests executed by Silk Performer's replay engine are extended by an additional HTTP header. For example, the following API call:

BrowserFormSubmit("//FORM[@name='loginForm']", "Login");

The HTTP header AppDynamicsTag (the tag attribute you defined during Silk Performer/AppDynamics plug-in configuration) contains the specified timer name NA=<TimerName> (for this example, NA=<Login>.

AppDynamics automatic transaction naming parses the HTTP header by applying the above custom expression “${getHeader(AppDynamicsTag).substring(Int/3)}” to the HTTPServletRequest object and evaluates it to the following Java code: request.getHeader(“AppDynamicsTag”).substring(3)

Note: The purpose of the substring method is to exclude the NA= portion of the HTTP header.

Requests containing the same AppDynamicsTag header are grouped into the same business transaction. For example, all requests with an AppDynamicsTag: NA=Login header would be grouped into a Login business transaction.