Keeping host metrics after setting it up again (AWS)

[skrystosik]

Hello,

our client deployment process contains killing host and creating it once again with one agent and new application build. Unfortunately the problem is that after each deployment metrics for this host are starting from the beginning. Host name and IP are the same. The question is... is it any way to tell dynatrace that this new host is the same that was available moment ago? Host is changing so processes has the same story.

Sebastian

[Julius_Loman]

Can you preserve the configuration directory of oneagent? It includes the generated unique ID of the host. I think this is also related to MAC addresses of network interfaces. Are they also preserved?

[skrystosik]

I think for now everything is being deleted to the ground and recreated so nothing is left after previous installation.

Sebastian

[Julius_Loman]

• When is the Oneagent installed?
• Is it a from scratch OS installation or some kind of VM image restore?
• Do the MAC addresses of network cards change between the individual lifecycles?
• Can you assure there will be no more than one instance of this VM?
• Can you somehow manage the lifecycle?
  

This is effectively an anti-pattern - as if the host gets really reinstalled - it is, in fact, a new host and should be treated accordingly.
If it is the same image just restored to a snapshot - you have to convince the customer to include oneagent into the image or at least the configuration files.

[skrystosik]

Julius, general it is AWS, so host is killed and srarted from scratch. One agent is installed after setting up new instance (after application deployment) with the same IP and host name. I don't know what with MAC Address. I don't think it will be easy to put oneagent into host image because there is 5 or 6 host types that use the same os image I think. For now I'm checking options we have.

Sebastian

[ChadTurner · Accepted solution]

At this time I dont think thats possible. AS if the AWS instance is completely cleared, then all the config files will be gone as well, and the oneagent will deploy with a new GUID and hence you will see a new host (might have the same name, but the Dynatrace GUID is different) It might be a good idea to post a RFE for this is your organization needs this functionality.