Tagged Web Requests Don't Show Up
Has anyone had trouble with Tabbed Web Requests not showing up in Dynatrace?
I've created a test script in Load Runner, saved it, and ran the Load Runner Script Converter on it in Dynatrace. Nothing shows up under Diagnose Performance, Tagged Web Requests regardless of what time frame I select.
This worked during our session with Steve from Compuware but then stopped working toward the end. We didn't have time to troubleshoot it.
Here's a snippet from the Load Runner script with the Dynatrace header:
addDynaTraceHeader("NA=;PC=Windchill");
web_url("Windchill",
"URL=http://server.facility.companyname.com/Windchill",
"TargetFrame=",
"Resource=0",
"RecContentType=text/html",
"Referer=",
"Snapshot=t1.inf",
"Mode=HTML",
EXTRARES,
"Url=/favicon.ico", "Referer=", ENDITEM,
LAST);
lr_think_time(20);
Regards,
Jerry
One thing that you can check is that dynaTrace is capturing the header values in the sensor configuration of you system profile.
if the headers values are not being captured then I believe that can be the reason you might not be seeing the tagged requests.
Make sure that no component between your load runner agents and the application server where you have dynaTrace is installed will remove the custom HTTP Header that our integration puts on the HTTP Requests. We add a header with the name "dynaTrace" or "X-dynaTrace". This is the header that dynaTrace will parse in the Servlet and ASP.NET Sensor Pack. If this header is present the Tagged Web Requests Dashlet will show these names. If the headers are not present - or maybe removed by a component in the middle this integration will not work
Thanks for the help guys. It's appreciated. I imagine I should be looking at the sensor configuration for our Windchill method server; however, I'm not sure which sensor pack's properties I should edit or if the correct sensor pack has been installed:
To follow Jacob's recommendation, edit the "servlets" sensor. Use wildcarding * to configure DT to capture any/all header fields.
After making this change, run some LoadRunner transactions. Then drilldown into a PurePath for one of the transactions. Right-click on the servlet node in the PurePath (probably the first node in the PP tree) and select "details". This will show all the details for the servlet execution. You will see all the captured headers in the details.
Look through the headers to see if the DT tags from the LR scripts are getting passed into the application.
hi Jerry,
as the documentation states (https://apmcommunity.compuware.com/community/display/DOCDT50/Integration+with+Web+Load+Testing+and+Monitoring+Tools), the timer name (NA) attribute is required. so it must not be empty, as it is in your snippet.
i'm pretty sure that setting it to any value should solve your problem.
best,
Christian
and for the sake of completeness: the capturing of header values is not required for this at all, it just may help you to see which headers are finally set.
so changes in sensor placement/configuration won't affect the behavior of tagged web requests, as long as you keep the servlet sensor placed and starting PurePaths.
Gentlemen,
Thank you very much for the assistance with tagged requests. Christian's suggestion proved to be the solution I was looking for.
Best Regards,
Jerry Goldsmith
