3 Replies

Kevin, do the PurePaths have same PurePath duration? URL? You can create a business transaction that only looks at Tagged Web Request that take longer than a few ms or create a view that filters on the tagged web request of the get URL.

The issue as I understand is becuase LoadRunner tags the POST request, since LoadRunner actualy does the submit, then the application code processes the POST data and submits a Redirect (GET) when displaying the PAGE, the Redirect maintains the same LoadRunner tag name but since they are both considered as PurePaths I get Two Purpaths that I would prefer analyzing as a single PurePath since from a users experience the simply clicked a submit or continue button.
Also the additional issue is we are comparing results from LoadRunner with DynaTrace, but Dynatrace provided two durations for what LoadRunner shows as one duration.

Although we may not be able to stitch these together as our tag is not being represented we can split them apart.

In this screen I filter on the right hand side for those transaction that contain the API "JDBC", these are the non-redirects.

On the right hand side I filter on the transactions that are part of the created BT "No SQL" which are purepaths that have a low warning threshold of 0 SQL Statements(count). These are the redirects which never contain SQL.

You can also use the "Analyze Load Test Results" default dashboard in the "Start Center" under "Analyze Performance". Edit the dashboard filter to include only transaction with the API "JDBC".. This is shown below.

Your answer

Hint: You can notify a user about this post by typing @username

Attachments:
Up to 5 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.