Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: explain about logging levels #12920

Merged
merged 1 commit into from Jan 13, 2017
Merged

doc: explain about logging levels #12920

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 3 additions & 1 deletion doc/rados/troubleshooting/log-and-debug.rst
View file
Open in desktop
Expand Up @@ -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
Expand Down Expand Up @@ -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.