Jump to: navigation, search

GVP MCP:log:message format
 
(6 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
<li><b>full</b> An application uses complete headers when writing log records in its log file.
 
<li><b>full</b> An application uses complete headers when writing log records in its log file.
 
|takeseffect=Immediately
 
|takeseffect=Immediately
−
|shortdesc=Specifies the format of log record headers that an application uses when writing logs in the log file. Using compressed log record headers improves application performance and reduces the log file's size. With the value set to short: <li>A header of the log file or the log file segment contains information about the application (such as the application name, application type, host type, and time zone), whereas single log records within the file or segment omit this information. <li>A log message priority is abbreviated to Std, Int, Trc, or Dbg, for Standard, Interaction, Trace, or Debug messages, respectively. <li>The message ID does not contain the prefix GCTI or the application type ID. <br />A log record in the full format looks like this: <br />2002-05-07T18:11:38.196 Standard localhost cfg_dbserver GCTI-00-05060 Application started <br />A log record in the short format looks like this: <br />2002-05-07T18:15:33.952 Std 05060 Application started
+
|shortdesc=Specifies the format of log record headers that an application uses when
 +
writing logs in the log file. Using compressed log record headers improves
 +
application performance and reduces the log file's size.
 +
With the value set to short:
 +
<li>A header of the log file or the log file segment contains information about
 +
the application (such as the application name, application type, host type,
 +
and time zone), whereas single log records within the file or segment omit
 +
this information.
 +
<li>A log message priority is abbreviated to Std, Int, Trc, or Dbg, for Standard,
 +
Interaction, Trace, or Debug messages, respectively.
 +
<li>The message ID does not contain the prefix GCTI or the application type ID.
 +
<br />A log record in the full format looks like this:
 +
<br />2002-05-07T18:11:38.196 Standard localhost cfg_dbserver GCTI-00-05060 Application started
 +
<br />A log record in the short format looks like this:
 +
<br />2002-05-07T18:15:33.952 Std 05060 Application started
 
}}
 
}}
 
{{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

message_format

Default Value: short

Valid Values:
  • short An application uses compressed headers when writing log records in its log file.
  • full An application uses complete headers when writing log records in its log file.
    Changes Take Effect: Immediately
    Specifies the format of log record headers that an application uses when writing logs in the log file. Using compressed log record headers improves application performance and reduces the log file's size. With the value set to short:
  • A header of the log file or the log file segment contains information about the application (such as the application name, application type, host type, and time zone), whereas single log records within the file or segment omit this information.
  • A log message priority is abbreviated to Std, Int, Trc, or Dbg, for Standard, Interaction, Trace, or Debug messages, respectively.
  • The message ID does not contain the prefix GCTI or the application type ID.
    A log record in the full format looks like this:
    2002-05-07T18:11:38.196 Standard localhost cfg_dbserver GCTI-00-05060 Application started
    A log record in the short format looks like this:
    2002-05-07T18:15:33.952 Std 05060 Application started

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