MATRIXX Engine Log Files

Each MATRIXX Engine server has a Log Manager that uses the rsyslog utility to collect, filter, and store messages generated during runtime for each server running in the pod. The logs can be analyzed to determine the root cause of issues that occur with the MATRIXX processes and transaction processing.

System messages are captured in the system log file, mtx_debug.log. This log has error, warning, and informational messages, including SNMP traps. If you set the debug and trace flags, it includes more detailed information.

Topology-based Python script debug messages are stored in the mtx_cmd.log file. This log has error, warning, and informational messages.

Message MDCs containing unsuccessful results in Diameter and MDC Gateway responses are consolidated into the diameter_error_mdc.log and mdc_gateway_error_mdc.log files, respectively. Diameter message MDCs that report an unsuccessful result (a Diameter result value other than 2001) are logged and can be useful in troubleshooting, for example, when a high-level service operation is successful, but a service context context is not. MDC Gateway message MDCs, such as SubMan API messages that contain errors, are returned in the API request and added to the MDC Gateway error log (mdc_gateway_error_mdc.log). API messages that contain errors are not logged to the mtx_debug.log unless you have turned on MDC Gateway tracing or debug.

Both error MDC logs are written only if Error MDC Logging is enabled in the MATRIXX Engine configuration. They are written in compact MDC format and located in the ${MTX_ERROR_MDC_LOG_DIR} directory.

If logging is not configured, MATRIXX uses default stderr logging mechanism. stderr is not consolidated. Instead, it creates a separate log file for messages from each server, with filename service_name_blade_number_stderr.log. For example, transaction_server_1_stderr.log. You configure logging in the MATRIXX configuration file (mtx_config.xml). You can also configure the interval at which log files are rotated for archiving purposes.

Note: For performance reasons, MATRIXX uses rsyslog rather than syslog to generate system logs. RHEL includes rsyslog by default. For more information, see the rsyslog website.

For more information about the MATRIXX environment variables, see the discussion about container directories and environment variables in MATRIXX Installation and Upgrade.