Edge Delta data input configuration fields

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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

    The Edge Delta data input configuration form is critical for enabling the streaming of log messages to a ServiceNow instance. It requires specific fields to be filled out for successful data input creation, including mandatory entries such as Data Input Name, MID Server, and Service Instance.

    Show full answer Show less

    Key Features

    • Data Input Name: A required field for identifying the new data input.
    • Description: Provides context regarding the purpose of the data input.
    • Transport Options: Choose between TCP or HTTP for streaming log data:
      • TCP: Suitable for large volumes of logs. Requires specifying the MID Server and port. Note that TLS/SSL is not supported.
      • HTTP: Ideal for smaller logs sent via RESTful APIs. Requires a MID Web Server, and the system auto-fills the MID Server and port based on this selection. Authentication options include Basic and API Key, necessitating the inclusion of relevant credentials and endpoints.
    • MID Web Server: The server to which log data is streamed, automatically populated for HTTP transport.
    • MID Server: The server used for streaming Edge Delta logs, required for configuration.
    • Port: The listening port for logs, which must be secure and available. Automatically populated for HTTP transport.
    • Service Instance: A critical field for correlating configuration items (CIs) and enabling root cause analysis. Must be operational and linked to relevant CIs.

    Key Outcomes

    By accurately completing the Edge Delta data input configuration, customers can effectively stream logs to their ServiceNow instance, enabling better log management, root cause analysis, and overall operational efficiency. Proper configuration ensures seamless communication between Edge Delta and ServiceNow, enhancing data visibility and support capabilities.

    Description of the fields on the Edge Delta data input configuration form.

    Table 1. Edge Delta data input configuration form
    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 to send log data to the instance from any source, using the same MID Server host and port you have 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. 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.
    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 and add CIs to it. Set the status of the new service instance to Operational.