AppD Archive

Monitoring LoadRunner Transactions

CommunityUser
Splunk Employee
Splunk Employee

Following the recent blog post by JK I was looking into setting up our AD instance to monitor the load runner transactions from our performance tests.

I have added the headers vto the LR scripts and created the custom rule to pick up the LR transaction names from the headers. I can now see the transactions appearing in the controller. All is good. Except...

In some cases we are seeing duplicate Transaction names in the Controller with different underlying calls.

Some of our LR transactions call URL's which have rediects in them and what seems to be happening is as follows

Load Runner Transaction LR1 calls URL A - Which points to a .net Node called XXlogin
This then redirects to another URL B which is running on another .net Node called YYWEB

This then calls a 3rd URL C on the same node YYWEB.

WHat we see in the controller is 2 Business Transactions called LR1.
But when you view the transactions one has the call information for the calls to XXLOGIIN    (URL A)

and the other has the call information for YYWEB (URL B and C)

Is there anyway that we can get this to apear as one single transaction and have the completem call flow in one place?

I have looked at Grouping the Transaction however this just creates a layer above the 2 transactions and you still need to view the flow diagrams for each one seperately.

I would like to be able to show them as one Transaction and flow diagram showing the call to the 2 different nodes

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

@pjohnson...one silly question. By any chance XXlogin and YYWEB nodes are in two different tiers? If they are, you will have two different transactions with same name. I saw this in our environment.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I'm a performance tester with good experience with LoadRunner but very new to App Dynamics.

I'm in a simlar situation as above, just not as far along.  I've made the request for the change to have the custom rule created but the apps that we're preparing to test are new and have not yet been intstrumented. 

What I'm hearing you say is that there's no way to properly correlate a LoadRunner transaction to an App Dynamics BT because where Loadrunner groujps all associated requests into one transaction, App Dynamics individually tags the requests so that the appear as being separate.

As I said, I'm new to App Dynamics but I would really appreicate having this cleared up.  Feel free to direct me to any info regarding this that i might not have already come across.

Thanks.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...