2005/12/15, Alexander V. Inyukhin <[EMAIL PROTECTED]>:
Hi Alexander,
interesting point: I'm thinking of some logging improvements, such as:
- making upslog a real daemon, able to log data from several UPSs,
- making log asynchronous and smart (ie log only things that have changed),
- switching by default to a NUT specific logfile (ie upsd.log), instead of the syslog default,
- adding the ability to log to other system, such as RRD...
So, I'm definitly interested in your work.Package: nut
Version: 2.0.2-2
Severity: wishlist
Hello.
Hi Alexander,
I think it is a good idea to log ups variables to rrd
database instead of log file. So, I create standalone
rrd logger dervied from upslog nut client.
Of course, this could be easily implemented using
upsc or upslog clients and a cron script
but stanalone application is better for some reasons.
Does anybody else need this functionality?
Should such a client be included in the nut
(with additional librrd dependency) or nut-rrd
package or distributed separately?
interesting point: I'm thinking of some logging improvements, such as:
- making upslog a real daemon, able to log data from several UPSs,
- making log asynchronous and smart (ie log only things that have changed),
- switching by default to a NUT specific logfile (ie upsd.log), instead of the syslog default,
- adding the ability to log to other system, such as RRD...
The final aim of all of that is to be able to use these data for plotting and other graphic / textual display... I've planned to get back on this when working on some MGE PSP [1] evolution such as the History feature in our case.
Arnaud
--
[1] http://www.mgeups.com/products/pdt230/software/sp97/solpaclinux.htm
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/
