Adding caches to the cache group

Cache properties

Stored log files directory

When ContentReporter collects log files from a NetCache or an FTP server, it copies (stores) the log files into the location specified to store the log files and then processes the log files. This directory is the ContentReporter server's "work area" for the cache. After processing, the ContentReporter server either leaves the log files in the folder or deletes them. By default, ContentReporter stores a cache's collected log files in the ContentReporter server directory:

..\Network Appliance\ContentReporter\jakarta-tomcat\webapps\ContentReporter\cache group\cache\

You can change this directory to a location that better suits your space requirements.

Temporary space requirements

While ContentReporter processes log files, it stores log files and creates temporary files in the stored log file directory. ContentReporter requires 2 GB of temporary space for every 1 GB of log data you collect and process during collection and processing.

Examples of space requirements

The following table lists the amount of temporary space you need during various collection and processing events.

Scheduled events to collect twenty 100-MB log files per cache	Temporary space needed during collection and processing
A scheduled event to process logs for a cache group with one cache	4 GB
A scheduled event to process logs for a cache group with five caches	20 GB
Two concurrent scheduled events to process logs for two cache groups with five caches	40 GB

Note
If ContentReporter stops processing a log file, it saves the log file in the stored log files directory even if you configured ContentReporter to delete the log file after processing. For example, if ContentReporter stops processing a log file with an unacceptable number of error lines, it save the log file in this directory. You should monitor the directories you select to store collected log files to ensure adequate disk space and to identify any unprocessed log files.

Headerless log file format

ContentReporter automatically recognizes NetCache appliance log files (as well as WMS and QuickTime log files) when it processes them because they contain identifying headers. However, some log files contain no headers by which they can be identified. If you add a cache to process headerless Web server or streaming server log files, you must specify the log file type when you set the cache properties in the New Cache window.

Note
If you attempt to process a headerless log file without specifying the format, the ContentReporter parser does not process the log file; it returns the invalid log file header error code (- 4) to the ContentReporter log file.

Delete log files after parsing

ContentReporter enables you to either leave the collected log files in the stored log files directories from which the log files were collected, or to delete them after processing. If you configure ContentReporter to collect a cache's log files at scheduled intervals and choose to leave the log files in the stored log files directory, you should monitor these locations to ensure disk space availability.

Stop parsing when error lines exceed maximum

By default, ContentReporter stops processing a log file if it records 200 error lines in a log file. You can change this value to a number that better suits your needs. To have no limit, set the number of error lines to 0. If the ContentReporter server stops processing a log file because number of error lines has exceeded the maximum, the error code (- 11) is written to the ContentReporter log file.