nsca_report

Report puppet runs to Nagios/Icinga using NSCA

Alexander Hofmann

alexh

9,415 downloads

9,215 latest version

3.9 quality score

Version information

  • 0.0.2 (latest)
  • 0.0.1
released Oct 9th 2013

Start using this module

Documentation

alexh/nsca_report — version 0.0.2 Oct 9th 2013

#puppet-nsca_report

####Table of Contents

  1. Overview
  2. Setup

Overview

The nsca_report module ships a custom puppet report processor to process and send the results of puppet agent runs to a Nagios/Icinga monitoring server.

Setup

Nagios/Icinga

On the Nagios/Icinga side configure a passive service check for each puppet client:

define service{
        use                             linux-service
        hostgroup_name                  linux
        service_description             NRPE_puppet_status
        check_command                   check_nrpe!check_filetime.py\!/var/lib/puppet/state/state.yaml\!3h\!4h
        max_check_attempts              1
        freshness_threshold             6000
        active_checks_enabled           0
        check_freshness                 1
        }

Puppetmaster

In order to process and send the Puppet agents results, enable report processing in /etc/puppet/puppet.conf.

On each puppet client put

  report = true 

in /etc/puppet/puppet.conf

On the server-side put

  reports = nsca
  pluginsync = true

in /etc/puppet/puppet.conf

The NSCA report expects a configuration file with connection information in /etc/puppet/nsca.yaml. Example:

---
:nsca_binary: /usr/bin/send_nsca
:nsca_host: <HOSTNAME>
:nsca_config: /etc/nagios/send_nsca.cfg
:nsca_port: 5667
:service_desc: NRPE_puppet_status
:strip_domain: true
:only_env: production