|COOKIES: By using this website you agree that we can place Google Analytics Cookies on your device for performance monitoring.|
Automatic insertion of useful log points in production programs
If you have a question about this talk, please contact Stephen Kell.
It is common for complicated systems which work perfectly in a test deployment to fail horribly in a production one, and a large proportion of the time needed to fix such failures is spent determining which aspects of the production environment were inadequately captured by the test one. Experienced programmers are fully aware of this difficulty, and so the vast majority of realistic systems include some mechanisms to simplify it. In particular, they almost always include some ad-hoc, manually-inserted logging of ``interesting’’ events. In this talklet, I will argue that this kind of logging should instead be systematic and automated, and suggest some (very, very preliminary) ideas for arranging this.
This talk is part of the Computer Laboratory NetOS Group Talklets series.
This talk is included in these lists:
Note that ex-directory lists are not shown.
Other listsCambridge PhD Training Programme in Chemical Biology & Molecular Medicine Computational Neuroscience Cambridge Environment
Other talksIs It Ethical to Keep Exotic Pets? Magic-State Distillation in All Prime Dimensions Using Quantum Reed-Muller Codes Humans + Automation: Greater than the sum of the parts Polymers for nanotechnology The Role of spontaneous activity in the developing nervous system Geographical perspectives on personality and wellbeing