starred/panel

Fork 0

mirror of https://github.com/ConvoyPanel/panel.git synced 2026-04-25 04:35:52 +03:00

[GH-ISSUE #104] Nodes Systemressources overview and monitoring #70

New issue

Open

opened 2026-02-26 17:31:14 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 17:31:14 +03:00

Owner

Originally created by @julianfegert on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/104

Is there an existing feature request for this?

I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

Convoy should offer a host node overview on the admin dashboard start page where the current utilization of CPU, RAM and the installed hard disks is displayed and should be able to monitor the Proxmox nodes via ping test. if the ping test fails, the administrator is informed by e-mail

Describe the solution you'd like.

Monitoring via ping test and system ressources overview of the Proxmox nodes

Additional context to this request.

No response

Originally created by @julianfegert on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/ConvoyPanel/panel/issues/104 ### Is there an existing feature request for this? - [X] I have searched the existing issues before opening this feature request. ### Describe the feature you would like to see. Convoy should offer a host node overview on the admin dashboard start page where the current utilization of CPU, RAM and the installed hard disks is displayed and should be able to monitor the Proxmox nodes via ping test. if the ping test fails, the administrator is informed by e-mail ### Describe the solution you'd like. Monitoring via ping test and system ressources overview of the Proxmox nodes ### Additional context to this request. _No response_

kerem added the

enhancement

label

2026-02-26 17:31:14 +03:00

kerem commented

2026-02-26 17:31:15 +03:00

Author

Owner

@staalexa commented on GitHub (Jul 10, 2024):

You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that.

@staalexa commented on GitHub (Jul 10, 2024): You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that.

kerem commented

2026-02-26 17:31:15 +03:00

Author

Owner

@ericwang401 commented on GitHub (Jul 10, 2024):

You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that.

This is a planned feature. I'll have Convoy pull only the metrics of the node into the panel.

@ericwang401 commented on GitHub (Jul 10, 2024): > You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that. This is a planned feature. I'll have Convoy pull only the metrics of the node into the panel.

kerem commented

2026-02-26 17:31:15 +03:00

Author

Owner

@ericwang401 commented on GitHub (Aug 3, 2024):

You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that.

This is a planned feature. I'll have Convoy pull only the metrics of the node into the panel.

A nice addition, if not already thought of, would be the ability to fetch machine usage (not cpu/ram usage, but like how many houses the machine was on, created etc). This would allow implementation of usage based billing. Also a way to send webhooks after a server was created, (possibly divided by api created or created via the web interface), would make metered billing a dream.

Houses the machine was on? What does this mean?

@ericwang401 commented on GitHub (Aug 3, 2024): > > > You should monitor your proxmox nodes seperately, there is no reason why convoy should be doing that. > > > > > > This is a planned feature. I'll have Convoy pull only the metrics of the node into the panel. > > A nice addition, if not already thought of, would be the ability to fetch machine usage (not cpu/ram usage, but like how many houses the machine was on, created etc). This would allow implementation of usage based billing. Also a way to send webhooks after a server was created, (possibly divided by api created or created via the web interface), would make metered billing a dream. Houses the machine was on? What does this mean?

kerem commented

2026-02-26 17:31:15 +03:00

Author

Owner

@staalexa commented on GitHub (Aug 3, 2024):

I guess he means hours

@staalexa commented on GitHub (Aug 3, 2024): I guess he means hours

kerem commented

2026-02-26 17:31:15 +03:00

Author

Owner

@GunniBusch commented on GitHub (Aug 3, 2024):