Next
When to use loggingThe logging functions are named after the level or severity of the events they are used to track. The standard levels and their applicability are described below (in increasing order of severity):
Level | When it’s used |
---|---|
DEBUG | Detailed information, typically of interest only when diagnosing problems. |
INFO | Confirmation that things are working as expected. |
WARNING | An indication that something unexpected happened, or indicative of some problem in the near future (e.g. ‘disk space low’). The software is still working as expected. |
ERROR | Due to a more serious problem, the software has not been able to perform some function. |
CRITICAL | A serious error, indicating that the program itself may be unable to continue running. |
The default level is WARNING, which means that only events of this level and above will be tracked, unless the logging package is configured to do otherwise.
Events that are tracked can be handled in different ways. The simplest way of handling tracked events is to print them to the console. Another common way is to write them to a disk file.
A simple exampleimport logging logging.warning("Watch out!") # will print a message to the console logging.info("I told you so") # will not print anything
If you type these lines into a script and run it, you’ll see:
WARNING:root:Watch out!
printed out on the console. The INFO message doesn’t appear because the default level is WARNING. The printed message includes the indication of the level and the description of the event provided in the logging call, i.e. ‘Watch out!’. Don’t worry about the ‘root’ part for now: it will be explained later. The actual output can be formatted quite flexibly if you need that; formatting options will also be explained later.
Logging to a fileA very common situation is that of recording logging events in a file, so let’s look at that next. Be sure to try the following in a newly-started Python interpreter, and don’t just continue from the session described above:
import logging logging.basicConfig(filename="example.log",level=logging.DEBUG) logging.debug("This message should go to the log file") logging.info("So should this") logging.warning("And this, too")
And now if we open the file and look at what we have, we should find the log messages:
DEBUG:root:This message should go to the log file INFO:root:So should this WARNING:root:And this, too
This example also shows how you can set the logging level which acts as the threshold for tracking. In this case, because we set the threshold to DEBUG, all of the messages were printed.
Logging variable dataTo log variable data, use a format string for the event description message and append the variable data as arguments. For example:
import logging logging.warning("%s before you %s", "Look", "leap!")
will display:
WARNING:root:Look before you leap!
As you can see, merging of variable data into the event description message uses the old, %-style of string formatting. This is for backwards compatibility: the logging package pre-dates newer formatting options such as str.format() and string.Template. These newer formatting options are supported, but exploring them is outside the scope of this tutorial: see Using particular formatting styles throughout your application for more information.
Changing the format of displayed messagesTo change the format which is used to display messages, you need to specify the format you want to use:
import logging logging.basicConfig(format="%(levelname)s:%(message)s", level=logging.DEBUG) logging.debug("This message should appear on the console") logging.info("So should this") logging.warning("And this, too")
which would print:
DEBUG:This message should appear on the console INFO:So should this WARNING:And this, too
Notice that the ‘root’ which appeared in earlier examples has disappeared. For a full set of things that can appear in format strings, you can refer to the documentation for LogRecord attributes, but for simple usage, you just need the levelname (severity), message (event description, including variable data) and perhaps to display when the event occurred. This is described in the next section.
Displaying the date/time in messagesTo display the date and time of an event, you would place ‘%(asctime)s’ in your format string:
import logging logging.basicConfig(format="%(asctime)s %(message)s") logging.warning("is when this event was logged.")
which should print something like this:
2010-12-12 11:41:42,612 is when this event was logged.
The default format for date/time display (shown above) is ISO8601. If you need more control over the formatting of the date/time, provide a datefmt argument to basicConfig, as in this example:
import logging logging.basicConfig(format="%(asctime)s %(message)s", datefmt="%m/%d/%Y %I:%M:%S %p") logging.warning("is when this event was logged.")
which would display something like this:
12/12/2010 11:46:36 AM is when this event was logged.
The format of the datefmt argument is the same as supported by time.strftime().
文章版权归作者所有,未经允许请勿转载,若此文章存在违规行为,您可以联系管理员删除。
转载请注明本文地址:https://www.ucloud.cn/yun/38381.html
python logging 备忘 常用format log_formatter = logging.Formatter(%(asctime)s %(process)s %(thread)s %(filename)s [%(levelname)-5.5s] %(message)s) 常用handler TimedRotatingFileHandler 按照日期切分日志 如下: from lo...
阅读 3315·2021-11-12 10:36
阅读 2467·2021-11-02 14:43
阅读 2146·2019-08-30 14:23
阅读 3462·2019-08-30 13:08
阅读 919·2019-08-28 18:09
阅读 3129·2019-08-26 12:22
阅读 3140·2019-08-23 18:24
阅读 2016·2019-08-23 18:17