log Section

PDF This Page

• all
• buffering
• expire
• messagefile
• segment
• standard
• trace
• verbose

     

all

Default Value: stdout
Valid Values: stdout Log events are sent to the Standard output (stdout). stderr Log events are sent to the Standard error output (stderr). network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. Setting the all log level option to the network output enables an application to send log events of the Standard, Interaction, and Trace levels to Message Server. Debug-level log events are neither sent to Message Server nor stored in the Log Database. memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance. [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
Changes Take Effect: Immediately

Specifies the outputs to which an application sends all log events. The log output types must be separated by a comma when more than one output is configured. For example: all = stdout, logfile

>> Back to Top

---

buffering

Default Value: false
Valid Values: true Enables buffering. false Disables buffering.
Changes Take Effect: Immediately

Turns on/off operating system file buffering. The option is applicable only to the stderr and stdout output. Setting this option to true increases the output performance.

>> Back to Top

---

expire

Default Value: 10

Valid Values:

false - No expiration; all generated segments are stored.

<number> file or <number> - Sets the maximum number of log files to store. Specify a number from 1-100.

<number> day - Sets the maximum number of days before log files are deleted. Specify a number from 1-100. If an option's value is set incorrectly-out of the range of valid values- it will be automatically reset to 10.

Changes Take Effect: Immediately
Determines whether log files expire. If they do, sets the measurement for determining when they expire, along with the maximum number of files (segments) or days before the files are removed. This option is ignored if log output is not configured to be sent to a log file.

>> Back to Top

---

messagefile

Default Value: ucsproxy.lms
Valid Values: ucsproxy.lms
Changes Take Effect: At start/restart

Logging message file used by Universal Contact Server Proxy.

>> Back to Top

---

segment

Default Value: false
Valid Values: false or any valid integer
Changes Take Effect: Immediately

Specifies the maximum log segment size:

• false—Disables log segmentation
• Any valid integer—Specifies the segment size in KB.

Note: UCS Proxy does not currently support the configuration of different units.

>> Back to Top

---

standard

Default Value: stdout
Valid Values: stdout Log events are sent to the Standard output (stdout). stderr Log events are sent to the Standard error output (stderr). network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance. [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
Changes Take Effect: Immediately

Specifies the outputs to which an application sends the log events of the Standard level. The log output types must be separated by a comma when more than one output is configured. For example: standard = stderr, network

>> Back to Top

---

trace

Default Value: stdout
Valid Values: stdout Log events are sent to the Standard output (stdout). stderr Log events are sent to the Standard error output (stderr). network Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database. memory Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance. [filename] Log events are stored in a file with the specified name. If a path is not specified, the file is created in the application’s working directory.
Changes Take Effect: Immediately

Specifies the outputs to which an application sends the log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels). The log outputs must be separated by a comma when more than one output is configured. For example: trace = stderr, network

>> Back to Top

---

verbose

Default Value: standard
Valid Values: all All log events (that is, log events of the Standard, Trace, Interaction, and Debug levels) are generated. debug The same as all. trace Log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels) are generated, but log events of the Debug level are not generated. interaction Log events of the Interaction level and higher (that is, log events of the Standard and Interaction levels) are generated, but log events of the Trace and Debug levels are not generated. standard Log events of the Standard level are generated, but log events of the Interaction, Trace, and Debug levels are not generated. none No output is produced.
Changes Take Effect: Immediately

Determines whether a log output is created. If it is, specifies the minimum level of log events generated. The log events levels, starting with the highest priority level, are Standard, Interaction, Trace, and Debug.

>> Back to Top

---