Commit Graph

15 Commits

Author SHA1 Message Date
Badreddin ac6dbe2e02 add --ignore-unrecognized-events flag
to avoid NaN in sensor reading when sensor Event has unrecognized-events
2019-10-01 11:29:41 +02:00
Conrad Hoffmann 11f380924f Escape hashes in password for config file
The hash is the comment character in the config file, even if it occurs
in the middle of the password. This can be worked around however by
escaping it.

This fixes #16.
2019-04-15 11:01:59 +02:00
Conrad Hoffmann ab356b2890 Remove accidentally merged debug output 2019-04-15 10:57:45 +02:00
Conrad Hoffmann a4a57fe40b Allow setting the session timeout
Now that we have a good config framework in place, this is low-hanging
fruit. Will apply to all collectors used, so total scrape time for
Prometheus could be (timeout * #-of-collectors) milliseconds for a given
module.

Related to #20.
2019-03-22 12:27:32 +01:00
Danny Kulchinsky 6aa7866dc1 rebased and adjusted per #17 2019-03-20 11:08:18 -04:00
Danny Kulchinsky 7108701389 one more log 2019-03-20 11:05:18 -04:00
Danny Kulchinsky a908a34812 typo :) 2019-03-20 11:05:18 -04:00
Danny Kulchinsky 7e5c643b90 adding rcmp.host to error log messages 2019-03-20 11:05:18 -04:00
Conrad Hoffmann 1a99329314 Refactor mapping of target to IPMI settings
Specifically, allow definition of a set of settings as module in the
configuration file, and the ability to use these settings by setting the
`module` URL parameter to the respective module name when scraping.

THIS COMMIT CHANGES THE CONFIG FORMAT IN A NON-BACKWARDS-COMPATIBLE WAY!

Based on this, the following "side effects" are noteworthy:

 - the exporter no longer requires a config file
 - the IPMI "privilege level" can be set in the config file
 - collectors can be enabled/disabled in the config file
 - anonymous IPMI access is now theoretically possible
 - there are now two example configurations (local & remote)

This fixes #10 by allowing to set the privilege level.
2019-03-16 16:11:32 +01:00
Conrad Hoffmann 1e16da97c1 Minor style fixes 2018-09-21 11:41:59 +02:00
Conrad Hoffmann 2c927eb68e Support collecting local IPMI metrics
This enables the standard `/metrics` endpoint. A scrape will trigger the
collection of IPMI metrics from the local machine (that the exporter is
running on).
2018-09-20 16:27:03 +02:00
Conrad Hoffmann ab14984e9a Fix return value in happy path
This fixes #7.
2018-08-03 16:24:49 +02:00
Conrad Hoffmann 9fb5f7296c Handle tool-specific failures more gracefully
Instead of failing hard and not returning any metrics at all if just one
(or two) of the three calls to IPMI tools fail, return whatever data was
properly received and add a `collector` label to the `ipmi_up` metric
indicating which tools failed.

This is only a small step towards the concept of "collectors" like they
exist e.g. in the node exporter, but it should help solve #1. Additional
functionality, like disabling certain collectors, can be built on top of
this.

Currently, an error in the `ipmi` collector is always logged as an error,
In the `dcmi` and `bmc` collectors, an error retrieving the data is only
logged as debug output, but an error processing retrieved data is logged
as an error. This should cover most use cases and will be improved upon
once more work is done to make the collectors selectable per scrape.
2018-07-31 09:24:54 +02:00
Conrad Hoffmann e11e76ed5c Use config file instead of command line arguments
Use a named pipe with 0600 permissions to pass the credentials to
FreeIPMI instead of using the command line, which certainly constitutes
bad security practice.

Template the `driver-type` while at it to potentially support local IPMI
at some point.
2018-07-26 16:14:26 +02:00
Conrad Hoffmann 670b92c799 Initial public release 2018-05-24 16:28:06 +02:00