{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30742,"path":"it-operations-management/health-log-analytics/hla-data-input-mid-server.md","title":"Configure a MID Server data input in Health Log Analytics manually","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure a MID Server data input in Health Log Analytics manually\n\nSet up a data input for collecting and streaming MID Server log messages to your ServiceNow instance.\n\n## Before you begin\n\n-   Verify that a MID Server is installed and configured with the Log Ingestion capability enabled. For more information, see [MID Server system requirements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md).\n\n    \\[Omitted image \"hla-mid-log-ingestion.png\"\\] Alt text: MID Server configuration with Log Ingestion capability enabled.\n\n    **Important:** Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.\n\n-   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 aren't routable over the internet. Without a public IP, external clients can't 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerProperties.md). If the MID Server and external clients are on the same network, connections can be made using the private IP address.\n-   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.\n\nRole required: evt\\_mgmt\\_admin\n\n## About this task\n\nThis procedure describes how to create a MID Server data input from the Data Inputs page. To configure the MID Server data input automatically, click the related link on the MID Server form.\n\n**Important:**\n\n-   When you create a MID Server data input, all logs are automatically mapped to the predefined mid\\_server\\_log source type. This source type includes preconfigured mapping settings to maximize the value of monitoring your MID Server logs. To review the mapping script, navigate directly from the data input configuration form to the mapping form by selecting **Go to Mapping** under Related Links. Review the source type by navigating to Source Type Structures and select the mid\\_server\\_log source type.\n-   For optimal performance, debug MID Server log messages are not processed by default. If you want to send debug messages to Health Log Analytics for processing, add the following to your MID Server properties: mid.hla.mid\\_data\\_input.ignore\\_debug\\_level\\_logs = false.\n\n## Procedure\n\n1.  Navigate to **All** > **Health Log Analytics** > **Data Input** > **Data Inputs**.\n\n2.  On the Data Inputs page, select **New**.\n\n3.  Choose the MID Server data input.\n\n4.  On the form, provide a description of the data input and the name of the MID Server from which the logs are streamed.\n\n    For a description of the fields, see [MID Server data input configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-mid-server-ref.md).\n\n5.  Select **Advanced** to set additional configuration fields.\n\n    On the form, fill in the fields. For a description of the fields, see [MID Server data input configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-mid-server-ref.md). For information about configuring the advanced settings later, see [Configure advanced settings for MID Server data inputs in Health Log Analytics manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-adv-mid-server.md).\n\n6.  Select **Submit**.\n\n\n## Result\n\nThe 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 collecting and streaming MID Server log messages to your ServiceNow instance.\n\nFor a description of how this data input can help you detect and resolve emerging issues in your organization's ServiceNow instance, see [Use Case: Proactive monitoring of your ServiceNow instance in Health Log Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-use-case-syslogs.md).\n\n**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.\n\n## What to do next\n\n[Make sure that the data input is streaming data.](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-streaming.md)\n\n**Parent Topic:**[Configuring data inputs for Health Log Analytics manually](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-inputs-configuring.md)\n\n"}}