[Nut-upsuser] How to handle flags as status?

[Shakil Shaikh]

Because (in this case at least) monitoring doesn't imply key events occurring.

To flesh out the question, the intention here is to send results to something like Prometheus.

But if the answer is "do what upsmon does" then that's fair enough too!
________________________________
From: Nut-upsuser <nut-upsuser-bounces+sshaikh=hotmail.com at alioth-lists.debian.net> on behalf of Roger Price <roger at rogerprice.org>
Sent: Tuesday, December 29, 2020 3:45:51 PM
To: Shakil Shaikh via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
Subject: Re: [Nut-upsuser] How to handle flags as status?

On Tue, 29 Dec 2020, Shakil Shaikh via Nut-upsuser wrote:

> I'm looking into the best way to handle the ups status that gets returned by NUT. I've had a brief look at the source and it appears that this status is
> actually a composite of flags, some of which cannot co-exist.
>
> In particular I have a UPS that returns both OL and OL TRIM, which seem like reasonable statuses, but encode multiple states. A monitoring client has to
> know that OL TRIM implies online.
>
> I assume that not all combinations of flags exist, but I also understand that the combinations that do are defined by the drivers. To that end it becomes
> difficult to enumerate them.
>
> Are clients therefore supposed to list all possibilities, or split on space to get the flags back?
>
> Thoughts appreciated

Why not let a program like upsmon do this for you?  Then all you have to do is
say in configuration file upsmon.conf what is to be done for the key events.

Roger

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201229/187d5d01/attachment.html>