--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # GCP PubSub # GCP PubSub integration configuration fields {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of GCP PubSub integration configuration fields This content details the configuration fields for setting up the Google Cloud Platform (GCP) Pub/Sub integration with ServiceNow Health Log Analytics. It guides customers on how to configure integration forms to ingest log data from GCP Pub/Sub topics into their ServiceNow instance, enabling centralized log analytics and monitoring. Show full answer Show less ## Integration Configuration Fields * **Integration Name:** A required unique identifier for the integration that also auto-updates the generic form name. * **Service Instance:** Required selection of the ServiceNow service instance to bind the log data. * **Execute on:** Choose whether to use a specific MID Server or a MID Server cluster to process logs. * **MID Server name:** When using a specific MID Server, select one with log ingestion enabled that supports basic authentication (mTLS MID Servers are excluded). Health Log Analytics auto-enables log ingestion if needed. Default max inputs per MID Server is 10 but can be modified. * **MID Server cluster:** When using a cluster, select a failover MID Server cluster where log ingestion must be enabled on each server. The system manages failover and capacity based on active and available MID Servers. * **Source:** Read-only field showing "PubSub" as the log data source. * **Description:** Optional field to add descriptive notes about the integration. ## Connection Setup Fields * **Project ID:** Required Google Cloud project identifier obtained from the Google Cloud homepage. * **Authentication method:** Required credential alias used by ServiceNow to authenticate with Google Cloud. Additional aliases can be managed and added. * **Topic name:** Required Google Cloud Pub/Sub topic to subscribe to for log data ingestion. * **Subscription name:** Optional subscription name for receiving logs; defaults to "ServiceNow-Subscription" if left blank. ## Advanced Settings * **Subscriber thread pool size:** Number of concurrent threads fetching logs from Pub/Sub; default is 1. * **Sub sample receive ratio:** Controls log sampling by specifying how many logs to group before receiving one; default is -1 (no sampling). * **Max length in bytes:** Maximum size of each log message; default is 32,766 bytes. * **Character encoding:** Read-only field set to UTF-8. * **Sub sample drop ratio:** Controls how many logs to discard within groups to reduce log volume; default is -1 (no dropping). * **Rate limit:** Maximum events processed per second; default is -1 (no limit). * **Default timezone:** Time zone applied to events lacking timezone info; default is GMT. * **Drop if queue is full:** Option to discard incoming logs if the MID Server queue is full, preventing backlog. ## Practical Implications for ServiceNow Customers By correctly configuring these fields, customers can enable reliable, scalable log ingestion from GCP Pub/Sub into ServiceNow Health Log Analytics. This setup ensures logs are processed efficiently with options for failover, sampling, and rate limiting, helping customers maintain performance and log data quality. Understanding these settings allows customers to tailor their integration to match their infrastructure capacity and monitoring needs. 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](https://www.servicenow.com/docs/a3aWGCEnzoRpOFA1C_z~8w "Set up an integration for receiving log messages that were published to a Google Cloud Platform (GCP) Pub/Sub topic and streaming them to your ServiceNow instance."). {#il-connector-hla-gcp-pubsub-fields__table_ptx_ylg_lgc__entry__2} | Field | Description | |-|-| | Integration Name | Unique 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 Instance | The service instance (formerly the application service) to which to bind the log data. This field is required. | | Execute on | Option 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. {#il-connector-hla-gcp-pubsub-fields__ul_xjl_yp5_r5b} 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. * 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. This is true even when that MID Server is down. {#il-connector-hla-gcp-pubsub-fields__ul_htt_wdq_dwb} For more information about MID Server clusters, see [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | Source | The source of the log data that the integration pulls to your ServiceNow instance: PubSub. This field is read-only. | | Description | Option to add a brief description of the integration to help identify it. | [Table 1. Provide details] {#il-connector-hla-gcp-pubsub-fields__table_ptx_ylg_lgc} {#il-connector-hla-gcp-pubsub-fields__table_fxz_2mg_lgc__entry__2} | Field | Description | |-|-| | Project ID | The 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 method | The 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 name | The 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 name | The 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. | [Table 2. Set up connection] {#il-connector-hla-gcp-pubsub-fields__table_fxz_2mg_lgc} {#il-connector-hla-gcp-pubsub-fields__table_j5p_f4g_lgc__entry__3} | Field | Description | Default value | |-|-|-| | Subscriber thread pool size | The number of concurrent threads that are downloading files from the Google Cloud Pub/Sub topic. | 1 | | Sub sample receive ratio | The 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 bytes | The maximum length of log messages, in bytes. | 32,766 | | Character encoding | The character encoding for this data input. This field is read-only. | UTF-8 | | Sub sample drop ratio | The 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 limit | The maximum number of events per second that this data input processes. | -1 | | Default timezone | The default time zone of events. The system uses this default when the log does not specify a time zone. | GMT | | Drop if queue is full | Option to discard logs if many processes are waiting in the queue to access the MID Server. | Clear | [Table 3. Advanced Settings] {#il-connector-hla-gcp-pubsub-fields__table_j5p_f4g_lgc}