Forge Home


Puppet module for Munin monitoring


10,224 latest version

3.4 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.4 (latest)
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Sep 13th 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'duritong-munin', '0.0.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add duritong-munin
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install duritong-munin --version 0.0.4

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Tags: munin


duritong/munin — version 0.0.4 Sep 13th 2014


Build Status

Munin is a performance monitoring system which creates nice RRD graphs and has a very easy plugin interface. The munin homepage is


  • puppet 2.7 or newer

  • install the concat and stdlib modules - the munin module depends on functions that are defined and installed via these modules

  • you will need storedconfigs enabled in your puppet setup, to do that you need to add a line to your puppet.conf in your [puppetmasterd] section which says:

  • You may wish to immediately setup a mysql/ pgsql database for your storedconfigs, as the default method uses sqlite, and is not very efficient, to do that you need lines such as the following below the storeconfigs=true line (adjust as needed):



Your modules directory will need all the files included in this repository placed under a directory called munin.

Master configuration

In the node definition in your site.pp for your main munin host, add the following:

  class { 'munin::host': }

If you want cgi graphing you can pass cgi_graphing => true. (For CentOS this is enabled in the default header config) for more information, see:

Client configuration

For every host you wish to gather munin statistics, add the class munin::client to that node. You will want to set the class parameter allow to be the IP(s) of the munin collector, this defines what IP is permitted to connect to the node, for example:

  node foo {
    class { 'munin::client': allow => ''}

for multiple munin nodes, you can pass an array:

  class { 'munin::client': allow => [ '', '' ] }
  1. In the node definition in your site.pp for your main munin host, add the following:

Local plugins

If there are particular munin plugins you want to enable or configure, you define them in the node definition, like follows:

  # Enable monitoring of disk stats in bytes
  munin::plugin { 'df_abs': }

  # Use a non-standard plugin path to use custom plugins
  munin::plugin { 'spamassassin':
    ensure         => present,
    script_path_in => '/usr/local/share/munin-plugins',

  # For wildcard plugins (eg. ip_, snmp_, etc.), use the name variable to
  # configure the plugin name, and the ensure parameter to indicate the base
  # plugin name to which you want a symlink, for example:
  munin::plugin { [ 'ip_192.168.0.1', 'ip_10.0.0.1' ]:
    ensure => 'ip_'

  # Use a special config to pass parameters to the plugin
  munin::plugin {
    [ 'apache_accesses', 'apache_processes', 'apache_volume' ]:
       ensure => present,
       config => 'env.url'

Note: The plugin must be installed at the client. For listing available plugins run as root munin-node-configure --suggest

External plugins

For deploying plugins which are not available at client, you can fetch them from puppet master using munin::plugin::deploy.

  munin::plugin::deploy { 'redis':
      source => 'munin/plugins/redis/redis_',
      config => ''   # pass parameters to plugin

In this example the file on master would be located in:


Module path is specified in puppet.conf, you can find out your {modulepath} easily by tying in console puppet config print modulepath.

Multiple munin instances

If you have Linux-Vservers configured, you will likely have multiple munin-node processes competing for the default port 4949, for those nodes, set an alternate port for munin-node to run on by putting something similar to the following class parameter:

  class { 'munin::client': allow => '', port => '4948' }