I am running Icinga 1.5 and trying to use escalation_condition similar to the one below in a serviceescalation definition. Before anyone replies that Icinga 1.5 is old...I know it is. I just want to know if I am doing something wrong or if this functionality doesn't work in 1.5. I will update to the newer version if it works in newer versions.
define serviceescalation {
hostgroup_name some-servers
service_description Apache: websites
first_notification 1
last_notification 0
notification_interval 120
contact_groups apacheContacts
escalation_condition host somehost=d
}
I am simulating an outage related to the above serviceescalation by changing the service check to look for the wrong return code. I verified that the alert was firing. I then added the above escalation_condition to the definition. The host "somehost" is UP in the Icinga GUI. After reading the Icinga docs, I expected that the alert would go into RECOVERY state and cause the above alert to be suppressed, this is not happening. Am I doing something wrong? I have reloaded the configuration etc. I also set host somewhat=u....I thought since d wasn't working doing the opposite might work, it didn't.
I have turned on debug and see that the check_escalation_condition has run, the output is below:
[1375455165.374406] [001.0] [pid=28175] check_escalation_condition()[1375455165.374413] [032.1] [pid=28175] Check host escalation condition somehost = 0.
[1375455165.374418] [032.1] [pid=28175] Check host escalation condition somehost = 0.
[1375455165.374423] [001.0] [pid=28175] is_valid_escalation_for_service_notification()
Any suggestions would be appreciated.
Regards
define serviceescalation {
hostgroup_name some-servers
service_description Apache: websites
first_notification 1
last_notification 0
notification_interval 120
contact_groups apacheContacts
escalation_condition host somehost=d
}
I am simulating an outage related to the above serviceescalation by changing the service check to look for the wrong return code. I verified that the alert was firing. I then added the above escalation_condition to the definition. The host "somehost" is UP in the Icinga GUI. After reading the Icinga docs, I expected that the alert would go into RECOVERY state and cause the above alert to be suppressed, this is not happening. Am I doing something wrong? I have reloaded the configuration etc. I also set host somewhat=u....I thought since d wasn't working doing the opposite might work, it didn't.
I have turned on debug and see that the check_escalation_condition has run, the output is below:
[1375455165.374406] [001.0] [pid=28175] check_escalation_condition()[1375455165.374413] [032.1] [pid=28175] Check host escalation condition somehost = 0.
[1375455165.374418] [032.1] [pid=28175] Check host escalation condition somehost = 0.
[1375455165.374423] [001.0] [pid=28175] is_valid_escalation_for_service_notification()
Any suggestions would be appreciated.
Regards
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
