MySQL Bugs: #42792: renaming db server is cumbersome to fix in dashboard

Bug #42792	renaming db server is cumbersome to fix in dashboard
Submitted:	12 Feb 2009 13:42	Modified:	9 Jan 2015 10:37
Reporter:	Oli Sennhauser	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S4 (Feature request)
Version:	any	OS:	Any (n.a.)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	rename server dashboard

Description:
Renaming servers can have confusing results on the dashboard as the name doesn't change there.

Customer installed on some servers agents. Then due to some problems they had to rename some of them.

The problem is that the dashboard does not make this very visible.

How to repeat:
Rename the servers hostname. Restart mysql.

Suggested fix:
Customer expects the dashboard to give some indication about these changes which it does not.

He expects to get:

1. a warning about hostname change of the instance being monitored
2. a warning about @@hostname changing on the mysqld

None of this happens.

When he was looking for the server name it was not there and it took him a while to find which instance was the old box, and perform the appropriate rename.

There is no option to search for an instance by uuid and they have 140 instances running in merlin so this is really unworkable if you lose a box and want to find it.

Verified on my systems. The old server name remains.

Will consider:
1) add search to Settings / Manage Servers page that looks through all server meta data (maybe google-like search box. Type IP:XXXX and press [search], you filter the rows dispalyed)
2) a new rule that detects changes in hostname (would not be auto-scheduled)