It is my understanding that in the old days of Dynatrace SaaS/Managed, if we want to an OneAgent to talk to Active Gate instead of directly to Dynatrace, we have to make sure we deploy Enviroment AG first before download the OneAgent installer.
Then afterwards, I remember I read that now, the OneAgent would periodically check if there is any new connected Environment AG.
BUT, what I experience now is that, despite a new Environment AG has been added for more than one week, the OneAgent deployed before AG is installed is still connected to Dynatrace Managed. Won't it try to connected to AG instead?
Based on my observation, it is almost instant (within a minute or minutes after the gateway has been installed). But I don't think the agent will reconnect immediately. Just new connections in case when agent gets restarted or the current connections drops will try the ActiveGates first.
Please validate if the gateway endpoints are added to the ruxitagentproc.conf to the [general] section (serverAddress) and if the gateway endpoint is there, check if the connection is possible from the agent host to the gateway port.
You are correct, the OneAgent is meant to pull from the Dynatrace Cluster a list of all available endpoints for connection. This list includes all Cluster Nodes, Cluster ActiveGates, Environment ActiveGates.
Every 5 minutes, every OneAgent is meant to review the list and decide whether a better connection point is available the following is a priority list (from highest to lowest):
Maybe there is a network/firewall issue forcing the agent to go directly to the cluster?
Wai, check in the ruxitagent_host_#.#.log file. It will tell you which connections it is attempting and which it has an issue with. You should see it at least attempting to connect to you EAG. The connection list is populated automatically as mentioned above.
If there is any doubt, restart the agent and watch it run through the start up connection attempts.