Complete service management #36
Comments
|
Andreas: One nice thing to have as part of service management would be to have something better than the top command to monitor individual services. What is the CPU usage of the service? What is the network usage? This would allow to notice that network usage is too high on the dashboard, click and dive into network monitoring from there, see that it's Process X that is eating all the bandwidth, get to the individual service page from there and kill or restart the service. |
|
Andreas: Is it possible to somehow get the numbers of active users of a service? Like 412 people are using, say, NFS. |
marusak
referenced
this issue
in marusak/cockpit
Jan 29, 2020
marusak
referenced
this issue
in marusak/cockpit
Jan 4, 2021
Release tarballs already have dist/. We can't rebuild the webpack in an RPM as that requires npm and network access for `npm install`. But we also don't want to ship the entire `node_modules/` as that is huge and would require lots of careful license review. So ship a stub node_modules/ that satisfies the Makefile dependency. Make sure that this is not newer than package.json or anything in dist/, so that none of the Makefile's rebuild rules trigger. Closes #36
ashley-cui
pushed a commit
to ashley-cui/cockpit
that referenced
this issue
Sep 13, 2024
…ress Address inputted by user is both used to figure out network subnet but also to assign address to virtual network's bridge. Network identifier nor brodcast should not be used as address for the bridge. For example, with network 192.168.2.0/24, addresses 192.168.2.0 and 192.168.2.255 cannot be used as address of bridge. Fixes cockpit-project#36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need to review and complete it.
The text was updated successfully, but these errors were encountered: