From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dietmar@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 5299E61F9D
 for <pve-devel@lists.proxmox.com>; Fri, 23 Oct 2020 09:50:57 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 461F525C59
 for <pve-devel@lists.proxmox.com>; Fri, 23 Oct 2020 09:50:57 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [212.186.127.180])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS id 3355D25C49
 for <pve-devel@lists.proxmox.com>; Fri, 23 Oct 2020 09:50:56 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id EE60145EF1;
 Fri, 23 Oct 2020 09:50:55 +0200 (CEST)
Date: Fri, 23 Oct 2020 09:50:29 +0200 (CEST)
From: Dietmar Maurer <dietmar@proxmox.com>
To: Alexandre Derumier <aderumier@odiso.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Message-ID: <192891807.455.1603439430434@webmail.proxmox.com>
In-Reply-To: <CAMGxVzAM2f1sbUZKwkSJ+bhRf6Zt1xbfRZnVwWAk2owJvOwZxg@mail.gmail.com>
References: <20201006115850.1026534-1-aderumier@odiso.com>
 <589366911.632.1602568628596@webmail.proxmox.com>
 <CAMGxVzAM2f1sbUZKwkSJ+bhRf6Zt1xbfRZnVwWAk2owJvOwZxg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.4-Rev11
X-Originating-Client: open-xchange-appsuite
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.064 Adjusted score from AWL reputation of From: address
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH pve-manager] pvestatd: stream host pressure
 counters
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 07:50:57 -0000

> 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 add something like "hostcpu" counter, will real metric
> (reading the vm cgroup cpu.stat)

make sense.

> Also, for memory, when ballooning is enabled, we don't have anymore
> the real memory usage on the host.
> For example, a windows vm with 16g mem is filling memory with zeroes
> at boot, so from the host all the 16G memory is used, but in windows
> guest we only see something like 2G.
> 
> so, I would like to add something like "hostmemory" counter
> 
> 
> what do you think about this ?

Sounds reasonable. We just need to find a way to add new values
in a compatible way.