Set up an Apache Kafka integration for Health Log Analytics
Set up an integration for streaming log data from Apache Kafka to your ServiceNow instance for processing by Health Log Analytics.
Avant de commencer
- 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.
- Consider whether to pull the log data to a single MID Server or to a MID Server cluster.
In MID Server clusters, multiple MID Servers are grouped together for failover protection. The active integration runs on a single MID Server in the cluster. If that MID Server fails, the system moves its tasks to the next available MID Server in the cluster in a configured order.
If you decide to use a MID Server cluster, verify the following:
- The MID Server cluster includes only MID Servers that support basic authentication.Remarque :mTLS is not supported for log ingestion.
- Log ingestion is enabled for each MID Server in the cluster.Remarque :If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.
- No more than the default maximum of 10 integrations will pull logs to a single MID Server.
A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 integrations running on it, even when that MID Server is down.
- The MID Server cluster includes only MID Servers that support basic authentication.
Role required: evt_mgmt_admin
Pourquoi et quand exécuter cette tâche
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.
Procédure
Que faire ensuite
- 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: