Temperature

Yes, it also does not make coffee or predict the winning lottery numbers. It's still an awesome product ;)
such a coffee-colored answer from such a "Distinguished Member"
And then you wonder why people dislike Linux users so much...
PS: I'm also searching for a decent solution to this thread's topic - and seeing answers like this makes me just dismiss the entire community
 
The trouble is that you can't have a "fits everything" solution. If you read more of the previous debates on this subject you would also encounter the (imho) most cruical counter-againt against such an feature: On a modern server you can easily end up in a lot of sensors (20 or 40 and more!) which would clutter the PVE UI quite badly. For homeusers the story is different but they usually don't pay for subscriptions. In a corporate environment however sysadmins usually have a dedicated monitoring software (like Zabbix, Prometheus, Icinga,checkmk, prtg or whatever) for large environment or and don't even need this feature even if they happen to work in a small company who have just one server. Thus it doesn't make much sense to invest development resources in a feature which would mainly benefit homeusers.

PS: I'm also searching for a decent solution to this thread's topic - and seeing answers like this makes me just dismiss the entire community

Setup a monitoring software of your preference is actually the most decent solution since it will always have more features and give more informations than any internal dashboard. LnxBils answer was a bit flippant, but basically correct: ProxmoxVE is a great product but it's not a monitoring tool and can't replace good monitoring you need to have anyhow.

Regarding the entire community: I prefer this forum compared to vlogger clickbait, Reddits /r/proxmox or /r/homelab with their ill-advised recommendations for non-supported (running "helper scripts" from the internet as root, installing docker inside lxcs, adding nfs/cifs shares over wan as network storage to PBS etc pp) as "best practices". In this forum are more people actually envolved in running corporate IT infrastructure, it shows and it's a good thing in my book.

Regarding distinguished member: That badge just comes from posting a lot, it's not a statement on their quality ;)
 
Last edited:
such a coffee-colored answer from such a "Distinguished Member"
That is better than repugnant coffee from a newbie. How dare you insult another member - for absolutely no reason! LnxBil has definitely earned his more than "Distinguished Member" status numerous times. He has helped dozens (if not hundreds) of users over the years on this forum, with his selfless advice & expert knowledge. I fail to see what you get out of just trying to degrade people.

Apart from this; his answer was absolutely on point. I'm not going to discuss this with you - since I don't feel you would actually be interested.

And then you wonder why people dislike Linux users so much...
Very weird (& distasteful IMHO) comment. In which other OS exactly, can you suggest any feature/s & basically get them if you push hard enough or work out the coding for such, or just Google around a bit?

makes me just dismiss the entire community
Please do so & unsubscribe. If you can't have the basic decency to treat other members accordingly - you don't belong here.
 
The trouble is that you can't have a "fits everything" solution.
Nobody asked this
If you read more of the previous debates on this subject you would also encounter the (imho) most cruical counter-againt against such an feature: On a modern server you can easily end up in a lot of sensors (20 or 40 and more!) which would clutter the PVE UI quite badly.
actually no, there's already an existing table for SMART, why not adding the proper info there too?
For homeusers the story is different but they usually don't pay for subscriptions. In a corporate environment however sysadmins usually have a dedicated monitoring software (like Zabbix, Prometheus, Icinga,checkmk, prtg or whatever) for large environment or and don't even need this feature even if they happen to work in a small company who have just one server. Thus it doesn't make much sense to invest development resources in a feature which would mainly benefit homeusers.
I know these explanations by heart; I'm a home-user working for a Corp.

Setup a monitoring software of your preference is actually the most decent solution since it will always have more features and give more informations than any internal dashboard. LnxBils answer was a bit flippant, but basically correct: ProxmoxVE is a great product but it's not a monitoring tool and can't replace good monitoring you need to have anyhow.
Basically he didn't say anything other than: you're on your own and my answer will NOT help you;
I do THANK YOU for taking time to answer in a decent and thoughtful manner though.
Regarding the entire community: I prefer this forum compared to vlogger clickbait, Reddits /r/proxmox or /r/homelab with their ill-advised recommendations for non-supported (running "helper scripts" from the internet as root, installing docker inside lxcs, adding nfs/cifs shares over wan as network storage to PBS etc pp) as "best practices". In this forum are more people actually envolved in running corporate IT infrastructure, it shows and it's a good thing in my book.
I'm new here but I've studied some of the answers around for the past year and a half; I agree this is not a bad community I was just pointing out the hypocrisy of some so called advanced Linux users - they "worship" the idea of open source but many are soooo closed minded when have to share knowledge
Regarding distinguished member: That badge just comes from posting a lot, it's not a statement on their quality ;)
I know, it was just a tongue-in-cheek kind of remark.
 
