4.2 Server compability with 4.1 agents and_or collectors
We are planning our upgrade to dynaTrace server version 4.2 from 4.1. However we have some questions:
Are there compability issues with any of the following configurations?
1. 4.2 dynaTrace Server, 4.2 dynaTrace Collector with 4.1 dynaTrace agents
This configuration will exist because in our production environment, we may not be able to restart the monitored processes (application pools, windows services) right away.
Will the agents still collect data with this configuration? Or will they stop collecting data? Was this configuration tested?
2. 4.2 dynaTrace Server with 4.1 dynaTrace Collector with 4.1 dynaTrace agents
We have overseas collectors that cannot be restarted due to various reasons. So these collectors may not get updated to 4.1. Will there be any issues under this configuration? Was this configuration tested?
Anyone have any insight? Should I log a support case for this instead?
This may be better documented in the 4.2 Release notes or 4.1 to 4.2 migration guide, but from my experience I can tell you that your option 1 is compatible because I fell in this scenerio and I think option 2 is compatible too. My Server and Collectors were at 4.2 and my agents were at 4.1 and I didn't have to restart any of the agents except for small number of applications on Windows and Linux (this was probably more of an environment issue on my end). The 4.1 agents should continue to work fine and when they do eventually get restarted, they will pull down the 4.2 files from the other components so there isn't even a need to install the 4.2 agent at all.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 