From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <aderumier@odiso.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 A4EF26228B for <pve-devel@lists.proxmox.com>; Sat, 24 Oct 2020 15:46:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 991262DCB1 for <pve-devel@lists.proxmox.com>; Sat, 24 Oct 2020 15:46:35 +0200 (CEST) Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 E3D402DCA6 for <pve-devel@lists.proxmox.com>; Sat, 24 Oct 2020 15:46:34 +0200 (CEST) Received: by mail-lj1-x243.google.com with SMTP id p15so4614168ljj.8 for <pve-devel@lists.proxmox.com>; Sat, 24 Oct 2020 06:46:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ZLWW3/83zJT3x6X3ifo74yaNN6BNH/HyK4gcw7uQBGY=; b=0F0fiWE9Xof3pAa0VKYG/2FQ5gOXfFF2tGvkm+WMw5EynE9tfyOGwigXqhyCCaMWJ/ ljrfWg7025lRAWAV4xrBtz4Bb5L2bJUbvxpg6Q/2Abn0SoLTsPFzXP/FUgq7m45SOVdZ TAzxze0zvrSXFq8b2htw0+Ec1zMGc9TrzA3iq0pTVAkOc1QPeA6GzVfynwiiz14BwXD3 GP/+aYQYlj1QXXhREk2a7SFdSWoDbvitH4kRFDRTANDfaQZuJlJj1zKTm7bMnA+9mKfD KtWlfUip2G9vdIxJNpOQDlVY2ZtOyhwsdFvyyVm9W2antJBT/cg/P3IcTl0o05fJnBQE GBLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ZLWW3/83zJT3x6X3ifo74yaNN6BNH/HyK4gcw7uQBGY=; b=gY8f0PBMWkQgxFZfdk6m3x5zIYdJomvTCYNPAluGWWvTN3o6LVfZxaN58ErsxKOWUk KkoW0K5wCPh/BZZfx3bsGeHs/2TEJptilSvJnreR7f6xIQ3BrgUpxG293hP3DD2DxqdV OrZ5o/ct4aoC3PuFDGH9X5IRzJ4VV60gYvbZcNU03n6R3ww1XkMyVEHDnc5MIfjvaWr9 lfRvJYJWTWBWpP/7PW3Cup60NLTIiXN09tXH3Jp/ihttCQuTE3iLz2IGlccIqdP1TTqV HAZJ6k/f0f3R93rpJjlIhBxEgkkP6TgK6Dvv3IVOogsZZVQGfsRIcL8+36zRofosH325 fblw== X-Gm-Message-State: AOAM531ZZ3RwrHO1/qUbBEpFqEdBtunLW2fWKWzouRxuNGuJulXUm4fw nvWYHvauTkpdqIu36CiKVrMrxr8WT34xwmhhHRtnTq3G6A4WCy1F X-Google-Smtp-Source: ABdhPJw2Wcnymbo7XZJeLJUTewbux4ImrFcHSJJ6jJSpBnb1k79KcApSGeUsohHnRiHa+oGrt9kUv2XemTwAW6DpmB0= X-Received: by 2002:a2e:8250:: with SMTP id j16mr2419813ljh.249.1603547187985; Sat, 24 Oct 2020 06:46:27 -0700 (PDT) MIME-Version: 1.0 References: <20201006115850.1026534-1-aderumier@odiso.com> <589366911.632.1602568628596@webmail.proxmox.com> <CAMGxVzAM2f1sbUZKwkSJ+bhRf6Zt1xbfRZnVwWAk2owJvOwZxg@mail.gmail.com> <192891807.455.1603439430434@webmail.proxmox.com> In-Reply-To: <192891807.455.1603439430434@webmail.proxmox.com> From: Alexandre Derumier <aderumier@odiso.com> Date: Sat, 24 Oct 2020 15:46:16 +0200 Message-ID: <CAMGxVzAqdVyYZ4-1vOvfmVtAcmZtPs1fVzo7XH2EXCxLDGb5zw@mail.gmail.com> To: Dietmar Maurer <dietmar@proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.050 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] 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: Sat, 24 Oct 2020 13:46:35 -0000 > 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 =C3=A0 09:50, Dietmar Maurer <dietmar@proxmox.com> a = =C3=A9crit : > > > 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. >