Dear visitor, in case we do not cover a topic you are looking for, then feel free to ask in our freshly created forum for IT-professionals for a solution. We hope our visitors can help you out with your questions. Have a good one. ~ Tom.

How to fix OP5 monitor execution time warning

In case you have a lot of monitors configured and/or monitors who will take some time until they are executed, it can happen that the OP5 internal monitor throws a warning about delays

Subject: [op5] PROBLEM: ‘Service check execution time’ on ‘thuop5.health.root.loc’ is WARNING

Service PROBLEM detected 2017-02-10 11:20:32.
‘Service check execution time’ on host ‘op5.yourdomain.local’ has passed the WARNING threshold.

Additional info:
WARNING: service execution_time min/avg/max = 0.00/0.92/96.76

To increase the WARNING and CRITICAL values, have a look at OP5 nrpe.cfg file. See below the default line commented out, the line above the commented out line contains the new WARNING and CRITICAL values.# cat /etc/nrpe.d/nrpe-merlin.cfg
###############################################################################
#
# op5-nrpe command configuration file
#
# COMMAND DEFINITIONS
# Syntax:
# command[<command_name>]=<command_line>
#
command[mon_procs]=/opt/plugins/check_procs -w 1:350 -c 1:600 -C naemon
command[mon_cpu]=/opt/plugins/check_procs -w 30 -c 50 --metric=CPU -C naemon
command[mon_vsz]=/opt/plugins/check_procs -w 700000 -c 800000 --metric=VSZ -C naemon
command[merlin_procs]=/opt/plugins/check_procs -w 1:1 -c 1:1 -C merlind
command[merlin_cpu]=/opt/plugins/check_procs -w 5 -c 10 --metric=CPU -C merlind
command[merlin_vsz]=/opt/plugins/check_procs -w 475000 -c 600000 --metric=VSZ -C merlind
command[mysql]=/opt/plugins/check_mysql -d merlin -u merlin -p merlin
command[mysql_vsz]=/opt/plugins/check_procs -w 5250000 -c 7500000 --metric=VSZ -C mysqld
command[mer_prog_status]=/usr/bin/asmonitor -q /usr/bin/mon check status
command[host_latency]=/usr/bin/asmonitor -q /usr/bin/mon check latency host
command[service_latency]=/usr/bin/asmonitor -q /usr/bin/mon check latency service
command[host_exectime]=/usr/bin/asmonitor -q /usr/bin/mon check exectime host
command[service_exectime]=/usr/bin/asmonitor -q /usr/bin/mon check exectime service --warning=1,5,100 --critical=5,30,120
#command[service_exectime]=/usr/bin/asmonitor -q /usr/bin/mon check exectime service
command[host_orphans]=/usr/bin/asmonitor -q /usr/bin/mon check orphans host
command[service_orphans]=/usr/bin/asmonitor -q /usr/bin/mon check orphans service
command[cores]=/usr/bin/asmonitor -q /usr/bin/mon check cores
command[spooled_checks]=/usr/bin/asmonitor -q /usr/bin/mon check spool checks --delete
command[spooled_perfdata]=/usr/bin/asmonitor -q /usr/bin/mon check spool perfdata
command[check_distribution]=/usr/bin/asmonitor -q /usr/bin/mon check distribution

Restart NRPE service after the file was modified# service nrpe restart

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.