I’ve been using telegraf’s ‘new’ SNMP input plugin for over a year now, with great success, until I upgraded (via
sudo apt-get update && sudo apt-get upgrade) to v1.6.0 the other day. (I was bumped to InfluxDB 1.5.2 at the same time.)
Since then, my interface counter values are not incrementing, so my Grafana panels for network input/output (based on
non_negative_derivative of the raw 64bit interface counters) are all showing 0.
It took me a while to work out how to debug, as I don’t touch the setup much when it’s working… but I’ve now enabled a text output (in addition to influxdb output) temporarily, and I can see that Telegraf is sending the same value for several interfaces, which never changes. Some samples:
These values are supposed to be from my router’s interfaces (via SNMP):
if_counters,agent_host=192.168.2.1,host=pi5,hostname=ubnt,interface=eth0 bytes_recv=2147483647i,bytes_sent=2147483647i 1524127390000000000 if_counters,agent_host=192.168.2.1,host=pi5,hostname=ubnt,interface=eth1 bytes_recv=2147483647i,bytes_sent=2147483647i 1524127390000000000
And these are supposed to be from my NAS (again via SNMP):
if_counters,agent_host=192.168.2.50,host=pi5,hostname=DiskStation,interface=eth1 bytes_recv=2147483647i,bytes_sent=2147483647i 1524127390000000000 if_counters,agent_host=192.168.2.50,host=pi5,hostname=DiskStation,interface=bond0 bytes_recv=2147483647i,bytes_sent=2147483647i 1524127390000000000
The value of
2147483647i seems to be the one that Telegraf has decided to stick with indefinitely, for some reason - very odd!
If I manually query the same hosts and OIDs via SNMP tools, the correct values are returned, and they change over time, as expected, e.g.:
$ snmpwalk -v 2c -c public 192.168.2.1 .18.104.22.168.22.214.171.124.1.1.6 SNMPv2-SMI::mib-126.96.36.199.1.6.1 = Counter64: 6441722 SNMPv2-SMI::mib-188.8.131.52.1.6.2 = Counter64: 619142896005 SNMPv2-SMI::mib-184.108.40.206.1.6.3 = Counter64: 224393229223 SNMPv2-SMI::mib-220.127.116.11.1.6.4 = Counter64: 0 SNMPv2-SMI::mib-18.104.22.168.1.6.5 = Counter64: 0
Could you please advise if this is likely to be a bug or perhaps something wrong with my SNMP input config? The same config has worked fine for the past year, I should add.