Feature request: Use /ThermalSubsystem endpoints instead of deprecated /Thermal for fan and temperature checks

[jiri-jurica]

Hello,

Thank you for creating this module — it's been a great help as we migrated our monitoring to the Redfish API. I'd like to raise a compatibility issue we've hit in production and propose a path forward.

Summary

On Dell PowerEdge R7615 servers running the latest iDRAC firmware 7.30.10.50, the /redfish/v1/Chassis/System.Embedded.1/Thermal endpoint intermittently returns Base.1.12.GeneralError. Around 10 out of our 23 R7615s running the newest fw version are affected, generating a significant volume of false unknown-state alerts in Icinga. During these failures, all other endpoints respond normally, and the iDRAC web UI continues to display correct readings — so the issue is specific to the /Thermal endpoint itself. We have a Dell support case open, but since /Thermal has been deprecated since Redfish standard version 1.7 (2020), migrating check_redfish to the newer endpoints seems like the right long-term fix regardless.

What we tried

We run three PowerEdge generations (R7525, R7615, R7715) and built a local patch on top of v2.1.2 that replaces /Thermal with the /ThermalSubsystem family of endpoints. It has been validated across all three platforms:

• Fans — collected from /ThermalSubsystem/Fans/ using SpeedPercent.SpeedRPM, with SecondarySpeedPercent handled for dual-rotor fans on newer generations
• Temperatures — collected by following DataSourceUri links from /ThermalSubsystem/ThermalMetrics to individual /Sensors/ resources, which expose full threshold and health data (Thresholds.UpperCritical, UpperCaution, LowerCritical, LowerCaution, and Upper/LowerFatal)

The patch is internal and not ready for upstream as-is, but happy to share it if it would be a useful reference.
0001-Thermal-subsystem-endpoints-switch.patch

Best regards
Jiří

[bb-Ricardo]

Hi,

thank you for letting me know. And also highly interested in a PR once it's ready. As far as I remember the Thermal subsystem has each item in a separate object which requires a HTTP query for each. I feel this results in a lot more requests to gather the infas before. But never the less, would be happy to implement it.

But if Dell is having issues in the current firmware then they either:

a) need to fix it or
b) officially depreciate the endpoint

If you don't mind, I would be highly interested in a Mockup of the new iDRAC version. Would be great if you could provide one.

Thank you.

[jiri-jurica]

Hello,

yes, the new approach does require significantly more HTTP requests — it's a broader Redfish trend we've run into elsewhere too (per-drive fetches being one example). It's just the direction the standard is heading.

Attached are responses from all three of our PowerEdge generations, covering both the legacy /Thermal and the new /ThermalSubsystem endpoints, including individual fan and sensor resources.
responses.zip