Member logging

Edit online

Logging information is compiled separately in each member type (informational, operational, WebSphere® eXtreme Scale catalog, WebSphere eXtreme Scale container).

Member logging in AS4 Microservice includes the following logging levels, in descending order of severity:
  • ERROR

    Shows items that did not work as intended or failed.

  • WARN

    Shows items that did not work as intended but the users might work around them. For example, default values.

  • INFO (default)

    Informational messages. For example, a service completed startup and is now initialized.

  • AUDIT
  • DEBUG

    Enables the user to trace through the code to see what went wrong.

    CAUTION:
    Use this setting only when IBM® Customer Support asks the user to enable a certain trace specification.

    When you debug logs, the transaction identifier that is displayed in the visibility events is also inserted at the beginning of the log messages.

  • TRACE

    Enables the user to trace through the code to see what went wrong.

    CAUTION:
    Use this setting only when IBM Customer Support asks the user to enable a certain trace specification.
The logs for each member type that is activated on a node are available by default in the following directories:
Member Type Default Directory
Operational <install directory>/Members/Operational/usr/servers/Operational/logs
Informational <install directory>/Members/Informational/usr/servers/Informational/logs
WebSphere eXtreme Scale catalog <install directory>/Members/WXSCatalog/usr/servers/WXSCatalog/logs
WebSphere eXtreme Scale container <install directory>/Members/WXSContainer/usr/servers/WXSContainer/logs
The following log file names are used in the directories for the member logs:
Member Type Log file for AUDIT, INFO, WARN, and ERROR Messages Log file for TRACE Messages
Operational Operational.log Operational_trace.log
Informational Informational.log Informational_trace.log
WebSphere eXtreme Scale catalog WXSCatalog.log WXSCatalog_trace.log
WebSphere eXtreme Scale container WXSContainer.log WXSContainer_trace.log

The member type log settings in AS4 Microservice are set at the member level and not at the node level. You can separately set the log settings for the different kinds of members (informational, operational, WebSphere eXtreme Scale catalog, WebSphere eXtreme Scale container).

Use the member set_logging command to set the log settings for each member. Any one of the following four attributes can be used in the member set_logging command. You can set only one attribute at a time with the member set_logging command.
Attribute Description Default Value
logDirectory

Sets the directory for all log files, including FFDC (first failure data capture).

This directory must be one of the following:
  • logs, so that the collect_logs command can find the logs.
  • Within an active file system mount point for the node. It can be within a subdirectory of the mount point.
 <install directory>/Members/<member-name>/usr/server/<member-name>/logs

For example:

  • <install directory>/Members/Operational/usr/servers/Operational/logs
  • <install directory>/Members/Informational/usr/servers/Informational/logs
  • <install directory>/Members/WXSCatalog/usr/servers/WXSCatalog/logs
  • <install directory>/Members/WXSContainer/usr/servers/WXSContainer/logs
maxFileSize The maximum size (in megabytes, 1 - 100) that a log file can reach. The maximum file size is approximate. 100
maxFiles

If an enforced maximum file size exists, this setting determines the number of each type of log file that is kept in a log directory (1 - 20). This setting also applies to the number of exception logs that summarize the exceptions that occurred on any day.

For example, if this number is 10, you might have up to 10 message log files, 10 trace log files, and 10 exception summaries in the ffdc/ directory.

 20
traceSpecification

The trace string is used to selectively enable trace.

For multiple packages, separate the entries with a colon. For example, to enable tracing on the org.apache.aries.blueprint and com.ibm.b2b packages, specify the following:

org.apache.aries.blueprint.*=all=enabled:com.ibm.b2b.*=all=enabled

CAUTION:
You need to carefully handle the punctuation of this value, particularly with the asterisk (*). You might need to enter the value in quotation marks for it to take effect.
 *=info=enabled
For example, the following commands update the maxFileSize and maxFiles attributes for the operational member: 
member set_logging operational maxFileSize=10
member set_logging operational maxFiles=5

You can also manage the settings with the following commands:

  • member reset_logging

    This command resets the logging settings to their default values.

  • member show_logging

    This command lists the values for the four logging settings.