28 Mar 2018 06:41 AM - last edited on 30 Aug 2022 03:47 AM by MaciejNeumann
As many other post about connectivity we are receiving this messages now as a frecuent issue.
In the other posts about connectivity i read that this maybe cause the server process being monitored has no tcp port opened and/or low incoming network connections. If this is the case how can we managed this problems? do we need to threat them as real issues? is there any way to disable or adjust the thresholds for low connectivity timeframe?
thanks for your concern.
Solved! Go to Solution.
Yes those events are raised on host level and the settings can be found within the global Anomaly detection settings for infrastructure or on each individual host.
If you know that connectivity issues or packet losses within your network is typical you can of course raise the thresholds there.
If it's not an anomaly for your team, you should just document it for future research and increase the threshold.
We are receiving connectivity problems on our environment explicitly on webservers.
We are not clear how we can troubleshoot when we get problems created as "connectivity problem".
It doesnot show enough tracability and doesnot show any root cause unlike other problems.
Does not show it this has a real user impact as well.
Hence voting for enhancing this problem detection and analysis
Dynatrace doesn't support such analysis by it self. You should look at NAM (other product). This is proper solution for troubleshoot network problems. In Dynatrace you will see that is network problem, sometimes you will have info between wich components problem was detected. But for Webservers, generaly you should check metrics such packets retransmissions etc and talk with network guys about additional info 🙂