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
filebyproc.d(1m)						   USER COMMANDS						  filebyproc.d(1m)

NAME
filebyproc.d - snoop opens by process name. Uses DTrace. SYNOPSIS
filebyproc.d DESCRIPTION
filebyproc.d is a DTrace OneLiner to print file pathnames as they are opened, including the name of the process calling the open. A line will be printed regardless of whether the open is actually successful or not. This is useful to learn which files applications are attempting to open, such as config files, database files, log files, etc. Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt in the DTraceToolkit contain this as a oneliner that can be cut-n-paste to run. Since this uses DTrace, only users with root privileges can run this command. EXAMPLES
This prints new process name and pathnames until Ctrl-C is hit. # filebyproc.d FIELDS
CPU The CPU that recieved the event ID A DTrace probe ID for the event FUNCTION:NAME The DTrace probe name for the event remaining fields The first is the name of the process, the second is the file pathname. DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver- bose descriptions explaining the output. EXIT
filebyproc.d will run forever until Ctrl-C is hit. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
opensnoop(1M), dtrace(1M), truss(1) version 1.00 May 15, 2005 filebyproc.d(1m)