Hi,
We see information point monitors total time itself part of target class and method, however the total time includes time spend on sub calls for synchrnous calls only, as there could be some sub calls in your case that are async that is separate thread initiated whcih is not tracked as expected.
However, we suggest to try BT on same API and method as we collect End-to-end response time including time spend on methods in async thread part of BT as referred in feature doc as part of business transaction detection as in below doc, also refer waterfall view to get end to end time in snapshot for total time that includes async time spent as well in UI:
https://docs.appdynamics.com/display/PRO44/Asynchronous+Transaction+Demarcators
OR define separate Information point on same sub thread initiated asynchrnously to track other API response time.
Hi,
We see information point monitors total time itself part of target class and method, however the total time includes time spend on sub calls for synchrnous calls only, as there could be some sub calls in your case that are async that is separate thread initiated whcih is not tracked as expected.
However, we suggest to try BT on same API and method as we collect End-to-end response time including time spend on methods in async thread part of BT as referred in feature doc as part of business transaction detection as in below doc, also refer waterfall view to get end to end time in snapshot for total time that includes async time spent as well in UI:
https://docs.appdynamics.com/display/PRO44/Asynchronous+Transaction+Demarcators
OR define separate Information point on same sub thread initiated asynchrnously to track other API response time.
