ITEMVALUE and ITEM.VALUE different. False trigger

[Andrea Cariddi]

Hello, i am having very strange problems with triggers. I think is a some sort of Bug. Sure you can help me.

I take an example from the last case that happened to me today.

In the screenshot Trigger.png Zabbix trigger an error as if the first value

xxxx.linux.backup-rdx: urbackup.last_image_date [Dc01] .last ()}> 0

was above 0.

As you can see from the values on the right the last value is -1. I then added, to understand what happens and why it happens, the tags

L: {ITEM.LASTVALUE} V: {ITEM.VALUE}

to the name of the trigger (See screenshot Discovery_Item.png) and actually they are different.
Zabbix seems consider ITEM. VALUE (old for me in this case) and not ITEM.LASTVALUE which is correct.
In the screenshot Last.png you can see the last values of the item.

But shouldn't ITEM.LASTVALUE and ITEM.VALUE be the same? Why zabbix gives me this error when the last value is correctly less than 0 and not greater?

Thanks

Zabbix Server: zabbix-server-mysql-4.0.31-1.el7.x86_64

[Andrea Cariddi]

After some test i see this problems in many triggers that always alert for previous value (Corresponding to {ITEM.VALUE}) and not to the real last value ({ITEM.LASTVALUE}). Any help?

Thanks

[cyber]

ITEM.VALUE and ITEM.LASTVALUE are not always the same... Depends, what are you looking at at the moment... problem list or events or something else...
As long as I see, everything is fine... using ITEM.VALUE in problem name resolves to "at the time value"ITEM.LASTVALUE will display latest value, which does not have to be the same any more, what it was at the time of event..
If you open the event, you might see different numbers. Probably both L and Vwill be 9...
Because: {ITEM.LASTVALUE} - "Note that since 4.0, when used in the problem name, it will not resolve to the latest item value when viewing problem events, instead it will keep the item value from the time of problem happening."