Bug #45161 Request for new advisor to detect relocated replication master

Description:
An idea for a new Advisor:

If a MySQL instance is an active replication master and if its network location is changed (due to maintenance, hardware migration, improper failover, etc) an advisor could be written to detect that change. 

How to repeat:
Change the hostname, IP address, or replication port of an active MASTER instance. 

Suggested fix:
Create an advisor that compares the network location information from a monitored MASTER to the state it had the last time it was online. If the master's location information has changed *and* if the slaves (also monitored) do not have the new information then send an advisory message that the MASTER has changed locations. Something like:

MySQL Enterprise Monitor has detected a change in the replication configuration of host .xxxxxx (master server has changed from user_old@master_old:port_old to user_new@master_new:port_new)

Sending a message would be pointless if the slaves had already been configured to use the new location settings. 

The message might also list the slaves that were affected by the move

Verified that MySQL Enterprise Monitor does not have the feature I described.