On Mon, Nov 17, 2008 at 4:47 AM, Arnaud Quette <[EMAIL PROTECTED]> wrote: > 2008/11/16 Charles Lepple <[EMAIL PROTECTED]>: >> On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <[EMAIL PROTECTED]> wrote: >> >>>>> The remainder, until the -pre stage, will be: >>>>> - the Powerman support (through the powerman driver) for more PDUs >>>>> - the possible RRD integration into upslog >>>> >>>> It would be nice to have native RRD support in upslog, but we may also >>>> want to point people to collectd - the NUT support in collectd is very >>>> easy to use, and collectd does a good job of monitoring other system >>>> statistics at the same time. >>> >>> I'm not very knowledgeable there! >>> is rrd's end collectd? if so, we can discard this patch and point collectd! >>> otherwise, I have a few things underhand for RRD (m4, pkginfo contributed, >>> ...) >> >> collectd is a standalone daemon to collect statistics, and its NUT >> plugin connects to upsd via libupsclient. >> >> The three main outputs of collectd are CSV, RRD and a network feed to >> another collectd instance. There is also a feed to Nagios, and some >> threshold detection and notification support. I have mainly been >> experimenting with the RRD support. >> >> http://collectd.org/images/architecture-schematic.png >> >> image from: http://collectd.org/features.shtml > > thanks for these info. > so, do you think that it's worth keeping the upslog patch? > or simply relying on collectd with RRD output is fine? > since I'm using neither, I just want to be sure that we don't shoot on > our users feets!
I don't know - I haven't tried the upslog patch at all. I guess I should look at the upslog stuff before commenting on it. -- - Charles Lepple _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
