-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNMP plugin doesn't write proper instance value #1043
Comments
Added pcap file |
Maybe I'm not quite reading this right, what are the 2 OID levels that are missing? |
.1.16 is missing |
got it, I see what you mean, @titilambert do you happen to know why those two elements of the instance wouldn't be included? |
hum, I did never hit this bug :( |
Sure thing, I captured the following: snmprec.py --agent-udpv4-endpoint=172.23.10.30 --protocol-version=2c --start-oid=.1.3.6.1.4.1.3375.2.2.10.2.3.1 --stop-oid=.1.3.6.1.4.1.3375.2.2.10.2.3.1.44 --output-file=test.snmprec |
@slemire thanks ! Could you give me your telegraf configuration ? |
Here's the config: |
Problem is still there using the latest nightly: |
I think maxRepetition := uint8(32) might have something to do with it. My OID tree is longer than that. |
I see, I think that has come up before, we may want to make that a configurable option. What do you think @titilambert? |
Um, I think I got confused. The maxRepetition is just the standard SNMP RFC knob to manage the size of SNMP bulk GETs. I've tried smaller and larger settings without success. |
I'm having issues polling the virtual server stats off an F5 load-balancer. It seems like the snmp plugin doesn't write the proper value in the instance field. In the example below, it's not writing two levels of OIDs below what I've defined in the configuration. That throws off the mapping table when I try to use it. In the example I'm not using the mapping table but you can see the data written in InfluxDB is missing two OID levels above .47.
Database measurements:
Here's the snmpwalk of the OID:
The text was updated successfully, but these errors were encountered: