yaml-configuration file of the node. We assume that you have built a node and are able to run it with our own custom configuration, which is described in this tutorial and in this tutorial.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.TurnOnLoggin to False:Debug, Info, Notice and Warning and 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 Notice):MinimalVerbosity, NormalVerbosity or 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 defaultScribes and setupScribes of the configuration file.defaultScribes makes types of scribes available. By default these types are FileSK for writing to a file and StdoutSK for writing to the console. (There are also the types JournalSK for systemd's journal system and DevNullSK for directing the output to nowhere, but those are not available by default.)setupScribes lists those scribes that are actually used. Their kinds must be configured in the defaultScribes section before they can be used. For example, if we want logging to go to logs/mylog.log in Json-format, we can configure this as follows:FileSK use 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 rotation.True or False accordingly. Those flags can be found in the section starting with the comment "##### Coarse grained logging control #####".