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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich 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: Zurich
* 
* 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/HAsJDjwq~LomU8Loa9TSOQ "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.").

OAuth authentication for the Kafka Metrics Connector is supported only in the Australia release and later. Ensure your instance is upgraded to Australia or a newer version before configuring OAuth.  
* Create Kafka SSL credentials on ServiceNow instance. For more information, see [Kafka SSL credentials fields](https://www.servicenow.com/docs/XYbkznnTjH3uNEOVs_ZQTw "Description of the fields on the Kafka SSL credentials form.").
* 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. Navigate to Event ManagementIntegrationsConnector Instances.
2. Select New and create a connector instance.  
   For details on the connector instance fields displayed on the page, see [Kafka connector instance form](https://www.servicenow.com/docs/neJJEWByt6KZi4wFtDlFdg "The Kafka connector instance form displays the fields you must fill in when creating a Kafka connector instance.").
3. In the MID Servers for connectors section,specify a MID Server that is up and is valid.
4. Right-click the form header and select Save.
5. In the table presenting the connector instance values, verify the populated connector instance values based on your Kafka setup and the message (JSON payload) that you received from the Kafka topic with \<field_mappings\> value.
6. **Optional:** In the Connector Instance Values section, you can edit the values of the mandatory Kafka parameters.  
   For details on the connector instance value parameters, see [Kafka connector instance value parameters](https://www.servicenow.com/docs/NTFWkHjKIOICjdFVURgppA "The following table displays the Kafka connector instance value parameters that you can fill in, as needed, when creating a Kafka connector instance.").
7. Right-click the form header and select Save.
8. Test the connection between the MID Server and the Kafka Metric Consumer connector.  
   * Select Test Connector.
   * If the test connection fails, verify whether the credential is valid, and that the network is connected from the MID Server to the Kafka broker.  
     Note:  
     Kafka topic name validation occurs only in Test Connector validation.
   {#configure-kafka-metrics-connector__ul_dxq_rkq_ygc}
9. After a successful test, make the connector instance active by selecting the Active check box.
10. Select Update.
{#configure-kafka-metrics-connector__steps_ik1_ffx_t2c}

*[\>]: and then