Skip to content
Integration configuration fields › Health Log Analytics reference › Health Log Analytics › ITOM AIOps › IT Operations Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Apache Kafka integration configuration fields

Description of the fields on the Apache Kafka integration configuration forms for Health Log Analytics.

For the Apache Kafka integration setup procedure, see Set up an Apache Kafka integration for Health Log Analytics.

FieldDescription
Integration NameUnique name of this integration. For example: My Kafka integration. This field is required.Note: When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered.
Execute onOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.
MID server name

(Only when the Execute on field is set to Specific MID Server)

MID Server to which log data from Apache Kafka is pulled. This field is required.Note:

  • You can select only MID Servers that support basic authentication. MID Servers that support mTLS are not listed.
  • The default maximum number of data inputs streaming logs to a single MID Server is 10. You can modify the maximum number by adding the property sn.occ.log_ingestion.max_datainputs_per_mid to the MID Server and then changing the default value.
  • If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically.
MID Server Cluster

(Only when Execute on is set to Specific MID Server cluster.)

The MID Server cluster to which the log data is pulled. This field is required.The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order.

Note:

  • Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters.
  • The MID Server cluster must include only MID Servers that support basic authentication. mTLS is not supported for log ingestion.
  • Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.
  • The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it, even when that MID Server is down.

For more information about MID Server clusters, see Configure a MID Server cluster.

Service instanceThe service instance \(formerly the application service\) to which to bind the log data. This field is required.
Data sourceThe source of the log data that the integration pulls to your ServiceNow instance: Kafka. This field is read-only.
DescriptionOption to add a brief description of the integration to help identify it.
FieldDescription
Kafka node namesA comma-separated list in the format HOST:PORT,HOST:PORT. This field is required.The list does not have to include all the Apache Kafka Cluster servers.
TopicsA comma-separated list of topics to which the data input must subscribe. This field is required.
Kafka credentialsThe Apache Kafka credentials.You can select existing Kafka SSL credentials, or create new ones by selecting Create Kafka credentials from the drop-down list. For a description of the fields on the Kafka SSL credentials form, see Kafka SSL credentials fields.
Group IDThe name of the Apache Kafka Consumer Group.
FieldDescriptionDefault value
TimeoutThe time, in milliseconds, spent waiting in the poll if data is not available in the topics.500
Default timezoneThe time zone of events that the system will use if a log does not specify the time zone.By default, the system uses GMT in such cases, but you can specify a different time zone.GMT
Sub sample receive ratioThe number of events to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received events.-1
Character encodingThe character encoding for this data input. This field is read-only.UTF-8
Node discovery timeoutThe time, in milliseconds, before node discovery times out.30
Sub sample drop ratioThe number of events to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched events.-1
Max length in bytesThe maximum length, in bytes, of events.32766
Drop if queue is fullOption to discard logs if there is a load on the MID Server.False

Parent Topic:Integration configuration fields