From: Wolf Noble <wolf@wolfspyre.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] qemu metrics tuning
Date: Mon, 27 Dec 2021 15:20:41 -0600 [thread overview]
Message-ID: <E85B9813-FC70-4505-BEE9-23E4265A2566@wolfspyre.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
Is there a good way to tune the metrics that are emitted per VMs?
it seems worth asking if there's a way to configure the metrics engine to NOT emit metrics for some devices attached to VMs.... say ... the cdrom image of the OS installer, or a cloudinit and efi blockdevs... or an interface that's around only for certain operations, or ...
(not trying to argue merits of various implementations, rather illustrating that there are some resources associated with a VM that an administrator might wish to opt-out of having metrics collected/emitted for.)
arguably taking it a step further, one might wish to not emit metrics for entire VMs....
The metrics facet of proxmox is a little light in the documentation; I went looking for what was configurable and didn't find much.... Am I just really bad at looking in the right places?
TIA!
❤️🐺
happy happy merry merry yadda yadda yadda TLDR: Be nice to each other and celebrate the fact that we're all still alive n stuff `k?
Wolf Noble
Hoof & Paw
wolf@wolfspyre.com
[= The contents of this message have been written, read, processed, erased, sorted, sniffed, compressed, rewritten, misspelled, overcompensated, lost, found, and most importantly delivered entirely with recycled electrons =]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-12-27 21:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E85B9813-FC70-4505-BEE9-23E4265A2566@wolfspyre.com \
--to=wolf@wolfspyre.com \
--cc=pve-user@lists.proxmox.com \
/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