Load Runner script is caputuring dynatrace monitoring requests
While I am trying to record load runner script, I see dynatrace monitoring related requests are also being captured. I am trying to understand what does it signify to us.
Here is an example of how request is being captured for a login transaction.
"Url=/login/dynaTraceMonitor?a=1%7C_load_%7C-%7C_load_%7C1396846141273%7C1396846142633%7C65%2C2%7C_onload_%7C-%7C_load_%7C1396846142616%7C1396846142632%7C65$fId=362941274_546$rId=RID_-1638294187$rpId=1515326124$dtV=5203$title=Channel%20Secure%20Login$domR=1396846141996$w=1276$h=839$time=1396846147632$",
This is the data that our JavaScript agent sends back. The JavaScript agent is the component responsible to capture Page Load Time, JavaScript Errors and other things in your browser. It is part of UEM (User Experience Management). If you record a scdript with Load Runner you will obviously get these HTTP Requests recorded as well. You should however EXCLUDE the /dynaTraceMonitor URL from recording a Load Runner script. Why? Because when you replay a LoadRunner script you typically do HTTP-based Load Testing and you do not want to have the UEM Data replayed from your recorded session. In case you replay your Load Runner script with the Browser-based reply you would get the UEM data anyway as our JavaScript agent also gets loaded into that browser.
So - either re-record the test script but make sure to not recorded this type of URL patter - or - delete these lines from your already recorded script
Andi
Earlier login transaction was taking only 2 seconds but now its taking 4 seconds. so does it mean additional time is contributed by this JavaScript agent. and if we turnoff dynatrace monitoring completely I won't be seeing this additional time?
I dont think these two are related unless Load Runner tells you that this is the URL that consumes most of the time.
Load Runner should be able to tell you exactly which requests are taking longer - have a look at their reports. Then go to dynaTrace and either open the Load Testing Dashboard or go to the Tagged Web Requests dashlet. from there you can analyze why Login takes that much longer.
