Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

GCP PubSub integration configuration fields

Description of the fields on the GCP PubSub integration configuration forms for Health Log Analytics.

For the GCP PubSub integration setup procedure, see Set up a GCP PubSub integration for Health Log Analytics.

FieldDescription
Integration NameUnique name of this integration. For example: My GCP PubSub integration. This field is required.Note: When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered.
Service InstanceThe service instance \(formerly the application service\) to which to bind the log data. This field is required.
Execute onOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.
MID Server name

(Only when Execute on is set to Specific MID Server.)

The MID Server to which the logs are streamed. Note:

  • You can only select a MID Server with log ingestion capability that supports basic authentication. MID Servers that support mTLS are not listed.
  • If log ingestion is not enabled on the selected MID Server, Health Log Analytics enables it automatically.
  • The default maximum number of data inputs streaming logs to a single MID Server is 10. You can modify this number in the MID Server properties.

This field is required.

MID Server cluster

(Only when Execute on is set to Specific MID Server cluster.)

The MID Server cluster to which the log data is pulled. This field is required.The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order.

Note:

  • Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters.
  • The MID Server cluster must include only MID Servers that support basic authentication. mTLS is not supported for log ingestion.
  • Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.
  • The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it, even when that MID Server is down.

For more information about MID Server clusters, see Configure a MID Server cluster.

SourceThe source of the log data that the integration pulls to your ServiceNow instance: PubSub. This field is read-only.
DescriptionOption to add a brief description of the integration to help identify it.
FieldDescription
Project IDThe project ID of the Google Cloud project. For example, my-project-id. This field is required.You can obtain the project ID from your Google Cloud homepage by selecting My Project. The project ID will be displayed.
Authentication methodThe credential alias ServiceNow® uses to access Google Cloud. The default value is sn_occ.HLA_Credential_Alias. This field is required.Note: You can add more credential aliases to the list of available aliases to choose from by selecting Manage credential aliases from the list and adding a credential alias.
Topic nameThe Google Cloud Pub/Sub topic to which to subscribe Health Log Analytics. For example, my\_topic. This field is required.You can obtain the topic name from your Google Cloud homepage by searching for Pub/Sub. All topic names will be displayed.
Subscription nameThe subscription Health Log Analytics uses to receive log data that is published on the Google Cloud Pub/Sub topic.If you leave this field blank, Health Log Analytics uses ServiceNow-Subscription.
FieldDescriptionDefault value
Subscriber thread pool sizeThe number of concurrent threads that are downloading files from the Google Cloud Pub/Sub topic.1
Sub sample receive ratioThe ratio of logs to receive. This setting determines the number of logs to group together, out of which one is received. It reduces the number of logs you receive. The default value is -1, meaning no logs are received. For example, if you want to receive one log out of every five, change the value to 5.-1
Max length in bytesThe maximum length of log messages, in bytes.32,766
Character encodingThe character encoding for this data input. This field is read-only.UTF-8
Sub sample drop ratioThe ratio of logs to discard.This setting determines the number of logs to group together, out of which one is dropped. It reduces the number of fetched logs. The default value is -1: no logs are discarded. For example, if you want one log out of every five to be dropped, change the value to 5.-1
Rate limitThe maximum number of events per second that this data input processes.-1
Default timezoneThe default time zone of events. The system uses this default when the log does not specify a time zone.GMT
Drop if queue is fullOption to discard logs if many processes are waiting in the queue to access the MID Server.Clear

Parent Topic:Integration configuration fields