We are getting below error :
"Some data could not be collected or transmitted. This is most likely due to a resource congestion on network, host or process level in your monitored environment. (Error code: C2) "
We are getting data in purepath but missing some part.
Please suggest why this is happening ?
Please find below snapshot ,in that there is delay of 58 seconds between 2 calls .
Please suggest why there is delay ?
Thanks & Regards,
Solved! Go to Solution.
I saw a support ticket where the same question was asked; I checked the detail of the ticket and saw in both that case and in your case, you have calls to unmonitored hosts. This was support's response:
If the data is sent to an unmonitored host then that explains why you see this message on the service level. The Agent is trying to collect the data from the receiving side which is unmonitored and couldn't so it shows the message. In the future, we are implementing improvements regarding these messages so you can understand them better.
Requests to unmonitored hosts are requests to host on your network that are not instrumented with a OneAgent. You will get the URI and response time of the request, but if you want more details you have to instrument that host with a OneAgent as well.
your answer could be misleading.
I accept that for corrupted purepath "request to unmonitored host" is one of the reason but not the only reason. It can also be broken due to resource congestion on network, host or process level This message has been recently added in Dynatrace for better explanation to the customer.
I can share my experience on this topic, given that I'm facing regularly with this issue. I found another "entry point" which allow me to get all my purepath from ASP.NET (which was initially corrupted or unmonitored). How did I handle it ? I took my purepaths in error from Outliers and was able to aggregate them thanks to host , then I ran through process where I could be able to click "on consuming process" and selected the main process (WCFHosting.exe) and made a CPU breakdown.
Thus, I sorted out my purepath again but this time I got .NET methods and with a backtrace I went back up to ASP.NET which was not in error.
I think there are few problems with web request ID during IIS processing, or maybe internal pre-configured Oneagent timeout.
If someone have more information, thank you in advance.