Jump to: navigation, search

GVP MCP:log:trace
 
(6 intermediate revisions by 2 users not shown)
Line 10: Line 10:
 
neither sent to Message Server nor stored in the Log Database.
 
neither sent to Message Server nor stored in the Log Database.
 
<li><b>memory</b> Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
 
<li><b>memory</b> Log events are sent to the memory output on the local disk. This is the safest output in terms of the application performance.
−
<li><b>&#91;filename]</b> 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.
+
<li><b>&#91;filename&#93;</b> 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.
 
|takeseffect=Immediately
 
|takeseffect=Immediately
−
|shortdesc=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.
+
|shortdesc=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.
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 16:09, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

trace

Default Value: ../logs/MCP

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.

    • Draft Option

    No draft option

    This page was last edited on June 29, 2020, at 16:09.
    Comments or questions about this documentation? Contact us for support!