[prev in list] [next in list] [prev in thread] [next in thread] 

List:       collectd
Subject:    [collectd] [plugin:virt]
From:       Gaël_THEROND <gael.therond () bitswalk ! com>
Date:       2021-09-09 14:33:03
Message-ID: CABNe=UtDtv47r+xaE1HpSdFNBbZ+x+u=RZOr_JAojA_hErccHA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi everyone,

I'm currently building some monitoring pages for our Openstack platform.
To do so I leverage collectd with collectd-virt plugin and write_prometheus
plugin.

Everything is fine, I'm receiving all metrics and I'm able to graph them
from Grafana using prometheus as our datasource.

The only issue that I'm facing is to manipulate those metrics.
Our platform is CentOS 8 based and uses Collectd 5.11 provided by CentOS.

The first issue that I've got is that few metrics labels exposed to
prometheus aren't listed in here or are having a different name (We do not
relabeled them yet): https://collectd.org/wiki/index.php/Plugin:virt

The second issue that I face is to find out the appropriate unit type of
those metrics as, yes, I've the data type, but are those float and int
expressing ms? ns? ms/s? time since epoch? or something else?

Here are the problematic metrics:
collectd_virt_virt_cpu_total_total - prometheus type counter
collectd_virt_ps_cputime_user_total - prometheus type counter
collectd_virt_ps_cputime_syst_total - prometheus type counter

Subsidiary question:
Is there any way to get the vm internal memory usage?
Because within the wiki page there is memory-rss etc but our collectd with
collectd-virt plugin is just exposing allocated memory.

Additional information:
OS Version: CentOS 8.4.2105
Kernel: 4.18.0-305.7.1
Collectd: 5.11.0-2
Collectd-virt: 5.11.0-2
Collectd-write_prometheus: 5.11.0-2

Feel free to tell me if I missed something important.
Cheers!

[Attachment #5 (text/html)]

<div dir="ltr">Hi everyone,<div><br></div><div>I&#39;m currently building some \
monitoring pages for our Openstack platform.</div><div>To do so I leverage collectd \
with collectd-virt plugin and write_prometheus \
plugin.</div><div><br></div><div>Everything is fine, I&#39;m receiving all metrics \
and I&#39;m able to graph them from Grafana using prometheus as our \
datasource.<br><br></div><div>The only issue that I&#39;m facing is to manipulate \
those metrics.</div><div>Our platform is CentOS 8 based and uses Collectd 5.11 \
provided by CentOS.</div><div><br></div><div>The first issue that I&#39;ve got is \
that few metrics labels exposed to prometheus aren&#39;t listed in here or are having \
a different name (We do not relabeled them yet):  <a \
href="https://collectd.org/wiki/index.php/Plugin:virt">https://collectd.org/wiki/index.php/Plugin:virt</a></div><div><br></div><div>The \
second issue that I face is to find out the appropriate unit type of those metrics \
as, yes, I&#39;ve the data type, but are those float and int expressing ms? ns? ms/s? \
time since epoch? or something else?</div><div><br></div><div>Here are the \
problematic metrics:</div><div>collectd_virt_virt_cpu_total_total - prometheus type \
counter</div><div>collectd_virt_ps_cputime_user_total - prometheus type \
counter</div><div>collectd_virt_ps_cputime_syst_total - prometheus type \
counter</div><div><br></div><div>Subsidiary question:<br>Is there any way to get the \
vm internal memory usage?</div><div>Because within the wiki page there is memory-rss \
etc but our collectd with collectd-virt plugin is just exposing allocated \
memory.</div><div><br></div><div>Additional information:</div><div>OS Version: CentOS \
8.4.2105</div><div>Kernel: 4.18.0-305.7.1<br></div><div>Collectd: \
5.11.0-2</div><div>Collectd-virt: 5.11.0-2</div><div>Collectd-write_prometheus: \
5.11.0-2</div><div><br></div><div>Feel free to tell me if I missed something \
important.<br>Cheers!</div></div>


[Attachment #6 (text/plain)]

_______________________________________________
collectd mailing list
collectd@verplant.org
https://mailman.verplant.org/listinfo/collectd

[prev in list] [next in list] [prev in thread] [next in thread]