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.
Up to 10 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.
Feb 12, 2019 at 04:53 PM
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).
Feb 12, 2019 at 12:36 PM
This network IO is between what? app => DB, app => app2? There can be multiple reasons, network problems, connection pools etc.
Check updated libraries and support added in the latest NAM service pack.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET
Answers and Comments
36 People are following this question.
What is IIS modules as the root cause?
How to turn a String Session Property to Long Property?
PurePath availability resiliency in Cluster failure condition
User Tagging issue with languages
How often is the user session data sent to Elasticsearch?