That is better than repugnant coffee from a newbie. How dare you insult another member - for absolutely no reason!
Oh no! another distinguished one that feels the need to answer for absolutely no reason
LnxBil has definitely earned his more than "Distinguished Member" status numerous times.
Doesn't seem to be up to that status with his answer.
He has helped dozens (if not hundreds) of users over the years on this forum, with his selfless advice & expert knowledge. I fail to see what you get out of just trying to degrade people.
I'm not degrading anyone, I'm sorry that you're so affected by words that you fail to see what was asked from this topic.
Apart from this; his answer was absolutely on point.
Riiiight, because writing stuff like "does not make coffe or predict the winning lottery numbers" is such on point
I'm not going to discuss this with you - since I don't feel you would actually be interested.
Is this a "superior" user attitude that I'm sensing?
Very weird (& distasteful IMHO) comment. In which other OS exactly, can you suggest any feature/s & basically get them if you push hard enough or work out the coding for such, or just Google around a bit?
man, you talk like you're vibe-coding, please stop advocating for others; you talk about distasteful comments and then you just ask people asking for solutions to simply google...
Please do so & unsubscribe. If you can't have the basic decency to treat other members accordingly - you don't belong here.
oh no, if I don't what are you going to do? ban me?
 
Last edited:
actually no, there's already an existing table for SMART, why not adding the proper info there too?

And for the smart table we already have the problem that it's not working for every device due to the way the manufactures use it. For example on two of my used micron server-ssds the wearout indicator reads n/a due to it being some propietary entry. I would expect similiar issues with temperature reading.

I'm new here but I've studied some of the answers around for the past year and a half; I agree this is not a bad community I was just pointing out the hypocrisy of some so called advanced Linux users - they "worship" the idea of open source but many are soooo closed minded when have to share knowledge

