LoadRunner script converter related issue
We have converted our LR scripts using the dynaTrace script converter utility and we see that the header elements are added correctly (in the HTTP request, i see the dynaTrace header added). However, when we execute the scripts, i don't see anything in the "Tagged Web Requests" dashlet and I was wondering why? We see the PurePath data collected.
The script contains a simple web_custom_request call (LR API) and this function is supported by the converter as per the dynaTrace documentation. we have converted the scripts many times in the past and have never faced this issue earlier.
So under what circumstances will it not appear in the "Tagged Web Requets" dashlet even though converted scripts (dT header) are being used?
Any suggestions or feedback is much appreciated.
Jigar
The only explanation I have for this is if there is any component between LR and the AppServer that removes these headers, e.g: a Proxy, a Web Server, ...
Check one of your PurePaths that you know has been created by the LR script. Open the details dialog of the Entry Point node (Servlet or ASP.NET). There you should see a value in the HTTP Tag field. If you dont see anything there it means that the HTTP Header didnt make it all the way to the AppServer
Andi
Thanks Andi for the prompt response.
Yes, I did look at the HTTP tag for the entry point node- doPost (servlet) and I didn't see anything there (screenshot attached).
Are there any workarounds or alternatives to overcome this? I understand that the header is removed by one of the component prior to reaching our instrumented server but i was wondering if there is any other we can get the same information ("tagged web requests")?
Thanks again,
Jigar
We actually support two HTTP Headers: "dynaTrace" and "X-dynaTrace". I think our LR header file uses "dynaTrace". So - you may want to edit our code that sets this header and change the header name to "X-dynaTrace". Headers starting with "X-" are more likely to pass through any proxies.
If that doesnt work either you need to figure out how to configure your infrastructure to let this header through - it is the only option we allow for tagged web requests
Thanks Andi. The header name was already set to X-dynaTrace (by the LR Script Converter)
web_add_header("X-dynaTrace", headerValue);
Anyways, thanks again for your suggestions.
Jigar
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 