This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients ncoghlan, vinay.sajip
Date 2020-12-15.02:20:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1607998821.36.0.619520119815.issue42642@roundup.psfhosted.org>
In-reply-to
Content
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)
History
Date User Action Args
2020-12-15 02:20:21ncoghlansetrecipients: + ncoghlan, vinay.sajip
2020-12-15 02:20:21ncoghlansetmessageid: <1607998821.36.0.619520119815.issue42642@roundup.psfhosted.org>
2020-12-15 02:20:21ncoghlanlinkissue42642 messages
2020-12-15 02:20:21ncoghlancreate