Most of the UNICOM Intelligence products write log files in a standard format. The Log DSC is an UNICOM Intelligence data source component that enables you to easily view and query these log files. The Log DSC supports only log files that are in the standard UNICOM Intelligence format. The Log DSC is read-only and includes MDSC as well as CDSC functionality. This means that you can use the Log DSC to read log files in UNICOM Intelligence Reporter and any other application that requires metadata.

You can specify the data location as any UNICOM Intelligence log file. UNICOM Intelligence log files typically have a .tmp or .log filename extension, and these are the default filename locations used by the Log DSC.

Log files are often linked together in a chain. When you select one log file, the Log DSC automatically enumerates all of the log files in the chain. Note that in UNICOM Intelligence Interviewer, the default configuration creates a limit of 10 log files in a chain. When a chain contains more than the maximum number of log files (10 in the default configuration), UNICOM Intelligence Interviewer automatically deletes the oldest log file in the chain whenever a new log file is created. In addition, a new chain is started whenever the computer is restarted.

You can view all of the log files that have a .tmp filename extension in a folder by specifying the folder location. This is useful when you are investigating a problem on a cluster, because you can combine server logs to get a more accurate picture of the events. It is also useful in any other situation in which you want to view a number of log files that are not linked together in a chain. To include log files in sub folders, specify the Custom connection properties used by Log DSC custom property in your connection string.

All standard UNICOM Intelligence log files contain the same variables when you view them using the Log DSC. For details, see Log variables.

The Log DSC reads files that are 25 MB or smaller. If it finds a file that is bigger than 25 MB, it does not read the file; instead, it creates the following log entry for the file at the Error log level:

For examples of running SQL queries on log files using the Log DSC, see the UNICOM Intelligence Developer Documentation Library.

UNICOM Intelligence Data Model