You encounter an initialization failure in the OI Connector when integrating with an external Kafka cluster. The logs show a TopicAuthorizationException because the connector attempts to create a syslog ingestion topic (netops.syslog.event-ingestion) even if you do not intend to use syslog data or have commented out the topic configuration.
The following error appears in the OI Connector logs:
[ERROR] ClusterAdmin - Topic creation failed: org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed. [ERROR] KafkaConfigurationManager - Failed to initialize KafkaConfigurationManager, will retry.com.ca.im.oinet.connector.kafka.config.ConfigurationException: Topic creation failed for netops.syslog.event-ingestion.
The OI Connector is hard-coded to attempt the creation of the netops.syslog.event-ingestion topic during initialization.
In environments where the Kafka principal used by the connector lacks "Create" permissions, this causes a fatal initialization loop, preventing other metrics from being processed.
Engineering is tracking this issue via defect DE209062. This issue is targeted to be fixed in 25.4.11 with an updated OI Connector with the fixed code. Watch the Performance Management Resolved Issues documentation for an entry referencing DE209062 to confirm it's inclusion in 25.4.11.
Until a formal fix is available, you can use one of the following methods to bypass the initialization error:
topic-create (or Describe and Create) permission on the topic netops.syslog.event-ingestion for the connector's principal.netops.syslog.event-ingestion manually.Describe permissions on the pre-created topic.Note: This topic is specific to a legacy syslog integration. No data flows into this topic during standard metric ingestion from NetOps Portal or the Data Aggregator, but the topic must exist for the connector to start.