dtrace discuss - Aug 2006 - picture of dtrace integration in osx (xray)

http://corenode.com/~ormandj/images/screenshots/picture3ap0.png (taken from
aeroxp)

Picture speaks for itself. ;) Some GUI stuff like this sure would help ease
new-users into using the advanced functionality of OSOL. A really slick ZFS
management tool, really slick Dtrace tool (for app devs and whathave), etc.. it
could make a big difference.

Food for thought,
David
 
 
This message posted from opensolaris.org

According to the Apple guys I talked with, none of the instruments in that
particular screen shot are using DTrace as the back end. The thing I''ve
been
impressed with about Xray is the ability to define your own DTrace instruments.

Adam

On Wed, Aug 09, 2006 at 11:18:44AM -0700, David J. Orman
wrote:
> http://corenode.com/~ormandj/images/screenshots/picture3ap0.png (taken from
aeroxp)
> 
> Picture speaks for itself. ;) Some GUI stuff like this sure would help ease
new-users into using the advanced functionality of OSOL. A really slick ZFS
management tool, really slick Dtrace tool (for app devs and whathave), etc.. it
could make a big difference.
> 
> Food for thought,
> David
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl

The Chime project lets you use your own DTrace scripts.  It has a wizard
to create new displays and edit existing displays.  It also has a
drilldown feature that lets you, for example, select from an aggregation
of system calls by execname and break down just the Xorg system calls by
probefunc.

Chime does not yet provide the context of a system observability GUI.  I
had originally thought of using kstats in an observability tool that can
launch Chime displays to answer questions raised by the kstats.  I think
that Chime displays can be dropped into other tools.  The table in the
bottom right pane of Xray very much resembles a Chime display.

Thanks David.  I''d like to try out Xray when I get a chance.

Tom

On Wed, Aug 09, 2006 at 11:22:43AM -0700, Adam Leventhal
wrote:
> According to the Apple guys I talked with, none of the instruments in that
> particular screen shot are using DTrace as the back end. The thing
I''ve been
> impressed with about Xray is the ability to define your own DTrace
instruments.
> 
> Adam
> 
> On Wed, Aug 09, 2006 at 11:18:44AM -0700, David J. Orman wrote:
> > http://corenode.com/~ormandj/images/screenshots/picture3ap0.png (taken
from aeroxp)
> > 
> > Picture speaks for itself. ;) Some GUI stuff like this sure would help
ease new-users into using the advanced functionality of OSOL. A really slick ZFS
management tool, really slick Dtrace tool (for app devs and whathave), etc.. it
could make a big difference.
> > 
> > Food for thought,
> > David
> >  
> >  
> > This message posted from opensolaris.org
> > _______________________________________________
> > dtrace-discuss mailing list
> > dtrace-discuss at opensolaris.org
> 
> -- 
> Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org

On Wed, Aug 09, 2006 at 03:14:45PM -0700, Tom Erickson
wrote:
> The Chime project lets you use your own DTrace scripts.  It has a wizard
> to create new displays and edit existing displays.  It also has a
> drilldown feature that lets you, for example, select from an aggregation
> of system calls by execname and break down just the Xorg system calls by
> probefunc.
> 
> Chime does not yet provide the context of a system observability GUI.  I
> had originally thought of using kstats in an observability tool that can
> launch Chime displays to answer questions raised by the kstats.  I think
> that Chime displays can be dropped into other tools.  The table in the
> bottom right pane of Xray very much resembles a Chime display.
It would be useful to have a GUI that helps construct and run D scripts.

For example:

 - listing probes available for, including for a particular target
   process; drag-n-drop of probe names would help

 - tracing function calls down from a particular function call
   invocation in a process or in the kernel, or system calls

 - listing a such a trace with indentation and so that the names of
   probes fired can be dragged-and-dropped into a script editor element

 - an action editor that knows to create visualization elements for
   aggregations used in a D script

 - a type viewer?

 - listings of includable D scripts, header files


Nico
--