I have adjusted the Nagios interval_length value to be 1 (from 60) so that several hosts are pinged every second. I have had to make some rules in WATO to change the “normal check interval for service checks” for agent hosts to be polled
at a more reasonable frequency. However, the input (and display) for this particular rule doesn’t consider the adjusted Nagios interval_length. So a check that I want to execute every 5 minutes needs to be scheduled to be checked every 5 hours.
The Nagios configuration that is generated (found with cmk –N (host)) reflects correct – the service gets checked every 300 seconds.
When I look at the service, the “time since last check” and “time of the next scheduled check” are correct (as being within the 5 minute window) – it’s just the configuration within WATO.
Is there a way to tell WATO that the interval_length is no longer 60?
No, as CMK don’t change anything inside the normal Nagios configuration.
You need to remember the factor how to multiply the check_interval to get the real interval the checks are done.
I have adjusted the Nagios interval_length value to be 1 (from 60) so that several hosts are pinged every second. I have had to make some rules in WATO to change the “normal check interval for service checks” for agent hosts to be polled
at a more reasonable frequency. However, the input (and display) for this particular rule doesn’t consider the adjusted Nagios interval_length. So a check that I want to execute every 5 minutes needs to be scheduled to be checked every 5 hours.
The Nagios configuration that is generated (found with cmk –N (host)) reflects correct – the service gets checked every 300 seconds.
When I look at the service, the “time since last check” and “time of the next scheduled check” are correct (as being within the 5 minute window) – it’s just the configuration within WATO.
Is there a way to tell WATO that the interval_length is no longer 60?