From: Kefu Chai Date: Sat, 29 Jun 2019 13:40:58 +0000 (+0800) Subject: doc/dev/crimson.rst: update logging related doc X-Git-Tag: v15.1.0~2342^2 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=a66c27ad26755f405c26ac3cd8482b5214cf6baa;p=ceph-ci.git doc/dev/crimson.rst: update logging related doc as crimson's logging levels are now connected those of ceph, there is no need to note down the difference between them anymore. Signed-off-by: Kefu Chai --- diff --git a/doc/dev/crimson.rst b/doc/dev/crimson.rst index 4d5683876c3..214e07361a3 100644 --- a/doc/dev/crimson.rst +++ b/doc/dev/crimson.rst @@ -58,19 +58,7 @@ over ``20`` will be printed using ``logger::trace()``. | > 20 | trace | +---------+---------+ -As we know, Ceph allows user to adjust the logging level at runtime. So, if -we set ``debug-osd=20``, all logging messages sent to osd subsystem can be -found in the specified log file. But when it comes to crimson, this is no longer -true. Seastar by default only prints logging messages whose severity is greater -or equal to ``info``. So even if the logging level of OSD subsystem is ``20``, -the logging messages whose levels are greater or equal to 5 are still -invisible, because they are barred by Seastar. This setting can be adjusted -using the ``--default-log-level`` command line option when starting -``crimson-osd``, like:: - - crimson-osd --default-log-level debug" - -And, another noticeable difference in the logging system is that, ``crimson-osd`` +Please note, ``crimson-osd`` does not send the logging message to specified ``log_file``. It writes the logging messages to stdout and/or syslog. Again, this behavior can be changed using ``--log-to-stdout`` and ``--log-to-syslog`` command line