fbpx

Setting up debug logging

dt logo 1.5inchAll Drastic software outputs a lot of information when running.  Working with our APIs and command line tools, having the debug logging can help sort out interface and programming issues.  Storing these logs locally, of via a syslog server, can also help sort out issue by comparing the issue to time in the logs.

Windows Logging

By default, Windows uses the DebugOuptutString interface to send debug logs.  This can be captured using the Microsoft DebugView tool:

https://docs.microsoft.com/en-us/sysinternals/downloads/debugview

This tool only captures the debug info when it is running, so if it is not running the debug information is lost.  To capture the information to a on disk log, the DDRConfig tool can be used to redirect it.  In this case it will be saved until it is deleted.  To setup on disk logging, run DDRConfig and go to the Advanced tab.  In the XML tree, go to /VVW/Debug and change EnableLog = 1

DDRConfig DebugLogging

This will cause the debug to be save to a file specified by DefaultLogName.

 

Linux 64 Bit (Centos, Ubuntu, etc)

By default, on any Linux system, all debug will be sent to the syslog.  If nothing is setup, then the log will be saved on the local system under /var/log/.  You can redirect the syslog using normal Linux syslog tools.