Incorrect mappings for new MIB #338
Comments
|
The issue here is the MIB, this should really be using a table rather than repeating the same thing 4 times. I'd suggest adjusting the MIB accordingly, with a dummy integer object for the index. |
|
It looks like the teltonika MIB is a bit invalid, as it assigns the same metric name to multiple OIDs. $ grep -A3 hotSpotUsersIp snmp.yml
- name: hotSpotUsersIp
oid: 1.3.6.1.4.1.48690.3.1.11
type: DisplayString
help: RUT2xx hot spot user ip address - 1.3.6.1.4.1.48690.3.1.11
--
- name: hotSpotUsersIp
oid: 1.3.6.1.4.1.48690.3.2.11
type: DisplayString
help: RUT2xx hot spot user ip address - 1.3.6.1.4.1.48690.3.2.11
--
- name: hotSpotUsersIp
oid: 1.3.6.1.4.1.48690.3.3.11
type: DisplayString
help: RUT2xx hot spot user ip address - 1.3.6.1.4.1.48690.3.3.11
--
- name: hotSpotUsersIp
oid: 1.3.6.1.4.1.48690.3.4.11
type: DisplayString
help: RUT2xx hot spot user ip address - 1.3.6.1.4.1.48690.3.4.11 |
|
Thanks guys for the reply! I've emailed their support about it, will keep this updated. Once it's ready, I'll merge it in. |
|
@sc250024 Maybe you can get them to support Prometheus/OpenMetrics directly. 😀 It's going to be a bit difficult to fix, since the devices are exposing the OIDs incorrectly for a normal table/entry walk to work (like it does with |
|
@SuperQ I ended up taking out the Here's an example: In the case of Normally metrics are in the format: But these metrics are a bit screwy. The actual value that I'm actually interested in is inside the |
|
@sc250024 Yea, the MIB and the "table" is invalid. You're going to have to write an snmp.yml for this by hand. |
|
The "table" is okay, it should be possible to write a MIB for this. |
Greetings
I'm trying to add Teltonika MIBs to this repository for future use. First I am using the generator, and testing it out within our infrastructure. I'm receiving some weird errors when I try to manually check using the
snmp_exporterinterface:Output of http://localhost:9116/snmp?target=10.161.XX.YY&module=teltonika
It seems as if the OID mappings are off. Here's the MIB provided by the manufacturer, which has a table of OIDs: https://wiki.teltonika.lt/index.php?title=SNMP
And a link to the MIB itself: https://wiki.teltonika.lt/images/9/98/TLT-MIB_RUT2XX.txt
I'm a little confused as to the error message in general. What does that mean?
Host operating system: output of
uname -aKubernetes, running Debian 9 nodes:
Linux ip-10-62-220-179 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
snmp_exporter version: output of
snmp_exporter -versionWhat device/snmpwalk OID are you using?
The base OID is
1.3.6.1.4.1.48690. The Teltonika wiki link above provides an exhaustive list of all the potential OIDs.If this is a new device, please link to the MIB(s).
See above
What did you do that produced an error?
Downloaded MIBs using
make mibsinsnmp_exporter/generator:Added the following to the
generator.ymlfile insnmp_exporter/generator:snmp.yamlfiles, and baked it into a custom Docker image. Here's theteltonikapart of thesnmp.yamlfile:snmp-teltonika.yaml
snmp-exporter, and called the URL http://localhost:9116/snmp?target=10.161.XX.YY&module=teltonika with port forwarding to Kubernetes enabled.What did you expect to see?
Prometheus formatted metrics in plain text
What did you see instead?
The error messages above.
The text was updated successfully, but these errors were encountered: