>>that'd drop all old statistics, and be a bit of a nuisance to upgrade inside
>>a cluster (old nodes get stuff they do not comprehend).
oh ok, I thinked that rrd was able to add new value. (don't have used
rrd since a long time since I'm using influxdb or other metrics
databases)
I'll look to
On 24.10.20 15:46, Alexandre Derumier wrote:
>> Sounds reasonable. We just need to find a way to add new values
>> in a compatible way.
>
> Last time in 2013, we had added a new rrd "pve2.3-vm/"
> https://lists.proxmox.com/pipermail/pve-devel/2013-January/005612.html
that'd drop all old
> Sounds reasonable. We just need to find a way to add new values
> in a compatible way.
Last time in 2013, we had added a new rrd "pve2.3-vm/"
https://lists.proxmox.com/pipermail/pve-devel/2013-January/005612.html
Le ven. 23 oct. 2020 à 09:50, Dietmar Maurer a écrit :
>
> > I would like also
> I would like also to add some improvement for vm memory/cpu stats.
>
> for cpu, currently, we only monitor the qemu process cpu usage, but
> with virtio-net + vhost-net,
> we are missing vhost-* process cpu usage. (For vms will a lot of
> traffic, this is really signifiant).
>
> I would like
Hi Dietmar,
I would like also to add some improvement for vm memory/cpu stats.
for cpu, currently, we only monitor the qemu process cpu usage, but
with virtio-net + vhost-net,
we are missing vhost-* process cpu usage. (For vms will a lot of
traffic, this is really signifiant).
I would like to
I wonder if we want to store that information with RRD instead?
> On 10/06/2020 1:58 PM Alexandre Derumier wrote:
>
>
> Signed-off-by: Alexandre Derumier
> ---
> PVE/Service/pvestatd.pm | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/PVE/Service/pvestatd.pm
Signed-off-by: Alexandre Derumier
---
PVE/Service/pvestatd.pm | 4
1 file changed, 4 insertions(+)
diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
index 5e533ca3..238c36ae 100755
--- a/PVE/Service/pvestatd.pm
+++ b/PVE/Service/pvestatd.pm
@@ -161,12 +161,16 @@ sub
