add twoweek atomic compose check

This commit is contained in:
Adam Miller 2016-01-29 15:50:12 -06:00 committed by Adam Miller
parent 8ebf1bed9d
commit 8f3a5a2015
2 changed files with 21 additions and 14 deletions

View file

@ -316,6 +316,12 @@ define service {
check_command check_by_nrpe!check_datanommer_autocloud
use defaulttemplate
}
define service {
host_name busgateway01
service_description Check datanommer for recent compose
check_command check_by_nrpe!check_datanommer_twoweekatomic
use defaulttemplate
}
# BEGIN, check consumers and producers

View file

@ -1,7 +1,7 @@
#############################################################################
# Sample NRPE Config File
# Sample NRPE Config File
# Written by: Ethan Galstad (nagios@nagios.org)
#
#
# Last Modified: 12-11-2006
#
# NOTES:
@ -39,9 +39,9 @@ server_port=5666
# NRPE USER
# This determines the effective user that the NRPE daemon should run as.
# This determines the effective user that the NRPE daemon should run as.
# You can either supply a username or a UID.
#
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
nrpe_user=nrpe
@ -49,9 +49,9 @@ nrpe_user=nrpe
# NRPE GROUP
# This determines the effective group that the NRPE daemon should run as.
# This determines the effective group that the NRPE daemon should run as.
# You can either supply a group name or a GID.
#
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
nrpe_group=nrpe
@ -59,7 +59,7 @@ nrpe_group=nrpe
# ALLOWED HOST ADDRESSES
# This is an optional comma-delimited list of IP address or hostnames
# This is an optional comma-delimited list of IP address or hostnames
# that are allowed to talk to the NRPE daemon.
#
# Note: The daemon only does rudimentary checking of the client's IP
@ -71,16 +71,16 @@ nrpe_group=nrpe
#allowed_hosts=127.0.0.1,192.168.0.2
allowed_hosts=10.5.126.41,127.0.0.1,192.168.1.10,192.168.1.20,209.132.181.35
# COMMAND ARGUMENT PROCESSING
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments to commands that are executed. This option only works
# if the daemon was configured with the --enable-command-args configure script
# option.
# option.
#
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
@ -96,9 +96,9 @@ dont_blame_nrpe=0
# command line from the command definition.
#
# *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
# Usage scenario:
# Usage scenario:
# Execute restricted commmands using sudo. For this to work, you need to add
# the nagios user to your /etc/sudoers. An example entry for alllowing
# the nagios user to your /etc/sudoers. An example entry for alllowing
# execution of the plugins from might be:
#
# nagios ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
@ -107,7 +107,7 @@ dont_blame_nrpe=0
# without asking for a password. If you do this, make sure you don't give
# random users write access to that directory or its contents!
# command_prefix=/usr/bin/sudo
# command_prefix=/usr/bin/sudo
@ -278,6 +278,7 @@ command[check_datanommer_fedocal]=/usr/lib64/nagios/plugins/check_datanommer_tim
command[check_datanommer_ansible]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py ansible 432000 604800
command[check_datanommer_anitya]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py anitya 604800 1814400
command[check_datanommer_autocloud]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py autocloud 604800 1814400
command[check_datanommer_twoweekatomic]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py org.fedoraproject.prod.releng.atomic.twoweek.complete 172800 345600
# These are not actually finished and deployed yet
command[check_datanommer_mailman]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py mailman 14400 86400
@ -355,7 +356,7 @@ command[service_httpd_graceful]=/usr/bin/sudo /sbin/service httpd graceful
command[service_rsyslog_restart]=/usr/bin/sudo /sbin/service rsyslog restart
# The following examples allow user-supplied arguments and can
# only be used if the NRPE daemon was compiled with support for
# only be used if the NRPE daemon was compiled with support for
# command arguments *AND* the dont_blame_nrpe directive in this
# config file is set to '1'...