And It All Went Horribly Wrong: Debugging Production ... - Joyent

More documents

Recommendations

Info

In the beginning... “As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs.” —Sir Maurice Wilkes, 1913 - 2010 Thursday, November 17, 2011
Debugging through the ages • As systems had more and more demands placed upon them, we became better at debugging their failures... • ...but as these systems were replaced (disrupted) by faster (cheaper) ones, debuggability often regressed • At the same time, software has been developed at a higher and higher layer of abstraction — and accelerated by extensive use of componentization • The high layers of abstraction have made it easer to get the system initially working (develop) — but often harder to understand it when it fails (deploy + operate) • Production systems are more complicated and less debuggable! Thursday, November 17, 2011
Page 1 and 2: And It All Went Horribly Wrong: Deb
Page 3: In the beginning... Sir Maurice Wil
Page 7 and 8: Do we still need to care about fail
Page 9 and 10: Wait, it gets worse • This assume
Page 11 and 12: Debugging in the modern era • Fai
Page 13 and 14: Postmortem advantages • There is
Page 15 and 16: Postmortem challenges • Must have
Page 17 and 18: Postmortem debugging • Postmortem
Page 19 and 20: Postmortem debugging: node.js • D
Page 21 and 22: Debugging transient component failu
Page 23 and 24: DTrace • Facility for dynamic ins
Page 25 and 26: DTrace for node.js • Given the na
Page 27 and 28: Extending DTrace into the VMs • T
Page 29: Thank you! • Dave Pacheco (@dapsa

And It All Went Horribly Wrong: Debugging Production ... - Joyent

Create successful ePaper yourself

Delete template?

Save as template?