Just my 2 cents:
UNIVENTION_NAGIOS
uses check_univention_procs_name
as plugin command. check_univention_procs_name
itself just calls check_procs
like this:
/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ -C $ARG3$
The arguments are defined at the LDAP object of the check UNIVENTION_NAGIOS
and can be altered via the UMC. The default is:
1:1!1:!nscd
This means check_procs
is called like this (the exclamation mark “!
” is the separator here):
/usr/lib/nagios/plugins/check_procs -w 1:1 -c 1: -C nscd
And this translates to:
- Generate a WARNING state if not exactly 1 process of
nscd
is running (the range ismin:max
) - Generate a CRITICAL state if no process of
nscd
is running (the given1:
means < 1)
With this knowledge we can add a custom Nagios check in the UMC, copy all the settings from UNIVENTION_NSCD but adjust the min:max
range as we need it and link this new check to the UCS host. With a UCS system with one Docker App running an additional nscd, we probably want something like this:
/usr/lib/nagios/plugins/check_procs -w 2:2 -c 2: -C nscd
For the UMC entry plugin command parameter, this would be:
2:2!2:!nscd
Best regards,
Michael