Hello,
When working with a customer to determine what is the problem when they are hitting their NPROC or EP limits, it is often difficult to explain to the customer. It would be much easier if the customer could view, in realtime, a list of current processes from within their cpanel.
For example, the output from "ps aux | grep username" the refreshes every x seconds would be great! This way, the customer can view their processes, and see live results as they try to debug the problem.
And also, while youre adding real-time stats, it would be great if the customer could see "lvetop" output for their user from within their cpanel. This way, they can monitor things in realtime when debugging...
I believe adding these "realtime" usage tools would greatly improve CloudLinux, because it would help make it more useful for the end-user customer to diagnose and understand what is limiting their website/account. It will help server owners, because then we can spend less time working with the customer to provide this information (which is not always useful since it is "after the fact"), too.
Thanks!
When working with a customer to determine what is the problem when they are hitting their NPROC or EP limits, it is often difficult to explain to the customer. It would be much easier if the customer could view, in realtime, a list of current processes from within their cpanel.
For example, the output from "ps aux | grep username" the refreshes every x seconds would be great! This way, the customer can view their processes, and see live results as they try to debug the problem.
And also, while youre adding real-time stats, it would be great if the customer could see "lvetop" output for their user from within their cpanel. This way, they can monitor things in realtime when debugging...
I believe adding these "realtime" usage tools would greatly improve CloudLinux, because it would help make it more useful for the end-user customer to diagnose and understand what is limiting their website/account. It will help server owners, because then we can spend less time working with the customer to provide this information (which is not always useful since it is "after the fact"), too.
Thanks!
Comment