12 Feb 2019
02:07 AM
- last edited on
27 Apr 2021
05:12 AM
by
MaciejNeumann
In some of the dynatrace response degradation problems the root cause appears to be Network IO which many a times is around 20s - 50s. At other times it is under 1s.
Solved! Go to Solution.
This network IO is between what? app => DB, app => app2? There can be multiple reasons, network problems, connection pools etc.
Sebastian
Does the downstream tier involved in this IO time issue have OneAgent installed? Or is it an unmonitored host?
if it's unmonitored, does that mean it could be the processing time on the unmonitored host(s)?
If you are sending request to unmonitored host and it takes long time, yes it is possible that this is because processing on this host side. It may be network as well but it is not common to stay 20-30s on network (most of the time it is up to 1-2% of response time).
Sebastian
Featured Posts