Running a newer version of OneAgent with an older version of Dynatrace Managed

[gchastne]

I thought I'd seen something in the documentation on this, but couldn't find it.

We have a situation where support are recommending that a problem we have is fixed in the latest version of OneAgent. Due to our normal release cycle we aren't at the latest and parallel version of Dynatrace Managed.

What are the rules around running a new version of OneAgent againsts a slightly older version of Dynatrace Managed? Does the same apply to ActiveGate?

[AntonioSousa · Accepted solution]

@gchastne,

Interesting scenario. Not sure if anyone has experienced with this, but I would say it is an unsupported scenario. I would not do it in a production environment. While most of the things might work, you might encounter very strange situations.

I would stick with Support on this one.

[PacoPorro]

Honestly, I've never been in such a situation. Usually, the cluster has controls to talk to supported agents and if the version is not in the list of active versions, the cluster rejects information from the oneagent. 
Agree with @AntonioSousa stick with support.

[Peter_Youssef]

Hi @gchastne 

through cluster update UI, you can exclude specific versions of Dynatrace updates and keep the required updates for Oneagents and activegates

for oneagent updates 

for AG, you can disable the automatic update to proceed most stable versions

under cluster API V1 you can create a token with the below scope to decide the update preferences 

Thanks

[Peter_Youssef]

Hi @gchastne 

for environment releases you can find it under environment api v2 

but you can only view it, no option to execute post.