Jump to: navigation, search

Web Engagement Cluster:log:standard

(Rpfeiffer used the OptionEdit action.)
Line 2: Line 2:
 
|hidden=false
 
|hidden=false
 
|default=stdout
 
|default=stdout
−
|valid=
 
 
|takeseffect=Immediately
 
|takeseffect=Immediately
 
|shortdesc=Specifies the outputs to which an application sends the log events of the <tt>Standard</tt> level. The log output types must be separated by a comma when more than one output is configured. For example: <tt>standard = stderr, network</tt>
 
|shortdesc=Specifies the outputs to which an application sends the log events of the <tt>Standard</tt> level. The log output types must be separated by a comma when more than one output is configured. For example: <tt>standard = stderr, network</tt>
Line 9: Line 8:
 
|hidden=false
 
|hidden=false
 
|default=stdout
 
|default=stdout
−
|valid=
+
|valid=See table
 
|takeseffect=Immediately
 
|takeseffect=Immediately
 
|shortdesc=Specifies the outputs to which an application sends the log events of the <tt>Standard</tt> level. The log output types must be separated by a comma when more than one output is configured. For example: <tt>standard = stderr, network</tt>
 
|shortdesc=Specifies the outputs to which an application sends the log events of the <tt>Standard</tt> level. The log output types must be separated by a comma when more than one output is configured. For example: <tt>standard = stderr, network</tt>
 
}}
 
}}
−
 
 
{{PubExtended}}
 
{{PubExtended}}
−
 
+
{{DraftExtended
−
{{DraftExtended}}
+
|moredesc='''Valid Values:'''
−
 
+
{{{!}} class="wikitable"
 +
{{!}}- valign="top"
 +
{{!}}
 +
<tt>stdout</tt>
 +
{{!}}
 +
Log events are sent to the Standard output (<tt>stdout</tt>).
 +
{{!}}- valign="top"
 +
{{!}}
 +
<tt>stderr</tt>
 +
{{!}}
 +
Log events are sent to the Standard error output (<tt>stderr</tt>).
 +
{{!}}- valign="top"
 +
{{!}}
 +
<tt>network</tt>
 +
{{!}}
 +
Log events are sent to Message Server, which can reside anywhere on the network. Message Server stores the log events in the Log Database.
 +
{{!}}- valign="top"
 +
{{!}}
 +
<tt>memory</tt>
 +
{{!}}
 +
Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
 +
{{!}}- valign="top"
 +
{{!}}
 +
<tt>[filename]</tt>
 +
{{!}}
 +
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.
 +
{{!}}}
 +
}}
 
{{OptionCreate
 
{{OptionCreate
 
|component=Web_Engagement_Cluster
 
|component=Web_Engagement_Cluster

Revision as of 00:29, March 21, 2018


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

standard

Default Value: stdout
Valid Values: See table
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

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.

Draft Option

No draft option

Comments or questions about this documentation? Contact us for support!