---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure the Kafka metrics connector instance

# Configure the Kafka metrics connector instance {#ariaid-title1}

* Release version: Australia
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the Kafka metric consumer connector instance to read message send to Kafka server over topic.

## Before you begin

To activate metric collection, ensure that the MID Server that retrieves metrics is configured with the Metric Intelligence extension and that the extension is in Started mode. See [Manually configure the Metric Intelligence extension](https://www.servicenow.com/docs/Sk0A01ip_TNJfR0JiGh3bA "Configure the MID Server Metric Intelligence extension to enable the MID Server to pull raw metrics from external systems, to detect anomalies and report anomalies to the instance along with raw data. This MID Server Metric Intelligence extension is required and must be running in order for your system to be able to collect Metric Intelligence data.").  
* For PLAINTEXT in the Credential field, create a Basic authentication credential.Select the Search icon (![search icon]()) next to the Credential field.

* ServiceNow does not support discovery for Kafka. Therefore, create the CI entry manually in the respective table.
{#configure-kafka-metrics-connector__ul_kv5_r1z_zbc}

Role required: evt_mgmt_admin

## Procedure

1. On the Credentials screen, select New.
2. From the list of available credentials, select Basic Auth Credentials.
3. On the Basic Authentication screen, give information for PLAINTEXT authentication, which doesn't require credentials.  
   For PLAINTEXT authentication, in the Name field, type any value and leave the User Name and Password fields empty.
4. Select Submit.
5. For a SASL_PLAINTEXT, SSL, or SASL_SSL authentication credential, in the Credential field, create a Kafka SSL credential.  
   1. Select the Search icon (![search icon]()) next to the Credential field.
   2. On the Credentials screen, select New.
   3. From the list of available credentials, select Kafka SSL Credentials.

      For the Kafka SSL credentials fields descriptions, see [Kafka SSL credentials fields](https://www.servicenow.com/docs/JZzAZEOLpNPVFTWf0nmPzg "Description of the fields on the Kafka SSL credentials form.").  
      Note:  
      If you clear the Disable hostname verification field, then in the Additional Kafka consumer properties field, enter the value of the ssl.endpoint.identification.algorithm parameter the same as of the Kafka server parameter value. For example:  

          ssl.enabled.protocols=TLSv1.2,TLSv1.1,TLSv1;
          sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required username=<username> password=<password>;
          sasl.enabled.mechanisms=PLAIN;ssl.endpoint.identification.algorithm=;

   {#configure-kafka-metrics-connector__ol_bxw_qlh_23c}
{#configure-kafka-metrics-connector__steps_ik1_ffx_t2c}