=doc #16706 fixed wrong link and minor style fixes

This commit is contained in:
Nikita Melkozerov 2015-01-22 23:15:44 +05:00
parent 0c42971758
commit d461675e6a
2 changed files with 5 additions and 5 deletions

View file

@ -26,7 +26,7 @@ as illustrated in this example:
The first parameter to ``Logging.getLogger`` could also be any
:class:`LoggingBus`, specifically ``system.eventStream()``; in the demonstrated
case, the actor systems address is included in the ``akkaSource``
representation of the log source (see `Logging Thread and Akka Source in MDC`_)
representation of the log source (see `Logging Thread, Akka Source and Actor System in MDC`_)
while in the second case this is not automatically done. The second parameter
to ``Logging.getLogger`` is the source of this logging channel. The source
object is translated to a String according to the following rules:
@ -306,7 +306,7 @@ the first case and ``LoggerFactory.getLogger(String s)`` in the second).
final LoggingAdapter log = Logging.getLogger(system.eventStream(), "my.string");
Logging Thread, Akka Source and Actor System in MDC
-------------------------------------
---------------------------------------------------
Since the logging is done asynchronously the thread in which the logging was performed is captured in
Mapped Diagnostic Context (MDC) with attribute name ``sourceThread``.
@ -348,7 +348,7 @@ For more details on what this attribute contains—also for non-actors—please
`How to Log`_.
More accurate timestamps for log output in MDC
------------------------------------------------
----------------------------------------------
Akka's logging is asynchronous which means that the timestamp of a log entry is taken from
when the underlying logger implementation is called, which can be surprising at first.

View file

@ -342,7 +342,7 @@ the first case and ``LoggerFactory.getLogger(s: String)`` in the second).
val log = Logging(system.eventStream, "my.nice.string")
Logging Thread, Akka Source and Actor System in MDC
-------------------------------------
---------------------------------------------------
Since the logging is done asynchronously the thread in which the logging was performed is captured in
Mapped Diagnostic Context (MDC) with attribute name ``sourceThread``.
@ -385,7 +385,7 @@ For more details on what this attribute contains—also for non-actors—please
More accurate timestamps for log output in MDC
------------------------------------------------
----------------------------------------------
Akka's logging is asynchronous which means that the timestamp of a log entry is taken from
when the underlying logger implementation is called, which can be surprising at first.