[Modernized Runtime Extension for Java (MoRE)]

Log and trace configuration service settings

Use this page to configure log and trace service settings for use in troubleshooting and problem determination.

Supported configurations: The following settings apply when the server is configured to use basic log and trace mode.

The Log and trace configuration page is available for Modernized Runtime Extension for Java only and is supported for managed Liberty servers only.

To view this administrative console page, click Troubleshooting > Logs and trace > server_name > Log and trace configuration.

Common log and trace configuration settings

To apply log and trace configuration settings changes to managed Liberty servers, you must synchronize the node after changing the settings.

If you select this option, you must specify the following parameters:

Maximum File Size

Specifies the maximum size, in megabytes, to which the output file is allowed to grow. This attribute is only valid if the File Size attribute is selected. When the file reaches this size, it is rolled over.

For a managed Liberty server, this setting maps to the Liberty maxFileSize attribute under the logging server configuration element. This configuration applies to all log files in Liberty, not just the Liberty trace.log file. To apply changes to the maxFileSize settings to managed Liberty servers, you must synchronize the node after.

Maximum Number of Historical Files

Specifies the maximum number of rolled over files to keep.

For a managed Liberty server, this setting maps to the Liberty maxFiles attribute under the logging server configuration element. This configuration applies to all log files in Liberty, not just the Liberty trace.log file. To apply changes to the maxFiles settings to managed Liberty servers, you must synchronize the node after.

Trace Configuration Settings

Trace file name

Specifies the name of the file to which the trace output is written.

For a managed Liberty server, the default value is trace.log. Only the file name, for example, trace.log, is used by the binary scanner to update the traceFileName logging attribute in the server.xml file. When you update this value, only valid file names are parsed and applied to the managed Liberty server. Absolute directory paths cannot be set. To apply changes to the Trace File Name settings to managed Liberty servers, you must synchronize the node after.

Trace output format

Specifies the format of the trace output.

You can specify one of three levels for trace output:

Basic (Compatible)

Preserves only basic trace information. Select this option to minimize the amount of space taken up by the trace output.

When Basic is set, it sets the managed Liberty server trace format to Enhanced, which is the default.

[9.0.5.25 or later] When Basic is set, it sets the managed Liberty server trace format to Basic, which is the default.

Advanced: Preserves more specific trace information. Select this option to see detailed trace information for use in troubleshooting and problem determination.
When Advanced is set, the format is set to Advanced for the managed Liberty server.

Enhanced: Preserves detailed trace information by including field names that are components from the log record for the trace message. Select this option to see additional trace information for use in troubleshooting and problem determination.
When Enhanced is set, the format is set to Enhanced for the managed Liberty server.

For a managed Liberty server, Basic, Advanced, and Enhanced trace formats are shown. When a trace format is set, it sets the managed Liberty server trace format to the respective one. To apply changes to the Trace Output or Trace Output Format settings to managed Liberty servers, you must synchronize the node after changing the settings.