First, make sure the node name is not already registered with the Controller using the same hostname. If it is, you can: Change the node name to a unique name Set the APPDYNAMICS_AGENT_UNIQUE_HOST_ID Environment Variable to proide a unique host name for the system the agent is running on. If the node name is NOT already registered with the Controller using the same hostname, check the node associated with the warning. If you can confirm the snapshots are collecting on the current node, and observe the expected agent uptime, it could be the issue is instead related to a hold-over from the node's registration on the Controller for identification. If your monitoring is working as expected, the warning itself can be ignored without resulting in any issues ... View more