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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# TCP

# TCP integration configuration fields {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of TCP integration configuration fields

This document details the configuration fields available in the TCP integration setup forms for Health Log Analytics within ServiceNow.
It helps customers understand how to configure TCP-based log streaming from their MID Server to their ServiceNow instance, ensuring proper data ingestion and log management.
Show full answer Show less  

## Key Configuration Fields

* **Integration Name:** A required unique name identifying the TCP integration. Changing this automatically adjusts the generic name displayed on the form.
* **MID Server Name:** Required selection of a MID Server capable of log ingestion with basic authentication. Only MID Servers supporting basic authentication (not mTLS) are listed. Note that by default, a single MID Server can handle up to 10 simultaneous data inputs, adjustable in MID Server properties.
* **Port:** A required unique port number on the MID Server through which logs are streamed. Customers must coordinate with their security team to ensure this port is open.
* **Service Instance:** The target ServiceNow service instance for binding the streamed log data. This field is mandatory.
* **Transport:** The protocol used for streaming logs---TCP. This is a read-only field.
* **Description:** An optional text field to add a brief description to help identify the integration.

## Advanced Settings

* **Use SSL/TLS:** Option to enable secure communication over SSL/TLS.
* **Lookup Hostnames:** Option to perform DNS lookups to resolve IP addresses to hostnames, aiding log clarity.
* **Boss Thread Count \& Worker Thread Count:** Settings to adjust the number of threads managing connections and handling incoming data, enabling tuning for performance.
* **Read Timeout Seconds:** Defines the timeout period for reading data.
* **Default Timezone:** Specifies the time zone the system uses when logs lack an explicit time zone; defaults to GMT if unspecified.
* **Sub Sample Drop Ratio \& Sub Sample Receive Ratio:** Control the ratio of events dropped or received, useful for managing data volume.
* **Max Length in Bytes:** Sets the maximum allowable size of individual log messages.
* **Character Encoding:** Defines the encoding standard used for the incoming data, ensuring proper interpretation of log content.
* **Drop if Queue is Full:** Enables discarding logs when the MID Server is under heavy load, preventing backlog.
* **Line Breaker Delimiters:** Specifies the characters used to separate log lines; multiple delimiters must be separated by ", " to correctly parse raw logs.

## Practical Application for ServiceNow Customers

Understanding and correctly configuring these fields enables ServiceNow customers to effectively stream and ingest log data using TCP integration. Proper setup ensures seamless log flow, security compliance (e.g., port management and SSL/TLS), and performance tuning through thread and sampling configurations. This foundation supports Health Log Analytics by providing accurate, well-structured log data for analysis and monitoring.  
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://www.servicenow.com/docs/897aDx~wM4zQfJLLvNOroQ "Set up an integration for sending log data to your ServiceNow instance directly over a TCP/SSL socket.").
{#il-connector-hla-tcp-fields__table_sfp_25d_pcc__entry__2}

| 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. {#il-connector-hla-tcp-fields__ul_gzy_3xd_pcc} |
| Port | The port for the MID Server. This field is required. Select a unique port. 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. |
[Table 1. Provide details tab]

{#il-connector-hla-tcp-fields__table_sfp_25d_pcc} {#il-connector-hla-tcp-fields__table_kfx_jyd_pcc__entry__2}

| 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, #". |
[Table 2. Advanced settings]

{#il-connector-hla-tcp-fields__table_kfx_jyd_pcc}