Re: Replication Monitoring Issue with MEM

[Mark Matthews]

Tom,

It sounds like, on the server that shows up as "unmonitored" in the replication tab, the agent doesn't have enough privileges to grab the replication status or configuration. MEM can "fill in the gaps" during replication discovery and create a stand-in, because the agent *is* communicating with that server, and knows the hostname and ports in use, but if the user the agent on that instance doesn't have at least the ability to "SHOW MASTER STATUS" and "SHOW SLAVE STATUS" (i.e. either has REPLICATION CLIENT or SUPER privs), it won't have enough to fill in the rest of the details on that page.


-Mark

Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html