LWN.net Logo

KHB: Dynamic Instrumentation of Production Systems (a.k.a. DTrace)

KHB: Dynamic Instrumentation of Production Systems (a.k.a. DTrace)

Posted Sep 15, 2006 18:17 UTC (Fri) by giraffedata (subscriber, #1954)
In reply to: KHB: Dynamic Instrumentation of Production Systems (a.k.a. DTrace) by richardm
Parent article: KHB: Dynamic Instrumentation of Production Systems (a.k.a. DTrace)

The problem with debugging technologies is that they have always been, and still are to some extent, considered to be poor relations to "the real operating system features".

I think this stems from another concept: that it's wrong for production systems to have bugs. If you think by the time a system goes into production, it shouldn't have bugs, then diverting investment to production debugging tools feels wrong. It's a lot like distributing clean needles to illegal drug users and condoms in school.

I reached a conclusion a long time ago that this view is wrong. Bugs in the field should be expected and investment should be diverted from preventing bugs to making them easier to work around, diagnose, and repair in the field.

I'm seeing more and more diagnostics enabled by default, even with a runtime cost (memory, CPU time, disk space), indicating people are coming around to this view.


(Log in to post comments)

KHB: Dynamic Instrumentation of Production Systems (a.k.a. DTrace)

Posted Sep 17, 2006 15:18 UTC (Sun) by kreutzm (guest, #4700) [Link]

I agree to this view. When you run an evaluation of an IT product, it is quite common to find bugs (even in code shipping for some time already). You can either be proud about the bugs you've found or you can optimize your tools and get those bugs fixed quickly.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds