all lists on lists.proxmox.com
 help / color / mirror / Atom feed
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] [PATCH container 0/1] API endpoint to provide hardware sensor reading for Proxmox VE nodes.
Date: Tue, 14 Oct 2025 21:36:08 +0200	[thread overview]
Message-ID: <mailman.911.1760476929.390.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 6996 bytes --]

From: Davide Guerri <davide.guerri@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container 0/1] API endpoint to provide hardware sensor reading for Proxmox VE nodes.
Date: Tue, 14 Oct 2025 21:36:08 +0200
Message-ID: <20251014193609.34452-1-davide.guerri@gmail.com>

The endpoint exposes via the REST API to read real-time hardware sensor
data from the system.

Main functionality:
- Temperature monitoring: Returns CPU, disk, and other temperature
  sensor readings in Celsius, including optional thresholds (max,
  critical) and core/package mappings for CPUs;
- Fan speed monitoring: Returns fan speeds in RPM, along with optional
  min/max values, target speeds, and alarm status.

This endpoint uses the PVE::SensorInfo module (submitted separately) to
gather sensor data from the underlying system.

It provides a hierarchical REST API at /nodes/{node}/hardware/sensors/

/sensors       -> GET index (returns: temperature, fan)
  /temperature -> GET index (returns: cpu, disk, other)
    /cpu       -> GET CPU temperature data
    /disk      -> GET disk temperature data
    /other     -> GET other temperature data
  /fan         -> GET fan speed data

Davide Guerri (1):
  api: add hardware sensors endpoint and API support

 PVE/API2/Hardware.pm         |   8 +-
 PVE/API2/Hardware/Makefile   |   1 +
 PVE/API2/Hardware/Sensors.pm | 420 +++++++++++++++++++++++++++++++++++
 3 files changed, 428 insertions(+), 1 deletion(-)
 create mode 100644 PVE/API2/Hardware/Sensors.pm

-- 
2.50.1 (Apple Git-155)



[-- 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-14 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=mailman.911.1760476929.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal