I'm running Zabbix Agents on several Windows Servers (64bit, 2008+) and they all overflow at some point when querying net.if.in[nic] and net.if.out[nic]:
Fri May 8 12:31:56 EEST 2015 2005196881
Fri May 8 12:32:02 EEST 2015 2527914095
Fri May 8 12:32:07 EEST 2015 3053020449
Fri May 8 12:32:12 EEST 2015 3505404387
Fri May 8 12:32:17 EEST 2015 4004120839
Fri May 8 12:32:22 EEST 2015 249495793
Fri May 8 12:32:28 EEST 2015 787788455
Fri May 8 12:32:33 EEST 2015 1301655529
Fri May 8 12:32:38 EEST 2015 1813406369
All of the NICs are 1Gbit/s, so when saturated at max, the counter overflows very quickly. The grahps doesn't show anything above 400-500Mbit/s.
I thought using the 64bit zabbix agent would use 64bit counters, but it doesn't seem to be the case.
Since this issue has only been posted a few times (relating to older versions of Zabbix), I'm wondering what I am doing wrong/different. Any takes?
As a workaround to this issue, I created a new template which uses perf_counter to get the traffic numbers, but this has issues with special chars in the nic name (like #1, #2, [, ], /) when using low level discovery - for example # is converted to _ at some point.
Fri May 8 12:31:56 EEST 2015 2005196881
Fri May 8 12:32:02 EEST 2015 2527914095
Fri May 8 12:32:07 EEST 2015 3053020449
Fri May 8 12:32:12 EEST 2015 3505404387
Fri May 8 12:32:17 EEST 2015 4004120839
Fri May 8 12:32:22 EEST 2015 249495793
Fri May 8 12:32:28 EEST 2015 787788455
Fri May 8 12:32:33 EEST 2015 1301655529
Fri May 8 12:32:38 EEST 2015 1813406369
All of the NICs are 1Gbit/s, so when saturated at max, the counter overflows very quickly. The grahps doesn't show anything above 400-500Mbit/s.
I thought using the 64bit zabbix agent would use 64bit counters, but it doesn't seem to be the case.
Since this issue has only been posted a few times (relating to older versions of Zabbix), I'm wondering what I am doing wrong/different. Any takes?
As a workaround to this issue, I created a new template which uses perf_counter to get the traffic numbers, but this has issues with special chars in the nic name (like #1, #2, [, ], /) when using low level discovery - for example # is converted to _ at some point.
Comment