You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ups_mibs:
walk:
- 1.3.6.1.4.1.318.1.1.1.9.3.3.1.8metrics:
- name: upsPhaseOutputMaxLoadoid: 1.3.6.1.4.1.318.1.1.1.9.3.3.1.8type: gaugehelp: The maximum output load in VA measured since the last reset (upsPhaseResetMaxMinValues),or -1 if it's unsupported by this UPS - 1.3.6.1.4.1.318.1.1.1.9.3.3.1.8indexes:
- labelname: upsPhaseOutputPhaseTableIndextype: gauge
- labelname: upsPhaseOutputPhaseIndextype: gaugeversion: 3auth:
community: publicsecurity_level: authPrivusername: <redacted>password: <redacted>auth_protocol: MD5priv_protocol: DESpriv_password: <redacted>
Then running snmp and prometheus in a docker-compose file (in notes section below), I used the following link to view the scrape data from Prometheus http://localhost:9116/snmp?module=ups_mibs&target=<redacted>
What did you expect to see?
I expected to see three values one for each phase of power from the device with the OID above.
What did you see instead?
An error has occurred during metrics gathering:
2 error(s) occurred:
* collected metric upsPhaseOutputMaxLoad label:<name:"upsPhaseOutputPhaseIndex" value:"1" > label:<name:"upsPhaseOutputPhaseTableIndex" value:"1" > gauge:<value:27280 > was collected before with the same name and label values
* collected metric upsPhaseOutputMaxLoad label:<name:"upsPhaseOutputPhaseIndex" value:"1" > label:<name:"upsPhaseOutputPhaseTableIndex" value:"1" > gauge:<value:25660 > was collected before with the same name and label values
I ran a snmpwalk and see that the correct values are returning from the device:
snmpbulkwalk -v3 -On -t 60 -u <redacted> -l authPriv -a MD5 -A <redacted> -x DES -X <redacted> -M /usr/share/snmp/mibs/ -m all u<redacted> upsPhaseOutputMaxLoad
.1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.1 = INTEGER: 23010
.1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.2 = INTEGER: 27280
.1.3.6.1.4.1.318.1.1.1.9.3.3.1.8.1.1.3 = INTEGER: 25660
Host operating system: output of
uname -a
:Linux localhost.localdomain 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
snmp_exporter version: output of
snmp_exporter -version
:Docker container:
prom/snmp-exporter:master
What device/snmpwalk OID are you using?
1.3.6.1.4.1.318.1.1.1.9.3.3.1.8
If this is a new device, please link to the MIB(s):
MIB
What did you do that produced an error?
I followed the procedures for generating and using the snmp_exporter to gather snmp metrics.
I used the
generator
to generate a snmp.yml file - the generator.yml file contains:The snmp.yml file:
Then running snmp and prometheus in a docker-compose file (in notes section below), I used the following link to view the scrape data from Prometheus
http://localhost:9116/snmp?module=ups_mibs&target=<redacted>
What did you expect to see?
I expected to see three values one for each phase of power from the device with the OID above.
What did you see instead?
I ran a
snmpwalk
and see that the correct values are returning from the device:Notes:
Here is the prometheus.yml section:
And the docker-compose.yml file, which should help with running this:
I've also read through the issues and google Groups but cannot determine if this is a configuration error on my part or a bug in the snmp_exporter.
The text was updated successfully, but these errors were encountered: