System log persistence during important events
Opened this issue · 4 comments
We do not save the system log right now, largely to save on disk io. We should have a mechanism to save the system log during important events though - when a user requests support, during system upgrades, etc.
Steve had an excellent idea - we can simply make this a user-toggleable boolean in the config page, which is way easier than bifurcating logs when we detect something is amiss, or automating this at all. I'm really into this idea and he's going to work on it.
It would also be excellent to select the actual log level, or at least turn on debug logging.
It would also be excellent to select the actual log level, or at least turn on debug logging.
Is this a request to add a separate setting for the log level on the frontend, to set the default log level to debug, or to ensure that the log level is debug when the boolean is true?
This is a request to either add:
- a drop down to select the log level
- or a boolean to turn on DEBUG logging
I had to swap the log level in lms_metadata.py to something less verbose than DEBUG already because it was absolutely inundating and wiping out the system log - but it would be nice to be able to turn that back on when necessary.