Split by Number of Method or Database Invocations per PurePath
Is it possible to split the BT based on the number of invocations of a specific method or database executions? For example, I have a stored procedure in which the number of times it executes tells me something specific about that transaction. I would like to see split response times results for purepaths where the procedure is called once, twice, three times, ect. I don't seem to be able to add the invocation type measures as a splitting BT measure.
I would like to do this as well, but I want to cover between 1 and 100 invocations. Is there a way to batch create the measures for the filter?
Hi Mark
Can you let me know more about your use case? would you want to do this in testing? dev? or even in production?
Thanks for the responses, this is very helpful.
Hi Alan,
There's a little more effort to getting the "exactly X" behavior and I want to make sure Andi's answer is clear. As Andi mentioned, you'd create a number of BTs such as "Exactly 1 MethodX call", etc.
For each of these BTs, you need 2 filters, not just one. If you put in one filter with a threshold of 2 (for example), you'd get PPs with at least two calls. If you want exactly two calls you need two filters, one with an Upper Bound of 2, and one with a Lower Bound of 2. For example, here's a BT that filters for exactly two calls of a method executeMethod with a particular signature. There's a screen shot of the BT definition, and then screen shots of the two FILTER measures I created to make this work. Hope this helps.
BT definition:
Upper Filter:
Lower Filter:
Example run:
Example PP showing two executions of executeMethod with desired signature:
Thats correct - we do not allow splitting by these types of measures as you can easily end up with a lot of different measures as you cann have a lot of different values for e.g: DB Invocations
The approach in your case is to create several Business Transactions, e.g: "PurePaths with 1 DB Call", "PP with 2 DB Calls", "PP with 3 DB Calls", .....
These BTs use a filter measuer to only filter on those PP that have exactle a certain amount of DB Calls.
