Can I exclude a check from being a "Problem"

[salderman1]

Hi,
We are using the check_yum plugin on RHEL variants to monitor available updates. I am curious if there is a way to exclude this service's status from being included as a "problem" when the returned status is not OK? Overall, I have about 140 hosts and 1440 services monitored, out of 52 "problems" today, 50 of them are check_yum results. We enjoy having the check_yum information, but we do not alert on the check.

I would appreciate anyone's suggestions.

Thank you for your time and consideration!

[sreinhardt]

Looking through the status page(where this is generated) filters, filtering specifically via hostname\service name does not seem to be possible. You can use other host\service properties, such as notifications disabled, so if you wanted to set one of those properties specifically for these services it would be possible. Otherwise it would require changes to the C code of the cgi\status.c file and a recompile of the nagios cgis.

[salderman1]

Looking through the status page(where this is generated) filters, filtering specifically via hostname\service name does not seem to be possible. You can use other host\service properties, such as notifications disabled, so if you wanted to set one of those properties specifically for these services it would be possible. Otherwise it would require changes to the C code of the cgi\status.c file and a recompile of the nagios cgis.

Thanks for taking a look, I suspected there would not be a whitelist/blacklist feature. We already do not notify on this service, my present concern is simply the reducing non-problem noise in the Nagios WebUI.

This isn't something that would be available if we went stepped up to the XI product is it?

[slansing]

Well, you could remove the ability for it to alert by removing contact associations, and/or states that are alerted on, and/or disabling notifications on the object completely. These options still hold true in Nagios XI.