Configure Hardware Monitoring with
On this page
Beginning with Automation Agent v. 2.7.0, if you use Ops Manager Automation, then Ops Manager displays the hardware data collected by the Automation Agent, not by Munin, when you view metrics.
Monitoring of hardware via
munin-node is deprecated functionality.
cpuplugin, which creates the
iostatplugin, which creates the
iostat_iosplugin, which creates the
must install the
munin-node package on all of the host systems that
you wish to monitor. Ensure that the Monitoring Agent can connect to the
munin-node process on port 4949 of the monitored host to collect data.
munin-node and hardware monitoring is only available for
MongoDB instances running on Linux hosts.
For details on installing
munin-node beyond the information provided
here, please see http://guide.munin-monitoring.org/en/latest/installation/install.html.
On Debian and Ubuntu systems, issue the following command to install
sudo apt-get install munin-node
On Red Hat, CentOS, and Fedora systems, you may need to first install the
EPEL repository before installing
https://fedoraproject.org/wiki/EPEL. To install
the following command:
yum install munin-node
When installation is complete, ensure that
is running. Use the command, “
ps -ef | grep "munin"” to confirm. If the process is not running, issue the appropriate command to start it, depending on your operating system.
If you use
systemctl, and if the munin-node service is not shown, try to reload the SystemD configuration and unit files.
will start following the next system reboot. This is the default behavior on most Debian-based systems. Red Hat and related distributions should use the “
chkconfig” command, to configure this behavior (i.e. “
chkconfig munin-node on”)
is accessible from the system running the agent.
munin-nodeuses port 4949, which needs to be open on the monitored system, so the agent can access this data source. Use the following procedure to test access:
telnet [HOSTNAME] 4949 fetch iostat fetch iostat_ios fetch cpu
[HOSTNAME]with the hostname of the monitored system. Run these commands from the system where the Monitoring Agent is running. If these “
fetch” commands return data, then
munin-nodeis running and accessible by the Monitoring Agent.
On some platforms,
munin-node does not have all required
For CentOS and Ubuntu, the
munin-node package does not have the
iostat_ios plugins enabled. Use the following operation to enable
sudo ln -s /usr/share/munin/plugins/iostat /etc/munin/plugins/iostat sudo ln -s /usr/share/munin/plugins/iostat_ios /etc/munin/plugins/iostat_ios
munin-node is running but inaccessible, make sure that you have
access granted for the system running the Monitoring Agent and that no
firewalls block the port between
munin-node and the Monitoring
Agent. You may find the
munin-node configuration at
depending on your distribution.
Additional Considerations for
If you have numbered disk devices (e.g.
/dev/sda2) then you will need to configure support for numbered disk in the munin iostat plugin. Find the configuration file at
/etc/munin/plugin-conf.d/munin-nodeor a similar path, and add the following value:
[iostat] env.SHOW_NUMBERED 1
If you have Munin enabled and do not have
iostat iosdata in your Munin charts, your
munin-nodemay not have write access to required state files in its
munin/plugin-state/directory. See the
munin-nodeplugin log (i.e.
/var/log/munin/munin-node.logor similar depending on your distribution) for more information.
The full path of this state directory depends on the system, but is typically
Run the following command sequence to correct this issue. The last command in the sequence changes permissions for the
/var/lib/munin/plugin-state/directory to ensure access for the
munin-nodeplugins. Depending on your setup, you might have to use a different permission level:
touch /var/lib/munin/plugin-state/iostat-ios.state chown -R [username]:[group] /var/lib/munin/plugin-state/ chmod -R 766 /var/lib/munin/plugin-state/
[group]with the username and group that the
munin-nodeprocess runs with.
Add the host running the Monitoring Agent to the allow directive in the
munin-node.conffile. The allow directive lists hosts allowed to query the munin-node process. Otherwise, traffic from the Ops Manager host will be allowed via firewall but will not be collected by munin.
munin-node.conffile is located in one of the following directories, depending on your distribution:
If you encounter any other problems, check the log files for
ensure that there are no errors with Munin.
munin-node writes logs files in
/var/log/ directory on the monitored system.