Global directives affect all munin master components unless specified otherwise.
The directory where munin stores its database files. Default: /var/lib/munin
The directory where munin stores its logfiles. Default: /var/log/munin
Directory for files tracking munin’s current running state. Default: /var/run/munin
This directive determines whether munin-update fork when gathering information from nodes. Default is “yes”.
If you set it to “no” munin-update will collect data from the nodes in sequence. This will take more time, but use less resources. Not recommended unless you have only a handful of nodes.
Default is “normal”.
“huge” saves the complete data with 5 minute resolution for 400 days.
Changing this directive has no effect on existing graphs
If set to “cron”, munin-graph will graph all services on all nodes every run interval.
Valid strategies are “cgi” and “cron”. Default is “cgi”.
If set to “cron”, munin-html will recreate all html pages every run interval.
The name of the secure shell command to use. Can be fully qualified or looked up in $PATH.
Defaults to “ssh”.
The options for the secure shell command.
Defaults are “-o ChallengeResponseAuthentication=no -o StrictHostKeyChecking=no”. Please adjust this according to your desired security level.
With the defaults, the master will accept and store the node ssh host keys with the first connection. If a host ever changes its ssh host keys, you will need to manually remove the old host key from the ssh known hosts file. (with: ssh-keygen -R <node-hostname>, as well as ssh-keygen -R <node-ip-address>)
You can remove “StrictHostKeyChecking=no” to increase security, but you will have to manually manage the known hosts file. Do so by running “ssh <node-hostname>” manually as the munin user, for each node, and accept the ssh host keys.
If you would like the master to accept all node host keys, even when they change, use the options “-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PreferredAuthentications=publickey”.
A minimal configuration file
[client.example.com] address client.example.com