During a disaster recovery test, we have stopped our Dynatrace Managed Cluster. As a result we encountered issues on all hosts with OneAgents installed. All processes showed a lag and in the various logs we could see connection attempts to the ActiveGates and Dynatrace Managed Cluster. As a consequence we decided to stopp all OneAgents. However, the processes continue logging and trying to connect to the ActiveGates and the Dynatrace Managed Cluster.
Has somebody experienced a simlilar behaviour and has a solution?
Thank you for this information. We already guessed this.
Currently we use Nagios in parallel. We discovered the behaviour when the checks of Nagios for the processes of the application resulted in timeouts. So it appears this has a negative effect. We are not sure if our application users also experience lag.
So the questions are:
- Why does this affect the checks made by Nagios?
- Do the application users also experience delays?
- How can we prevent this from happening?
Nagios executes a Python script which issues the following for the Java-Processes:
java -cp /opt/sense/server/communitynode_tomcat/lib/sensecommonlib/h2-1.4.197.jar org.h2.tools.Shell -url "jdbc:h2:file:/opt/sense/atnaCache/cn/logging;AUTO_SERVER=TRUE" -user sense -password sense -sql "select * from public.messages"