Frank,
On 3/18/15 2:25 PM, Frank Ch. Eigler wrote:
Hi -
A potential pcp user recently asked whether pcp can match the data
gathering capabilities of collectd [1], listing a smorgasbord of
their-equivalent-of-pmda's. The simple answer is "no", but maybe we
can get to "not yet" and maybe even "soon", while not reinventing the
wheel.
We don't have a need for this yet, but I could see a need for processing
collectd data in our workflow at some point in the future.
........
- write a pcp data sink plugin for collectd
This would leave collectd as the driver, but we could get an
incrementally written pcp log-archive as output.
I think this would be our use case, but I'm not sure exactly since we
haven't explored too deeply yet. Something along the lines of "leave a
functioning collectd implementation exactly as it is but also provide a
pcp archive of the data"
As an alternative, we may be able to make do with just a collectd2pcp
type utility to get pcp archives out of existing collectd files. I
think collectd just uses rrd on the back-end for storage, just as
ganglia does. Its on my todo list to add configurability to the metrics
that ganglia2pcp can handle. Hacking in collectd support in this way
might be good enough for our needs, but I haven't spent more than 10
minutes thinking about this.
Martins
|