Temperature

[Johannes S]

And there is already code in that direction, submitted for inclusion: https://bugzilla.proxmox.com/show_bug.cgi?id=208#c23
It's a halfway, but it would be already a good step. But it doesn't get enough attention.

Which code are you meaning? https://github.com/Meliox/PVE-mods doesn't address Andreas Steinels (aka @LnxBil ) argument that typical servers have a lot of temperature sensors which would clutter the UI and for monitoring it's best to setup a dedicated monitoring software anyhow. For inclusion the author of the mod would have to sign a contributor agreement. In corportate environments Prometheus, Zabbix or a nagios variant (Icinga2, checkmk etc ) are often used for monitoring, for the typical homelab something like Pulse (https://github.com/rcourtman/Pulse ) should fit your needs. Pulse has temperature monitoring btw: https://github.com/rcourtman/Pulse/blob/main/docs/TEMPERATURE_MONITORING.md

 

[templar]

Which code are you meaning?

Sorry for asking, but have you followed the link I gave? It leads direct to the code's author's comment with his explanation and links to the submitted patches. If he did sign the agreement or not - I don't know, you can ask him yourself.

 

[Johannes S]

Sorry for asking, but have you followed the link I gave? It leads direct to the code's author's comment with his explanation and links to the submitted patches. If he did sign the agreement or not - I don't know, you can ask him yourself.

Sorry, missed that comment, thanks for the hint. . i think adding this information to the API is a good thing since it makes it easier to implement this functionality in third-party-monitoring (e.G. pulse, ProxmoxVE-specifig plugins for Icinga2/Zabbix/Prometheus exporters), so in that regard these patches are a good enhancement and will hopefully included. I still think that it's these information doesn't belong in the main dashboard because this would clutter the UI for the reasons explained by Andreas Steinel and others.

 

[templar]

adding this information to the API is a good thing since it makes it easier to implement this functionality in third-party-monitoring

Exact my thoughts too. I personally use Zabbix and just wanted to omit installing of its agent. Zabbix already has template for reading from PVE API, and PVE API already has S.M.A.R.T. data. And if it would return also sensors data I would be totally happy.

I still think that it's these information doesn't belong in the main dashboard because this would clutter the UI

And I can agree with you here too, I can't deny it

 

[DerekG]

Exact my thoughts too. I personally use Zabbix and just wanted to omit installing of its agent. Zabbix already has template for reading from PVE API, and PVE API already has S.M.A.R.T. data. And if it would return also sensors data I would be totally happy.

As I understand it the sensors data is already available via Proxmox api, Pulse Monitor manages to pull the info for the CPU and NVMe at least.

 

[Johannes S]

As I understand it the sensors data is already available via Proxmox api, Pulse Monitor manages to pull the info for the CPU and NVMe at least.

Yes but not for temperature, the pulse feature for monitoring temperatures uses a specific agent together with lm-sensors see: https://github.com/rcourtman/Pulse/blob/main/internal/sensors/collector.go , https://github.com/rcourtman/Pulse/blob/main/docs/TEMPERATURE_MONITORING.md and https://github.com/rcourtman/Pulse/blob/main/ARCHITECTURE.md

 

[patch]

I still think that it's these information doesn't belong in the main dashboard because this would clutter the UI

Agree it belongs in a "Hardware" tab mirroring what is already there for VM's. On the dashboard just showing the highest current or range of all sensors would be optimal.

 

[Johannes S]

Agree it belongs in a "Hardware" tab mirroring what is already there for VM's

The hardware tabwould also be cluttered as explained by Andreas Steinel in the bug ticket:

Normally, servers have more than 20 temperature sensors (including the disks), so ONE display can never be sufficient. You should just look into external monitoring which is better suited to do what you want ... MONITORING, not just a display
https://bugzilla.proxmox.com/show_bug.cgi?id=208#c16

And since temperature monitoring is easily available by using a real monitoring software it's not even needed.

 

[patch]

From the opening post

Is there any way to show the temperature from the thermal sensor(s).

This thread is about showing temperature not ongoing monitoring. Please remain on topic.

CPU usage, Memory usage, Hard disk space can all be readily monitored by external software. If availability of monitoring really negated the merit of displaying current values, then you should raise a bug to remove from the summary page Current CPU usage, Current memory usage, Current hard disk space. Which is clearly a ridiculous suggestion. So in a thread about displaying current values, please stick to real issues with displaying current values.

The hardware tab would also be cluttered

Displaying 20 temperatures on one page maybe too cluttered for you.

For me if my hardware had 20 temperature sensors then I would want to be able to see what they all show. So displaying all of my 20 temperature sensors on one page would be an efficient method of assessing current temperature status.

cluttered as explained by Andreas Steinel in the bug ticket

Your reading of the words is different to mine.

In response to the opening but post

One feature i would like into Proxmox, along with the ones proposed in this thread, would be to have a sensors panel into the web interface, meaning besides the CPU and memory usage graphs, I would like to have temperature readings from the host's sensors. CPU and the likes.

Andreas Steinel responds

Normally, servers have more than 20 temperature sensors (including the disks), so ONE display can never be sufficient.

Which reads to me as the bug opening post was suggesting a panel of temperature readings.

Andreas Steinel was repeating multiple temperatures would need to be displayed, not the at most single value HE would like on the SUMMARY page.
Nowhere in the bug report is a hardware tab discussed, so I fail to see how Andreas Steinel comments say anything about a hardware tab being cluttered by 20 temperature readings.

 

[uzumo]

So, assuming we add lm-sensors and various sensor configurations, who do you think should provide support for them?

If you want items displaying lm-sensors values, you need lm-sensors itself.

Items that won't display if it's not installed serve no purpose.

Don't you think Proxmox should handle support for lm-sensors?

That's not something they should support.

Requested features should not burden them.

 

[Johannes S]

This thread is about showing temperature not ongoing monitoring. Please remain on topic.

Nonsense. Displaying and alerting on (if a temperature gets higher than a set treshhold ) Temperature is one part of monitoring as well as displaying and alerting on CPU load, RAM or storage usage. And the funny thing is if you don't want to get alerts Pulse ( or any other monitoring tool configured correctly) will also display temperatures without sending alerts.

To be blunt: This request is a typical homelabbers "I want everything in one interface although for my apps I'm fine with having different interfaces (for Paperless, Jellyfin, nextcloud, whatever)"-request. ProxmoxVE however is really not about homelabs but for running infrastructure in a way suitable for professional run IT environments. In these environments you always have a dedicated monitoring software since it will always have more features and be more flexible than any vendor-specific integrated function. Now if you happen to have a homelab you want to run like pros do or want to learn stuff then ProxmoxVEs is a great, flexible and incredible powerful tool. I use it myself exactly for this, my homelab is mostly for learning things.
But I don't think that new features should be added which would mainly benefit non-paying homeusers like myself. Instead development should focus on features which will convince more companys to migrate their virtualization environments to a payed Proxmox support subscription since this will guarantee the further development of Proxmox products. And thier continueing development funded by companys will also benefit us hobbyists

The nice thing on Pulse is, that it's a great solution which fits most of the boxes for a homelabs but (thanks to it's integrated export of metrics to Prometheus) can also be used to integrate in a corporate monitoring setup. I really don't get why any effort should be spent on integrating part of it's features in ProxmoxVE if the end result will still have less features so you end up in installing the monitoring software nontheless

 

[mikeyo]

FWIW, having a seperate host menu item called Sensors would be a massive plus. I have 2 x Proxmox host and both have IPMI. Being able to go into that menu and see stats for IPMI and SMART data for disks would be fantastic!