Load Testing Integration. Way to group multiple requests in one transaction.

[istakentwice]

I am trying to figure out how to configure Dynatrace in such way, that several requests would be combined into one transaction, and make Dynatrace track and measure such transactions.

Why we need this:

In performance (load) testing we usually do not work with particular requests, we measure response time and performance of groups of such requests (transactions) that represents singular user actions.

For example. User clicks a button, that loads different page - several request are being sent to backend - but it is a singular action from user pint of view, therefor whole exchange with backend should be measured as one.

On load script level

TG01_HomePage:
	Request_01
	Request_02

(how it looks in JMeter)

So I am looking for a way to make Dynatrace measure and show "TG01_HomePage" response time as sum of "Request_01" + "Request_02" response times.

I have tried to achieve that using request attributes and naming rules.
I have marked all the requests within transaction with the same attribute, and then applied singe naming rule for all requests that have such attribute.
So, in "Transactions & Services" -> "View Dynamic Requests" I can see these tagged requests being combined in groups (that represent transactions in load script).

And in "top web request" I can see breakdown with statistics for each particular request within transaction.

But.
With this setup, Dynatrace do not calculate response times as sum of response times of requests within.
Is there any way to make Dynatrace treat such multi-request transactions as one entity?

Would appreciate any guidance,
Thanks.

[Yosi_Neuman · Accepted solution]

HI @Juhan R.

Did you try web request naming rules for that.

Request-naming rules enable you to change how requests are grouped together in charts, baselining, and performance analysis.

It should do the trick.

Yos

[timothyyara]

@istakentwice - Did you ever find a solution for this? While a request naming rule will help you rename a few requests, it won't "group" them in the way you talk about it(from my understanding).

I have a similar use case for a customer and I am still working towards a resolution here. The use case is that they have say 2-4 top web request rules and they ultimately want to "group" or "daisy chain" the requests to have what they call a "successful" business flow (don't mistake this for Dynatrace Business flows). While we can mark them into Key requests, and request attributes, and set up a rule for the requests to be in a single web request rule, it doesn't give the granularity they need to understand the flow.

A thought might be to use traces on Grail, some kind of "bond" to hold the business flow together like a JSession:ID (this is a java app), and then do a few lookup/join commands in DQL but it's all a theory at the moment. 

TYara