31 Jul
2012
31 Jul
'12
11:08 a.m.
Ok. I've put in place. Looks like the crank errors had already been in the queue before I got this done. We'll see when they come back if we get flooded with errors. I'm also thinking that the NRPE checks should return UNKNOWN state instead of CRITICAL and have the actual NRPE health check return critical when it fails. On Jul 31, 2012, at 11:04 AM, Craig Stacey <[email protected]> wrote:
No argument here. Sounds like a great idea. -- Craig
On Jul 31, 2012, at 10:37 AM, Ti Leggett wrote:
Does anyone object to adding service dependencies for all NRPE checks on check_remote_nrpe service check? That way when NRPE goes south, we don't a flood of other notifications (like with crank last night).