Multiple Method Calls Within Same PurePath

Hi Frank,

Working together via email I believe we've got you set, though I agree it's not the most intuitive thing ever.

Here's a cleansed image based on the session you sent to me via email: one PP, with 5 calls to a method using 5 different values for arg 1, with ExecTime values computed per arg value. I edited the BT to get the results you wanted:

Here's a wrap-up for the forum.

The key was to create a "Calculate Results" return value/measure for the BT. This return value should be the same as the "Split" BT criterion. That is, it will be a "Business Transaction Evaluation/Filter/Grouping Values - Argument Value" measure. Just exactly like the splitting measure, to start off with.

The difference is that you need continue on to the "Details" tab of that measure definition, go all the way to the bottom, open up the section that says "Transaction", select "Grouping value", and pick the value of interest - in our case "Exec Time":

 
After doing that, we're now able to compute different Exec Times for the same methods executed multiple times on the same PP, grouped by an argument to that method, as shown in the image above.
 
Whew.
 
Rob
 

We've got this working now. Hopefully this will be useful to other folks searching the forums for help. This was a definite need for us and I'm thankful to this forum (Rob especially) for helping to get this working. Hopefully Dynatrace will make this a bit more intuitive in future versions of the product. At least in our company we expected the Avg Time to calculate with the method execution time and not the entire Purepath time. Also, make sure that you choose "Reanalyze Purepaths" after you finish modifying the transaction.

Hi Frank,

I wish I could help you out, but creating a measure or business transaction for tracking the execution time of a particular method, conditional on the value of one of its arguments, isn't possible. I'd be happy to be wrong here, but I don't think I am.

As you noted, you can get close by splitting on the argument, but then you end up with PurePath time, or execution time of all invocations of your target method, but not with the execution times differentiated by the argument value.

If it's critical for you to get this info, there is a way to do it. As an easy way where you don't have to change the Calculate code, you could create a new "wrapper" method called CalculateWrapper with the same signature as Calculate and replace your calls to Calculate with calls to CalculateWrapper. In that wrapper method, you check your string argument and call a specialized method (like CalculateConsultingRevenue), which then does nothing more than call Calculate("ConsultingRevenue"). Now you can have measures that track all of the indivual specialized methods, and you'll know how much time is being spent on each one, and how many times they're being called.

I hope this helps some,

Rob

Frank. Is it possible to export one of your PurePaths and send it over to me? Either attach it to this forum or send it to me via email