STINNER Victor <victor.stin...@gmail.com> added the comment: Vinay: > I feel that there is no need for a TRACE level in the stdlib
Ok, that's fine. I just pushed the idea of someone on IRC. Since I had the same idea once, I tried, but I lost :-) I can easily survive without TRACE in the stdlib ;-) Vinay: > Victor says "we need to a 6th level since DEBUG might be too verbose" - but > as the PR is currently constituted, enabling the TRACE level would output > DEBUG messages too, and so be even more verbose than just DEBUG! In this case > I feel that, when considering the number of levels, "less is more". Oh, I'm not sure that I explained my point correctly, since someone else on IRC told me that he misunderstood. My point is that logs have different consumers who have different expectations and usages of the logs. In my case, the customer may want to go to up to the DEBUG level "by default" to collect more data on failures. Enabling TRACE would produce too many logs and should be restricted to the most tricky bugs where you cannot guess the bug only with the DEBUG level. I tried to explain that if you are putting all debug traces at the DEBUG level, you may produce 10 MB of log per minute (arbitrary number for my explanation). But producing 10 MB per machine in a large datacenter made of thousands of servers can lead to practical storage issues: too many logs would fill the log partition too quickly, especially when logs are centralized. The idea is to reduce debug traces to 10% at the DEBUG level, and put the remaings traces at the TRACE level. For example, you can imagine to log an exception message at DEBUG, but log the traceback at TRACE level. The traceback is likely to produce 10x more logs. The TRACE level is only enabled on-demand for a short period of time on a few selected servers. Technically, you can already do that INFO and DEBUG levels. But in OpenStack, these levels are already "busy" with enough messages and we needed a 6th level :-) (I don't want to reopen the discssion, just to make sure that I was correctly understood ;-)) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31732> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
