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 servi
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:2
Am 07.11.2015 um 09:29 schrieb Ervin Hegedüs:
> Hi there,
>
Hi,
> 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
> af
Hi there,
may be this is a recurring question, but I didn't found any
information in documantation, or archives... Sorry.
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
