|
Introduction
In IISLogs 2.0, we introduced a new feature called Per Directory.
This feature allows 17 options to be specified on a Per Directory
basis. You get all the powerful and flexible features IISLogs provides on
a per directory basis.
How to Manage
The Per Directory feature can be managed using IISLogsGUI. Here is a
screenshot of the management interface. You can also manage the Per
Directory feature via the config file called SampleZipPerDirectory.xml.
(Note: The name of the file can't be altered).
You can update the file using a text editor (such as Notepad).
We recommend you manage a few directories using IISLogsGUI before managing the
configuration file directly. If you decide to manage the file
directly, all data including <Table1></Table1> brackets need to be
added for each folder entry. Please review the sample configuration
file in the Options section.
Options
Each directory has 17 options that can be defined. Here is the complete
list on a per directory basis.
| Option Name |
Description |
| <DirectoryName>c:\windows\system32\inetsrv\urlscan\logs\</DirectoryName> |
Directory name |
| <ZipFile>true</ZipFile> |
Compress file |
| <ZipRetentionPeriod>48</ZipRetentionPeriod> |
Time period in hours |
| <DeleteOriginalFile>true</DeleteOriginalFile> |
Delete original file after compressed has completed. |
| <DeleteFile>false</DeleteFile> |
Separate option to delete files. |
| <DeleteRetentionPeriod>0</DeleteRetentionPeriod> |
Retention Period in hours for how
old the file should be. |
| <Recursive>false</Recursive> |
Recursive Option to start at a particular directory and
recursively get all sub-folders. i.e. d:\wwwlogs |
| <ProcessRootFolderRecursive>false</ProcessRootFolderRecursive> |
Process the 'Root folder as well as sub-folders'. |
| <ZipFilePath>local</ZipFilePath> |
Where files are store. local is default, this leaves the file
in the original location This can also be a UNC path |
| <IncludeComputerName>false</IncludeComputerName> |
When using a UNC path or alternative directory, include PC name.
|
| <ProcessUnknownExtensions>false</ProcessUnknownExtensions> |
Process Unknown file extensions. System file extensions and
folders aren't processed. |
| <ProcessTXT>false</ProcessTXT> |
Process TXT based file extensions |
| <ProcessBAK>false</ProcessBAK> |
Process BAK based file extensions |
| <ProcessDAT>false</ProcessDAT> |
Process DAT based file extensions |
| <ProcessXML>false</ProcessXML> |
Process XML based file extensions |
| <NamingConvention>Default</NamingConvention> |
Implemented for future use |
| <Delimiter>!</Delimiter> |
Implemented for future use |
Example configuration file with multiple folders.
<?xml version="1.0" standalone="yes"?>
<NewDataSet>
<Table1>
<DirectoryName>c:\windows\system32\inetsrv\urlscan\logs\</DirectoryName>
<ZipFile>true</ZipFile>
<ZipRetentionPeriod>48</ZipRetentionPeriod>
<DeleteOriginalFile>true</DeleteOriginalFile>
<DeleteFile>false</DeleteFile>
<DeleteRetentionPeriod>0</DeleteRetentionPeriod>
<Recursive>false</Recursive>
<ProcessRootFolderRecursive>false</ProcessRootFolderRecursive>
<ZipFilePath>local</ZipFilePath>
<IncludeComputerName>false</IncludeComputerName>
<ProcessUnknownExtensions>false</ProcessUnknownExtensions>
<ProcessTXT>false</ProcessTXT>
<ProcessBAK>false</ProcessBAK>
<ProcessDAT>false</ProcessDAT>
<ProcessXML>false</ProcessXML>
<NamingConvention>Default</NamingConvention>
<Delimiter>!</Delimiter>
</Table1>
<Table1>
<DirectoryName>c:\inetpub\logs\</DirectoryName>
<ZipFile>true</ZipFile>
<ZipRetentionPeriod>48</ZipRetentionPeriod>
<DeleteOriginalFile>false</DeleteOriginalFile>
<DeleteFile>false</DeleteFile>
<DeleteRetentionPeriod>0</DeleteRetentionPeriod>
<Recursive>false</Recursive>
<ProcessRootFolderRecursive>false</ProcessRootFolderRecursive>
<ZipFilePath>local</ZipFilePath>
<IncludeComputerName>false</IncludeComputerName>
<ProcessUnknownExtensions>false</ProcessUnknownExtensions>
<ProcessTXT>false</ProcessTXT>
<ProcessBAK>false</ProcessBAK>
<ProcessDAT>false</ProcessDAT>
<ProcessXML>false</ProcessXML>
<NamingConvention>Default</NamingConvention>
<Delimiter>!</Delimiter>
</Table1>
</NewDataSet>
Misc items
- If you use the Per Directory features along with other features
such as SpecificDirectoriese, you'll need to agree to the
Compression Folder policy and Delete file File policy. These can be
set using the IISLogsGUI 'quick wizard' option. Here is a
article that discussed this option further.
http://www.iislogs.com/help/IISLogs20/123goconfigure2.htm
If policies aren't set, no files will be processed.
- When using the Per Directory feature and storing files in a alternative
location besides the local directory, all directory information will be
included in the path. For example. If your log files are stored
locally in d:\wwwlog\w3svc1.
When you store the files on a remote server such as
\\FileServer01\D$\LogFiles.
The path to stored files would be
\\FileServer01\D$\Logfiles\ServerName\wwwlogs\w3svc1. Note:
wwwlogs\w3svc1 are included and can't be excluded. IISLogs is
designed to keep original file location information on a remote server.
The Per Directory option allows you to include or exclude the server name in
the path. We designed IISlogs to have multiple machines move
files to a central location. This is why the server name is included
to keep the folders unique.
- Per Directory has a option called ProcessUnknownExtensions. The feature is designed to handle log files with custom naming conventions such as .06302008. By default, IISLogs by default only handles certain file extensions. One security feature integrated into IISLogs no system files or folders will be processed, either when using ProcessUnknownExtensions or regular IISlogs options.C:\Windows\System32\Logfiles is the only folder below C:\windows that will be processed. We strongly encourage you test this option on a non-production machine before implementing. Also, make sure you have backups of all files before running IISLogs.
|