---
title: TCP integration configuration fields
description: Description of the fields on the TCP integration configuration forms for Health Log Analytics.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/health-log-analytics/il-connector-hla-tcp-fields.html
release: australia
product: Health Log Analytics
classification: health-log-analytics
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 2
keywords: [TCP, data input, integration, configuration, field, description, ServiceNow, Health Log Analytics, HLA]
breadcrumb: [Integration configuration fields, Health Log Analytics reference, Health Log Analytics, ITOM AIOps, IT Operations Management]
---
# TCP integration configuration fields
Description of the fields on the TCP integration configuration forms for Health Log Analytics.
For the TCP integration setup procedure, see [Set up a TCP integration for Health Log Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-hla-tcp.md).
|
Field
|
Description
|
|---|
|
Integration Name
|
Unique name of this integration. For example: My TCP 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.
|
|
MID server name
|
The MID Server to which the logs are streamed. This field is required.- You can select only MID Servers with log ingestion capability 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 this number in the MID Server properties.
|
|
Port
|
The port for the MID Server. This field is required.Select a unique port from the array. The placeholder shows the range of ports from which to choose. Make sure that your organization’s security team opens the selected port.
|
|
Service instance
|
The service instance to which to bind the log data. This field is required.
|
|
Transport
|
The protocol used for streaming log messages to your ServiceNow instance: TCP. This field is read-only.
|
|
Description
|
Option to add a brief description of the integration to help identify it.
|
|
Field
|
Description
|
|---|
|
Use SSL/TLS
|
Option to use SSL/TLS.
|
|
Lookup hostnames
|
Option to perform DNS lookup to resolve IPs to hostnames.
|
|
Boss thread count
|
The number of threads that manage connections.
|
|
Worker thread count
|
The number of threads that handle incoming data.
|
|
Read timeout seconds
|
The 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.
|
|
Default timezone
|
The default time zone of events. The system uses this default when the log does not specify a time zone.
|
|
Sub sample drop ratio
|
The ratio of events to drop.
|
|
Sub sample receive ratio
|
The ratio of events to receive.
|
|
Max length in bytes
|
The maximum length of log messages in bytes.
|
|
Character encoding
|
The character encoding for this data input.
|
|
Drop if queue is full
|
Option to discard logs if there is a load on the MID Server.
|
|
Line breaker delimiters
|
The line break character separating the raw log lines.Splitting values must be separated by a comma followed by a space: ", ". For example: "\\r, \\n, , splitHere, \#".
|
**Parent Topic:**[Integration configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown)