network_ups_tools_ups_status metric is missing when using NUT_EXPORTER_VARIABLES

[varac]

I am using this docker-compose.yaml file:

services:
  nut-exporter:
    # https://github.com/DRuggeri/nut_exporter/pkgs/container/nut_exporter
    image: ghcr.io/druggeri/nut_exporter:3.1.1
    hostname: nut-exporter
    container_name: nut-exporter
    restart: unless-stopped
    ports:
      - 10.27.65.51:9199:9199/TCP
    environment:
      - NUT_EXPORTER_SERVER=10.27.65.51
      - NUT_EXPORTER_USERNAME=monitor
      - NUT_EXPORTER_PASSWORD=...

Everything work fine, the metrics network_ups_tools_ups_status is returned for different lables.

But I'd like to get the content of more variables, so I set:

NUT_EXPORTER_VARIABLES="ups.realpower,ups.load,output.voltage,outlet.power,battery.runtime,battery.charge,battery.charge.low,battery.runtime.low"

With this, the metric network_ups_tools_ups_status is missing completely.
How can I get more variables and have still the network_ups_tools_ups_status metric ?

[maybesheforgot]

I think I figured it out: the variables need to be in alphabetical order. Tested on my container with this as the env variable: NUT_EXPORTER_VARIABLES=battery.charge,battery.charge.low,battery.runtime,battery.runtime.low,battery.voltage,battery.voltage.nominal,input.voltage,input.voltage.nominal,outlet.power,output.power,output.voltage,ups.load,ups.realpower.nominal,ups.status and I'm able to get everything.

[DRuggeri]

Hey there, @maybesheforgot - thanks for sharing this. At first blush, alphabetical order or not sounds like it should be irrelevant. I'll take a look to see if anything stands out. I'm curious how you landed on this solution? What other permutations did you try that ultimately led here?

[DRuggeri]

Circling back - I'm able to see the expected status metrics if I use NUT_EXPORTER_VARIABLES="ups.realpower,ups.load,output.voltage,outlet.power,battery.runtime,battery.charge,ups.status,battery.charge.low,battery.runtime.low". At least as far as the original report from @varac, I believe the reason that you didn't see status is because ups.status was just not in the list of requested variables. @maybesheforgot, similarly, I can get status information if I put the ups.status anywhere in the list - so maybe the alphabetical ordering was just coincidence?

Either way, I just pushed a new commit that will issue a warning on startup if ups.status is not in the list of requested metrics since that's one that I anticipate just about everyone would expect to see.

[maybesheforgot]

Ah, must’ve been coincidental then @DRuggeri. I was looking at the values from another NUT exporter utility I had running on my machine and all the values were listed alphabetically. And since that was what stood out compared to the way they were randomly listed by @varac, I figured that might be why. I want to say I originally only tested a few variables alphabetically at first, but it’s possible ups.status was among those in the test.

Thanks for following up and further clarifying this!

[varac]

Sorry for the late feedback. I can now export all important metrics thanks to @maybesheforgot !