From: Sascha Westermann via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Sascha Westermann <sascha.westermann@hl-services.de>
Subject: [pve-devel] [PATCH pve-common/pve-manager/qemu-server 0/3] Fix #5708: Add CPU raw counters
Date: Tue, 17 Sep 2024 07:50:17 +0200 [thread overview]
Message-ID: <mailman.5.1726728980.332.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 11917 bytes --]
From: Sascha Westermann <sascha.westermann@hl-services.de>
To: pve-devel@lists.proxmox.com
Cc: Sascha Westermann <sascha.westermann@hl-services.de>
Subject: [PATCH pve-common/pve-manager/qemu-server 0/3] Fix #5708: Add CPU raw counters
Date: Tue, 17 Sep 2024 07:50:17 +0200
Message-ID: <20240917055020.10507-1-sascha.westermann@hl-services.de>
To monitor the CPU utilization of nodes and Qemu VMs at arbitrary
intervals (e.g. every 30 seconds) via the Proxmox API, there are no
suitable endpoints right now:
/api2/json/nodes/{node}/status (cpu): Instant value
/api2/json/nodes/{node}/rrddata?timeframe=hour (cpu): Average values
per minute
/api2/json/nodes/{node}/qemu (cpu): Instant value
/api2/json/nodes/{node}/qemu/{vmid}/rrddata?timeframe=hour (cpu):
Average values per minute
Instant values have the disadvantage that short-term peaks distort the
value. The average values from rrddata provide usable average values,
but you are restricted to a minute time window and the values can be
up to one minute old.
The following patches add raw counter values to a "cpustat" map in
the corresponding endpoints.
pve-common:
Sascha Westermann (1):
Add CPU raw counters
src/PVE/ProcFSTools.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
pve-manager:
Sascha Westermann (1):
Add CPU raw counters
PVE/API2/Nodes.pm | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
qemu-server:
Sascha Westermann (1):
Add CPU raw counters
PVE/QemuServer.pm | 55 +++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 53 insertions(+), 2 deletions(-)
--
2.46.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-09-19 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 5:50 Sascha Westermann via pve-devel [this message]
2024-09-24 12:24 ` Daniel Kral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.5.1726728980.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=sascha.westermann@hl-services.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox