Nagios: monitor that resultsdb sends messages on the bus

Signed-off-by: Clement Verna <cverna@tutanota.com>
This commit is contained in:
Clement Verna 2019-04-24 09:48:26 +02:00
parent de0f2763a9
commit 93d0eeaf54
2 changed files with 7 additions and 0 deletions

View file

@ -40,6 +40,7 @@ command[check_datanommer_autocloud]={{libdir}}/nagios/plugins/check_datanommer_t
command[check_datanommer_twoweekatomic]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py org.fedoraproject.prod.releng.atomic.twoweek.complete 1296000 1382400
command[check_datanommer_mdapi]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py mdapi 28800 86400
command[check_datanommer_greenwave]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py greenwave 172800 172800
command[check_datanommer_resultsdb]=/usr/lib64/nagios/plugins/check_datanommer_timesince.py resultsdb 172800 172800
# This one is retired since it times out all the time. Too few messages.
#command[check_datanommer_nuancier]={{libdir}}/nagios/plugins/check_datanommer_timesince.py nuancier 23652000 31536000

View file

@ -320,6 +320,12 @@ define service {
check_command check_by_nrpe!check_datanommer_greenwave
use defaulttemplate
}
define service {
host_name busgateway01.phx2.fedoraproject.org
service_description Check datanommer for recent resultsdb messages
check_command check_by_nrpe!check_datanommer_resultsdb
use defaulttemplate
}
# BEGIN, check consumers and producers