Common ID to group transactions across tiers
We are trying to group all the transactions across different tiers for debugging purpose, etc. So we are looking for an ID which is common across different tiers (web, App, Midtier, etc).
My questions is, since we have dynatrace integration, can we use any dynatrace ID to group these transactions across tiers. Some time i see some dynatrace IDs in the headers. Do you know if dynatrace pass any ID which is common across the tiers. Also if we have UEM, do you have anything using which we can group the transactions for each session across the tiers..if so we can look for these IDs in our splunk logs to correlate these.
From the way you worded the question, it sounds like you are trying to use something other than dynatrace to look at the transactions (grouped across tiers). Are you trying to look at the data using DCRUM? Splunk?
Maybe you can clarify a little more about what you are trying to do?
Hi Ryan,
We have splunk. But the problem is, say i have used "SessionID" to group transactions, it is valid only for web tier. I don't have this in App tier or Midtier. It would be nice to have single identifier across all the tiers. So it is easy to stitch them together incase of issues.
Actually i am looking to see if we can use anything from dynatrace. How does it track each purepath as it crosses different layers? Wondering if we can use the same thing to track all our transactions across tiers. Otherwise we might have to pass an common identifier across layers.
There is a PurePath identifier that dynaTrace "tags" to each leg of the transaction. Depending on how one tier talks to the next (SOAP, JMS, etc) depends on where/how dynaTrace places it's PurePath identifier (such as the HTTP header for SOAP and HTTP requests).
Looking at transactions as they execute across tiers and troubleshooting them is done automatically in dynaTrace (from the browser through al the backend tiers). Assuming that you know this already, it's curious why you are trying to view it in Splunk when it's already done for you in dynaTrace?
Thanks Ryan. Problem with Dyna is some times we are not able to see the post parameters and also we have Endeca as our search Engine which dynatrace does not support. So some times it is required to go into splunk for debugging high times...
You might try using the Endeca plugin that is available. You may be able to create some incidents in dT around the measures captured from Endeca, and send those into Splunk via the Splunk Alert Plugin. This may be able to provide some additional correlation within your Splunk queries.
Kevin
Nice!!!. I did not know that we have Endeca plug-in. i will use that. Thanks again.
