---
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


---

# Edge Delta data input configuration fields

# Edge Delta data input 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 Edge Delta data input configuration fields

This guide explains the configuration fields required to set up Edge Delta data inputs for streaming log data into your ServiceNow instance.
Proper configuration enables efficient log ingestion and correlation with Configuration Items (CIs) and service instances for improved root cause analysis.
Show full answer Show less  

## Key Configuration Fields

* **Data input name:** Required field to name the data input for identification.
* **Description:** Optional field to describe the data input's purpose.
* **Transport:** Selects the protocol for streaming logs:
  * **TCP:** Preferred for large log volumes; requires specifying MID Server and port. Note that TLS/SSL is not supported with TCP.
  * **HTTP/HTTPS:** Ideal for smaller logs using RESTful APIs. Requires configuration of MID Web Server on the MID Server. The system auto-populates MID Server and port based on the selected MID Web Server. Secure connection and authentication type (Basic or API Key) must be aligned with MID Web Server settings. Proper HTTP headers (Authorization and Content-Type) must be set in advanced settings.
* **MID Web Server:** The MID Web Server instance receiving streamed log data; mandatory for HTTP transport.
* **MID Server:** The MID Server receiving the logs; required field. Auto-populated if HTTP transport is chosen.
* **Port:** Port on the MID Server used for log listening. Must be within allowed range and free of conflicts. Requires coordination with security teams to ensure port accessibility. Auto-populated for HTTP transport.
* **Service instance:** Required field to bind log data to a service instance in the CMDB, facilitating correlation and root cause analysis. If no service instance exists, customers should create one, add relevant CIs, and set its status to Operational.

## Practical Application

By accurately completing these configuration fields, ServiceNow customers ensure seamless log data streaming from Edge Delta into their instances, enabling enhanced visibility into service health and actionable insights through effective CI and service instance correlation.  
Description of the fields on the Edge Delta data input configuration form.
{#hla-data-input-edge-delta-ref__table_c4h_ldt_sdc__entry__2}

| Field | Description |
|-|-|
| Data input name | Name of the new data input. This field is required. |
| Description | Description of the data input. |
| Transport | The Edge Delta destination used for streaming log messages to the ServiceNow instance. The options are: * TCP - Frequently used for handling large volumes of log data.If you select TCP, you must provide the MID Server and port. When choosing the TCP transport option, create a TCP destination in Edge Delta. Use the same MID Server host and port you configured for the Edge Delta data input. Note: For TCP, TLS/SSL is not supported. * HTTP: Frequently used for sending smaller logs via RESTful APIs, HTTP, or HTTPS for secure transmission. Note: For the HTTP protocol, authentication is used. If you select HTTP, you must provide the MID Web Server that is running on the MID Server. The system then populates the MID Server and port fields automatically, based on the provided MID Web Server. Depending on the MID Web Server configuration, you can send logs using either HTTP or HTTPS. If the Secure Connection check box on the MID Web Server extension form is clear, use HTTP. If it is selected, use HTTPS. For more information, see [Event Management MID Web Server extension form](https://www.servicenow.com/docs/1v_MifKT~A7VgKyXHp7W_w "Fields in the form for creating or modifying a MID Web Server extension."). In addition, if the Authentication Type on the MID Web Server extension form is Basic, provide Basic authentication details in the Authorization header. If the Authentication Type is API Key, provide the key as "Key Api_Key". When choosing the HTTP transport option, create an HTTP destination in Edge Delta and enter the Endpoint URL in the following format: http://{MID_SERVER_IP}:{MID_WEB_SERVER_PORT}/api/mid/hla/raw. In Advanced Settings, create two headers to be attached to the HTTP request: * An Authorization header with the MID Web Server API key value or basic credentials as MID Web Server configured. * A Content-Type header named with the application/json value. {#hla-data-input-edge-delta-ref__ul_tf3_wxb_tdc} {#hla-data-input-edge-delta-ref__ul_n3x_y3t_sdc} |
| MID web server | The MID Web Server to which the log data is streamed. |
| MID server | The MID Server to which the Edge Delta logs are streamed. This field is required. If you selected HTTP in the Transport field, this field is populated automatically based on the selected MID Web Server. |
| Port | The port on the MID Server used for listening to logs. Choose a port within the suggested range from the array. In the case of TCP transport, the port must not be occupied by another process. Make sure that your organization's security team opens the selected port. This field is required. If you selected HTTP in the Transport field, this field is populated automatically based on the selected MID Web Server. |
| Service instance | The service instance to which to bind the log data. This field is required. Choosing the service instance enables HLA to correlate CIs and service instances in the CMDB for root cause analysis. Note: If no relevant service instance exists, [Create an service instance](https://www.servicenow.com/docs/access?context=create-it-services&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) and add CIs to it. Set the status of the new service instance to Operational. |
[Table 1. Edge Delta data input configuration form]

{#hla-data-input-edge-delta-ref__table_c4h_ldt_sdc}