logs/, minimal severity is
Notice, and verbosity is normal. We will see how to change all of these and more in this tutorial using various options in the configuration file.
Error), and we can specify the minimal severity of messages that will be passed on (the the console, a file or another logging backend). Messages with a lower severity will be suppressed. By changing this minimal severity to
Debug, we will therefore see messages of all severities; by changing it to
Error, we will only see the most severe messages:
Debug, and there are two with severity
MaximalVerbosity. Changing the verbosity will not change which messages will be displayed, but the amount of information contained in each message.
logs/mainnet.log. This behavior is handled by so-called "scribes", which we can configure in sections
setupScribesof the configuration file.
defaultScribesmakes types of scribes available. By default these types are
FileSKfor writing to a file and
StdoutSKfor writing to the console. (There are also the types
systemd's journal system and
DevNullSKfor directing the output to nowhere, but those are not available by default.)
setupScribeslists those scribes that are actually used. Their kinds must be configured in the
defaultScribessection before they can be used. For example, if we want logging to go to
logs/mylog.login Json-format, we can configure this as follows:
FileSKuse rotating log files (keeping the newest log messages in the configured log file and moving older messages to archive files), and the rotation-behavior can be configured in section
Falseaccordingly. Those flags can be found in the section starting with the comment "
##### Coarse grained logging control #####".