--log-file-log-level vs. --log-level (and --log-file-log-filter), and, how many log files are there, and, what are the different logs, and, what is the meaning of the levels

kenkendk · January 22, 2019, 8:31am

They are intended to be in verbosity order, as defined here:

duplicati/duplicati/blob/master/Duplicati/Library/Logging/Log.cs#L29-L63


      
          public enum LogMessageType

          {

              /// <summary>

              /// The message should only be shown if it is explicitly requested

              /// </summary>

              ExplicitOnly,

              /// <summary>

              /// The message is a profiling message

              /// </summary>

              Profiling,

              /// <summary>

              /// Messages that are normally not wanted for display

              /// </summary>

              Verbose,

              /// <summary>

              /// The message is from a retry

              /// </summary>

              Retry,

              /// <summary>

              /// The message is informative but does not indicate problems

This file has been truncated. show original

The ExplicitOnly level is special. The messages emitted with the level ExplicitOnly are only emitted if a filter matches them directly, or the level is set to ExplicitOnly. These messages are generally just noise, as they are expected messages (such as failing to load some native libraries during backend loading, etc).

I have done some work trying to make the logging more sane, but a core issue is that the backup itself (which can also run on the commandline) is emitting some log messages, and the server (which is showing the UI, running the tasks, and having the scheduler) is also emitting some messages. I am mentioning this as it might help to understand it until we figure out a better way of presenting the messages.