I'm a big fan of sharing knowledge and empowerment, I'm not a fan of dumbing down things or appeasing the laziness of homeusers. Sadly enough often enough discussions ended heated here since even if given an explaination why typical homelabbing requests ( here is another one: https://forum.proxmox.com/threads/p...this-one-thing-the-memory-usage-graph.149473/ which inspired me to wrote a faq on that subject https://forum.proxmox.com/threads/f...ram-usage-of-the-vms-in-the-dashboard.165943/ ) are not that good idea people think them to be. I suspect that part of the more veteran community members are getting more flippant over the years. Because the sad truth is that even if you explain people why the "best practices" of Reddit homelabbing space are actually bad ideas they don't want to hear it. At some point you end up in not wanting to waste your time anymore with them. Now I'm not going so far in thinking that it's a good idea to be rude but I also lack the energy to do more than referencing earlier debates if some beaten-to-dead-horse reappears.
 
Last edited:
  • Like
Reactions: uzumo and nashu2k
And for the smart table we already have the problem that it's not working for every device due to the way the manufactures use it. For example on two of my used micron server-ssds the wearout indicator reads n/a due to it being some propietary entry. I would expect similiar issues with temperature reading.
I do agree not everything is SMART enough to be properly shown
I'm a big fan of sharing knowledge and empowerment, I'm not a fan of dumbing down things or appeasing the laziness of homeusers.
well, it's not about dumbing down here; it's finding the decent solution for a quite decent issue - and (for example) I know unRAID is paid but they managed to do it in a very user friendly way and I don't find it dumbed down
Sadly enough often enough discussions ended heated here since even if given an explaination why typical homelabbing requests ( here is another one: https://forum.proxmox.com/threads/p...this-one-thing-the-memory-usage-graph.149473/ which inspired me to wrote a faq on that subject https://forum.proxmox.com/threads/f...ram-usage-of-the-vms-in-the-dashboard.165943/ )
I know a thing or two about stuff on zee internetz and do agree some things need to be very thoroughly explained.
I suspect that part of the more veteran community members are getting more flippant over the years.
maybe not reply on all threads if just for snark remarks?
Because the sad truth is that even if you explain people why the "best practices" of Reddit homelabbing space are actually bad ideas they don't want to hear it.
Maybe not everything is bad; I tend to not be absolute when it comes to technology.
At some point you end up in not wanting to waste your time anymore with them. Now I'm not going so far in thinking that it's a good idea to be rude but I also lack the energy to do more than referencing earlier debates if some beaten-to-dead-horse reappears.
I agree; I was a forum moderator for about 10 years and it's energy and time consuming -> doesn't mean we have to reply like this;

PS: I apologize if my post was too acid but I also tend to be more dumbed down when it comes to (apparently) simple solutions; I've been using Linux since RedHat 4.0 in different variations and I'm amazed how far some things have come but also a bit frustrated to how others are not (case in point -> this thread)
 
such a coffee-colored answer from such a "Distinguished Member"
And then you wonder why people dislike Linux users so much...
Firstly- no one wonders this. And apart from that blanket statement I had no idea such a dislike existed. More to the point, it takes two to tango. the original comment wasnt pointed at you and required no reply.

PS: I'm also searching for a decent solution to this thread's topic - and seeing answers like this makes me just dismiss the entire community
the PVE interface isnt/was never meant to replace a environmental monitoring solution. PVE very nicely exports its own data so you can import it to your grafana/prometheus/whatever, which can (and is meant to) monitor things like your temperatures. Such a feature request has been made to the pve devs for inclusion to the pve ui, but they don't feel that it is a very important feature. If you DO feel so strongly about it, write the code and submit it for inclusion.
 
Firstly- no one wonders this. And apart from that blanket statement I had no idea such a dislike existed. More to the point, it takes two to tango. the original comment wasnt pointed at you and required no reply.
Oh well, that's your opinion - just try to go outside your bubble and you'll see... the battle of OSes is quite real
the PVE interface isnt/was never meant to replace a environmental monitoring solution. PVE very nicely exports its own data so you can import it to your grafana/prometheus/whatever, which can (and is meant to) monitor things like your temperatures. Such a feature request has been made to the pve devs for inclusion to the pve ui, but they don't feel that it is a very important feature. If you DO feel so strongly about it, write the code and submit it for inclusion.
this answer was probably what I was expecting more than the "coffee" response...

PS: found a good solution btw - help.rackzar.com/knowledgebase/article/how-to-monitor-cpu-temps-and-fan-speeds-in-proxmox-virtual-environment -> hope this helps others too
 
That appears to use a mod script from here. It in fact, mods the PVE GUI quite substantially.
It is, yes
Be aware that this has the potential of breaking the PVE, especially on future updates/upgrades.
That's why I'm using backups and what not
Running any script from the WWW on a hypervisor host system, is something that cannot be condoned.
While I agree with the approach of not condoning altering things manually, a UI change shouldn't "break" the hypervisor as a whole. I'll try to test some kind of fallback for the UI if the scripts are failing.
 
While I agree with the approach of not condoning altering things manually, a UI change shouldn't "break" the hypervisor as a whole. I'll try to test some kind of fallback for the UI if the scripts are failing.
The trouble is (like reported several time in this forum) that the Proxmox developers can't and won't test whether the modified GUI will still work when they change something in the UI. Thus some change to the UI via a script might (and will sooner or later) lead to a breakage after an update.
I can't speak for everyone but I prefer my infrastructure (even if it's only my homelab) not to break due to this. I also don't fancy troubleshooting after upgrades and I guess this is true for most non-techy homeusers. That's the reason why I don't like the "Just run this script bro"-"best-practices" in r/proxmox, it's actually bad advice for newbies
 
Last edited:
  • Like
Reactions: uzumo
Just to add some input into the conversation, I use the 'Pulse' monitoring app to keep an eye on Proxmox, it plugs into the Proxmox api to provide all the info you need, works with clusters, docker, hosts, PBS, the works, complete with user defined notifications. The tool is very light on resources, has a polished UI and is being constantly updated with new features.

It might be worth checking out: https://github.com/rcourtman/Pulse
 
Last edited:
  • Like
Reactions: Johannes S
PS: I'm also searching for a decent solution to this thread's topic - and seeing answers like this makes me just dismiss the entire community
I don't understand why you're attributing issues caused by modifications to the Proxmox product to Proxmox itself.

If you hadn't made changes, it would have worked fine, right?

I want you to realize that you're proving his response was correct.
 
  • Like
Reactions: Johannes S
I'm also searching for a decent solution to this thread's topic
Me to
On a modern server you can easily end up in a lot of sensors (20 or 40 and more!) which would clutter the PVE UI quite badly.
  • Fair point against putting detailed information the node summary page.
  • Indeed putting details about all sensor temperatures on a Node "Hardware" tab would make more appropriate and consistent with VM tab structure.

sysadmins usually have a dedicated monitoring software (like ... ) for large environment or and don't even need this feature
  • Continuous monitoring / reporting is a separate function to current status ready access.
  • I agree continuous monitoring is best done by separate / currently available software applications which can monitor temperature together with many other parameters.
  • But just because a parameter can be continuous monitored, does not imply most users would not benefit from ready display of a devices current status even to just to verify their monitoring solution. Consistent with this monitoring products also monitor memory use, processor load, disk IO load, disk space used etc yet it would be silly to suggest user receive no real benefit from Proxmox also displaying current values of these parameters via built in GUI.

for the smart table we already have the problem that it's not working for every device due to the way the manufactures use it. For example on two of my used micron server-ssds the wearout indicator reads n/a due to it being some propietary entry. I would expect similiar issues with temperature reading.
Fair point. It maybe difficult to support the common devices used my most main stream Proxmox subscribers.

a good solution btw - help.rackzar.com/knowledgebase/article/how-to-monitor-cpu-temps-and-fan-speeds-in-proxmox-virtual-environment -> hope this helps others too
Be aware that this has the potential of breaking the PVE, especially on future updates/upgrades.

Running any script from the WWW on a hypervisor host system, is something that cannot be condoned.
Proxmox developers can't and won't test whether the modified GUI will still work when they change something in the UI. Thus some change to the UI via a script might (and will sooner or later) lead to a breakage after an update.
I can't speak for everyone but I prefer my infrastructure (even if it's only my homelab) not to break due to this.
So we agree relying on a script from the www to display hardware temperature within Proxmox is not an good solution. Which leaves me still looking for what I believe would be a widely useful capability.

