Node uptime and node graph

[Oxim0v]

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.

In the admin panel I think it would be good to display the uptime of a node and to be able to schedule a task (such as rebooting the node in the same principle as for servers) And also displayed the average uptime of all the nodes combined and put a graph in the page of the node for the use of the processor and the ram.

Describe the solution you'd like.

For example for the use of the processor and the ram (global) a graph as for the servers (see the screen below)

and for the uptime of the node add it in the information section

Additional context to this request.

No response

[richiedevs]

Maybe this should be an optional features

[argonaut-network]

I believe Wings pulls that information from each Docker container's stats using the Docker socket. Problematically, the Docker socket does not provide a way to monitor system-wide resource usage, so the team would be required to engineer a brand new solution -- or at least use a different one than what's used now -- to accomplish this.

[matthewpi]

I believe Wings pulls that information from each Docker container's stats using the Docker socket. Problematically, the Docker socket does not provide a way to monitor system-wide resource usage, so the team would be required to engineer a brand new solution -- or at least use a different one than what's used now -- to accomplish this.

Wings can do things outside of the Docker socket which is shown by half the functionality that exists in it. Please don't state information about our software architecture without actually looking into it.

---

In terms of the issue, I can see showing an uptime for nodes individually (both the system itself and wings independently), but historical uptime or graphs, especially in aggregate will not be added.

[argonaut-network]

Fair enough. I assumed Wings used the Docker socket for monitoring resource usage of containers specifically, since the containerized version of Wings doesn't ask for access to /proc. You know what they say about assumptions, though.