Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
serviceescalation assignet to servicegroups #1756
I think there is an issue with escalations which are assigned to a servicegroup
This "old" fashioned Nagios escalation doesnt work - boss2 gets never informed.
The "new" escalation works nice (but does not fit well within my setup)
Fresh shinken 2.4.2 (pip) - Configuration migration from an (working) Nagios Setup cannot say if its new in 2.4.2...
Maybe somebody can me some advice to start troubleshooting? Is there a way to see the "compiled" running configuration which shinken use?
thanks in advance
Sorry for my late answer.
In your first configuration sample, you explicitly set the escalations on the host through the
I highly suspect that both methods are mutually exclusive (on a same host).
So I'd say that either you define the
Could you try with the old fashion configuration, but remove the
I have the same problem, not able to use old "serviceescalation" with servicegroups. Reproduced with minimal changes to template config of shinken 2.0, but also affects our "production" instances running 2.4.
Is this expected to work ??
It'd be really nice to know if this was expected/intended/tested to work.
I tried using servicegroup dependencies as described and found another problem.
It seems to me that servicegroups aren't exploded, as needed at least for dependencies and escalations .. no ?