The real challenge I see is how to readily support extension of a solution to a usefully wide enough variety of devices. Perhaps there would need to be user entry of device monitoring settings.
 
Last edited:
People who use servers want something simple and robust.

Adding features compromises that.

*I prefer Hyper-V Server over Hyper-V on Windows Server (Server Core). But management became too cumbersome, so I switched to VMware and then Proxmox.

Because extra features impact the most essential functionality.

Expecting everything to be perfect by adding what various people want is unrealistic, right?

A flexible interface that enables this also guarantees that things created by others will work. But if someone reports it doesn't work after an addition, a fix becomes necessary. Working on that fix alongside critical functionality updates is extremely difficult.

It would be great if Proxmox added hardware monitoring as a program under its own management.

But even that would be difficult, requiring verification of chips from various manufacturers.

*Various people will likely seek support regarding their temperature being displayed at a high level or not being displayed at all, right?
 
Last edited:
  • Like
Reactions: Johannes S
So we agree relying on a script from the www to display hardware temperature within Proxmox is not an good solution. Which leaves me still looking for what I believe would be a widely useful capability.

The real challenge I see is how to readily support extension of a solution to a usefully wide enough variety of devices. Perhaps there would need to be user entry of device monitoring settings.
I suggest once again that people evaluate the Pulse monitoring app, which uses the Proxmox api to monitor not only the temps, but the CPU/RAM/Disk/Backups/hosts/docker apps etc. on a single pane of glass, right across your estate. They have made the app secure and really easy to install.

https://github.com/rcourtman/Pulse

Here is the sample from my very messy homelab:

1765012832503.png
 
Last edited: