log Section

PDF This Page

• all
• buffering
• CallbackService
• ChatService
• ClusterService
• consistency-errors-suppress
• CoreService
• DataDepotService
• debug
• DistributedJobExecutor
• DistributedJobQueue
• expire
• NotificationService
• OrsService
• segment
• ServicesService
• SharedService
• standard
• StatisticService
• StorageService
• SubscriptionService
• trace
• UrsService
• verbose

     

all

Default Value:

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.

>> Back to Top

---

buffering

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately.

True to turn operating system file buffering on. This option applies only to stderr and stdout output. Setting this option to true increases output performance. Note: When you enable buffering, messages may appear at the console with delay.

>> Back to Top

---

CallbackService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Callback Service.

>> Back to Top

---

ChatService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Chat Service.

>> Back to Top

---

ClusterService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Cluster Service.

>> Back to Top

---

consistency-errors-suppress

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Disables consistency level message errors when down to 1.

>> Back to Top

---

CoreService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for options at startup.

>> Back to Top

---

DataDepotService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for DataDepot Service.

>> Back to Top

---

debug

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 the log events of the Debug level and higher (that is, log events of the Standard, Interaction, Trace, and Debug levels). The log output types must be separated by a comma when more than one output is configured.

>> Back to Top

---

DistributedJobExecutor

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for job engine executor.

>> Back to Top

---

DistributedJobQueue

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for job engine queue.

>> Back to Top

---

expire

Default Value: 20

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.
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.

>> Back to Top

---

NotificationService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Notification Service.

>> Back to Top

---

OrsService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for ORS Service.

>> Back to Top

---

segment

Default Value: 10000

Valid Values:

false No segmentation is allowed.

[number] KB or [number] Sets the maximum segment size, in kilobytes. The minimum segment size is 100 KB.

[number] MB Sets the maximum segment size, in megabytes.

[number] hr Sets the number of hours for the segment to stay open. The minimum number is 1 hour.
Changes Take Effect: Immediately.
Specifies whether there is a segmentation limit for a log file. If there is, sets the mode of measurement, along with the maximum size. If the current log segment exceeds the size set by this option, the file is closed and a new one is created.

>> Back to Top

---

ServicesService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Services.

>> Back to Top

---

SharedService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Shared Service.

>> 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. 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 the log events of the Standard level. The log output types must be separated by a comma when more than one output is configured.

>> Back to Top

---

StatisticService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for statistics.

>> Back to Top

---

StorageService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Storage Service.

>> Back to Top

---

SubscriptionService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for Subscription Service.

>> 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. 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 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.

>> Back to Top

---

UrsService

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Enables log for URS Service.

>> 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

---