[collectd] Bug#495936: "Redesign" of the Debian collectd package
XANi
xani666 at gmail.com
Mon Oct 5 23:35:41 CEST 2009
>on 2009-10-05 at 23:27:14
>Sebastian Harl <sh at tokkee.org> wrote:
> Hi Raimund,
>
> On Thu, Oct 01, 2009 at 09:57:47AM +0200, Raimund Sacherer wrote:
> > * About the enPlugin disPlugin, i do not think the user will have a
> > lot of benefit here.
> >
> > It's great if there are a bunch of plugins which do not really need
> > configuration, if a (very) few packages need them it's ok, but if
> > you *need* to configure every plugin it would be a little
> > configuration nightmare.
>
> That's what I fear as well. So, I guess, I'll just drop that idea ;-)
> It probably makes much more sense to work on some nifty configuration
> tool upstream but not even that might be of much benefit (especially
> when compared to the required efforts) …
Hmm maybe make 4 confing files:
* Global (Interval, basedir, plugindir TypesDB etc).
* Input plugins
* Output plugins (rrdtool, csv etc.)
* Filters
Then for example Admin could use same output plugin config for all
nodes and tweak others per-node.
Regards
Mariusz Gronczewski
More information about the collectd
mailing list