A- Old server name
B - Old collector name
C- NEW SERVER name
D- NEW collector name
A, B are windows 2008 C, D are windows 2016
My task moving dynatrace set up to new 2016 servers
1. I have migrated all server config and collector config using migration command new collector started reporting to new server nicely.
2. Now I need to change all my collector name manually in all my application servers then restart to point to new collector C which is reporting to server D
2.1.Instaed of the above step, I have made new collector point to old server A for a while. So new collector C got added to collector group list which is used for load balancing.
2.2.All agents now having new collector name C in their collector list. B and D both in ACC collector.
2.3.Now I have stopped all servers , collectors.
2.4.I made new collector again point to new server by editing server name in that collector config file.(now old server is shut down)
2.5.All agents anyways reporting to new collector now. Now old server ,old collector are shut down. All agents report to new collector.
New collector report to new server Migration to 2016 successful
But my question here is whether agent will search for old collector when it get restart again.
Should I really manually change the collector name . what is mechanism behind it.
Agents wont have any problem, if actually configured servers are shut down?.
And will it get connected to new collectors which was in group
Thanks a lot in advance Please reply asap ,
because I need to manually edit if above trick does not work
IN SIMPLE WORDS 1.Changing the JVM srart up parameters ContextFactory -agentpath:/u01/app/dynatrace/dynatrace-6.1.0/agent/lib64/libdtagent.so=name=Weblogic,server=BBBBB:9998 2.collector list file in /u01/app/dynatrace/dynatrace-6.1.0/agent/conf/ collectorlist.ACC Though BBBB is no more. Will agent ll connect to all other collectors in collector list
Answer by Kyle K. ·
Provided the agents are connected to the system and have an understanding of the collector group it will try to access what we have defined in the agent path first, if that fails I believe that it will look at your collector list. For an agent that was disconnected before it has an understanding of a collector group you would have to manually point it to a new collector in the group for it to pull down a new collector list file.