From: Davide Guerri via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Davide Guerri <davide.guerri@gmail.com>
Subject: [pve-devel] [sensors] Patch proposal: add sensors for cpu, disk and fans
Date: Tue, 7 Oct 2025 22:51:20 +0200 [thread overview]
Message-ID: <mailman.739.1759870330.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6181 bytes --]
From: Davide Guerri <davide.guerri@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [sensors] Patch proposal: add sensors for cpu, disk and fans
Date: Tue, 7 Oct 2025 22:51:20 +0200
Message-ID: <FEF0F799-2293-4D63-8319-74C5640BC5D5@gmail.com>
Hi,
I added support for reading sensor data (where available) and exposing them via the API.
The API is exposed under the hardware section, so the API calls would look like:
- https://{{hostname}}:8006/api2/json/nodes/{{node}}/hardware/sensors/temperature/disk/values
- https://{{hostname}}:8006/api2/json/nodes/{{node}}/hardware/sensors/temperature/cpu/values
- https://{{hostname}}:8006/api2/json/nodes/{{node}}/hardware/sensors/fan/speeds
The library needs some more testing on platforms other than Intel. Should you be interested/willing to help, please feel free to reach out to me.
If everything makes sense, I can submit the patches in this ML:
Library https://github.com/dguerri/pve-common/commit/6a19bb03392ff94598e9efc76202fd1f60bd86b8
API: https://github.com/dguerri/pve-manager/commit/b152f153d98037c896430d6a131a28e496b30d4a
Thanks,
Davide.
[-- 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
reply other threads:[~2025-10-07 20:52 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=mailman.739.1759870330.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=davide.guerri@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.