Dynamic diagnostic log configuration is activated using the -diag-log startup option and specifying the diagnostic log options. Note that the file name specification is preceded by a '+' character.
> run CLIENT --diag-log +$vol.subvol.logcfg [--monitor diag-log:15 ] ...
Configuration Reference
The log configuration must be preceded by a [diag-log] header
|
Option |
Description |
|---|---|
|
enabled |
The value may be "0" to disable message dumping or "1" to enable it. The default is "0". |
|
subvol |
Specifies the subvol in which the individual diagnostic log files will be created. If not specified the logs current subvol of the CLIENT program. |
|
replyCodeFilter |
A list of reply code values that should be selected for logging, specified as a range. |
|
httpStatusFilter |
A list of HTTP status values that should be selected for logging, specified as a range. |
|
content |
A list of selectors indicating the content that should be selected for logging. The following selectors are available:
If omitted, "default" is used. |
Examples
# Log to a file. Only log when the LightWave reply code is 1 or 2 or the HTTP status code is 400-999
[diag-log]
enabled=1
subvol=$data1.diaglogs
replyCodeFilter=1,2
httpStatusFilter=400:999
content=body