Forge Home


A puppet module and report processor for zabbix.


10,684 latest version

4.1 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.0.1 (latest)
released Sep 19th 2012

Start using this module

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

Add this module to your Puppetfile:

mod 'thomasvandoren-zabbix', '0.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thomasvandoren-zabbix
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thomasvandoren-zabbix --version 0.0.1

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.

Tags: report, zabbix


thomasvandoren/zabbix — version 0.0.1 Sep 19th 2012

Zabbix Report Processor

Build Status


A Puppet report handler for sending data from puppet runs to Zabbix.


  • open4
  • puppet
  • zabbix_sender binary (comes with zabbix-agent packages, usually)

Installation and Usage

Puppet Master and Agents

  • Install the open4 gem on the puppet master.
sudo gem install open4
  • Install puppet-zabbix as a module in your puppet master's module path.

  • Update the zabbix_host, zabbix_port, and zabbix_sender variables in zabbix.yaml. Copy zabbix.yaml to /etc/puppet.

  • Enable pluginsync and reports on your master and clients in puppet.conf.

report     = true
pluginsync = true

reports = zabbix
  • Run the puppet client to sync the report as a plugin.


  • Import the zabbix template in doc/zabbix_template.xml.

  • Link the template to hosts managed by puppet. Note that the "technical" host name will need to match the puppet certname (defaults to FQDN) for each host.


Thomas Van Doren