IISW3C Input Format Parameters
The IISW3C input format supports the following parameters:
iCodepage | ||
Values: | codepage ID (number) | |
Default: | -2 | |
Description: | Codepage of the log file. | |
Details: | 0 is the system codepage; -2 specifies that the codepage is automatically determined by inspecting the filename and/or the site's "LogInUTF8" property. | |
Example: | -iCodepage:1245 | |
recurse | ||
Values: | recursion level (number) | |
Default: | 0 | |
Description: | Max subdirectory recursion level. | |
Details: | 0 disables subdirectory recursion; -1 enables unlimited recursion. | |
Example: | -recurse:-1 | |
minDateMod | ||
Values: | date/time (in "yyyy-MM-dd hh:mm:ss" format) | |
Default: | not specified | |
Description: | Minimum file last modified date, in local time coordinates. | |
Details: | When this parameter is specified, the IISW3C input format processes only log files that have been modified after the specified date. | |
Example: | -minDateMod:"2004-05-28 22:05:10" | |
dQuotes | ||
Values: | ON | OFF | |
Default: | OFF | |
Description: | Specifies that string values in the log are double-quoted. | |
Details: | Log processors might generate W3C logs whose string values are enclosed in double-quotes. | |
Example: | -dQuotes:ON | |
dirTime | ||
Values: | ON | OFF | |
Default: | OFF | |
Description: | Use the value of the "#Date" directive for the "date" and/or "time" field values when these fields are not logged. | |
Details: | When a log file is configured to not log the "date" and/or "time" fields, specifying "ON" for this parameters causes the IISW3C input format to generate "date" and "time" values using the value of the last seen "#Date" directive. | |
Example: | -dirTime:ON | |
consolidateLogs | ||
Values: | ON | OFF | |
Default: | OFF | |
Description: | Return entries from all the input log files ordering by date and time. | |
Details: | When a from-entity refers to log files from multiple IIS
virtual sites, specifying ON for this parameter causes the IISW3C input format to
parse all the input log files in parallel, returning entries ordered by the values of the
"date" and "time" fields in the log files; the input records
returned will thus appear as if a single IISW3C log file was being parsed. Enabling this feature is equivalent to executing a query with an "ORDER BY date, time" clause on all the log files. However, the implementation of this feature leverages the pre-existing chronological order of entries in each log file, and it does not require the extensive memory resources otherwise required by the ORDER BY query clause. |
|
Example: | -consolidateLogs:ON | |
iCheckpoint | ||
Values: | checkpoint filename | |
Default: | not specified | |
Description: | Load and save checkpoint information to this file. | |
Details: | This parameter enables the "Incremental Parsing" feature that allows sequential executions of the same query to only process new log entries that have been logged since the last execution. For more information, see Parsing Input Incrementally. | |
Example: | -iCheckpoint:C:\Temp\myCheckpoint.lpc | |