Agent active checks BufferSize
Hi all,
I'm running zabbix server 3.4 (last stable docker container from docker hub) to monitor systems running zabbix-agent version 2.2 with only active checks because of network connectivity issues.
Everything is working as expected, except that I want to configure some persistence on the agent when there is a connectivity problem to send the data to the master.
I setup the BufferSize to 65535 but what I see is that the agent only stores one value per item, for instance if I loose connectivity to master for 30min. and the cpu item is set to read that value every 60s, when the connection to master is back the agent only sends one value for that item for the whole 30min. :
key:'hostname:system.cpu.util[,system]' value:'3.210394'
from my understanding it should have sent 30 values for that same key, but what I see in the bedug logs, is that the JSON sent to master only has one key for every item being monitored. Is this the intended behavior? Or is this because of the agent version (2.2)? Or is it because I may be missing some config directive?
Thanks for any help
I'm running zabbix server 3.4 (last stable docker container from docker hub) to monitor systems running zabbix-agent version 2.2 with only active checks because of network connectivity issues.
Everything is working as expected, except that I want to configure some persistence on the agent when there is a connectivity problem to send the data to the master.
I setup the BufferSize to 65535 but what I see is that the agent only stores one value per item, for instance if I loose connectivity to master for 30min. and the cpu item is set to read that value every 60s, when the connection to master is back the agent only sends one value for that item for the whole 30min. :
key:'hostname:system.cpu.util[,system]' value:'3.210394'
from my understanding it should have sent 30 values for that same key, but what I see in the bedug logs, is that the JSON sent to master only has one key for every item being monitored. Is this the intended behavior? Or is this because of the agent version (2.2)? Or is it because I may be missing some config directive?
Thanks for any help