Forge Home

35,337 downloads

3,272 latest version

5.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

  • 0.1.24 (latest)
  • 0.1.23
  • 0.1.22
  • 0.1.20
  • 0.1.19
  • 0.1.18
  • 0.1.16
  • 0.1.15
  • 0.1.14
  • 0.1.13
  • 0.1.12
  • 0.1.11
  • 0.1.10
  • 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 Jan 17th 2017
This version is compatible with:
  • Puppet Enterprise >= 3.8.0
  • Puppet >= 3.8.0
  • , , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'eyp-nrpe', '0.1.5'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-nrpe
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-nrpe --version 0.1.5

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

eyp/nrpe — version 0.1.5 Jan 17th 2017

nrpe

Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development

Overview

NRPE setup and configuration

Module Description

This module installs NRPE and manages it's configuration file

Setup

What nrpe affects

  • A list of files, packages, services, or operations that the module will alter, impact, or execute on the system it's installed on.
  • This is a great place to stick any warnings.
  • Can be in list or paragraph form.

Setup Requirements

This module requires pluginsync enabled

Beginning with nrpe

class { '::nrpe':
  dont_blame_nrpe   => true,
  allowed_hosts     => [ '1.2.3.4', '1.1.1.1' ],
  nrpe_conf_dir     => '/etc/nagios/nrpe.d/',
  nrpe_conf_purge   => false,
  nrpe_conf_recurse => true,
}

Usage

nrpe::command { 'check_plugin_custom':
  command => '$ARG1$',
}

Reference

classes

nrpe

  • dont_blame_nrpe: # This option determines whether or not the NRPE daemon will allow clients to specify arguments to commands that are executed. (default: false) - WARNING: On Ubuntu 16.04 this option is ignored due to a supposed security risk
  • allow_bash_command_substitution = false
  • debug = false
  • command_timeout = '60'
  • connection_timeout = '300'
  • allow_weak_random_seed = false
  • install_plugins = true
  • allowed_hosts = [ '127.0.0.1' ]
  • command_prefix = undef
  • nrped_purge = true
  • nrped_recurse = true
  • server_address = undef
  • server_port = '5666'
  • username = $nrpe::params::username_default,
  • group = $nrpe::params::group_default,
  • nrpe_conf_dir = $nrpe::params::nrpe_conf_dir_default,

defines

nrpe::command

nrpe::includedir

Limitations

Tested on:

  • CentOS 5
  • CentOS 6
  • CentOS 7
  • Ubuntu 14.04

Development

We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature

TODO

  • multi instance support
  • enable/disable SSL support

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request