Lines Matching full:logging
552 <p>While logging is necessary it has a significantly negative impact on
554 terse. The logging facilities provides five different levels of logging. Below
559 This level of logging should be used when something fatal has happened,
563 level is always logged. Issues that justify some logging at the ERROR level
569 This level of logging should used when something serious and unexpected
574 logged. Issues that justify some logging at the WARNING level might also be
579 This level of logging should used be to note that something interesting to
583 authoritative in that domain (to avoid duplicate logging by non-authoritative
588 This level of logging should be used to further note what is happening on the
592 you probably should be using verbose logging. </p>
597 logging. There must therefore be no active logic in an <code>if (LOCAL_LOG)</code> block.
599 (LOCAL_LOG)</code> block. The logging call should not be re-factored out into a
608 This level of logging should be used for everything else. This level will only
620 error, and callers in the same module should only add some logging if that
627 if logging provides information that is not otherwise available to the caller.
633 framework should not trigger logging higher than the DEBUG level. The only
634 situations that should trigger logging at the INFORMATIVE level or higher is
639 <p>When a condition that would normally justify some logging is
659 connections) is considered expected and should not trigger any logging at a
661 logging should be as limited as possible).</p>
674 <p>Any logging that is meant to be read by other people and to be
676 be reasonably understandable. This includes all logging up to the DEBUG
680 <p>When possible, logging should be kept on a single line if it
686 <p>Logging that reports successes should never be used at levels
690 <p>Temporary logging that is used to diagnose an issue that's
708 <p><em>The golden rule of logging is that your logs may not
