All global directives have to be defined in the first section of the file! It will not work if you place them in later sections of the config file. We recommend to use the delivered munin.conf file and adapt it to your needs.
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
Directories for templates used by munin-httpd to generate HTML pages. Default /etc/munin/templates
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.
This directive determines how long munin-update allows a worker to fetch data from a single node. Default is “180”.
The palette used by munin-httpd to color the graphs. The “default” palette has more colors and better contrast than the “old” palette.
rrggbb rrggbb ...¶
The user defined custom palette used by munin-httpd to color the graphs. This option overrides the existing palette. The palette must be space-separated 24-bit hex color code.
This directive sets the resolution of the RRD files that are created by munin-update.
Default is “normal”.
“huge” saves the complete data with 5 minute resolution for 400 days.
Changing this directive has no effect on existing graphs
.<contact name>.command <command>¶
Define which contact command to run.
.<contact name>.text <text>¶
Text to pipe into the command.
.<contact name>.max_messages <number>¶
Close (and reopen) command after given number of messages. E.g. if set to 1 for an email target, Munin sends 1 email for each warning/critical. Useful when relaying messages to external processes that may handle a limited number of simultaneous warnings.
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”.
Node definitions can have several types. In all forms, the definition is used to generate the node name and group for the node, and the following lines define its directives. All following directives apply to that node until another node definition or EOF.
When defining a nodename it is vital that you use a standard DNS name, as in, one that uses only “a-z”, “-”, and ”.”. While other characters can be used in a DNS name, it is against the RFC, and Munin uses the other characters as delimiters. If they appear in nodenames, unexpected behavior may occur.
The simplest node definition defines the section for a new node by simply wrapping the DNS name of
the node in brackets, e.g.
[machine1.example.com]. This will add the node machine1.example.com
to the group example.com.
The next form of definition is used to define the node and group explicitly. It follows the form
[example.com;machine1.sub.example.com]. This adds the node machine1.sub.example.com to the
group example.com. This can be useful if you have machines you want to put together as a group
that are under different domains (as in the given example). This can also solve a problem if your
machine is example.com, where having a group of com makes little sense.
A deeper hierarchy can be specified by using a list of groups, separated with ”;”. For example:
These are directives that can follow a node definition and will apply only to that node.
Specifies the host name or IP address, with an optional scheme.
Permitted schemes are “munin://”, “ssh://” or “cmd://”. If no scheme is specified, the default is “munin://”
The port number of the node. Ignored if using alternate transport. Default is “4949”.
The local address to connect to the node from. This overrides a group or global directive.
Overrides the name supplied by the node. Allowed values: “yes” and “no”. Defaults to “no”.
A list of contacts used by munin-limits to report values passing the warning and critical thresholds.
If set to something else than “no”, names a list of contacts which should be notified for this node. Default is “no”.
Used by munin-limits.
If set, changes the name by which the node presents itself when warning through munin-limits.
If set, ignore any unknown values reported by the node. Allowed values are “yes” and “no”. Defaults to “no”.
Useful when a node is expected to be off-line frequently.
These directives follow a node definition and are of the form “plugin.directive <value>”.
Using these directives you can override various directives for a plugin, such as its contacts, and can also be used to create graphs containing data from other plugins.
These directives follow a node definition and are of the form “plugin.field <value>”.
Using these directives you can override values originally set by plugins on the nodes, such as warning and critical levels or graph names.
The graph height for a specific service. Default is 175. Affects: munin-httpd.
The value at which munin-limits will mark the service as being in a warning state. Value can be a single number to specify a limit that must be passed or they can be a comma separated pair of numbers defining a valid range of values. Affects: munin-limits.
A minimal configuration file, using default settings for everything, and specifying three nodes.
[mail.example.com] address mail.example.com [web.example.com] address web.example.com [munin.example.com] address localhost
A virtual node definition. Disable update, and make a graph consisting of data from other graphs.
[example.com;Totals] update no load.graph_title Total load load.sum_load.label load load.sum_load.special_stack mail=mail.example.com web=web.example.com munin=munin.example.com
The scheme tells munin how to connect to munin nodes.
The munin:// scheme is default, if no scheme is specified. By default, Munin will connect to the munin node with TCP on port 4949.
The following examples are equivalent:
# master: /etc/munin/munin.conf.d/node.example.conf [mail.site2.example.org] address munin://mail.site2.example.org [mail.site2.example.org] address munin://mail.site2.example.org:4949 [mail.site2.example.org] address mail.site2.example.org [mail.site2.example.org] address mail.site2.example.org port 4949
To connect to a munin node through a shell command, use the “cmd://” prefix.
# master: /etc/munin/munin.conf.d/node.example.conf [mail.site2.example.org] address cmd:///usr/bin/munin-async [...]
To connect through ssh, use the “ssh://” prefix.
# master: /etc/munin/munin.conf.d/node.example.conf [mail.site2.example.org] address ssh://bastion.site2.example.org/bin/nc mail.site2.example.org 4949 [www.site2.example.org] address ssh://bastion.site2.example.org/bin/nc www.site2.example.org 4949
When using the ssh:// transport, you can configure how ssh behaves by editing ~munin/.ssh/config. See the ssh transport configuration examples.