Ben Kochie
Ben Kochie
This seems solved.
For questions/help/support please use our [community](https://prometheus.io/community/) channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided.
I think that was one of those cases where the device and the MIB don't match. I'd have to dig through the issues, but I've seen that one before.
For questions/help/support please use our [community](https://prometheus.io/community/) channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided.
For questions/help/support please use our [community](https://prometheus.io/community/) channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided.
This does seem like there may be an actual walk issue with SNMPv1 here. But it does seem like this is a device bug we may need to workaround in...
I wonder if we should change the exporter default to 10 to match net-snmp.
@dswarbrick I setup https://github.com/prometheus-community/snmp as a place to start a project to create a whole bunch of snmp_exporter generator.yml examples for various devices. But I never got around to deciding...
This needs a DCO sign-off. You can use `git commit -s --amend` to add it.
This belongs in promu.