Forge Home


Deploys and Configures netdata.


4,657 latest version

4.7 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.2.2 (latest)
  • 0.2.1
  • 0.2.0
  • 0.1.9
  • 0.1.8
  • 0.1.7
  • 0.1.6
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Apr 16th 2020
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'denver-netdata', '0.2.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add denver-netdata
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install denver-netdata --version 0.2.2

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.



denver/netdata — version 0.2.2 Apr 16th 2020


Build Status Code Coverage Puppet Forge Puppet Forge - downloads Puppet Forge - scores

Table of Contents

  1. Description
  2. Setup
  3. Usage
  4. Limitations
  5. Development


This module deploys and configures netdata. Netdata is a system for distributed real-time performance and health monitoring. More can be found on the netdata website.


Setup requirements

This module requires you have a compatible OS and a functioning puppet infrastructure.


Basic usage

To deploy and configure default netdata...

class {'::netdata': }

To remove a deployed netdata...

class {'::netdata': ensure => 'absent'}

Note, ensure => 'absent' is not currently supported on Ubuntu 14.04 due to the way puppet manages upstart.

Advanced useage

To configure netdata as a Slave. Note, the GUID displayed here is just an example.

class {'::netdata':
  remote_master        => '',
  remote_master_apikey => '9a83b18a-5cdb-4baf-8958-ad291ab781d3',

netdata::stream To configure netdata as a Master

class {'::netdata':
  master => true,

In order for netdata metrics to stream to a master, you must define a netdata stream API key. You can generate a GUID with uuidgen. More information can be found on netdata replication here.

netdata::stream {'9a83b18a-5cdb-4baf-8958-ad291ab781d3': }

To configure netdata as a Proxy

class {'::netdata':
  master               => true,
  remote_master        => '',
  remote_master_apikey => '9a83b18a-5cdb-4baf-8958-ad291ab781d3',

netdata::stream {'9a83b18a-5cdb-4baf-8958-ad291ab781d3': }


netdata::plugin::bind_rndc This plugin tracks bind rndc stats. More here.

netdata::plugin::bind_rndc {'': }
  • update Optional. Data collection frequency.
  • priority Optional. Order of the dashboard.
  • retries Optional. Number of restoration attempts.
  • detect_retry Optional. re-detect interval in seconds.

netdata::plugin::web_log This plugin supports apache, apache_cache, nginx, gunicorn, and squid. More here.

netdata::plugin::web_log {'':
  logfile => '/var/log/nginx/',
  • type Optional. Type of service generating the log file.
  • logfile Required. This should be the full path of the logfile being monitored.

Class Parameters

  • history Default: 3600 Desc: The number of entries the netdata daemon will by default keep in memory for each chart dimension.

  • debug_flags Desc: Debug Flags. See more info.

  • memory_mode Default: save Desc: The mode for storing metrics. Options are save, map ram and none.

  • web_mode Default: multi-threaded Desc: Web UI mode, options are none, single-threaded and multi-threaded.

  • update_every Default: 1 Desc: The frequency in seconds, for data collection.

  • port Default: 19999 Desc: The default port to listen for web clients.

  • bind_to Default: * Desc: The IPv4 address and port to listen to.

  • master Default: false Desc: Set this to true for netdata to act as a master.

  • remote_master Default: undef Desc: The Hostname of a remote netdata master.

  • remote_master_port Default: 19999 Desc: Port for remote netdata master.

  • remote_master_apikey Default: undef Desc: This sets the API Key for talking to an upstream netdata. This must be a GUID. A netdata master must have a matching GUID defined with netdata::stream.

  • registry Default: false Desc: Set to true in order for a netdata to act as a registry.

  • registry_allowgroup Default: * Desc: List of subnets allowed to register.

  • remote_registry Default: undef Desc: A central netdata that is configured with registry => true.

  • remote_registry_port Default: 19999 Desc: Port configured on the remote registry.


This module is tested with CentOS 6 and 7, Ubunu LTS 14.04, and 16.04. There is no guarantee that this module will work for other operating systems.


To execute acceptance tests...

PUPPET_INSTALL_TYPE=agent BEAKER_PUPPET_COLLECTION=puppet5 BEAKER_debug=true BEAKER_set=docker/centos-7 bundle exec rake beaker
PUPPET_INSTALL_TYPE=agent BEAKER_PUPPET_COLLECTION=puppet5 BEAKER_debug=true BEAKER_set=docker/ubuntu-18.04 bundle exec rake beaker

For this to work you must have docker installed and running locally

This module is currently maintained by Denver McAnally ( Please feel free to contribute. When doing so, please be sure to provide appropriate test coverage. Please see puppetlabs contribution guide for more information.

Netdata is developed and maintained at netdata/netdata.