Bug #48010 | Service Manager should allow Agent to report problems when mysqld UUID not known | ||
---|---|---|---|
Submitted: | 12 Oct 2009 21:44 | Modified: | 12 Oct 2009 21:47 |
Reporter: | Andy Bang | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1096 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[12 Oct 2009 21:44]
Andy Bang
[12 Oct 2009 22:13]
Enterprise Tools JIRA Robot
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.