...
Code Block | ||
---|---|---|
| ||
<loggers> <logger name="Continua.Shared.Logging.WindowsEventLogLogger, Continua.Shared.Logging" level="Quiet"/> <!-- Uncomment the following line to enable logging to the diagnostics app. <logger name="Continua.Shared.Logging.UdpLogger, Continua.Shared.Logging" level="Debug" /> --> <!-- Uncomment the following line to enable logging to a file <logger name="Continua.Shared.Logging.FileLogger, Continua.Shared.Logging" level="Debug" /> --> <!-- Uncomment the following line to see logging when running Continua with the -console flag --> <logger name="Continua.Shared.Logging.FormattedConsoleLogger, Continua.Shared.Logging" level="Quiet"/> </loggers> |
File Logging
Enabling file logging will write all debug information to C:\ProgramData\VSoft\Continua\Logs. Note that ProgramData may be a hidden directory. Logs will be written to this folder and each log can be identified by the date the log was generated. Each log has the following name <year><month><date>. Logging will be added to the current log until the next day ticks over.
...
The Continua Server and / or Agent service will need to be restarted once you have enabled or disabled file debugging.
UDP Logging
Enabling UDP logging will write all debug information to the Continua.Diagnostics command window. The Continua.Diagnostics application can be found in the same directory as the config file. Run the diagnostics tool and Continua will immediately start debugging to the diagnostic tools. If you are having issues with the Continua service starting up then make sure the diagnostic tool is running before you reset the Continua service.
...