ipmi_exporter
ipmi_exporter copied to clipboard
lovoo
IPMI Exporter for prometheus.io, written in Go.
Hi, @SqiSch Recently, If trigger an exception 1. The output of "ipmitool sensor" on the node as follows: [root@node-17 opt]# ipmitool sensor SDRR successfully erased Err in cmd get sensor...
There's a bug in convertRawOutput that seems to be turning any value >= 128 into a 0... I suspect that it's related to this conversion: https://github.com/lovoo/ipmi_exporter/blob/4c54ecc2bb53341cad990784aaba762e46b115fe/collector/collector.go#L104 Unfortunately, I can't get...
What confuse me is how use ipmi_exporter in the windows server perfectly ? I found ipmi_exporter_windows_amd64.exe in the release package, because ipmi_exporter depend on ipmitool, but I can not found...
In case of unresponsive BMC, ipmi_exporter keeps on spawning ipmitool processes (so eventually will kill the system): # ps -ef | grep export root 142647 1 0 13:47 ? 00:00:23...
I get this error from the ipmi_exporter on the machines that have a Supermicro X10DRT-HIBF board: could not parse ipmi output: encoding/hex: invalid byte: U+0050 'P'" source="collector.go:102" An example output...
I'd like command line parameters added to the exporter so I could specify a remote host and login credentials to the ipmitool. For example, if I were to specify `ipmi_exporter...
Looks like there are no packages available for CentOS 7. Used script to install: `curl -s https://packagecloud.io/install/repositories/LovooOS/prometheus-exporters/script.rpm.sh | bash` And run: ``` #yum install ipmi-exporter ... No package ipmi-exporter available....
I'm using the docker configuration as documented in the readme. When accessing the metrics endpoint the following is logged: ``` ERRO[0007] error while calling ipmitool: exit status 1 source=collector.go:44 ERRO[0007]...
We are able to get power cnsumption values from our systems via `ipmitool dcmi power reading` ``` Instantaneous power reading: 215 Watts Minimum during sampling period: 162 Watts Maximum during...
