I seem to have issues with dependencies again. I have a trigger to monitor when a system is rebooted. When it has, I don't want to get alerts that it becomes unavailable, obviously. However I do. The unavailable trigger is dependent on the reboot trigger. Has anyone had luck with 1.4.6 and getting this working?
-
-
Trigger dependencies
Hey there.
I have separate alerts, in the "Actions" page, for each of them, and I do not have both triggers dependent.
You can let zabbix fire the trigger internally but do not alert you when it does..
Simply create "alert rules" so that zabbix knows what to do when each type of trigger fires.
cheers,
Ivo -
The problem is both triggers will end up firing, if I could prevent the second trigger from firing, that would be optimal. I read the manual, and it appears that the trigger should still fire, but the action not take place. Maybe I should just wait for 1.6 to roll out in 2 weeks.Comment
-
Ok, I've read through WAY too much logging, and I've come across something curious. I rebooted a test system, which fires trigger 16573. My next ping check sees that it is dependent on 16573, and makes a note that it will not update. Then, I see this happen:
2696:20080905:102134 In update_triggers_status_to_unknown()
2696:20080905:102134 Query [select distinct t.triggerid,t.expression,t.description,t.status,t. priority,t.value,t.url,t.comments from hosts h,items i,triggers t,functions f where f.triggerid=t.triggerid and f.itemid=i.itemid and h.hostid=i.hostid and h.hostid=10025 and i.key_ not in ('status','icmpping','icmppingsec')]
2696:20080905:102134 In update_trigger_value(triggerid:13387,old:2,new:2,1 220624494,Host is unavailable.)
2696:20080905:102134 End update_trigger_value()
2696:20080905:102134 In update_trigger_value(triggerid:13384,old:2,new:2,1 220624494,Host is unavailable.)
2696:20080905:102134 End update_trigger_value()
2696:20080905:102134 In update_trigger_value(triggerid:13451,old:2,new:2,1 220624494,Host is unavailable.)
2696:20080905:102134 End update_trigger_value()
2696:20080905:102134 In update_trigger_value(triggerid:16573,old:1,new:2,1 220624494,Host is unavailable.)
2696:20080905:102134 In trigger_dependent(triggerid:16573)
2696:20080905:102134 In trigger_dependent_rec(triggerid:16573,level:0)
2696:20080905:102134 Query [select t.triggerid, t.value from trigger_depends d,triggers t where d.triggerid_down=16573 and d.triggerid_up=t.triggerid]
2696:20080905:102134 End of trigger_dependent_rec(ret:FAIL)
2696:20080905:102134 End of trigger_dependent(ret:FAIL)
2696:20080905:102134 In get_latest_event_status(triggerid:16573
2696:20080905:102134 Query [select eventid,value,clock from events where source=0 and object=0 and objectid=16573 order by clock desc limit 2]
2696:20080905:102134 tr value [1] event_prev_value [0] event_last_status [1] new_value [2]
2696:20080905:102134 Updating trigger
This appears to update the trigger status to Unknown, which coincides with my trigger log.
2008.Sep.05 10:21:34 UNKNOWN - 5.6 mins 13.2 mins 95.88%
2008.Sep.05 10:18:13 TRUE - 3.4 mins 3.4 mins 19.88%
Then the next check doesn't return the dependency, because the trigger is now unknown. Can someone explain WHY it sets my trigger to unknown after 3.5 minutes? This item is a zabbix trapper item.Comment
Comment