From 117c0fef2353a8cb855e1424c534b714bf343e7b Mon Sep 17 00:00:00 2001 From: Arne Teuke Date: Mon, 13 Sep 2021 15:38:55 +0200 Subject: [PATCH] TODO-0001 - markdown lint --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c5ba5e1..1572630 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ All dependencies must be included in the catalogue. ## Deployment `cd_nrpe` does typically not need to be specifically declared. It will be auto-required by `cd_nagios` with default settings. Only if you want to override settings declare it specifically. - + * native Puppet deployment via site.pp or nodes.pp @@ -76,14 +76,15 @@ In order to connect a Nagios monitoring server to clients through NRPE, you must The commands are created within /etc/nrpe.d/command.cfg , every set of instructions creates a new line. Defining commands is as simple as that: -``` + +```ruby cd_nrpe::commands::definitions { 'check_users': ne_check_cmd => 'check_users', ne_cmd_argstring => '-w $ARG1$ -c $ARG2$', } ``` -It is very recommendable to define such commands directly within Puppet modules or profiles, so any node running the particular service controlled by the module will automatically get the required check commands defined as well, while nodes not running the service also do not contain the command check. The same then is true for Nagios checks, so you would have both the NRPE command definition and the Nagios check contained in Puppet modules or profiles to have it in one location. +It is very recommendable to define such commands directly within Puppet modules or profiles, so any node running the particular service controlled by the module will automatically get the required check commands defined as well, while nodes not running the service also do not contain the command check. The same then is true for Nagios checks, so you would have both the NRPE command definition and the Nagios check contained in Puppet modules or profiles to have it in one location. ## SELINUX