v2.0.0

New / Breaking

• The ups.status variable was more complicated than anticipated. It is no longer coaxed to a single integer, but instead returned as network_ups_tools_ups_status metric with a flag label and constant value of 1 for each status flag set. See the README and issue #5 for more information.

v1.2.0

New

• Expanded the ups.status metric values to include several new values. See the README for a translation table of their meanings
• Support scraping multiple NUT servers from a single exporter. Thanks @sshaikh for the idea in #3!

Fixed

• Just a dumb typo or two in the README for scrape examples

v1.1.0

New

• Coax ups.status values to an integer so they can be used. Thanks @demokom-gmail-com for the idea in #2!

v1.0.2

New

• Improve handling of non-number types to reduce noisy logs

Fixed

• Fix bug in warning log when unknown types are found
• Fix Dockerfile - thanks, @c0defre4k!

v1.0.1

Fixed

• Fix use case where no variables are set (export all metrics), but no variables ended up being exported

v1.0.0

New

• The exporter is now listed in the Prometheus exporters and integrations page which has required a number of changes to conform with best practices (see below)!

Breaking Changes

• The exporter now exports UPS metrics at the /ups_metrics endpoint. It continues to export internal metrics about the exporter itself at /metrics
• You no longer specify the UPS to monitor on command line or ENV variable. Instead, just pass a query string to /ups_metrics like so: /ups_metrics?ups=foo
• It is now an error condition if multiple UPS devices are found by the exporter and the UPS to scrape is not passed as noted above
• Names of NUT variables are incorporated into the name of the metric rather than as labels. See README for examples.

v0.1.0

New

• New exporter just released! Head on over to README for more information