Pure Path Data

Hi,

We're having an interesting problem in DynaTrace.  We have the following 3 system profiles setup in our environment.  All of the applications run on the same WebSphere Application Server.

Dev App 1 Profile - contains a group of JVMs/applications that handle its business functions.

Dev App 2 Profile - contains a group of JVMs/applications that handle its business functions.  

NOTE: App 1 and App 2's businesses are totally different.

Dev Settlement Profile - contains a group of JVMs/applications which handle the settlement of transactions sent by App 1 and App 2.  The Settlement group of JVMs/applications also contain their own set of business functions.

Example:

App 1 handles a transaction in its boundary and then puts a message on queue and an application in the Setttlement system profile listens to that queue and processes the settlement portion of the transaction.  If everything goes right, an ack is sent back to App 1 to denote a success.

Issue : RFH2 Header enabled and missing pure path in Settlement.

Because of the use of queues and several JVM hops in our business transaction, we've been instructed to append the RFH2 Header on the queue.  This allows DynaTrace to use the same purepath tag ID and stitches together a full round trip of our business transaction.

In App 1 and Settlement's case: App 1 starts a new transaction (pure path TAG ID is constructed in App1) and puts a message on a queue that an app in the Settlement system profile listens to and the Settlement app processes it.  The problem is the pure path data of the Settlement app is being housed in the App 1 profile.  

Meaning, we are seeing the pure path data of the Settlement application (processing of App 1 message sent) in App 1 System Profile.  But when we look at the Settlement Profile, there is no pure path data available as if nothing was ever processed.

Ideally, what we would like is to see the pure path data in both the App 1 and Settlement System Profile.  If that is not possible, then we would want to the pure path data housed in the Settlement System Profile since it is a function of one the applications in Settlement.

FYI - If we disable the RFH2 Header, the pure path data is housed in their respective system profiles but that isn't a true reflection of the full end-to-end business transaction.  App 1 starts a new transaction (new pure path TAG ID) and when it puts the message on the queue for the Settlement application, a new pure path ID is created.  Meaning the transaction is not stitched together. 

Is this possible in DT?  I hope this is clear.