Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Connect 7.0 Agent to 6.3 Server?


We have a 6.3 dynatrace server and want to migrate to 7.0. We have a lot of 5.6 Bootstrapped Agents currently online (about 100-200).

We plan to upgrate alle the agents to 7.0 at first and then migrate the Appmon Server from 6.3 to 7.0 Ist this possible?


Dynatrace Pro
Dynatrace Pro

Hi Kay,

[Edit: No, see answer below also], see:

Because with 6.5 and higher, the 5.6 bootstrap agents were desupported (although technically still working, but may not be true for all future releases).




On the Links there it is not mentioned that this is possible. In our first test it looked that it is possible event if its not supported as mentioned in the links.
So additional what is better:

Agent 7.0 --> Collector 6.3 --> Server 6.3
Agent 7.0 --> Collector 7.0 --> Server 6.3

Sorry Kay,

I misread your post. The server has to be upgraded first! So:

Server 7.0 -> Collector 7.0 -> Agents 7.0.

Which is also the order in the upgrade guide.

Best regards, Thomas



we hoped it would work in general, because it was working for one agent. 7.0 bootstrap took the 6.3 agent from the server/collector

2017-10-11 08:12:56 [ba96b8cc] info  [native] High-resolution POSIX timer detected.<br>2017-10-11 08:12:56 [ba96b8cc] info  [native] Detected application server: BEA/Oracle WebLogic
08:12:56 [ba96b8cc] info [native]
08:12:56 [ba96b8cc] info [native] dynaTrace Agent for Java Copyright
(C) 2004-2015 Dynatrace, <a href=""></a>
2017-10-11 08:12:56
[ba96b8cc] info [native]
2017-10-11 08:12:56 [ba96b8cc] info [native] Version ....................., build date Apr 14 2017 20:42:02, svn rev. 715610
2017-10-11 08:12:56 [ba96b8cc] info [native] Command line is /opt/soa/jvm/rt_PERM02/bin/java -Dweblogic ...
2017-10-11 08:12:56 [ba96b8cc] info [native] Build platform .............. Linux x86 64-bit
08:12:56 [ba96b8cc] info [native] Platform .................... Linux
4.4.49- x86_64
2017-10-11 08:12:56 [ba96b8cc] info [native] System startup time ......... 2017-09-15 05:04:33
2017-10-11 08:12:56 [ba96b8cc] info [native] User name ................... wlsadmin
2017-10-11 08:12:56 [ba96b8cc] info [native] Bootstrap version ...........

This is the expected behavior, the bootstrapper gets a version that is known to be compatible with the collector, even if it means downgrading.

Note that operating higher version agents with lower version collectors and servers is not supported - this is not tested and not recommended.

Any reason why you would want to upgrade the Agents first? The other way around is very well tested, covered and documented, as it is the usual upgrade scenario.


Okay, the reason is that we somewhere read that 5.6 Agents ar not compatible with 7.0 Server and Collector. We can upgrade the server at first, instant to 7.0.

We are not 100% sure. Can we use the 5.6 Bootstraped agent to connecto to 7.0 Server and 7.0 Collector?

5.6 Agents are compatible with 7.0 servers and collectors. See also here:

Notice that however the 5.6 (and older..) bootstrap agents need to upgraded to be supported - but they should work nevertheless, see:

Please follow the migration guide in the correct order:

It walks you through all the steps in the correct order and contains all the info mentioned here.

Best regards,