I've had this issue posted to this mailing list some months ago, and the reply I received was that the dependencies that a service has to it's parent host are automatically created.

So, what definitions would anybody need to create ?

I am also interested in fixing this.

On 2/10/2017 3:44 PM, Antony Stone wrote:
On Friday 10 Feb 2017 at 13:29, Jorge Ferrando wrote:

Hi Antony

I already read that before but I don't see how that can solve my problem.
Can you clarify it?

"If the dependency should be triggered in the parent object's soft state, you
need to set ignore_soft_states to false."

Have you done that?

I guess that also applies for icinga2 and that's exactly the problem. Host
is DOWN but SOFT so I don't get any notification. But that makes the
service DOWN and HARD so I immediately get a notification for every service
in the host. That's what I want to avoid.

Maybe you should show us the dependency definitions you've created for an
example host/service, so we can see where you're starting from.


Antony.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to