MySQL Bugs: #48012: Update "Agent Not Communicating..." rule with new data collection item

Bug #48012	Update "Agent Not Communicating..." rule with new data collection item
Submitted:	12 Oct 2009 22:00	Modified:	12 Oct 2009 22:04
Reporter:	Andy Bang	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S3 (Non-critical)
Version:	2.1.0.1096	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When the Agent can't communicate with the mysqld it is monitoring, the "MySQL Agent Not Communicating With Database Server" rule is triggered.  However, this rule is currently only triggered if the Agent's login credentials (to the mysqld being monitored) are changed while the Agent is running (and thus the Agent knows the UUID for the mysqld).  If the agent is restarted, it can only report the problem in its error log (because it can't determine the UUID).

So this is related to Bug #48010 and Bug #48011.  When those two are fixed, the rule should be updated accordingly.

How to repeat:
Option 1
--------
1) Install an agent and give it the wrong login credentials for the mysqld it is supposed to monitor.
2) Start the agent.
3) Notice that nothing shows up in the Dashboard -- there's only a message in the Agent's error log indicating the problem.

Option 2
--------
1) Get everything working nicely, with an Agent showing up in a Dashboard.
2) Change the user or password in the Agent's etc/instances/mysql/agent-instance.ini file.
3) Restart the agent.
4) Notice that Agent still shows as "down" in the Dashboard -- there's only a message in the Agent's error log indicating the problem.

Andy Bang writes: 
This is one of three related issues:

* EM-3645/Bug #48010 - Service Manager should allow Agent to report problems when mysqld UUID not known
* EM-3646/Bug #48011 - Agent should report problems to Service Manager even when mysqld UUID not known
* EM-3647/Bug #48012 - Update "Agent Not Communicating..." rule with new data collection item

These (along with EM-300/Bug #41630 - A more intelligent agent installer) are meant to address EM-2935/Bug #37829 - MEM doesn't report a problem appropriately when the user and password are wrong.