Logging

Service use two logs

Log service for all error & information messages
File log if the log service isn't available or logged message has log level "Debug", because of debug log level generate very large logs

If the log service isn't available, information about it will be logged by the file log. After the log service will be available again, information about it will be logged by the log service

DPE Log service

DPE Log service is used for all error & information messages. If the service isn't available, then the file log will be used and information about it will be logged by file log. After the log service will be available again, information about it will be logged by the log service.

If the logged message has log level is "Debug", then only file log will be used, because of debug log level generate very large logs. For all other messages (e.g. with log level "Error") DPE Log service will be used if it's available, otherwise file log.

File log

The file log is used for all messages with "Debug" log level, and for all other messages (e.g. "with log level Error") if the DPE Log Service it's available or if DPE log is disabled (see parameter UseDPELog https://davidsystems.atlassian.net/wiki/spaces/LTPS/pages/209387612/DigaSystem+registry+subkeys+and+parameters#TurboPlayerService\ConfigurationName for details here).

If the DPE Log service isn't available, then the file log will be used and information about it will be logged by file log. After the log service will be available again, information about it will be logged by the log service.

log4net.config

this file contains configuration for the file-based logger. File-based logger is used if the log service isn't available or specified log level creates too much log information. File logger has various parameters and can be strong customized.

This file contains configuration for the file log. By default, file logs will be created in the subdirectory "log\ServiceConfigurationName", split per 50 MB size files and formatted as "YYYY-MM-DD HH:MM:SS.sss LogLevel Message". E.g.

CODE

2022-04-14 12:18:58.144 INFO Application started

Hint. By the first installation rename the file template_log4net.config to log4net.config This file contains a typical configuration for file log and can be used without changes in mostly standard workflows even with multiple service configurations workflows or can be used as a start point to optimize file log for custom workflows

log4net.config requirements

Service use the log4net.config as a template to create separated file logs for every configuration. All file logs are created under the main log directory in subdirectories with the configuration names. All parameters in configuration file can be changed except followed

logger with name "DefaultLogger" must be present in configuration file. Service use this logger as a template to create separated loggers for every configuration
appender with name "DefaultAppender" must be present in configuration file. Service use this appender as a template to create separated appenders for every configuration
- Parameter “file” in appender section must be located to the main log directory. Service create subdirectories for all used configurations in this directory

See here information about configuration files
https://logging.apache.org/log4net/release/manual/configuration.html

See here configuration file examples
https://logging.apache.org/log4net/release/config-examples.html