ZipFile Storage Preference ( Daily, Weekly, Monthly )
Control your zip files retention period. By default, IISLogs creates a zip file on a daily basis. Introduced in IISLogs 4.0, there are options to zip files on a daily, weekly or monthly basis. This can reduce the number of zip files created on disk. You can use IISLogs classic options to apply the same rules to all folders. The SpecificDirectories and Advanced Dir Config options are classic IISLogs options. The Per Directory (introduced in IISLogs 2.0) option allows for the same Zip options (Daily, Weekly, Monthly). Using the PerDirectory option, you can apply separate rules on a per directory basis.
Per Directory enhancements in IISLogs 4.0
In addition to providing Daily, Weekly, Monthly zip options in Per Directory feature, an additional option to Preserve Directory path, this option is called PreserveDirPath in IISLogsGUI). When IISLogs compresses a file stored to an alternative location, either a different directory on the same machine or UNC path, IISLogs preserves the original folder path when writing to disk. For example, if store your IISLogs on c:\inetpub\logs\logfiles\w3svc1, when a file is stored, keeps the original log path, it would be \\ServerName\ShareName\MachineName\inetpubLogs\logfiles\w3svc1\filename.zip (when Include ComputerName checked) or \\ServerName\ShareName\inetpub\Logs\logfiles\w3svc1\filename.zip (when IncludeComputerName not checked) When you disable PreserveDirPath, IISLogs will not retain the original folder path and write to the root of the alternative folder path configured in ZipFilePath. In this example, \\Server\Share\filename.zip
Storing log files on a central based file server
One of the features of IISLogs is to store log files on a central file server, this feature is very powerful and requires a detailed knowledge how your network is designed and maintained. Once IISLogs determines a file needs to be compressed, it first compresses file locally before attempting to save the compressed file on a different directory path, partition or a remote network share. When dealing with large compressed files and putting on a remote file share, this can have unknown consequences on your network performance. We strongly recommend complete testing in a controlled environment before turning over to production.
Deleting files configuration setting options
This feature is a powerful and one of the core benefits to IISLogs, log files can quickly take up a lot of disk space if not managed properly. There are many things that should be taken into account before before turning on or enabling ANY of the DELETE functions in IISLogs. This is why the default settings on all configuration options are turned off by default and explicitly have to be configured to be turned on. You should research and verify all legal parameters on how long log files should be kept before purging. If you configure IISLogs to purge files and these files are NOT backed up to another system for later review. IISLogs isn't responsible for deleted files that are later determined needed for whatever reason. Reviewing your company and/or legal policy on log management should be a must. If your company doesn't have detailed log management solution, one should be created.
Email reports from Local computer
Careful configuration should be considered before emailing reports from servers that are internet facing. The potential for a mis-configured system could be targeted as an open-relay server and used by mass-mailers.
Custom Naming of ZIP Files
Control what the name of the archive files.
This is a new feature introduced in IISLogs 2.0. This provides the flexibility to have separate settings for each folder.
Allows WWW, FTP, or SMTP settings to be automatically added to the configuration file.
Advanced Dir Config
Performs recursive functionality on a root and all sub-folders.
Any questions, please feel free to contact firstname.lastname@example.org.