Set up a Splunk TCP integration for Health Log Analytics
Set up an integration to stream log messages to your ServiceNow instance over the TCP transport protocol using a Splunk heavy forwarder. Health Log Analytics processes the ingested log data.
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.
- 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.
- The MID Server must support basic authentication.Note:mTLS is not supported for log ingestion.
- No more than the default maximum of 10 integrations will stream logs to a single MID Server. You can modify the maximum number by adding the property
sn.occ.log_ingestion.max_datainputs_per_midto the MID Server and then changing the default value.To find out how many data inputs are streaming logs to the same MID Server, navigate to the Streaming Sources table and count the data inputs that stream to a specific MID Server.
Role required: evt_mgmt_admin
About this task
You set up integrations through the Integrations Launchpad in Service Operations Workspace, which you access from the ITOM AIOps configuration center. The AIOps configuration center is a centralized workspace for configuring and managing AIOps features from a single place. The integrations setup process reduces implementation time compared to manual data input setup in the classic interface in Health Log Analytics. For more information, see Integrations Launchpad in Service Operations Workspace for ITOM.
Procedure
What to do next
- Use the displayed information to refine how Health Log Analytics reads the log data. For more information, see Review log streaming data and adjust integration settings in Health Log Analytics.
- Use the More options menu (
) to open the Data Input Mapping, Source Type Structures, or Log Sources pages with context from the integration. If your log data is not properly mapped, structured, or sourced, go back and adjust the configuration. If the Service Operations Workspace Log Analytics application is installed, the More options menu also provides direct access to the Log Viewer. Use the Log Viewer to review raw log messages ingested by the integration. For more information, see: