Manage logs
UNICOM Intelligence Interviewer - Server Admin and the activities and applications that run inside it create a number of log files that provide an audit trail of what each activity has done. If you experience problems with UNICOM Intelligence, the UNICOM Intelligence administrator or a UNICOM Systems, Inc. support representative will need to look at these files to find out what is causing the problems. In a small installation where everything is installed on a single computer, all the log files will be stored in a single folder and can be viewed easily using any text editor. On clustered installations, log files are created on each computer in the cluster, which makes viewing them and matching up records between files quite difficult.
Manage Logs provides an easy method of viewing log files, and can be used to create a zip file containing logs for sending to an UNICOM Systems, Inc. support representative.
Note Although the primary purpose of log files is to record events, some log entries may contain actual data or respondent details or references that enable data or respondent details to be extracted from other files. In addition, log files are not project specific and many log entries contain the project name, making it easy to locate information for a particular project.
Since these things are likely to be security issues in companies that provide UNICOM Intelligence services to a number of external clients or where different teams work on different clients' projects, this release of Manage Logs is available only to UNICOM Intelligence administrators. It is planned that future releases will automatically filter log entries so that users see only the entries that refer either to the system as a whole or to their own projects. Administrators will still have access to all records.
Including or excluding Windows Event logs
The Manage Logs activity's Web.config file is in:
C:\InetPub\wwwroot\SPSSMR\ManageLogs
It defines keys that control the following aspects of the activity's behavior. The following key controls whether the Windows Event logs are exported:
<appSettings>
<add key="IncludeEventLogOption" value="true"/>
</appSettings>
See