Closed gabrieleiannetti closed 3 years ago
On my production system, the error counters are exported correctly, there might be a difference with the output of your ibqueryerrors
that does not work with the existing regex. Im using Centos 7 and infiniband-diags-2.1.0-1.el7.x86_64
to provide ibqueryerrors
.
I will check #21 in a few days and probably add a dump of our system to make it easier to run automated tests on a known input.
Interesting, we are also using the same version of ibqueryerrors
in version 2.1.0 on CentOS7:
yum list installed | grep infiniband-diags
infiniband-diags.x86_64 2.1.0-1.el7 @anaconda
ibqueryerrors --version
ibqueryerrors BUILD VERSION: 2.1.0 Build date: Aug 9 2019 14:06:43
As figured out in https://github.com/guilbaults/infiniband-exporter/issues/21 the ibqueryerrors
program needs to be executed with the proper parameter.
Then the exporter exports the SymbolErrorCounter errors.
This short file works for quick test: ibqueryerrors_short.txt
Hi,
it looks like, that the metric
symbolerrorcounter
is not exported for positive values.A short example:
ibqueryerrors
and verify forSymbolErrorCounter
errors:As you can see no positive values for the
symbolerrorcounter
metric is exported, nor the both GUIDs are listed too.For completeness I have added the redirected messages to stderr from the exporter:
exporter_stderr.txt
The GUIDs from above are not listed in the
exporter_stderr.txt
.I would have expected, that the metrics for the GUIDs were exported.
The metric for
PortXmitWait
is also be missing then.Can you please verify?
If I am not mistaken, then we should also check for other not exported metrics.
I would like to test the exporter with a local metrics file. But I do not get it working, for which I will create another issue.
Best
Gabriele