Hi,
it seems that Shinken ignores the check_period parameter for passive hosts and services checks ... is there any solution for that passively submitted checks are ignored for certain period of time ?
BR, Fred.
Hi,
it seems that Shinken ignores the check_period parameter for passive hosts and services checks ... is there any solution for that passively submitted checks are ignored for certain period of time ?
BR, Fred.
Nop, passive is toally under taht sender responsability sorry![]()
No direct support by personal message. Please open a thread so everyone can see the solution
I think that it should be interesting il Shinken was able to take care about check_period ... even if a new parameter is necessary. What do you think about it ?
For passive? not sure that getting the responsability for cheduling is a good idea, after all, the last state is always better than the old one. If you don't want notification, look at first_notification_delay parameter![]()
No direct support by personal message. Please open a thread so everyone can see the solution