Jump to: navigation, search

log Section

all

Default Value: stdout, ./logs/gax.log
Valid Values:

Value

Description

stdout


Log events are sent to the Standard output.


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.


[filename]


Log events are stored in a file with the specified name. If a path and filename are not specified, the file is created in the application's working directory.

Changes Take Effect: After Genesys Administrator Extension is restarted.

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: stdout, logfile

expire

Default Value: 20
Valid Values: Any integer value.
Changes Take Effect: After Genesys Administrator Extension is restarted.

Specifies the maximum number of log files to be kept.

log-cache-size

Default Value: 16000
Valid Values: Any integer value.
Changes Take Effect: After Genesys Administrator Extension is restarted.

Specifies the maximum number of logs in the log message queue.

segment

Default Value: 10000
Valid Values: Any valid file size.
Changes Take Effect: After Genesys Administrator Extension is restarted.

Specifies the maximum log file size in kilobytes.

standard

Default Value: ""
Valid Values:

Value

Description

stdout


Log events are sent to the Standard output.


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.


[filename]


Log events are stored in a file with the specified name. If a path and filename are not specified, the file is created in the application's working directory.

Changes Take Effect: After Genesys Administrator Extension is restarted.

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: stderr, network

trace

Default Value: ""
Valid Values:

Value

Description

stdout


Log events are sent to the Standard output.


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.


[filename]


Log events are stored in a file with the specified name. If a path and filename are not specified, the file is created in the application's working directory.

Changes Take Effect: After Genesys Administrator Extension is restarted.

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: stderr, network

verbose

Default Value: standard
Valid Values:

Value

Description

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


The same as interaction.


none


No output is produced.

Changes Take Effect: After Genesys Administrator Extension is restarted.

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.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on December 12, 2018, at 22:18.