MySQL Bugs: #50990: Add agent uuid and basedir to instance management reporting

Bug #50990	Add agent uuid and basedir to instance management reporting
Submitted:	8 Feb 2010 13:03
Reporter:	Mark Leith	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.1.0.1093	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	windmill

Description:
If you run multiple agent instances on the same machine, it's not possible to tell from the Duplicate Agent UUID exception which agents are in error:

2010-01-27 10:33:47: (critical) exception received from server: E1402: DuplicateAgentUuidException: [a2c86b14-ed5b-4c27-bff3-6a1d2c47210b, 1264582692130.5194, server1.com, -1, server1.com]

Note both server's listed are the same. 

How to repeat:
o Set up two agent installs on the same machine, with the same agent-uuid (and imagine more than that with different uuids). 
o Start them all up. 
o Try to diagnose which specific installation is in error 

Suggested fix:
1) Agent to provide the "agent basedir" to the server
2) Server to use this in agent related errors, such as DuplicateAgentUuidException

It is possible that original exception was caused by related bug #53400