Tracing and debugging IBM Match 360 event streaming issues

The IBM Match 360 event streaming feature includes optional trace logs that can help you to validate and resolve message delivery failures. You must enable the logging capability before you can review and analyze the logs.

Analyzing the event streaming trace logs is an integral part of the event streaming message reconciliation process. For more information about message reconciliation, see IBM Match 360 event streaming message reconciliation.

Enabling event streaming trace logs

A cluster administrator must enable trace logs by using the OpenShift® Console to include the required packages.

Roles and permissions
Cluster administrator To complete this task, you must have the cluster administrator role.

The event streaming logs are captured in the IBM Match 360 data-ms logs. Logs specific to the reconciliation process are captured in the IBM Match 360 model-ms logs.

To enable tracing logs for the data-ms and model-ms microservices, edit the IBM Match 360 instance CR (mdm-cr):
  1. Open the OpenShift Console and go to Administration > CustomResourceDefinition .
  2. Select MasterDataManagement (CRD).
  3. Select the Instance tab, then select mdm-cr and open the YAML tab.
  4. Add the data-ms and model-ms logs under the wlp > logging > trace > specification section.
    • Include the following packages for data-ms logging:
      com.ibm.mdmx.common.events.streaming.*=all
:com.ibm.mdmx.common.events.producer.*=all
:com.ibm.mdmx.common.rabbitmq.*=all
:com.ibm.mdmx.common.events.cache.*=all
:com.ibm.entity.analytics.operational.cache.api.rest.messaging.*=all
    • Include the following packages for model-ms logging: 
      com.ibm.entity.analytics.meta.core.rabbitmq.*=all
:com.ibm.entity.analytics.meta.core.service.*=all
:com.ibm.entity.analytics.meta.core.cache.*=all
:com.ibm.mdmx.common.events.streaming.*=all
:com.ibm.mdmx.common.events.producer.*=all
:com.ibm.mdmx.common.rabbitmq.*=all
:com.ibm.mdmx.common.events.cache.*=all
    • Click Save, then reload the page to ensure that the parameters were added correctly.
  5. Restart the IBM Match 360 data-ms and model-ms pods to enable the new configuration to take effect.

Examples of event streaming log messages (data-ms)

The event streaming trace log can include messages similar to the following examples.

Total messages published
Count of eventstreamingMessageReceived : {x} 
Total number of messages received by data-ms to publish
Total success messages (published to Kafka)
Count of eventstreamingkafkaSentSuccesfully : {x} 
total count of messages successfully published to Kafka
Total messages staged for retry
Count of eventstreamingMessageException : {x}
Count of eventstreamingKafkaSentFailed : {y}

Examples of reconciliation log messages (model-ms)

The message reconciliation trace log can include messages similar to the following examples.

Total Success messages published to RabbitMQ
Count of eventstreamingRabbitMQSentSuccessfully : {x} 
total count of messages successfully published to RabbitMQ
Total failed messages logged
Count of eventstreamingRabbitMQSentFailed : {X} 
total count of messages sent to log file