search

EndPointCorp / end-point-blog

End Point Dev blog
https://www.endpointdev.com/blog/
17 stars 65 forks source link

Comments for dstat: better system resource monitoring #239

Open phinjensen opened 6 years ago

phinjensen commented 6 years ago

Comments for https://www.endpointdev.com/blog/2009/12/dstat/ By Jon Jensen

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
phinjensen commented 6 years ago 
original author: Greg Smith
date: 2009-12-25T12:24:36-05:00

The best thing about dstat is that you can configure it to include a timestamp in the output, so that if you capture data from it you can later line it up against other system events. It's great for questions like "was this I/O spike during some event?" I'll use this:

dstat -tcdm

And then save the output into a CSV file for that sort of work.

Being able to break out individual drives is great for database work too, I'll usually monitor the system drive, the database drive, and the WAL drive separately on larger PostgreSQL systems where those are split.

phinjensen commented 6 years ago 
original author: Jon Jensen
date: 2009-12-25T18:04:24-05:00

Thanks for pointing that out, Greg. I hadn't noticed it before, but as you say, the -t option is great for logging data over time.