Log Server Configuration Utility > Configuring log cache files

Configuring log cache files

 

Related topics: Configuring Log Server connections Configuring Log Server database options Configuring consolidation options Configuring WebCatcher Stopping and starting Log Server

The Settings tab of the Log Server Configuration utility lets you manage the log cache file creation options, and specify whether Log Server tracks the individual files that make up each Web site requested, or just the Web site.

1.	Enter the path for storing log cache files in the Cache file path location field. The default path is <installation directory>\bin\Cache. (The default installation directory is C:\Program Files\Websense\).

2.	For Cache file creation rate, indicate the maximum number of minutes Log Server should spend sending Internet access information to a log cache file (logn.tmp) before closing it and creating a new file.

This setting works in combination with the size setting: Log Server creates a new log cache file as soon as either limit is reached.

3.	For Cache file maximum file size, specify how large a log cache file should be before Log Server closes it and creates a new one.

This setting works in combination with the creation rate setting: Log Server creates a new log cache file as soon as either limit is reached.

4.	Check Enable visits to create a log record for each Web site visited.

Note  Managing Log Database size is an important concern in high-volume networks. Enabling visits logging is one way to control database size and growth.

When this option is deselected, a separate log record is created for each HTTP request generated to display the different page elements, such as graphics and advertisements. Also known as logging hits, this option creates a much larger Log Database that grows rapidly.

When this option is selected, Log Server combines the individual elements that create the Web page (such as graphics and advertisements) into a single log record.

If you have installed Websense Web Security Gateway, the results of scanning activity are always reported in hits, even when visits logging is enabled. In this situation, the numbers shown on Web filtering reports that include traffic blocked by scanning will be lower than the numbers shown on scanning-specific reports.

Note  It is best to create a new database partition prior to changing the method of logging between visits and hits. See the Settings > Reporting > Log Database page in Web Security Manager to create a new database partition.

5.	Click Apply to save any changes, then stop and restart Log Server (see Stopping and starting Log Server).

Log Server Configuration Utility > Configuring log cache files