Timed Out PurePath
We are fairly new to Dynatrace and recently received the alert below which we are not sure what it means and what would be the recommended steps for looking into it. We we can get some guidance it will be appreciated. Thank you
Timed Out PurePaths indicate that either a transaction is stuck or exceeds the PurePath completion timeout. This incident is closed after there are no timed out PurePaths for a certain timeframe (default is 1h). |
Hi Juan
It means that you have PurePaths that take longer than our default timeout. After 10 minutes we let a PurePath timeout - that means - a request that still executes methods but that doesnt complete within 10 minutes is something that we do no longer actively wait for. It might not be a bad thing - it could be that you simply have some very long running requests running. But - it could also mean that you have some requests that take unusually long.
The best way is to drill to the PurePath Dashlet from your Incident. Then sort the list of PurePaths on the Duration Column. You will see those that timeout on the top. Looking at them will tell you which requests these are and then you can figure out whether this is something
a) that you want your team to address because they shouldnt take that long
b) something that is OK -> in that case you have multiple options such as configuring dynaTrace to not capture these PurePaths; or extending the timeout limit
c) you find out that this is a purepath of a batch job process that you have manually configured via custom sensors to capture. In this case it is possible that you need to rethink the Entry Point method and maybe choose a different entry point for this purepath
Andi
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! 