Bug #33686 Display monitoring MySQL's OS/CPU without installing an agent to the same PC.
Submitted: 4 Jan 2008 9:27
Reporter: Meiji KIMURA Email Updates:
Status: Open Impact on me:
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version:1.2 OS:Any
Assigned to: Mark Matthews CPU Architecture:Any

[4 Jan 2008 9:27] Meiji KIMURA
Now I configure that the one agent can monitor multiple servers.

In that case, The OS and CPU information applies to the machine on which the agent is running. 

In future version, The OS and CPU information applies to the machine hosting the monitored server.

How to repeat:
[4 Jan 2008 13:48] Mark Matthews
Until the MySQL server can provide this information itself, the agent *has* to be on the same physical machine as the mysql server being monitored to provide CPU and OS statistics.
[21 Jan 2008 16:17] Meiji KIMURA
I think so. 

For example, IBM DB2 newest edition (Version 9.5) has a new admin view  SYSIBMADM.ENV_SYS_RESOURCES. It return the information OS and CPU.
[25 Jan 2008 20:15] Mark Matthews
We can't get this information without changes to the MySQL server itself, either deploying a UDF, or deploying Leith's I_S views that use Sigar to provide this information.
[9 Jun 2009 16:20] Mark Leith
The I_S plugin was enhanced as a part of the Google Summer of Code in 2008 by Muslim Chochlov:


We should consider getting this in to the Server if at all possible for all Sigar supported platforms. 

This bug should also be considered in a wider "remote monitoring" task set.