Home
MATRIXX Monitoring and Logging
Monitoring Components
The following information describes monitoring different components for MATRIXX.
Monitoring Diameter Events
Diameter Event Logger listens to the Diameter Gateway through a TCP connection and logs diameter application messages to a JSON file.

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.
  - Monitoring MATRIXX Business API Gateway
    Business API Gateway SNMP statistics are defined in the matrixx_web_mib.txt file and you display them using the snmp-net-utils snmpwalk command.
  - Monitoring MATRIXX Call Control Framework
    The topics in this section have information about monitoring Call Control Framework (CCF) components, including Network Enabler and CAMEL Gateway.
  - Monitoring Diameter Events
    Diameter Event Logger listens to the Diameter Gateway through a TCP connection and logs diameter application messages to a JSON file.
    - Managing Diameter Event Logger
      The following example YAML Kubernetes deployment file demonstrates how to deploy Diameter Event Logger.
    - Configuring Diameter Event Logger
      Diameter Event Logger loads default configuration parameter values from the classpath. You can configure Diameter Event Logger listening port, output directory, and log file rollover time.
    - Change Diameter Event Logger Log level
      You can set the Diameter Event Logger log level to debug any issues. The default log level is INFO.
  - Monitoring Event Streaming
    Event streaming errors are logged in the Event Streaming Framework mtx_event_streamer.log file. Event Streaming Framework uses Log4j 2.x to log error, debugging, and informational messages. You can also monitor event streaming performance using the performance_analysis_event_server.py script. For information about the script, see the discussion about performance_analysis_event_server.py.
  - Monitoring MATRIXX Route Cache
    Monitor the Route Cache by reading watermark log messages for each Route Cache table and Route Cache SNMP statistics. The SNMP statistics are defined in the matrixx_rc_mib.txt MIB file and returned by the print_snmp_stats.py script. They include statistics on subscriber and session data, statistics on insert, fetch, erase, and iterator operations, general statistics on subscriber records, and garbage collection.
  - Monitoring Payment Service Logging
    Payment service logs messages to the payment-service.log.
  - Monitoring MATRIXX SNMP Statistics
    By default, the SNMP Agent running on a MATRIXX Engine monitors the status and health of all the servers and clusters it has. It collects statistics to aid in identifying potential processing issues.
  - Monitoring MATRIXX Traffic Routing Agent
    Traffic Routing Agent SNMP statistics are defined in the matrixx_tra_mib.txt MIB file and are returned by the print_snmp_stats.py script when run on any of the Traffic Routing Agent servers. They include categories such as TCP traffic, UDP traffic, Diameter Gateway traffic, and MDC Gateway traffic.
  - Monitoring MATRIXX Web Apps
    Use the MATRIXX system logs and SNMP statistics and notifications to monitor the MATRIXX web-facing applications, such as RS Gateway, Gateway Proxy, and My MATRIXX.
  - Monitoring MATRIXX SBA Gateway
    The MATRIXX SBA Gateway SNMP statistics are defined in the matrixx_web_mib.txt file, using the snmp-net-utils snmpwalk command to display them.
  - Monitoring 5G Event Streaming
    5G event streaming can be monitored with standard Kafka and custom metrics.
  - Monitoring Kafka CDR Consumer
    Use aggregated logging and the Prometheus and Grafana third-party products to monitor Kafka CDR Consumer.
- Appendixes
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

Monitoring Diameter Events

Diameter Event Logger listens to the Diameter Gateway through a TCP connection and logs diameter application messages to a JSON file.

For information about installing Diameter Event Logger, see the discussion about Installing the MATRIXX charts in a Kubernetes cluster in MATRIXX Installation and Upgrade.

The Diameter Gateway uses a persistent connection to Diameter Event Logger. If the connection is lost, the Diameter Gateway attempts to reconnect. It is possible that some events will not be logged if the connection is intermittent.

During MATRIXX Engine configuration, you must answer the following create_config.info question to enable Diameter Event Logger: If using the Diameter Gateway external log service, what is its address (host:port)?

This configuration is per-server. If you answered this question with a host and port, in the following create_config.info question, specify which Diameter applications for which you want to log messages. What diameter application ids should be exported (comma separated)?

For example, to log messages for the Sy and Rx applications, answer the question like this: Engine 1:Cluster 1:LogicalBlade 1:What diameter application ids should be exported (comma separated)?Rx, Sy

Supported IDs are listed in the diameter_dictionary.xml file. For example:

<application name="Common" code="0">
<application name="NASREQ" code="1">
<application name="Accounting" code="3">
<application name="Credit-Control" code="4">
<application name="Sh" code="16777217">
<application name="Rx" code="16777236">
<application name="Gx" code="16777238">
<application name="Sy" code="16777302">
<application name="DiameterWrappedMDC" code="33686018">

For information about the configuration parameters, see the discussion about configuring Diameter Event Logger.

Diameter Event Logger is packaged with the latest MATRIXX Engine system MDC definitions. It loads any custom MDC definitions in /opt/mtx/conf/mdc_config_custom.xml when you start it.