Home
MATRIXX Monitoring and Logging
Monitoring Components
The following information describes monitoring different components for MATRIXX.
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.
Apache ActiveMQ
The activemq.log file, queues, and topics should be monitored for any errors.

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.
  - 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.
    - All MATRIXX SNMP Statistics
      This topic lists the MATRIXX SNMP Statistics that are collected from the MATRIXX Engine MIB files. For more information on the MIB files, see the discussion about MATRIXX MIB files in MATRIXX Engine Administration.
    - MATRIXX MIB Files
      An SNMP Management Information Base (MIB) file is an ASCII text file that contains dictionaries of the SNMP network elements as a list of data objects. Each element in the MIB has an Object Identifier (OID) that identifies it in the SNMP architecture. Each OID is associated with a human-readable text label.
    - MATRIXX SMI File
      The MATRIXX Engine matrixx_smi.txt SMI file defines top-level object identifiers and textual conventions used in the MATRIXX SNMP MIB modules. The file is located in the ${MTX_DATA_DIR}/snmp/mibs directory. It is recreated here in case you do not have a MATRIXX Engine installation available.
    - MATRIXX Engine SNMP Statistic Monitoring Recommendations
      This topic lists the MATRIXX SNMP statistics you should actively monitor. These statistics are important indicators of the efficiency of your MATRIXX implementation.
    - Display SNMP Statistics on the Command Line
      If you do not have access to a network control center, you can view SNMP statistics in a terminal window.
    - Apache ActiveMQ
      The activemq.log file, queues, and topics should be monitored for any errors.
    - System Notifications
      System notifications are sent when the value of a variable associated with a trap moves above a defined threshold.
  - 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

Apache ActiveMQ

The activemq.log file, queues, and topics should be monitored for any errors.

Log Monitoring

Grep the /opt/activemq/data/activemq.log file for any ERROR messages. For example:

2014-05-07 01:33:08,359 | ERROR | 
Temporary Store limit is 51200 mb, 
whilst the temporary data directory: 
/opt/apache-activemq-5.9.0/data/localhost/tmp_storage only has 15771 mb 
of usable space - resetting to maximum available 15771 mb. | 
org.apache.activemq.broker.BrokerService | main

Queue and Topic Monitoring

Apache ActiveMQ queues and topics should be monitored to ensure that Messages Enqueued = Messages Dequeued. Log into http://<ip_address>:8161/admin/queues.jsp where <ip_address> is the IP address of the Apache ActiveMQ host server to monitor queues. For example:

A table with 4 columns: Name, Number of Consumers, Number of Messages Enqueued, Number of Messages Dequeued — Figure 1. Apache ActiveMQ Queue Monitoring

For more information about monitoring Apache ActiveMQ, see the Apache ActiveMQ documentation.