Unexpected behavior of Zabbix'es trigger values calculation algorithm
I have strange situation:
My Zabbix 3.0.1 calculates item values perfectly and "as schedulled", but for some items triggers doesnt recalculates or calculates incorrectly.
For example, i have metric/item called "Cluster status", and it contains the word "green". But trigger, which checks equality of this word to "red", was calculated to "1". When i update table "triggers" in zabbix database directly (execute UPDATE statement) and set the value of the trigger to "0" - trigger did not turns to "1" again.
Before 06.11 all works properly with this triggers and items (nothing was added to zabbix).
Because there is no "last_clock" or so in the "triggers" table - i cant make it clear, when the trigger was calculated last time. Maybe its "problem" state is for 06.11, but last item value was collected at 08/11? - who knows
I'm in doubt, what to do: there are many (>10) triggers which "sticks on" "problem" value and never turns to "ok" itself, but keep its "ok" value if i set it by hand in db.
Anybody, help me, please. Maybe, you have some ideas, why trigger value may not appropriate to its corresponding item value?
Thank you very much!
My Zabbix 3.0.1 calculates item values perfectly and "as schedulled", but for some items triggers doesnt recalculates or calculates incorrectly.
For example, i have metric/item called "Cluster status", and it contains the word "green". But trigger, which checks equality of this word to "red", was calculated to "1". When i update table "triggers" in zabbix database directly (execute UPDATE statement) and set the value of the trigger to "0" - trigger did not turns to "1" again.
Before 06.11 all works properly with this triggers and items (nothing was added to zabbix).
Because there is no "last_clock" or so in the "triggers" table - i cant make it clear, when the trigger was calculated last time. Maybe its "problem" state is for 06.11, but last item value was collected at 08/11? - who knows
I'm in doubt, what to do: there are many (>10) triggers which "sticks on" "problem" value and never turns to "ok" itself, but keep its "ok" value if i set it by hand in db.
Anybody, help me, please. Maybe, you have some ideas, why trigger value may not appropriate to its corresponding item value?
Thank you very much!