alert using lastvalue different from value that triggered alert

[keul]

Hello,

I'm working with the zabbix trapper to send email when the server receive SNMP traps. But there's a problem when I receive traps in a short time (eg : send trap A B C D) : The email use {ITEM.LASTVALUE}.
And because the email process is launched a few seconds after the record of the zabbix trapped values in database, the {ITEM.LASTVALUE} return the wrong value, in my case : C D D D
({TRIGGER.VALUE} only return the result of the expression witch is 0, 1 or 2 for unknow))
Is there a way to add a macro {TRIGGER.TRIGGERING_VALUE} ?

I also found that the triggers are only triggered when the result of the expression changes (if I receive 2 traps with the word "temperature" in it, only the first one will be included). I've found 2 workarounds :
- send NO_NEW_DATA to the zabbix trapper
- send two times the trap and set the trigger to act when the 2 last values are different.
But it would be nice to set in trigger a checkbox with "auto-reset trigger" or "execute action each time expression returns true (and not only the first time it's found true)" or "execute action each time expression returns true and item value changes"

(the server is running zabbix 1.8.4 and will be upgraded to the last version in 2 weeks...)

[keul]

solution

(can some moderator remove the spam and add rel=nofollow?)

In fact, this one works :
{ITEM.VALUE}
(and {ITEM.VALUE1} {ITEM.VALUE2}… for each expression value)

But the system can bug when there is snmp traps sent at the same moment. I've added a delay of 0.5sec and it works