Nagios Support Forum

Hi Team,

Current NagiosXI version 5.4.12
Core version : 4.2.4

As per Nagios if host is down, services will be suppressed automatically.
But, We found that once the Host is down, services are immediately triggering alerts before suppressing.
in short service alerts are triggering for the first time before getting suppressed

Hello, @vignesha. This is a design flaw in the latest Core. We already filed a bug report to fix this issue.
https://github.com/NagiosEnterprises/na ... issues/584

This only happens if a host goes into a Soft Critical State first. As a temporary workaround, you could change the max_check_attempts option to 1, for hosts in XI.

If you say that this issue is being solved in latest upgrade then we are can upgrade it to 5.5.3 nagiosXI version.


or else if we change the max_check_interval to 1 then we are facing alerts for host down frequently because there is slight connectivity issue where the ping response is dropped in between.... That's the reason we need we cannot set max_check_interval to 1... we are planning to keep 5,1,5 . At present its 3,1,3 due to which e are getting host down alert due to frequent ping issue

@vignesha, I see. At this point, I don't have the information whether this is going to be patched in the next XI release. It will depend on the complexity of the fix. However, feel free to check our GitHub page for updates or PM me and I'll update you on the status.

In our scenario .. The remote server is running fine with proper uptime, but we are getting home down alert due to latency or packet loss.. to over come this issue we are planning to set standard check interval for host i.e 5,1,5.
And for services 5,1,7.

This will take time for service to go down after host down .
Let us know if this would be the best practice to do.

This sounds like a good plan