07 Jun 2021 01:01 PM - last edited on 28 Sep 2022 02:29 AM by MaciejNeumann
We have the following problems with KVM-type virtual machines, it happens that we are duplicating this type of machine a lot, and we cannot square the list of hosts that have the agent installed.
Apparently these KVM machines only use them for a few days, they report to Dynatrace, and then they no longer occupy them, the host changes state to "unmonitored", then changes to "lost" state, and they continue to generate other new KVM machines, Apparently it is something dynamic, but we are getting clutter in Dynatrace, at the moment we are disabling all the hosts in "Lost" status by console, and it is getting complicated because we are talking about thousands of hosts.
Is there a way to control this type of situation?
KVM hosts do not have IPs, they appear with the duplicate name, but Dynatrace assigns them a different ID.
Please your comments.
It looks like need to to integrate Dynatrace into your process of creating/decomissioning KVM machines. I'm not familiar with your situation - how do your OneAgents communicate if they don't have IP addresses? How get agents installed on the KVM machines and how the decommissioning process looks like?
The agent does not bring the IP addresses, we have a big problem with these KVM microservices that are generated dynamically. They are KVMs that run on a Red Hat Enterprise Linux Server.
We need some solution.
Does anyone have a background on this problem?
Can you open a support ticket or contact Dynatrace One via chat? It needs more information about your deployment.
Cloning VMs can be accomplished by cloning it properly