[dtrace-discuss] Guidelines for Long Running DTrace Scripts

Marcelo Leal
Sat, 28 Mar 2009 19:14:41 -0000

Hello there...
 I need to implement something similar, and before start, i did think to look
here first. And that is the good in being part of such community. ;-)
 As there is only one comment for the Ben''s question, and a good one, i
think if we can work in a prototype together, and maybe create a general
framework for that. And publish the result FMA/Dtrace scripts, and the
processing scripts. I''m thinking in use orca to do the plotting, so,
even the necessary steps for that.
 Ben did not talk about specifically what is the dtrace script he wants to
implement in "daemon" mode. So, i will explain my case, and ask Ben if
he can do the same, so we can implement together.
 I want the following informations for each ZFS dataset (FS or VOL), regarding
NFS operations, for all NFS servers:

 1 - Total requests (reads and writes);
 2 - Latency for each operation;
 3 - Total Sync operations (Zil);
 4 - And the spa_sync informations too.

 Would be nice to see if for "some reason" we have more requests that
we can handle... but i don''t think that is possible (in the end we
would have all done with big latency times, i guess). Anyway...

 Obviously, we do not need to get for example *all* the NFS operations, but we
do need something representative. Maybe aggregate in memory, and persist on disk
from time to time. I don''t know if there is some kind of
"timer" in dtrace to activate and deactivate probes.

 ps.: But a real time monitor(like analytics) would be very nice! ;-)

 That''s it, i wait your comments, and thanks a lot for your time!

 Leal
[ http://www.eall.com.br ]
--
This message posted from opensolaris.org