test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #27931 -- Clarified the meaning of "django catch-all logger."

This commit is contained in:
Kim DoHyeon 2017-08-23 05:24:18 +09:00 committed by Tim Graham
parent 9ad6071aab
commit f21915bb3a
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/topics/logging.txt
View File

@ -456,8 +456,8 @@ Django provides several built-in loggers.
``django``
~~~~~~~~~~
``django`` is the catch-all logger. No messages are posted directly to
this logger.
The catch-all logger for messages in the ``django`` hierarchy. No messages are
posted using this name but instead using one of the loggers below.
.. _django-request-logger:
@ -734,18 +734,19 @@ By default, Django configures the following logging:
When :setting:`DEBUG` is ``True``:
* The ``django`` catch-all logger sends all messages at the ``INFO`` level or
higher to the console.
* The ``django`` logger sends messages in the ``django`` hierarchy (except
``django.server``) at the ``INFO`` level or higher to the console.
When :setting:`DEBUG` is ``False``:
* The ``django`` logger send messages with ``ERROR`` or ``CRITICAL`` level to
* The ``django`` logger sends messages in the ``django`` hierarchy (except
``django.server``) with ``ERROR`` or ``CRITICAL`` level to
:class:`AdminEmailHandler`.
Independent of the value of :setting:`DEBUG`:
* The :ref:`django-server-logger` logger sends all messages at the ``INFO``
level or higher to the console.
* The :ref:`django-server-logger` logger sends messages at the ``INFO`` level
or higher to the console.
See also :ref:`Configuring logging <configuring-logging>` to learn how you can
complement or replace this default logging configuration.