14 Mar 2019 12:34 AM - last edited on 11 Apr 2023 01:41 AM by Karolina_Linda
Does Dynatrace have a duration limit for PurePath? In my case I have heavy SQL Select, which executed more than 5 hours - it contains several hundred bind values. I see only part of distributed trace (with 35 seconds response time) it does not contain my SQL request.
Previosly I had enabled bind value collecting, I saw distributed trace with 2.27 of response time, but when I tried to open distributed trace - I had an error.
Solved! Go to Solution.
The instrumentation has internal limits when it comes to getting instrumentation responses from the application. If you encounter such situations you are probably facing a corrupted purepath. The native oneagent part timed out while waiting for response from the monitored app. Thus the PurePath is not complete and becomes corrupted.
Currently, you cannot display corrupted PurePaths within Dynatrace UI. This should be available from 1.164.
Thank you for answer. What is current timeout? can i encrease this value?
That's internal and you have no control over it.