Two triggers on 1 item

[ronfulkerson]

Hello All,

I am attempting to setup two triggers on a single item using Zabbix 1.8.10. The first trigger (triggerA) has a High Severity for an item value above a certain threshold. The second trigger (triggerB) has a Warning Severity for a lower value on the same item.

I have made triggerB dependent on triggerA to prevent both from firing simultaneously. This, however, is not working. It appears that there is a race like condition, but because I am using the same item I cannot adjust the update interval to prevent this from happening.

I am hopeful that I can get both triggers working as desired. Has anyone encountered a similar situation in the past? What is the best solution?

Thanks for any ideas!

[c.mammoli]

Hello All,

I am attempting to setup two triggers on a single item using Zabbix 1.8.10. The first trigger (triggerA) has a High Severity for an item value above a certain threshold. The second trigger (triggerB) has a Warning Severity for a lower value on the same item.

I have made triggerB dependent on triggerA to prevent both from firing simultaneously. This, however, is not working. It appears that there is a race like condition, but because I am using the same item I cannot adjust the update interval to prevent this from happening.

I am hopeful that I can get both triggers working as desired. Has anyone encountered a similar situation in the past? What is the best solution?

Thanks for any ideas!

I don't use dependences:

Suppose you monitor cpu usage and want a warning trigger when load is higher than 75% and an average trigger when then load i higher than 90%:

warning trigger: {Template:cpu.load}>75 & {Template:cpu.load}<90
average trigger: {Template:cpu.load}>90

[ronfulkerson]

Thanks for your reply. I had come up with something very similar, but was hoping someone had got dependencies to work.

In my approach, I prevent the warning trigger from being 'resolved' when the severity goes from warning to critical:

warning trigger: ({TRIGGER.VALUE}=0&{Template:cpu.load}>75 & {Template:cpu.load}<90)|({TRIGGER.VALUE}=1&{Templa te:cpu.load}>75)

Thanks for your input. I appreciate the great community that exists around Zabbix!

[c.mammoli]

Yep, but there are no dependencies for trigger prototypes in 2.0 so I went straight with the same approach everywhere