Title | Debugging information not available when customer makes a support call |
Status | suspended |
Priority | nice |
Assigned user | Nick Barnes |
Organization | Ravenbrook |
Description | When a customer contacts us with a difficult problem, it's very useful to have all the debugging log messages. However, it's inconvenient to run with log_level = message.DEBUG all the time, so we have to ask the customer to set the log_level and repeat their error. If the error is hard to repeat we might have no way to figure out what went wrong. |
Analysis | We could arrange to always have the relevant information in the log if we kept a buffer in memory of all log messages over the last poll. We would immediately log messages at log_level or higher; then when an error occurs we would log all the messages in the buffer. See [Marick 2000] for discussion of this approach. |
How found | inspection |
Evidence | [Marick 2000] "Using Ring Buffer Logging to Help Find Bugs"; Brian Marick; 2000; <http://visibleworkings.com/trace/Documentation/ring-buffer.pdf >. |
Observed in | 1.3.3 |
Created by | Gareth Rees |
Created on | 2001-12-13 15:26:37 |
Last modified by | Nick Barnes |
Last modified on | 2018-07-05 17:27:50 |
History | 2001-12-13 GDR Created. 2018-07-05 NB Suspended because the P4DTI is obsolete. |