---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure UDP data inputs

# Configure UDP data inputs {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configure a data input for sending raw log messages to your ServiceNow instance directly over a UDP socket.

## Before you begin

This feature is supported in the Health Log Analytics application, Version 25.0.17 - November 2022 and later, available from the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home).  
* Verify that a MID Server is installed and configured with the Log Ingestion capability enabled. For more information, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

  Important:  
  Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.
* Unless the MID Server and external clients are on the same network, the MID Server must have a public IP address. This is required when its IP is exposed through network address translation (NAT), a load balancer, or a similar device. The public IP address enables external clients, such as Filebeat agents located outside its network, to reach the MID Server. Private IP addresses are not routable over the internet. Without a public IP, external clients cannot connect to the MID Server even if they are configured with its address. In the MID Server properties, add a property named mid.public_ip with the public IP address as the value. For more information, see [Create a MID Server property](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=yokohama&pubname=yokohama-servicenow-platform&section=t_SetMIDServerProperties&ft:locale=en-US). If the MID Server and external clients are on the same network, connections can be made using the private IP address.
* For shipping your logs encrypted using SSL TLS, see the [Streaming Data With Rsyslog \& Filebeat Using SSL \[KB0866319\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0866319) article in the Now Support Knowledge Base.
{#hla-data-input-udp__ul_ql4_dhx_lnb}

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllHealth Log AnalyticsData InputData Inputs.
2. On the Data Inputs page, select New.
3. Choose the UDP data input type.  
   Note:  
   The selected data input type complements the passive data input (listener). For more information, see [Supported data inputs for Health Log Analytics](https://servicenow-prod.fluidtopics.net/2BBiqGf_XyB3Y7e3Ner22Q "Health Log Analytics (HLA) enables you to connect your ServiceNow instance to several types of data input.").
4. On the form, fill in the fields.  
   For a description of the fields, see [UDP data input configuration fields](https://servicenow-prod.fluidtopics.net/WzMldZNihvX0dnfNrk8gXw "Description of the fields on the UDP data input configuration form.").
5. **Optional:** Select Advanced to set additional configuration fields.  
   For a description of the fields, see [UDP data input configuration fields](https://servicenow-prod.fluidtopics.net/WzMldZNihvX0dnfNrk8gXw "Description of the fields on the UDP data input configuration form.").
6. Select Save.  
   Health Log Analytics adds the data input record to the Data Inputs table.
7. Ensure that the data input is configured correctly by selecting Test connection.  
   Health Log Analytics tries to connect the MID Server to the data repository.  
   * If the connection was established, the Test connection button is turned off and the Publish button is enabled.
   * If the connection failed, the reason for the failure displays in the Error message field. Resolve the issue, select Save if you modified the configuration, and then select Test connection to test the connection again.  
     Note:  
     You can only publish the data input configuration when the connection is created successfully.

   {#hla-data-input-udp__ul_z2d_sxt_r5b}  
   Note:  
   You can revert to the last published configuration by selecting Revert Changes. This option is available only when you're modifying a configuration that has been published previously.
8. Select Publish to publish the data input to the MID Server.

## Result

The data input configuration process is complete. Health Log Analytics adds the data input record to the Data Inputs table and attaches the configuration file to the data input record. The data input starts sending raw
log messages to your ServiceNow
instance directly over a UDP socket.  
Note:  
If the HLA engine is down and data has stopped streaming, a notification appears at the top of the data input configuration page. When this happens, contact ServiceNow support.

## What to do next

[Make sure that the data input is streaming data.](https://servicenow-prod.fluidtopics.net/xKLHpaqO7y8J5FCQaVbyMw "Identify and address log streaming issues to ensure that the data inputs you have configured for Health Log Analytics are streaming data properly to your ServiceNow instance.")
**Related tasks**   

* [Configure advanced settings for Rsyslog, Splunk, TCP data inputs](https://servicenow-prod.fluidtopics.net/xUDAhqL4PuYI9IOrYuGiGQ "Manually configure advanced settings for data inputs that use Rsyslog, Splunk, or TCP agents in Health Log Analytics.")

*[\>]: and then