[collectd] collection4 nitpicking

[Trent W. Buck]

Some more feedback / bitching.

When I edit collection.conf, how do I tell c4 to reread it?

I suppose it happens automatically after enough requests when apache
kills the old c4 process and starts a new one, but I've simply been
doing "pkill collection.fcgi", which is... suboptimal.


When I fuck up the collection.conf, where are the parse errors
reported?  I can't see them in apache's logs, nor in syslog, and
apparently if I just run collection.fcgi by hand, it immediately exits
(IIRC FCGI passes data via the environment instead of stdin?).

For example, I accidentally typed "</DEF><DEF>" without a newline in
the middle, which apparently liboconfig(?) can't handle.

I think it would be most convenient if c4 reported errors via syslog.


The co-worker who maintains the old munin system says a "killer
feature" of munin is the ability to use a logarithmic scale for the
dependent variable (y axis).  This prevents an abnormal spike (e.g. in
network traffic) from "damping" the rest of the graph and making it
impossible to see smaller spikes.  The ability to zoom interactively
makes this less of an issue in c4, but I'd still like to have the
option in collection.conf.  (Maybe it's already there and I haven't
spotted it.)