Home
MATRIXX Monitoring and Logging
Appendixes
System Log Configuration Files
Use the system log scripts and configuration files to configure log rotation, gather system logs, set object tracing, and change the log level dynamically.
rsyslog_mtx.conf File
Specify configuration settings for the rsyslog utility in the rsyslog_mtx.conf configuration file. MATRIXX Engine uses the rsyslog utility to generate and manage log files.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
- About MATRIXX Monitoring and Logging
  MATRIXX Monitoring and Logging describes monitoring and logging for MATRIXX components in a MATRIXX environment.
- Metrics and Alerts
  The following information describes monitoring metrics and alerts information for MATRIXX. MATRIXX Support recommends using the Prometheus and Grafana third-party products to monitor a MATRIXX environment, along with aggregated logging.
- Logging
  The following describes logging information for MATRIXX.
- Tracing
  The following information describes tracing information for MATRIXX.
- Monitoring Components
  The following information describes monitoring different components for MATRIXX.
- Appendixes
  - System Log Configuration Files
    Use the system log scripts and configuration files to configure log rotation, gather system logs, set object tracing, and change the log level dynamically.
    - cron-hourly-logrotate-mtx
      The cron-hourly-logrotate-mtx command is a cron job that checks if the system logs must be rotated on an hourly basis instead of the default daily basis. If the logs must be rotated, the script calls the logrotate utility to perform the rotation.
    - logrotate_mtx.conf File
      Use the logrotate_mtx.conf file to configure system log rotation behavior. By default, the log volume is checked on a daily basis to determine if log rotation is needed, based on the settings defined in this file.
    - logrotate_tra.conf File
      Use the logrotate_tra.conf file to configure system log rotation behavior for a Traffic Routing Agent (TRA) server deployed in Kubernetes. By default, the log volume is checked on a daily basis to determine if log rotation is needed based on the settings defined in this file.
    - rotate_mtx_logs.py
      The rotate_mtx_logs.py script runs the logrotate command from $MTX_LOG_DIR.
    - gather_logs.py
      The gather_logs.py script collects system logs from the ${MTX_LOG_DIR} directory, core files, and custom configuration files that are used at runtime and adds them to a ZIP file so they can be offloaded to a non-engine sever. The gather_logs.py script also analyzes the data in the core file and writes the results to a file with the same name but with a .log extension.
    - rsyslog_mtx.conf File
      Specify configuration settings for the rsyslog utility in the rsyslog_mtx.conf configuration file. MATRIXX Engine uses the rsyslog utility to generate and manage log files.
    - Debug and Trace Logs
      System logs set to the debug or trace level show more details about the processing operations for each MATRIXX process.
    - set_trace.py
      The set_trace.py script changes the system log level dynamically for a single MATRIXX Engine server during runtime for the current session. Specific messages can be logged for one or more MATRIXX services, including more specific tasks that form a service. The script updates the values set in the ${MTX_CUSTOM_DIR}/mtx_log_config_update.cfg file but does not change the base system configuration parameter in the ${MTX_CONF_DIR}/mtx_config.xml file. The script only makes logging changes on the server on which the script runs.
    - set_subscriber_trace.py
      The set_subscriber_trace.py script turns on tracing, which changes the log level for the specified gateway (Diameter Gateway, CAMEL Application Part (CAP), or both), and the Charging Server dynamically during runtime. Turning on tracing allows these MATRIXX processes to log trace messages to the mtx_debug.log file. The script applies to all servers in the specified engine.
    - System Log
      System logs contain standard information that identifies day-to-day processing. They are organized into logical sections.
    - split_mtx_debug_log.py
      The split_mtx_debug_log.py script reads the specified MATRIXX debug log file, retrieves all logical log entries that match the specified input parameter, and writes them to the specified output file.
  - Analytical and Informational Scripts
    Use the scripts in this section to gather information about system performance, system topology, performance statistics, system configuration, and MATRIXX Engine versioning. All scripts run locally on a server as user mtx.
  - Configuration, Demo, and Test Scripts
    Use these scripts to configure MATRIXX Engine, create demos, and test system functionality.
  - Dynamic Logging Scripts
    Use the system log scripts to change the log level dynamically.
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

rsyslog_mtx.conf File

Specify configuration settings for the rsyslog utility in the rsyslog_mtx.conf configuration file. MATRIXX Engine uses the rsyslog utility to generate and manage log files.

The rsyslog_mtx.conf file, located in the /opt/mtx/data directory, has the following configuration settings.

local0.log_level /var/log/mtx/mtx.log
local1.* /var/log/mtx/mtx_process_ctrl.log
& stop

Where:

Local0 is the facility that MATRIXX uses to send messages to the rsyslog utility.
.log_level is the logging level output to the specified file. Possible values are:
- .* — Consolidates messages of all levels to the specified file. This is the default.
- .criti — Records critical messages to the specified file.
- .err — Records error messages to the specified file.
- .warn — Records warning messages to the specified file.
- .info – Records info messages to the specified file.
- .debug — Records debug messages to the specified file.
/var/log/mtx/mtx.log is the full path of the log file. The directory must point to the shared storage.
Local1* is the facility that routes messages from the Process Controller to the /var/log/mtx/mtx_process_ctrl.log file.
& stop disables logging of the message levels specified in log_level to the mtx_debug.log file. To have messages written to both files (debug and system log files), comment out this line. MATRIXX does not recommend writing messages to both log files due to the extra processing requirements.

Example Configuration

This example records messages for each different log level to a separate file, instead of consolidating them in the mtx.log file.

local0.criti /var/log/mtx/mtx_critical.log
local0.err /var/log/mtx/mtx_error.log  
local0.warn /var/log/mtx/mtx_warning.log
local0.info /var/log/mtx/mtx_info.log
local0.debug /var/log/mtx/mtx_debug.log 
local1.* /var/log/mtx/mtx_process_ctrl.log
& stop