[ale] System Load Summary Script?

[Todor Fassl]

Right, but that is my point. If I run uptime and I see the load on a 
system is high, I still have to manually figure out if it is cpu bound, 
memory bound, or disk IO bound, or network IO bound. If you google for 
tutorials on diagnosing load problems, they all say something like 
"First run top and look at column 10. Then run iotop and look at column 
23. Then run netstat and ..." I don't think I should have to do that in 
2019.

Surely by now someone has written something to just take a good guess, 
right? I mean, I could write it myself in perl. Parse the output from 
top. Then parse the output from iotop. Etcetra. But surely someone  it, 
has already written that script, right?

On 6/26/19 12:35 PM, Lightner, Jeffrey via Ale wrote:
> +1 for htop
> 
> It all depends on what you mean by "load".  In UNIX days load averages in top and other tools were only for the CPU.   In Linux that isn't the case.  Coincidentally I'd just been in another thread mentioning that when someone shared this discussion of why that is different in Linux:
> 
> http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html
> 
> As far as monitoring goes you could use something like Nagios and the plugins it provides (or just the plugins and make your own routine to run the plugin and email you the output).
> 
> -----Original Message-----
> From: Ale <ale-bounces at ale.org> On Behalf Of Beddingfield, Allen via Ale
> Sent: Wednesday, June 26, 2019 1:26 PM
> To: ale at ale.org
> Subject: Re: [ale] System Load Summary Script?
> 
> When troubleshooting that type of issue, "htop" is always my first-glance sanity check.
> 
> Allen B.
> 
> On 6/26/19 12:21 PM, Todor Fassl via Ale wrote:
>> Anybody know of a debian/ubuntu package that provides a simple system
>> load summary? Maybe you are familiar with mysqltuner. I am looking for
>> something like that for system loads. Every time I have a problem with
>> a system under high load, I have go google for tutorials on diagnosing
>> load problems. Top, iostat, iotop, sar, etc. I'd like something that
>> did each of the things these tools do individually and take a best
>> guess at what is wrong.
>>
> 
> --
> Allen Beddingfield
> Systems Engineer
> Office of Information Technology
> The University of Alabama
> Office 205-348-2251
> allen at ua.edu
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> https://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> https://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
> 

-- 
Todd