topic Re: Host not recognized after server reboot in Dynatrace Managed Q&A

Host not recognized after server reboot

stephane_kies — Mon, 16 May 2022 07:58:36 GMT

We had a maintenance and we have restarted several servers, after restart they were recognized as new host by Dynatrace.

How is it possible, it is very annoying as we have tags and specific alert for this host.

Is it possible to force the host unique identification to ensure that this kind of issue does not happen anymore.

Re: Host not recognized after server reboot

pahofmann — Mon, 16 May 2022 08:35:39 GMT

By default dynatrace determines the host identifier automatically and saves it to a file on the host. If that file is not deleted, the host should be recognized as the same one after a reboot, or even reinstallation of the OneAgent.

You could also change the way dynatrace determines the host id.

Re: Host not recognized after server reboot

stephane_kies — Mon, 16 May 2022 08:36:18 GMT

Thank you, I just checked and the file ruxithost.id has been updated after the restart, I do understand that it can be cause by environment change or clone as it is a VM.

We will reinstall the agent in deterministic mode.

There is not a possibility to activate this option afterwards, we need absolutely to reinstall it ?

Re: Host not recognized after server reboot

pahofmann — Mon, 16 May 2022 08:52:24 GMT

It can also be set via the oneagentctl command-line utility.