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
Hi all, i'm not sure i can open a issue for this behaviour but you will tell me :). I'm a simple network engineer so i'm sorry if my understanding of the snmp_exporter code is really limited.
Host operating system: output of uname -a
Linux sys-d063323c.ctrl.cs 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
snmp_exporter version: output of snmp_exporter -version
snmp_exporter, version 0.8.0 (branch: HEAD, revision: 17cefca)
build user: root@57f813d2791a
build date: 20171120-12:36:57
go version: go1.9.2
What device/snmpwalk OID are you using?
ltmVirtualServStatClientCurConns | 1.3.6.1.4.1.3375.2.2.10.2.3.1.12 from F5-BIGIP-LOCAL-MIB
If this is a new device, please link to the MIB(s).
When i check the /metrics output from snmp_exporter for that target i can see this error.
collected metric "ltmVirtualServStatClientCurConns" { label:<name:"ltmVirtualServStatName" value:"/Common/ref-si-silo-cs-pdct-rp2web2app.private.sfr.com.app/vip-ref-si-silo-cs-pdct-rp2web2app.pri" > counter:<value:0 > } was collected before with the same name and label values
I should have two different metrics with two different "ltmVirtualServStatName" label value below:
but it seems that the "ltmVirtualServStatName" label_value is limited to "/Common/ref-si-silo-cs-pdct-rp2web2app.private.sfr.com.app/vip-ref-si-silo-cs-pdct-rp2web2app.pri" in the /metric output so the snmp_exporter is seeing the same metric two times and drop the error.
What did you expect to see?
I have another F5 LTM in the cluster with the same configuration (but another version) and i can get two different metrics
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.
Hi all, i'm not sure i can open a issue for this behaviour but you will tell me :). I'm a simple network engineer so i'm sorry if my understanding of the snmp_exporter code is really limited.
Host operating system: output of
uname -a
Linux sys-d063323c.ctrl.cs 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
snmp_exporter version: output of
snmp_exporter -version
snmp_exporter, version 0.8.0 (branch: HEAD, revision: 17cefca)
build user: root@57f813d2791a
build date: 20171120-12:36:57
go version: go1.9.2
What device/snmpwalk OID are you using?
ltmVirtualServStatClientCurConns | 1.3.6.1.4.1.3375.2.2.10.2.3.1.12 from F5-BIGIP-LOCAL-MIB
If this is a new device, please link to the MIB(s).
No it's a standart F5 LTM
http://www.oidview.com/mibs/3375/F5-BIGIP-LOCAL-MIB.html
What did you do that produced an error?
When i check the /metrics output from snmp_exporter for that target i can see this error.
I should have two different metrics with two different "ltmVirtualServStatName" label value below:
but it seems that the "ltmVirtualServStatName" label_value is limited to "/Common/ref-si-silo-cs-pdct-rp2web2app.private.sfr.com.app/vip-ref-si-silo-cs-pdct-rp2web2app.pri" in the /metric output so the snmp_exporter is seeing the same metric two times and drop the error.
What did you expect to see?
I have another F5 LTM in the cluster with the same configuration (but another version) and i can get two different metrics
This time it seems that the snmp_exporter is putting a random string at the end of the label ltmVirtualServStatName to make it unique
Do you have any idea why this is happening when the MIB used is the same on both devices?
What did you see instead?
The text was updated successfully, but these errors were encountered: