Forge Home


Module for installing and managing the Riemann monitoring tool


13,416 latest version

2.3 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.6.0 (latest)
  • 0.5.4
  • 0.5.3
  • 0.5.2
  • 0.5.1
  • 0.5.0
  • 0.4.2
  • 0.4.1
  • 0.4.0 (deleted)
  • 0.3.3
  • 0.3.2
  • 0.3.1
  • 0.3.0
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.0
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Dec 4th 2014
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x

Start using this module

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

Add this module to your Puppetfile:

mod 'garethr-riemann', '0.6.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add garethr-riemann
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install garethr-riemann --version 0.6.0

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.



garethr/riemann — version 0.6.0 Dec 4th 2014

Puppet module for installing and managing Riemann, the event agregation and monitoring tool.

This module is also available on the Puppet Forge

Status Dependency


The module includes three main components:

include riemann
include riemann::dash
include riemann::tools

Riemann represents the Riemann daemon and associated configuration, riemann:dash the dashboard and riemann::tools the client and a couple of daemons for pushing example data into Riemann.


The riemann class has some defaults that can be overridden, for instance if you wanted a specific version of riemann:

class { 'riemann': version => '0.1.1' }

More useful is probably the ability to override the default configuration file.

class { 'riemann': config_file => '/etc/riemann.config' }

In this last case you're responsible for making sure that file exists, via another puppet resource or otherwise.


For a fully working example of this module you may also be interested in the riemann-vagrant project.