New submission from Nick Coghlan <ncogh...@gmail.com>:
When using the logging module for long running services, there's one limitation of the predefined logging levels that I semi-regularly run into: the only entirely reliable log level for reporting that a WARNING state has been cleared is itself WARNING. Using INFO instead means that it is common to get error logs that show warning states being entered without any matching "error cleared" notification. My idea for resolving this would be to define a new ESSENTIAL log level between WARNING and ERROR. The idea of the new log level would be to have a logged-by-default level for non-fault-but-essential messages like: * service startup (including version info) * service shutdown * warnings being cleared (NOTICE would be another possible name for such a level) ---------- messages: 383027 nosy: ncoghlan, vinay.sajip priority: low severity: normal stage: needs patch status: open title: logging: add high priority log level for warnings being cleared type: enhancement versions: Python 3.10 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42642> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
