Zabbix 7.0.4
I have a data collection item which gathers some informatie from a website (JSON) this is called masteritem.
On this masteritem i have dependent item with preprocessing JSON path > this works
Discard unchanged > OK
However when the master item has a timeout and later becomes available again it writes the same value again in the history.
I don't really care about the value however the trigger i have on this item is fired as well that is something i want to prevent.
Trigger is
And without any changes this is fine. And when needed to trigger (a actual value change) this works fine as well.
The itemhistory shows a bunch of same values and looking at the logs i see that the master item was unsupported due to timeout a few times.
How can I prevent this from happening.
I was thinking about adding "Check for not supported value", any error as first pre-processing step in the dependent item. Only it's hard to test network time outs without triggering a switch of value (it's a HA cluster and wants to switch if there is an actual disruption between nodes) or should I add this to the master item?
I have a data collection item which gathers some informatie from a website (JSON) this is called masteritem.
On this masteritem i have dependent item with preprocessing JSON path > this works
Discard unchanged > OK
However when the master item has a timeout and later becomes available again it writes the same value again in the history.
I don't really care about the value however the trigger i have on this item is fired as well that is something i want to prevent.
Trigger is
Code:
changecount(/templatename/itemkey,4h)>0
The itemhistory shows a bunch of same values and looking at the logs i see that the master item was unsupported due to timeout a few times.
How can I prevent this from happening.
I was thinking about adding "Check for not supported value", any error as first pre-processing step in the dependent item. Only it's hard to test network time outs without triggering a switch of value (it's a HA cluster and wants to switch if there is an actual disruption between nodes) or should I add this to the master item?
Comment