Tracing transaction
I would like to reproduce the issue and trace that paticular transaction alone in dynaTrace. How can I do it ?
Good news is that EVERY transaction is automatically traced by dynaTrace - of course assuming that dynaTrace is installed on your application. If that is the case you will get a PurePath for every transaction. If you found a problem in your app and you already have a PurePath for it you can now run the same transaction again (e.g: using your browser to access the same page, ...) - then you can find the PurePath of that transaction by e.g: finding it through the Web Request Dashlet or directly in the PurePath dashlet.
Does this make sense?
Thanks Andreas. I would like to know how would I filter-out web request for transaction I make in the browser.
If you have UEM (=User Experience Management) you can easily find your user/visit by the IP Address and from there drill to the PurePaths.
If you dont have UEM you can e.g: open the WEb Requests Dashlet for the given Time Period of your Request. Then find your request by its URL and then drill to the PurePath.
One last option you have is to enable "Always add dynaTrace header to response" which can be done in the Servlet and ASP.NET SEnsor. This will add an HTTP Response Header to every Web Request. If you have a browser that allows you to see HTTP Headers you can then look for the X-dynaTrace header. Copy that value. Then go to your dynaTrace Client and in the Tools Menu click "Search PurePath". Here you paste the value of the HTTP HEader and you will get to the PurePath.
Last option I can offer is to use our Browser Agent (in case you have the license for it). It will capture your browser activity as Browser PurePaths. More on that can be found here: Browser Diagnostics and Browser Performance Report
I would like perform a manual smoke test in the website parallel to testing performed by other user in pre-production. I don’t have web server agents/UEM installed
Just to let the community know: we had a previous email discussion about and now bringing it back to the forum
If you are running an HTTP based smoke test the best is probably to use our Load Testing Integration which allows your test tool to add an additional HTTP Header for each of your requests as described here: Integration with Web Load Testing and Monitoring Tools. You may already use this for your other pre-prod testing. What you can do however is to use different values for this HTTP HEader, e.g: use your own Timer Names for your tests.
Once this tagging is in place you can use the "Tagged Web Request" Dashlet which will show you all PurePaths that came in with these custom headers - grouped by e.g. Timer Name, Script Name, ... - from there you can then drill further and just analyze those PurePaths that you executed. More information on the tagged web requests dashlet can be found here: Tagged Web Requests
You may also want to look into this Load Test Overview Dashboard
