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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Edge Delta TCP

# Edge Delta TCP integration configuration fields {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Description of the fields on the Edge Delta TCP integration configuration forms for Health Log Analytics.
For the Edge Delta TCP integration setup procedure, see [Set up an Edge Delta TCP integration for Health Log Analytics](https://www.servicenow.com/docs/2CqAWZ6Okg5RC49gZirLZA "Set up an Edge Delta TCP integration to enable Health Log Analytics to process logs it receives from Edge Delta in a distinct format. These logs stream into your ServiceNow instance over the TCP transport protocol.").
{#il-connector-hla-edgedelta-tcp-fields__table_avj_dqh_chc__entry__2}

| Field | Description |
|-|-|
| Integration Name | Unique name of this integration. For example: My Edge Delta 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 | MID Server to which the Edge Delta logs are streamed. 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 this number in the MID Server properties. * If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically. {#il-connector-hla-edgedelta-tcp-fields__ul_ddx_wlg_q2c} |
| Port | The port on the MID Server used for listening to logs. This field is required. Important: Enter a unique port that no other application on the MID Server uses. Ask your security team to confirm that traffic on that port is allowed. |
| 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]

{#il-connector-hla-edgedelta-tcp-fields__table_avj_dqh_chc} {#il-connector-hla-edgedelta-tcp-fields__table_i3k_rqh_chc__entry__2}

| Field | Description |
|-|-|
| Lookup hostnames | Option to perform DNS lookup to resolve IPs to hostnames. The default value is false. |
| Sub sample drop ratio | The ratio of logs to drop. The default value is -1: no logs are dropped. For example: If you want one out of every five logs to be dropped, change the value to 5. |
| Sub sample receive ratio | The ratio of logs to receive. The default value is -1: no logs are received. For example: If you want one out of every five logs to be received, change the value to 5. |
| Max length in bytes | The maximum length of log messages in bytes. The default value is 32766. |
| Character encoding | The character encoding for this data input. Default is UTF-8. |
| 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, #". |
| 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 timeout in seconds since the last read. When the timeout expires, the system closes the channel. |
| Default timezone | The time zone of events that the system uses if a log does not specify the time zone. By default, the system uses GMT, but you can specify a different time zone. |
| Drop if queue is full | Option to discard logs if there is a load on the MID Server. |
[Table 2. Advanced settings]

{#il-connector-hla-edgedelta-tcp-fields__table_i3k_rqh_chc}