Tracing Objects

You can set trace counters on multiple objects, and all results are logged to mtx_debug.log.

You can set trace counters on the following objects using the trace_object.py script:
  • MtxAccountObject
  • MtxDeviceObject
  • MtxGroupObject
  • MtxSubscriberObject
  • MtxUserObject
When tracing is enabled, an LM_TRACE message is logged with the ObjectId of the traced object and the current TraceCounter value allowing you to correlate messages (RelatedMsgId) using the ObjectId across different logical flow categories, task-chain executions, and processing servers. For example, after running the following command: 
trace_object.py -t ObjectId 0:1:5:1 0:1:5:2 --traceCounter 10
The log file includes information for both objects:
LM_INFO  25868|25976 2021-05-25 10:56:13.151419 [charging_server_1:1:1:1(5230.82827)] MDC-8000658b894a76cc | SubManFunctions::traceDatabaseObject: Setting TraceCounter=10 on MtxMobileDeviceObject: OID=0:1:5:1
...
LM_INFO  25868|25978 2021-05-25 10:56:13.156675 [charging_server_1:1:1:1(5230.82827)] MDC-8001658b894a8bea | SubManFunctions::traceDatabaseObject: Setting TraceCounter=10 on MtxLoginDeviceObject: OID=0:1:5:2

For information about the trace_object.py script, see the discussion about trace_object.py in the appendixes.

Note: You can run this script on a maintenance VM and point it to the MDC port of the Traffic Routing Agent (TRA) in a Kubernetes cluster.
The TraceCounter field is applied to the specified objects on all servers on active and standby engines. The default TraceCounter value (10) is set in mtx_config.xml. You can change this value in the /opt/mtx/custom/mtx_config_base_xml_sed.extra file. For example:
s@default_object_trace_counter>.*<@default_object_trace_counter>20<@