Configure REST API data inputs
Configure a REST API data input for streaming log data to your ServiceNow instance in JSON format.
Before you begin
- Verify that a MID Server is installed and configured with the Log Ingestion capability enabled. For more information, see MID Server system requirements. Important:Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.
On the MID Web Server Context form, in the Execute on field, select Specific MID Server and not the cluster option. In the MID Server field, select the specific MID Server to which the log data is pulled.
- 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. If the MID Server and external clients are on the same network, connections can be made using the private IP address.
Role required: evt_mgmt_admin
About this task
To stream log messages to the MID Server, the URL must have the format http://{MID_SERVER_IP}:{MID_WEB_SERVER_PORT}/api/mid/hla/raw, where /api/mid/hla/raw is the endpoint.
Procedure
Result
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.