My preference would be to use a generic configuration management tool like Puppet. There will inevitably be other services that need to be configured; you don't want to end up maintaining a separate mechanism for each one.
Ben On 28 Sep 2012 09:20, "Steve Cook" <[email protected]> wrote: > I'm looking at deploying collectd over a large number of servers. As such, > I want to avoid having any local configuration if possible, and manage/push > configuration from a central place. > Seems like I can write a custom plugin that itself can dynamically > start/stop other plugins using e.g. plugin_load(), but is there any way to > configure these plugins, other than having them read from the default .conf > file? > /steve > > _______________________________________________ > collectd mailing list > [email protected] > http://mailman.verplant.org/listinfo/collectd > >
_______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
