Using DTrace to Analyze Your Webstack


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Using DTrace to Analyze Your Webstack
# 1  
Old 12-16-2009
Using DTrace to Analyze Your Webstack

A Jack Adams conversation with Sriram Natarajan, at OSCON 2009.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

Solaris x86 - Webstack 1.5 - Apache Stops reponding

Solaris 10x86 running multiple zones Webstack 1.5 loaded in the global and one zone is using the Apache webserver which it provides. Rest of zones working fine, no issues etc... The Apache web server however just stops responding. It is still running, but not processing requests. There... (4 Replies)
Discussion started by: dweeber
4 Replies

2. Shell Programming and Scripting

DTRACE help required...

if dtrace -n 'syscall::open*:entry { printf("%i %s %s %s",uid,execname,cwd,copyinstr(arg0)); }' will show me all files that are opened as follows... 3 522 open:entry 0 init / /etc/inittab 3 522 open:entry 0 init /... (5 Replies)
Discussion started by: smurf4568
5 Replies

3. Solaris

PID Provider dtrace script

I'm just starting to mess about with dtrace on Solaris. How do I configure a probe in a PID provider dtrace script to trigger when the process being traced exits? I've tried pid$1:::exit where $1 is the PID but I get 'exit' is an invalid probe name (0 Replies)
Discussion started by: JerryHone
0 Replies
Login or Register to Ask a Question
profile(7D)							      Devices							       profile(7D)

NAME
profile - DTrace profile interrupt provider DESCRIPTION
The profile driver is a DTrace dynamic tracing provider that adds time-based interrupt event sources that can be used as DTrace probes. Each profile event source is a time-based interrupt firing every fixed, specified time interval. You can use these probes to sample some aspect of system state every unit time and the samples can then be used to infer system behavior. If the sampling rate is high, or the sam- pling time is long, an accurate inference is possible. By using the DTrace facility to bind arbitrary actions to probes, you can use the profile provider to sample practically anything in the system. For example, you could sample the state of the current thread, the CPU state, or the current machine instruction each time a probe fires. The profile driver is not a public interface and you access the instrumentation offered by this provider through DTrace. Refer to the Solaris Dynamic Tracing Guide for a description of the public documented interfaces available for the DTrace facility and the probes offered by the profile provider. ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdtrp | +-----------------------------+-----------------------------+ |Interface Stability |Private | +-----------------------------+-----------------------------+ SEE ALSO
dtrace(1M), attributes(5), dtrace(7D) Solaris Dynamic Tracing Guide SunOS 5.11 4 Sep 2003 profile(7D)