10:11 a.m.
This is a multi-part message in MIME format.
--------------A2FDAF300209D96688B3E8CC
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
On 02/26/2017 03:13 PM, Yaniv Dary wrote:
> 2. collectd *intentionally* report metrics as rates, not as
> absolute
> values as Vdsm does. This may be one issue in presence of
> restarts/data
> loss in the link between collectd and the metrics store.
>
>
> How does this work?
> If we want to show memory usage over time for example, we need to
> have the usage, not the rate.
> How would this be reported?
I was imprecise, my fault.
Let me retry:
collectd intentionally report quite a lot of metrics we care about
as rates, not as absolute values.
Memory is actually ok fine.
a0/virt/disk_octets-hdc -> rate
a0/virt/disk_octets-vda
a0/virt/disk_ops-hdc -> rate
a0/virt/disk_ops-vda
a0/virt/disk_time-hdc -> rate
a0/virt/disk_time-vda
a0/virt/if_dropped-vnet0 -> rate
a0/virt/if_errors-vnet0 -> rate
a0/virt/if_octets-vnet0 -> rate
a0/virt/if_packets-vnet0 -> rate
a0/virt/memory-actual_balloon -> absolute
a0/virt/memory-rss -> absolute
a0/virt/memory-total -> absolute
a0/virt/ps_cputime -> rate
a0/virt/total_requests-flush-hdc -> rate
a0/virt/total_requests-flush-vda
a0/virt/total_time_in_ms-flush-hdc -> rate
a0/virt/total_time_in_ms-flush-vda
a0/virt/virt_cpu_total -> rate
a0/virt/virt_vcpu-0 -> rate
a0/virt/virt_vcpu-1
collectd "just" reports the changes since the last sampling. I'm
not sure which is the best way to handle that; I've sent a mail to
collectd list some time ago, no answer so far.
Can you CC on that thread?
I don't know how ES would work with rates at all.
I want to be able to show CPU usage over time and I need to know if
its 80% or 10%.
Thanks to the awkward gmail interface I can't reply to myself and CC
other people, but I can share the link:
https://mailman.verplant.org/pipermail/collectd/2017-January/006965.html
--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani
--------------A2FDAF300209D96688B3E8CC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 02/26/2017 03:13 PM, Yaniv Dary
wrote:<br>
</div>
<blockquote
cite="mid:CACKMAy_kfX=LCNe+7EFD2Cjw_Wit+aDS8FR+RPKEo=cMXU+H+A@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div class="h5">
<blockquote type="cite">
<div dir="auto">
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote
class="m_-684850395146887592quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex"> 2.
collectd *intentionally* report metrics
as rates, not as absolute<br>
values as Vdsm does. This may be one
issue in presence of restarts/data<br>
loss in the link between collectd and
the metrics store.<br>
</blockquote>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">How does this work? </div>
<div dir="auto">If we want to show memory usage
over time for example, we need to have the
usage, not the rate. </div>
<div dir="auto">How would this be reported?
<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
I was imprecise, my fault.<br>
<br>
Let me retry:<br>
collectd intentionally report quite a lot of metrics we
care about as rates, not as absolute values.<br>
Memory is actually ok fine.<br>
<br>
a0/virt/disk_octets-hdc -> rate<br>
a0/virt/disk_octets-vda<br>
a0/virt/disk_ops-hdc -> rate<br>
a0/virt/disk_ops-vda<br>
a0/virt/disk_time-hdc -> rate<br>
a0/virt/disk_time-vda<br>
a0/virt/if_dropped-vnet0 -> rate<br>
a0/virt/if_errors-vnet0 -> rate<br>
a0/virt/if_octets-vnet0 -> rate<br>
a0/virt/if_packets-vnet0 -> rate<br>
a0/virt/memory-actual_balloon -> absolute<br>
a0/virt/memory-rss -> absolute<br>
a0/virt/memory-total -> absolute<br>
a0/virt/ps_cputime -> rate<br>
a0/virt/total_requests-flush-<wbr>hdc -> rate<br>
a0/virt/total_requests-flush-<wbr>vda<br>
a0/virt/total_time_in_ms-<wbr>flush-hdc -> rate<br>
a0/virt/total_time_in_ms-<wbr>flush-vda<br>
a0/virt/virt_cpu_total -> rate<br>
a0/virt/virt_vcpu-0 -> rate<br>
a0/virt/virt_vcpu-1<br>
<br>
collectd "just" reports the changes since the last
sampling. I'm not sure which is the best way to handle
that; I've sent a mail to collectd list some time ago,
no answer so far.</div>
</blockquote>
<div><br>
</div>
<div>Can you CC on that thread?</div>
<div>I don't know how ES would work with rates at all. </div>
<div>I want to be able to show CPU usage over time and I
need to know if its 80% or 10%.</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
Thanks to the awkward gmail interface I can't reply to myself and CC
other people, but I can share the link:<br>
<br>
<a class="moz-txt-link-freetext"
href="https://mailman.verplant.org/pipermail/collectd/2017-January/0...
<br>
<pre class="moz-signature" cols="72">--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani</pre>
</body>
</html>
--------------A2FDAF300209D96688B3E8CC--