The Network UPS Tools repository. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271 Please star NUT on GitHub, this helps with sponsorships!
Current monitoring integrations to represent NUT data points for SNMP scripted agents, MRTG collectors, etc. rely on running upsc in scripts, often once per data point. All this process forking comes at a cost.
We should consider exposing the readings (R/O at least, since they are public info for protocol-based tools without extra auth) in a shared-memory filesystem endpoint, similar to Linux use of /proc and /sys.
Challenges:
See if similar facilities exist for other OSes (BSD, illumos, ...)
Should this be an option for upsd itself, reflecting changes as soon as they come, or a separate persistent client similar to upsmon which could so expose remote devices, take care of R/W value setting while honouring NUT user accounts and SSL, etc.? Maybe both, in different namespaces...
Current monitoring integrations to represent NUT data points for SNMP scripted agents, MRTG collectors, etc. rely on running
upsc
in scripts, often once per data point. All this process forking comes at a cost.We should consider exposing the readings (R/O at least, since they are public info for protocol-based tools without extra auth) in a shared-memory filesystem endpoint, similar to Linux use of
/proc
and/sys
.Challenges:
upsd
itself, reflecting changes as soon as they come, or a separate persistent client similar toupsmon
which could so expose remote devices, take care of R/W value setting while honouring NUT user accounts and SSL, etc.? Maybe both, in different namespaces...