Instrumentation channel disconnected - server did not reply to ping request
Is it possible to prompt the agent to ping the dT server again in order to establish the instrumentation channel?
Regards,
Anoh Brou
In our case though the agents are up (connected), we are not able to see certain metrics like webrequests, purepaths...
Can you please let me know how to proceed further on this...
Hi Grabner , how can we resolve this kind of issue, is there a way to alert users/admins about this issue?
The only way to resolve this is to make sure the collector is started + reachable from the agent and then restart the JVM or CLR. The agent should then connect and start delivering data.
Alerting is tricky, because the problem is that the agent has no connection to the rest of the dynaTrace infrastructure. It is written into the agent log file during startup thou...
Best, Roman
The dynaTrace Agent - once connected to a Collector - will retry connecting to the collector in case the connectdion is lost. That is default behavior. But - it is the Collector that it connects to and not the server
Unfortunately the agent could not connect to the collector at midnight since the collector was being restarted. I checked the log file and the agent has not tried to connect since.
If the agent doesnt get a connection during startup (within the first 60s) then it will not try to reconnect
Is there any daemon that can be started without restarting the agent itself to remedy this situation?
There is no daemon approach. The Agent needs a connection to the Collector during startup. There are some critical tasks that can only be done during startup of the JVM/CLR. If the agent doesnt get a connection to the collector it cant wait forever as this would block the loading of the application.
