Merge pull request #12920 from Liuchang0812/update-document-for-logging-level

doc: explain about logging levels

Reviewed-by: Sage Weil <sage@redhat.com>
This commit is contained in:
Sage Weil 2017-01-13 09:15:10 -06:00 committed by GitHub
commit 3c26e7dad6

View File

@ -150,7 +150,7 @@ Each subsystem has a logging level for its output logs, and for its logs
in-memory. You may set different values for each of these subsystems by setting
a log file level and a memory level for debug logging. Ceph's logging levels
operate on a scale of ``1`` to ``20``, where ``1`` is terse and ``20`` is
verbose. In general, the logs in-memory are not sent to the output log unless:
verbose [#]_ . In general, the logs in-memory are not sent to the output log unless:
- a fatal signal is raised or
- an ``assert`` in source code is triggered or
@ -555,3 +555,5 @@ RADOS Gateway
:Type: Boolean
:Required: No
:Default: ``false``
.. [#] there are levels >20 in some rare cases and that they are extremely verbose.