Hello,
I'm looking for suggestions on how to implement "discard unchanged" processing in a way that it will survive system/service reboot/restart.
As reported here:
and in the documentation, here:
"Discard unchanged" doesn't "survive" system/service reboot/restart.
Has anyone found a way/workaround to make this thing consistent even at system/service reboot/restart?
Thank you
I'm looking for suggestions on how to implement "discard unchanged" processing in a way that it will survive system/service reboot/restart.
As reported here:
and in the documentation, here:
For change and throttling preprocessing steps Zabbix has to remember the last value to calculate/compare the new value as required. These previous values are handled by the preprocessing manager. If Zabbix server or proxy is restarted or there is any change made to preprocessing steps the last value of the corresponding item is reset, resulting in:
- for Simple change, Change per second steps - the next value will be ignored because there is no previous value to calculated change from;
- for Discard unchanged. Discard unchanged with heartbeat steps - the next value will never be discarded, even if it should have been because of discarding rules.
Has anyone found a way/workaround to make this thing consistent even at system/service reboot/restart?
Thank you