On 02/21/2017 02:44 PM, Yaniv Kaul wrote:
Hello
everyone,
in the last weeks I've been submitting PRs to collectd
upstream, to
bring the virt plugin up to date with Vdsm and oVirt needs.
Previously, the collectd virt plugin reported only a subset
of metrics
oVirt uses.
In current collectd master, the collectd virt plugin
provides all the
data Vdsm (thus Engine) needs. This means that it is now
possible for Vdsm or Engine to query collectd, not
Vdsm/libvirt, and
have the same data.
Do we wish to ship the unixsock collectd plugin? I'm not
sure we do these days (4.1).
We can do that later, of course, when we ship this.
Y.
AFAIR the collectd unixsock plugin it's built and shipped by default
by the collectd (even RPMs). It is the way the command line
`collectdctl` too uses to talk with the daemon.
I can confirm this is exactly what I see, on F25 at least. Just to add that it is disabled by default in collectd.conf
Our client module is still work in progress.
I'd be happy to just use a third party client module, the
(semi-)official one is not shipped by default last time I checked;
perhaps just file one RFE about that?
--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel