I think there are two reasons for that. The D language, which looks like C, but has a few fundamental differences, is pretty far from what Java developers are used to. And the second reason is the fact that DTrace is in reality instrumenting JVM and not the application running in the JVM. This means that dtracing Java is limited by abilities of the Java DTrace provider and also that the transition between the different layers of the stack can add some awkwardness.
Having said that, DTrace is really awesome and can be enormously helpful in many cases when developing or troubleshooting (Java) apps.
One thing I really miss in DTrace is regex support in any part of D scripts. There is a limited globbing support and some workarounds, but they ain't pretty.
Here are some DTrace resources that I found useful:
- DTrace Wiki Docs - the complete documentation (I love to see cool docs like this at our SunWikis)
- a DTrace HowTo
- DTrace for Java at Solaris Internals
- DTrace Toolkit - a compilation of DTrace scripts written by DTrace pros
No comments:
Post a Comment