E. USDT Example
This appendix was contributed by Alan Hargreaves.
Throughout this book, the suggested strategies for tracing user-land applications typically end with using the pid provider to trace application internals, should easier, stable providers not be available. Using the unstable pid provider can be extremely complex, can be extremely time-consuming, and can make for some brittle and difficult-to-maintain scripts. It can take days to figure out how to extract the desired information from the running internals of an application. Another option exists for using DTrace to observe and analyze application software; if the source code is available, you can insert your own User Statically Defined Tracing (USDT) provider into the source code ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access