Forge Home

diamond

Module for installing and managing the Diamond stats collection tool

28,028 downloads

22,259 latest version

3.0 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

  • 1.0.0 (latest)
  • 0.9.0
  • 0.8.0
  • 0.7.0
  • 0.6.6
  • 0.6.4
  • 0.6.2
  • 0.6.1
  • 0.6.0
  • 0.5.0
  • 0.4.0
  • 0.3.0
  • 0.2.0
  • 0.1.1
  • 0.1.0
  • 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-diamond', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install garethr-diamond --version 1.0.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.

Download

Documentation

garethr/diamond — version 1.0.0 Dec 4th 2014

A Puppet module for managing the installation and configuration of Diamond.

Puppet
Forge Build
Status

Usage

For experimenting you're probably fine just with:

include diamond

This installs diamond but doesn't ship the metrics anywhere, it just runs the archive handler.

Configuration

This module currently exposes a few configurable options, for example the Graphite host and polling interval. So you can also do:

class { 'diamond':
  graphite_host => 'graphite.example.com',
  graphite_port => 2013,
  interval      => 10,
}

You can also add additional collectors:

diamond::collector { 'RedisCollector':
  options => {
    'instances' => 'main@localhost:6379, other@localhost:6380'
  }
}

Some collectors support multiple sections, for example the NetApp and RabbitMQ collectors

diamond::collector { 'NetAppCollector':
  options => {
    'path_prefix' => '/opt/netapp/lib/python'
  },
  sections => {
    '[devices]' => {},
    '[[host01]]' => {
         'ip' => '10.10.10.1',
         'username' => 'bob',
         'password' => 'alice'
    },
    '[[host02]]' => {
         'ip' => '10.10.10.2',
         'username' => 'alice',
         'password' => 'bob'
    }
  }
}

diamond::collector { 'RabbitMQCollector':
  options => {
    'host' => '10.10.10.1',
    'user' => 'bob',
    'password' => 'alice'
  },
  sections => {
    '[vhosts]' => {
      '*' => '*'
    }
  }
}

Diamond supports a number of different handlers, for the moment this module supports only the Graphite, Librato and Riemann handers. Pull request happily accepted to add others.

With Librato:

class { 'diamond':
  librato_user   => 'bob',
  librato_apikey => 'jim',
}

With Riemann:

class { 'diamond':
  riemann_host => 'riemann.example.com',
}

Note that you can include more than one of these at once.

class { 'diamond':
  librato_user   => 'bob',
  librato_apikey => 'jim',
  riemann_host   => 'riemann.example.com',
  graphite_host  => 'graphite.example.com',
}