Set up a data input for receiving log messages that were published to a Google Cloud Platform (GCP) Pub/Sub topic and streaming them to your ServiceNow instance.

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.

    MID Server configuration with Log Ingestion capability enabled.

    Important: Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.
  • When the MID Server IP address is exposed through network address translation (NAT), a load balancer, or a similar device, the MID Server must have a public IP address to be reachable by external clients, such as Filebeat agents, located outside its network. Private IP addresses are not routable over the internet, so without a public IP, these 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.
    Note: If the MID Server and external clients are on the same network, a public IP is not necessary, and 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.

Role required: evt_mgmt_admin

Procedure

  1. Navigate to All > Health Log Analytics > Data Input > Data Inputs.
  2. On the Data Inputs page, select New.
  3. Choose the GCP PubSub data input type.
    Note: The selected data input type complements the passive data input (listener). For more information, see Supported data inputs for Health Log Analytics.
  4. On the form, fill in the fields.
    For a description of the fields, see GCP PubSub data input configuration fields.
  5. (Optional) Select Advanced to set additional configuration fields.
    For a description of the fields, see GCP PubSub data input configuration fields.
  6. Select Save.
    Health Log Analytics adds the data input record to the Data Inputs table.
  7. Verify that the data input is configured correctly by selecting Test connection.

    Health Log Analytics tries to connect the MID Server to the data repository.

    If the data input is configured to run on a MID Server cluster, the system tries to connect all the MID Servers contained in the cluster to the repository. The cluster passes the test if at least one of its MID Servers gets connected. This feature is supported in the Health Log Analytics application, Version 26.0.17 - February 2023 and later, available from the ServiceNow Store.

    • If the connection was established, the Test connection button is turned off and the Publish button is enabled.
    • If the connection failed, the reason for the failure displays in the Error message field. Resolve the issue, select Save if you changed the configuration, and then select Test connection to test the connection again.
      Note: You can only publish the data input configuration when the connection is created successfully.
    Note: You can revert to the last published configuration by selecting Revert Changes. This option is available only when you're modifying a configuration that has been published previously.
  8. Select Publish to publish the data input to the MID Server.

Result

The 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 to receive log messages from the Google Cloud Pub/Sub topic and streams them to your ServiceNow instance via the MID Server.

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.