Mainframe APM Traces on IA primary instance stopped – ERROR Fatal error during KafkaServer startup

Products

• DX APM SaaS
• DX Application Performance Management
• DX Operational Observability

Issue/Introduction

The secondary APMIA is getting traces but not on primary APMIA (the primary IA is the one connected to ZAB and the secondary is the one pointed to the kafka queue running on the primary APMIA)

 

We tried restarting the APMIA but it didn't help

The below error is reported in the Agent log:

 

2025-08-22 10:39:11,186] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
kafka.common.InconsistentClusterIdException: The Cluster ID <####> doesn't match stored clusterId Some(<####>) in meta.properties. The broker is trying to join the wrong cluster. Configured zookeeper.connect may be wrong.
        at kafka.server.KafkaServer.startup(KafkaServer.scala:243)
        at kafka.Kafka$.main(Kafka.scala:113)
        at kafka.Kafka.main(Kafka.scala)
[2025-08-22 10:39:11,187] INFO shutting down (kafka.server.KafkaServer)

Environment

DX O2 > APM Infrastructure Agent > Mainframe extension

Resolution

Set a unique value for the below property on each of the APMIA, you can use the below property:

introscope.agent.mainframe.group.id