What are you actually trying to tell management?

I'd look at "stats show (volume|aggregate)" to get ops / second on your volume/aggregate, and if you actually want disk stats for a particular aggregate you could do a: "aggr status <agg name> -r"  to get a list of disks and then do a "stats show disk".

filer1(takeover)> stats show aggregate
aggregate:aggr0:total_transfers:0/s
aggregate:aggr0:user_reads:0/s
aggregate:aggr0:user_writes:0/s
aggregate:aggr0:cp_reads:0/s
aggregate:aggr0:user_read_blocks:0/s
aggregate:aggr0:user_write_blocks:0/s
aggregate:aggr0:cp_read_blocks:0/s

volume:testvol:avg_latency:0ms
volume:testvol:total_ops:0/s
volume:testvol:read_data:0b/s
volume:testvol:read_latency:0ms
volume:testvol:read_ops:0/s
volume:testvol:write_data:0b/s
volume:testvol:write_latency:0ms
volume:testvol:write_ops:0/s
volume:testvol:other_latency:0ms
volume:testvol:other_ops:0/s

I’d point to the “average_latency” output as pretty management friendly information.

Also, MRTG, cricket, and toasterview all expose various pieces of information in graph form, and I don’t know how it is where you work, but where I’ve worked, management likes graphs better than spreadsheets. No slight against management folks, the whole point is to look at the big picture, right?


 


On 8/7/08 11:40 AM, "George Kahler" <george@YorkU.CA> wrote:

>

--
Nicholas Bernstein
Technologist, Consultant, Instructor
http://nicholasbernstein.com