Multiple MySQL AWS instances all show up under one hostname in Mysql Enterprise Monitor 3.x
(Doc ID 1629728.1)
Last updated on MARCH 09, 2020
Applies to:MySQL Server - Version 5.5 and later
MySQL Enterprise Monitor - Version 3.0 and later
Information in this document applies to any platform.
Several cloned Amazon AWS instances are all showing up under one instance in MEM Service Monitor.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Step 1. Identify affected instances.|
|Step 2. Shutdown the MEM agents monitoring the affected instances.|
|Step 3. Remove duplicate UUIDs|
|Step 4. Identify VMs with duplicate SSH keys for servers with MEM 3.0 agents|
|Step 5. Regenerate SSH public keys on servers with duplicate key fingerprints|
|Step 6. Delete all affected (MySQL UUID and SSH hostid) MySQL instances from MySQL Enterprise Monitor Service Monitor Dashboard.|
|Step 7. (version 5.6) Restart your MySQL instances to re-generate the UUID (auto.cnf)|
|Step 8. Start the MySQL Enterprise Monitor Agent on each server from Step 2|
|Step 9. It may take 5 minutes for MEM to clear the old instances and advisor data from the dashboard, wait until all of the errant instances are gone.|
|Step 10. Add your MySQL instances to the MEM dashboard to be monitored.|