Keeping Trigger Visbile if log file or trap changes

[Axilla]

I'm trying to setup SNMP Trap triggers but if a new trap comes in the trigger clears regardless... How can I prevent the trigger from clearing if the lastvalue changes?

Just because the last value changes doesn't mean the problem has gone away.. this leads to problems going unnoticed.

I have created a query which will allow me to clear an alarm if acknowledged but it does me no good if the trigger clears because a new unimportant trap has come in from zabbix_sender.

This is a major issue with zabbix as it renders log monitoring and snmp traps practically useless unless i'm doing something wrong. thoughts on how to get around this maybe sending triggers to a log file or something?

Clear trigger when acknowledged query

host=$1

SELECT count(t.triggerid) AS counter FROM triggers t JOIN functions f ON f.triggerid = t.triggerid JOIN items i ON i.itemid = f.itemid JOIN hosts h ON h.hostid = i.hostid JOIN events e ON e.objectid = t.triggerid WHERE h.ip = '$host' AND e.acknowledged = 0 AND e.value = 1 AND h.status = 0 AND t.value = 1 AND t.status = 0 AND i.status = 0;

[themons]

More ideas ???

This topic is quite old but I try to see if somebody had an idea since it was posted.

In my case I have an file transfer application. I would like every time a job succeed or fail a value is send to Zabbix (OK/KO - error message).

I agree I have to create a specific trigger for each flow. But if I can limit the number of item to manage it's a good thing.

If anybody have a GOOD idea, he's welcom.