When the Dynatrace/NeoLoad integration module is configured, starting a load test in NeoLoad displays the test requests in Dynatrace.
The requests are stored in the recorded session (see the Stored Session Details section in Dynatrace user interface). The naming format of your session is "NeoLoad-<project>-<test name>-<system profile name>" as described in the example below.
The HTTP headers of the requests include Dynatrace parameters:
VUis the unique identifier of the current Virtual User instance.
VU=0and second one with
PCis the name of the NeoLoad web page.
index.htmlwhich requests many CSS, PNG, JS, etc. resources, all the request resources are executed with
IDis the NeoLoad unique identifier of the request.
50), both Virtual Users execute the request with
NAis the NeoLoad name of the HTTP request, as it can be seen in the NeoLoad Virtual User tree.
SIis the Source ID that can be used to identify the product that triggered the request (e.g. WLT (WebLoad Testing), PE (Private Enterprise), BB(Backbone), LM (LastMile), etc.).
GRis Geographic Region, useful only for the Private Enterprise solution, filled by the name of the Zone, as specified in the NeoLoad project (Runtime view).
SNis Script Name. This groups a set of requests that together make up a multi-step transaction like buying an article.
SN=Virtual user name.
TEis TEst Name. It is the name of the entire load test - it uniquely identifies a test run