Advanced Logging and Obtaining Additional Debug Output

Introduction

When working in Foresight Analytics Platform, the kernel forms and displays debug output. By default this information is not recorded anywhere. In some cases it may be needed to determine the cause of some errors. For this purpose, the user can write debug output to a file. All the settings for logging debug information are stored in the registry of the operating system. Note that outputting debug information to a file slows down the development environment and applications. Thus, remove the parameters specified below after the problem is investigated and the log file is no more required.

Work Log

To output debug information to a file in the registry, make the following changes:

• Create the Log folder in the HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\9.0 branch.

• In this section, create the following values:

• FileName. The string value that contains path and name of the file, to which the debug information is output.

• SeverityLevel. The DWORD value that contains the logging level. For the current parameter, the following values can be set:

• 0. All debug output generated by Foresight Analytics Platform kernel is registered.

• 1. Warnings, errors and critical errors are recorded.

• 2. Errors and critical errors are recorded.

• 3. Only critical errors are recorded.

• IsolatedByDate. DWORD parameter that specifies whether a file should be split by dates. If the parameter is created and has the 1 value, a new file is created each day, to which debug output is written. The current date is added to the file name.

Development Environment Debug Output

To record debug output generated by the development environment kernel to a file, add the following parameters in the registry:

• Create the following DWORD parameters in the HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\9.0\Debug branch and set the 1 value:

• GCTrace. It specifies whether it is required to register all garbage collector messages.

• DisableMetabaseSqlLog. It disables output of SQL queries to repository system tables to debagging information, that are created on addressing to repository objects.

• Create the following DWORD parameters with the 1 value in the HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\9.0\DevEnv section:

• DevEnvDebug. Fixing information about components creation.

• DevEnvParserDebug. Record development environment parser information.

NOTE. Development environment debug information is output if the SeverityLevel parameter is set to 0.