Initial configuration¶

Node¶

Plugins¶

Decide which plugins to use. The munin node runs all plugins present in CONFDIR/plugins/

The quick auto-plug-and-play solution:

munin-node-configure --shell --families=contrib,auto | sh -x

Access¶

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

The “cidr_allow”, “cidr_deny”, “allow” and “deny” statements are used.

cidr_allow uses the following syntax (the /32 is not implicit, so for a single host, you need to add it):

cidr_allow 127.0.0.0/8

cidr_allow 192.0.2.1/32

allow uses regular expression matching against the client IP address.

allow ‘^127.’

allow ‘^192.0.2.1$’

For specific information about the syntax, see Net::Server. Please keep in mind that cidr_allow is a recent addition, and may not be available on all systems.

Startup¶

Start the node agent (as root) SBINDIR/munin-node. Restart it it it was already started. The node only discovers new plugins when it is restarted.

You probably want to use an init-script instead and you might find a good one under build/dists or in the build/resources directory (maybe you need to edit the init script, check the given paths in the script you might use).

Master¶

Add some nodes¶

Add some nodes to CONFDIR/munin.conf

[node.example.com]: address 192.0.2.4
[node2.example.com]: address node2.example.com
[node3.example.com]: address 2001:db8::de:caf:bad

Configure web server¶

On the master, you need to configure a web server.

If you have installed “munin” through distribution packages, a webserver may have been configured for you already.

If you installed from source, there is a minimal configuration example in the “resources” directory in the source tarball.

For a more complex example, see Apache virtualhost configuration