MySQL Bugs: #40642: OPTIONALLY Indicate server being connected to in login screen

Bug #40642	OPTIONALLY Indicate server being connected to in login screen
Submitted:	11 Nov 2008 16:17	Modified:	20 Jul 2009 13:44
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S4 (Feature request)
Version:	2.0.0.7088	OS:	Any
Assigned to:	MEM Service Manager Devs	CPU Architecture:	Any

Description:
OPTIONALLY provide some sort of banner indicating which box we're talking to.
I'm getting confused between the 2 instances we're running 1.3 and 2.0.
The initial login looks the same and the main page looks very similar.
We're likely to have more than one instance running in the future so it would be nice to distinguish them.

How to repeat:
Run 2 different instances of merlin and switch between them a lot. Can be a bit confusing working out which one is which.

The URL is not always a clear indicator as sometime direct access to merlin may not be possible so ssh port forwarding for example may be used and as such the url used does not clearly distinguish the boxes.

Suggested fix:
Perhaps include the hostname at the top of the login screen and the top of the Dashboard.

Make it optional for the login screen so that no security sensitive information is shown.
Surely easy to implement.

default should be hostname of the monitoring box?

Yes, that would seem logical.

It's probably sufficient except when multiple instances of merlin are running on the same server which might be why making it configurable is useful.

Also perhaps the option of the short hostname. Unless a long name doesn't interfere.

Eric Herman writes: 
added a name for the server on the login page
 name defaults to the hostname
 may change the name on the Settings page

Keith Russell writes: 
Patch installed in versions => 2.1.0.1077.

Marcos Palacios writes: 
Verified fixed in build 2.1.0.1077.

An entry was added to the 2.1.0 changelog:

When running multiple instances of the Enterprise Dashboard it could be difficult to determine which instance is currently being logged into.

This was fixed by adding a name for the server on the login page. The name defaults to the hostname but may be changed in the Settings page.