Hm. IMO this is not enough: You will still get notifications if the host goes down between host and service check. There are workarounds though: you could play with „hard“ state settings for host and service as well, so you could guarantee that there will be a (hard) host state before any service check will switch to „hard“ state. I always draw a timeline for not getting confused :-)
Best wishes Jan Dreyer > Am 07.11.2015 um 16:31 schrieb Horatiu N <hora...@ddhosted.com>: > > Hi, this is probably caused by differences in host vs service check > intervals. > Lower your host checks or increase your service checks so that hosts are > checked more often than services thus avoiding service checks on a > down(ed) host. > > On 07-Nov-15 4:48 PM, Dustin Funk wrote: >> Am 07.11.2015 um 09:29 schrieb Ervin Hegedüs: >> >>> There are several hosts, with several services. Icinga2 is >>> working as well: if host gone to down, I get several e-mails >>> about host and the connected services. >>> >>> But if the host is DOWN, it would be enough to notify the >>> affected admin only about that - it doesn't need to send >>> notification about any services. >>> >> >> We got the same issue. [1] might help. >> >> Cheers, >> nuts >> >> http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/monitoring-basics#dependencies-implicit-host-service >> >> >> >> >> >> >> _______________________________________________ >> icinga-users mailing list >> icinga-users@lists.icinga.org >> https://lists.icinga.org/mailman/listinfo/icinga-users >> > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
