Forge Home

graphite

manages carbon daemons for a graphite installation

10,919 downloads

10,919 latest version

3.6 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.1.0 (latest)
released Apr 6th 2015

Start using this module

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

Add this module to your Puppetfile:

mod 'nationbuilder-graphite', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add nationbuilder-graphite
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install nationbuilder-graphite --version 0.1.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

nationbuilder/graphite — version 0.1.0 Apr 6th 2015

Graphite module for puppet

Description

Puppet module for installing and configuring graphite

Usage

Graphite is a beast. This module tries to tame it a bit.

For your simplest setup, you really only need a cache:

graphite::cache { 'a': }

This will start up a graphite cache listening on port 2003, 2004, and 7002 to receive metrics and to accept queries from graphite-web and other graphite metrics consumers.

Multiple Caches

Multiple caches can be managed with this module:

graphite::cache {
    'a':
        line_receiver_port => 2003,
        udp_receiver_port => 2003,
        pickle_receiver_port => 2004
        cache_query_port => 7002;
    'b':
        line_receiver_port => 2103,
        udp_receiver_port => 2103,
        pickle_receiver_port => 2104
        cache_query_port => 7102;
}

Generally you would want to have these behind a relay instance:

class { 'graphite::relay':
    destinations => ['127.0.0.1:2004:a','127.0.0.1:2104:b']
}

Aggregator Support

If you want to have an aggregator running in front of your cache(s), use the graphite::aggregator class:

class { 'graphite::aggregator':
    destinations => ['127.0.0.1:2014:a'],
}

Other Defines

  • graphite::relay_rule
  • graphite::blacklist
  • graphite::whitelist
  • graphite::storage_aggregation
  • graphite::storage_schema

Contact

If you have problems with this module, please file issues or PRs over at [https://github.com/nationbuilder/puppet-graphite](our project page)