Set up data inputs in Health Log Analytics manually
Set up your Health Log Analytics data inputs for Health Log Analytics manually. Data input configuration is an essential step in setting up the Health Log Analytics application.
Avant de commencer
Remarque :
Consider using the Health Log Analytics data input guided setup, which ensures that you have the minimum required setup for the data input process. For more information, see Set up data inputs in Health Log Analytics using guided setup.
- 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.
- 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.
- For shipping your logs encrypted using SSL TLS, see the Streaming Data With Rsyslog & Filebeat Using SSL [KB0866319] article in the Now Support Knowledge Base.
- For MID Server proxy requirements, see MID Server proxy preconditions for streaming logs to Health Log Analytics.
Role required: evt_mgmt_admin. For the ServiceNow System Logs data input: admin.