Asynchronous invocations versus elapsed time disparity
When looking at purepath, we can see number of asynch calls being made to different webservices. However, the "elapsed time" reported in DT increases as if the calls were executed one after the other, is this a known bug?
The "Elapsed Time" column tells you when this node was created in relation to the start of the purepath. Looking at this screenshot tells me that you make 3 different async SOAP calls. The first starts after 526ms, the second after 724 and the third after 1026ms.
So - my first throught is not that this is a bug in dynaTrace - but that your app is reallying making these calls sequentially.
Looks like you're using the tagging ADK here. Is it possible the call is configured to be detected by dynaTrace as "asynchronous" despite the application actually working synchronously?
Check out this doc page and search for "asynchronous" to see the various signatures of linkClientPurePath():
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 