Freshness Checking Clarification

[jbennett]

Per the documentation, I see where I can turn on fresheness checking for the entire Nagios install for hosts and for services.

I would like to enable freshness checking for just a single service that comes over via NRDS (I have around 40 checks per host).

I have set this on the service from within the CCM but I'm wondering how the settings in nagios.cfg come into play.

If I have the following set in this file, does it over ride the settings from within CCM?
check_service_freshness=1
service_freshness_check_interval=60

Since our install has close to 19000 service checks, I don't necessarially want to check ALL of them for freshness. It seems like it would make more sense to just check one service that all hosts return for freshness.

On that note, how are service checks forced with NRDS if the freshenss check finds the last result out of date?

[slansing]

The nagios.cfg object only checks freshness periodically. It does not mean that nagios will check the freshness of every host and service at rates of a minute or less "this can cause huge performance issues." You should be all set to go, the default is "1" and I would leave that as it is.

http://nagios.sourceforge.net/docs/3_0/freshness.html

Typically we see users use the check_dummy check as the active check that is triggered when freshness checking finds results to be stale, you can then have check_dummy post a status message to your service, for example "No backups were ran in the last 24 hours" or something to that effect.

[jbennett]

Typically we see users use the check_dummy check as the active check that is triggered when freshness checking finds results to be stale, you can then have check_dummy post a status message to your service, for example "No backups were ran in the last 24 hours" or something to that effect.

I just went and re-read the freshness page again. This draws it all together.

I will give this a try.

Many thanks.

[abrist]

No problem, let us know if you have any other issues.