Download munin

We strongly recommend a packaged install, as the source distribution isn’t as tested as the packaged one. The current state of the packages is so satisfactory, that even the developers use them instead.

From packages

Installation

You will have to install the munin-node package on each node you want to monitor, and munin on the master. Example instructions for Ubuntu / Debian:

On each node

user@node01:~$
sudo apt-get install munin-node
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:

On the master

user@master:~$
sudo apt-get install munin
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:

Please note that this might not be the latest version of Munin. On Debian you have the option of enabling “backports”, which may give access to later versions of Munin.


Configuration

On each node

The munin node listens on all interfaces by default, but has a restrictive access list. You need to add your master’s IP address.

# /etc/munin/munin-node.conf
# A list of addresses that are allowed to connect. This must be a
# regular expression, since Net::Server does not understand CIDR-style
# network notation unless the perl module Net::CIDR is installed. You
# may repeat the allow line as many times as you'd like
allow ‘^127.’
allow ‘^192.0.2.1$’
# If you have installed the Net::CIDR perl module, you can use one or more
# cidr_allow and cidr_deny address/mask patterns. A connecting client must
# match any cidr_allow, and not match any cidr_deny. Note that a netmask

Start munin-node service, or restart it if it was already started:

user@node01:~$
sudo service munin-node restart
[ ok ] Stopping Munin-Node: done.
[ ok ] Starting Munin-Node: done.

On the master

Add the previously configured nodes to the master configuration file:

# /etc/munin/munin.conf
# a simple host tree
[node01.example.com]
    address 192.0.2.4

[node02.example.com]
    address node02.example.com

[node03.example.com]
    address 2001:db8::de:caf:bad
#
# A more complex example of a host tree
#
## First our "normal" host.
# [fii.foo.com]

The master service does not need to be reloaded: its configuration file will be read on the next poll.


Now that munin is up and running, you can view report pages by accessing the master's munin-httpd service on port 4948 in your browser. You may have to wait up to 5 minutes until nodes gets polled and data goes live on the report pages.

If anything goes wrong, please head to the support page and check the FAQ: chances are that you will find a solution for your issues here.

Read more on Munin Guide

From source

Usually you don’t want to do that. The following lines are for completeness, and reference for packagers. The other reason would be because you want to contribute to the development of Munin, and then you should use a development install.


Read more on Munin Guide