"Dynatrace OneAgent has been updated" notification

[dantonag]

Hello,

on our Dynatrace instance this message is appearing:

What does it mean, exactly? That the OneAgent process should be restarted?

Thanks

[justin_hogue]

Hello,

That's telling you that you'll need to restart some of the processes that the OneAgent is monitoring. Monitoring of the processes shouldn't be impacted, but for the processes to pick up the new version of the OneAgent a restart is needed.

Hope that helps,

JH

[suresh_sssu]

Hi JH

Is the 'restart process' only solution ? It becomes difficult to restart the pods/process to restart in prod environment,  every time OneAgent gets updated. 

Thanks

Suresh

[DanielS · Accepted solution]

Hi, I show you a detailed example

1. If you go to Deployment Status
2. then OneAgents and select a server as example
3. here Dynatrace indicates you that you still have the monitoring activated for a process on that server but is using an older version (1.175.270 for this example)
4. Here is the process from 3. In this case Apache Tomcat, an DT indicates you that if you restart this process you get and updated version for that particular process, if you restart the Apache, 3 and 4 messages would disappear.
5. ADDITIONAL INFO. Here you can see that a newer version of the agent has been released. And you have an older one on that host.
6. ADDITIONAL INFO. As you can see in 5 this is your current OneAgent Version, but this is available even if the detail is collapsed.

[dantonag]

Hello,
I think the backend processes have been restarted, but Dynatrace is still showing the attached message. What do we have to do?
Thanks

[DanielS]

If you already restarted the processes only click on the "x" on the yellow box.

Because if you click on the pull down "v" you can see the detail of the processes pending to be restarted. (see the example below)

[ayamaya]

Is it possible for these processes to restart automatically?

[NicolasT]

This is not a correct solution. We should have a real event that can feed Davis.

In my corp, we had issue with big simultaneous auto update (massive IO usage on datastorage array)... If there has been an event triggered, it should have triggered Davis.

[alicia_pepper]

We strongly suggest this RFE: Create New Informational Problem Type - Dynatrace Community but we would have MAJOR issues with DT forcing an auto restart for the processes as this could cause other concerns/issues.