Log files

Location

Connect's log files are located in the following folder: C:\Users\[UserName]\Connect\logs.
Where [username] is replaced by the appropriate Windows user name.

Tip: Actually, the path may not begin with 'C:\Users', as this is language-dependent. On a French system, for example, it would be 'C:\Utilisateurs'.

Type %userprofile% in a Windows File Explorer and press Enter to open the actual current user's home directory.

Every time output is generated, the Designer and any engines involved in the operation produce their own log files.

Each component writes its log files to a dedicated subfolder of the Log folder. The following folders will likely be of the most benefit.

  • Merge engines write to the logs/Mergeengine folder

  • Weaver engines to the logs/Weaverengine folder

Note that actions of the Cleanup service are only logged in the Server's log file. (See also: Clean-up Service preferences.)

Tip: For more information about Connect's architecture, see: OL Connect: a peek under the hood.

Name

The name of a log file consists of the component's name, a time stamp and the Windows process ID.
The Windows process ID is needed since multiple engines of the same type could be running at the same time, depending on the engine configuration (see Engine configuration) and the size of a job.

Format

The log files are text files that can be opened in any text processor. Each log file contains a header section containing a snapshot of the current working environment (Connect version, operating system, system locale settings, disk and RAM information, and such like).

The logging level is configurable, as well as the exact format - the "logging pattern" - of the individual log messages.

The Designer's log messages are also displayed in the Messages pane (see Preflight Results and Messages). The Log Filter allows you to decide what kind of events may be shown in the Messages pane (see Log Filter). That doesn't change the actual logging level of the Designer, however; it only filters the log file.