[ovirt-devel] [monitoring][collectd] the collectd virt plugin is now on par with Vdsm needs

[Yaniv Dary]

We need good answers from them to why they do not support this use case.
Maybe a github issue on the use case would get more attention. They should
allow us to choose how to present and collect the data.
Can you open one?

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306 <+972%209-769-2306>
        8272306
Email: ydary at redhat.com
IRC : ydary


On Tue, Feb 28, 2017 at 1:07 PM, Francesco Romani <fromani at redhat.com>
wrote:

>
> On 02/27/2017 01:32 PM, Yaniv Dary wrote:
> > This is about accumulative values, I'm also asking about stats like
> > CPU usage of the VM\Host that is not reported in absolute value.
> > Can you bump the thread?
>
> Done, let's see.
>
>
> Speaking about options: during the reviews of my pull requests we also
> discussed the (semi?)recommended way to report more values without
> adding new collectd types, which is something the collectd upstream
> really tries to avoid.
>
> So we could report the current values *and* the absolutes, making
> everyone happy; but I'm afraid this will require a new plugin, like the
> one I had in the working (https://github.com/fromanirh/collectd-ovirt)
>
> TL;DR: in the worst case, we have one safe fallback option.
>
> --
> Francesco Romani
> Red Hat Engineering Virtualization R & D
> IRC: fromani
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170228/6d56f5c5/attachment.html>