Bug #70495 make etc/init.d/mysql-monitor-agent provide more status information
Submitted: 3 Oct 2013 5:51 Modified: 4 Oct 2013 9:25
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S4 (Feature request)
Version:3.0.1.2893 OS:Any
Assigned to: CPU Architecture:Any
Tags: windmill
Triage: Needs Triage: D5 (Feature request)

[3 Oct 2013 5:51] Simon Mudd
Description:
When starting a merlin agent I see:

[root@myhost smudd]# /opt/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start
Starting MySQL Enterprise Agent service...                 [  OK  ]
[root@myhost smudd]# /opt/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent status
MySQL Enterprise Agent is running
[root@myhost smudd]# 

Given that the agent has to talk to the merlin dashboard and also has to reach one or more MySQL instances it would be convenient if the status output indicated which of these tasks it was doing and the status of them, apart from whether it is running. (that is provide more output).

How to repeat:
See above.

Suggested fix:
Provide information on access to the dashboard.
Provide information on access to the MySQL server(s) being monitored.

Something like:

host: myhost.FQDN.com being monitored correctly
dashboard: [mydashboard.FQDN.com:port]: reachable and up
instance [hostname:port or socket_path]: reachable and up

or if things are bad:

dashboard: [mydashboard.FQDN.com:port]: not reachable, authentication problems, since ....
dashboard: [mydashboard.FQDN.com:port]: not reachable, failed to connect, since ....
instance [hostname:port or socket_path]: not reachable, authentication problems for user ..., since ...
instance [hostname:port or socket_path]: not reachable, since ...

This avoids you having to double check if everything is configured properly by looking in the agent's log files.
[4 Oct 2013 9:25] Umesh Shastry
Hello Simon,

Thank you for the feature request!

Thanks,
Umesh