Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


munin (17) Versions 1.0.2

Installs and configures munin

cookbook 'munin', '= 1.0.2', :supermarket
cookbook 'munin', '= 1.0.2'
knife supermarket install munin
knife supermarket download munin
Quality -%


Installs and configures Munin for a server and for clients using Chef 0.8 search capabilities.


Requires Chef 0.10 for Chef environments.

The monitoring server that uses this recipe should have a role named 'monitoring'. The recipes use search, and narrow the results to nodes in the same chef_environment.

Because of the heavy use of search, this recipe will not work with Chef Solo, as it cannot do any searches without a server.


  • Debian/Ubuntu
  • Red Hat 5.7, 6.1
  • ArchLinux


Opscode cookbooks

  • apache2

Not required (users can simply be in a data bag and the recipe will search), but useful for setting the openid list (see OpenID Authentication, below).

  • users (see Data Bags)

Not required, but recommended to install perl cpan modules for munin plugins

  • perl


  • node['munin']['sysadmin_email'] - default email address for serveradmin in vhost.
  • node['munin']['server_auth_method'] - the authentication method to use, default is openid. Any other value will use htauth basic with an htpasswd file.
  • node['munin']['server_role'] - role of the munin server. Default is monitoring.
  • node['munin']['docroot'] - document root for the server apache vhost. on archlinux, the default is /srv/http/munin, or /var/www/munin on other platforms.



The client recipe installs munin-node package and starts the service. It also searches for a node with the role for the munin server, by default node['munin']['server_role']. On Archlinux, it builds the list of plugins to enable.


The server recipe will set up the munin server with Apache. It will create a cron job for generating the munin graphs, search for any nodes that have munin attributes (node['munin']), and use those nodes to connect for the graphs.

Data Bags

Create a users data bag that will contain the users that will be able to log into the Munin webui. Each user can use htauth with a specified password, or an openid. Users that should be able to log in should be in the sysadmin group. Example user data bag item:

  "id": "munin,
  "groups": "sysadmin",
  "htpasswd": "hashed_htpassword",
  "openid": ""

When using server_auth_method 'openid', use the openid in the data bag item. Any other value for this attribute (e.g., "htauth", "htpasswd", etc) will use the htpasswd value as the password in /etc/munin/htpasswd.users.

The openid must have the http:// and trailing /. See OpenID Authentication below for more information.

The htpasswd must be the hashed value. Get this value with htpasswd:

% htpasswd -n -s munin
New password:
Re-type new password:

For example use the {SHA}oCagzV4lMZyS7jl2Z0WlmLxEkt4= value in the data bag.


Create a role named monitoring that includes the munin::server recipe in the run list. Adjust the docroot to suit your environment.

% cat roles/monitoring.rb
name "monitoring"
description "The monitoring server"

Apply this role to a node and it will be the munin server. Optionally create a DNS entry for it as munin, that will be used in the Apache vhost.

Use Chef 0.10's environments. For example, create a "production" environment Ruby DSL file and upload it to the Chef Server

% cat environments/production.rb
name "production"
description "Nodes in production"
% knife environment from file production.rb

Clients will automatically search for the server based on the value of the node['munin']['server_role'] attribute in the same environment. If you don't use monitoring as the role name, change it in a role that is applied to any nodes that get the munin::client recipe.

OpenID Authentication

The recipe apache2::mod_auth_openid is updated to a version of the module that apparently does not support the AuthOpenIDUserProgram directive anymore. The virtual host file has been updated to use the Apache HTTPD require user directive, with a concatenated list from node['apache']['allowed_openids']. This value must be an array of OpenIDs. Use of the users::sysadmins recipe will set this up based on data bag search results.

Custom Plugins

This section describes how to add custom munin plugins.

The munin cookbook now has a definition that can be used to enable a new plugin for data gathering on a client. If an existing munin plugin is desired, call the definition

munin_plugin "nfs_client"

By default the plugin file name is the name parameter here. Specify the plugin parameter to use something else.

munin_plugin "nfs_client"
  plugin "nfs_client_"

This creates a symlink from the plugins distribution directory, /usr/share/munin/plugins to the enabled plugins directory, /etc/munin/plugins, and once the server poller picks it up will have new graph data for that plugin. See the plugins distribution directory for available
plugins or add your own.

If a custom plugin is required, add the plugin file to the munin cookbook in site-cookbooks/munin/files/default/plugins. Call the definition specifying that the plugin file should be downloaded from the cookbook.

munin_plugin "nfs_client_custom"
  create_file true

By default in both cases, the plugin is enabled. If a plugin should be disabled, use the enable parameter

munin_plugin "nfs_client_custom"
  enable false

Some plugins may require other configuration. For example, to use the memcache plugins, you'll need the Cache::Memcache cpan module installed, and use the munin_plugin definition. The perl cookbook from opscode includes a definition to handle this easily.

cpan_module "Cache::Memcached"

Then for example in your memcache recipe

).each do |plugin_name|
  munin_plugin plugin_name do
    plugin "#{plugin_name}#{node[:ipaddress].gsub('.','_')}_#{node[:memcached][:port]}"
    create_file true



  • [COOK-920] - FreeBSD support


  • COOK-923 - account for empty node search results
  • COOK-500 - sort server list from search
  • COOK-501 - add support for RHEL platforms
  • COOK-918 - updates required for latest mod_auth_openid and add htauth basic option.


  • Use Chef 0.10's node.chef_environment instead of node['app_environment'].

License and Author

Author:: Nathan Haneysmith
Author:: Joshua Timberman

Copyright 2009-2011, Opscode, Inc

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

apache2 >= 1.0.6

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found