HTTPERR Input Format Parameters
The HTTPERR input format supports the following parameters:
| iCodepage | ||
| Values: | codepage ID (number) | |
| Default: | 0 | |
| Description: | Codepage of the log file. | |
| Details: | 0 is the system codepage, -1 is UNICODE. | |
| Example: | -iCodepage:1245 | |
| 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 HTTPERR input format processes only log files that have been modified after the specified date. | |
| Example: | -minDateMod:"2004-05-28 22:05:10" | |
| 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 HTTPERR input format to generate "date" and "time" values using the value of the last seen "#Date" directive. | |
| Example: | -dirTime: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 | |