You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see stats on Proxmox VMs and LXCs similar to how it is done for Docker containers to see what individual VM or LXC resources are from the total CPU and RAM use. I would also like to see a list of them and have the option to get a notification if the VM or LXC goes down even though the host may still be up.
I have been using Beszel for a few months since DBTech did a video on it and I have really liked it! I decided to deploy it on about 40+ NUCs running Proxmox that I deployed for my company. It would be great to get the extra stat info requested to help me monitor and troubleshoot them remotely (better than I am now).
The text was updated successfully, but these errors were encountered:
Good idea. I think Proxmox has an API to get resource usage, right?
I don't actually run Proxmox at the moment so it will probably be a bit before I can look into it.
Someone made an HACS Home Assistant integration utilizing their API. You might be able to see how they did it by checking out their repo. https://github.com/dougiteixeira/proxmoxve
If you ever dive into it, ping me and I will give it a try for you and see if I can help you along with testing.
I would like to see stats on Proxmox VMs and LXCs similar to how it is done for Docker containers to see what individual VM or LXC resources are from the total CPU and RAM use. I would also like to see a list of them and have the option to get a notification if the VM or LXC goes down even though the host may still be up.
I have been using Beszel for a few months since DBTech did a video on it and I have really liked it! I decided to deploy it on about 40+ NUCs running Proxmox that I deployed for my company. It would be great to get the extra stat info requested to help me monitor and troubleshoot them remotely (better than I am now).
The text was updated successfully, but these errors were encountered: