--- 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 data input configuration fields # GCP PubSub data input configuration fields {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 data input configuration fields This guide details the configuration fields for setting up a GCP PubSub data input in ServiceNow's Health Log Analytics, enabling customers to stream log data from Google Cloud Pub/Sub topics through MID Servers. Proper configuration ensures effective log ingestion and failover support within MID Server clusters. Show full answer Show less ## Basic Configuration * **Name:** Required field to name the new data input. * **Port:** Required unique port number for the MID Server. Ensure the organization's security team opens this port. * **Execute on:** Choose between a specific MID Server or a MID Server cluster for log streaming. * **MID Server:** When selecting a specific MID Server, only those with log ingestion capability and basic authentication are listed. Supports up to 10 concurrent data inputs by default, adjustable in MID Server properties. Log ingestion is auto-enabled if not already active. * **MID Server Cluster:** When selecting a cluster, only failover clusters are displayed. The data input runs on one MID Server and fails over to others as needed. Each MID Server must have log ingestion enabled, which is auto-enabled if necessary. Capacity validation requires at least one MID Server with fewer than 10 data inputs. * **Service instance:** Required to bind the log data. If none exists, create one and set its status to Operational. ## Read-Only Transport Information * **Transport:** Protocol used is PubSub. * **Sources count:** Number of log sources created by this input. * **Status:** Current status of the data input. * **Disabled since:** Timestamp when input stopped or failed. * **Last log time:** Timestamp of the last log received. ## Transport Tab Fields * **Project ID:** Google Cloud project identifier. * **Topic Name:** Google Cloud Pub/Sub topic subscribed to by Health Log Analytics. * **GCP Credential Alias:** Credential alias for authentication, selectable or creatable within ServiceNow. * **Subscription Name:** Pub/Sub subscription name used to receive logs; defaults to "ServiceNow-Subscription" if left blank. ## Advanced Configuration * **Subscriber Thread Pool Size:** Number of concurrent threads downloading files (default 1). * **Default timezone:** Time zone applied when logs lack time zone information (default GMT). * **Max length in bytes:** Maximum log message size (default 32,766 bytes). * **Character encoding:** Fixed to UTF-8. * **Sub sample drop ratio \& receive ratio:** Controls event sampling rates (default -1, meaning no sampling). * **Rate limit:** Max events per second processed (-1 indicates no limit). * **Drop if queue is full:** Option to discard logs when MID Server queue is overloaded. ## Practical Application for ServiceNow Customers By correctly configuring these fields, customers can efficiently stream and ingest Google Cloud Pub/Sub logs into ServiceNow. The configuration supports failover through MID Server clusters, ensuring continuous log collection. Adjusting thread pools, event rates, and queue handling allows tuning performance to meet organizational needs while maintaining security and operational reliability. Description of the fields on the GCP PubSub data input configuration form. ## Basic configuration {#hla-data-input-gcp-pubsub-ref__section_hng_2pc_lvb} {#hla-data-input-gcp-pubsub-ref__table_c5d_gpc_lvb__entry__2} | Field | Description | |-|-| | Name | Name of the new data input. This field is required. | | Port | The port for the MID Server. Select a unique port from the array. The placeholder shows the range of ports from which to choose. Make sure that your organization's security team opens the selected port. 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 | (Only when the Execute on field is set to Specific MID Server) The MID Server to which the logs are streamed. Note: * You can select only MID Servers with log ingestion capability that support basic authentication. MID Servers that support mTLS are not listed. * 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. * If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically. {#hla-data-input-gcp-pubsub-ref__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. {#hla-data-input-gcp-pubsub-ref__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). | | Service instance | The service instance to which to bind the log data. This field is required. Note: If no relevant service instance exists, [Create an service instance](https://www.servicenow.com/docs/access?context=create-it-services&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) and add CIs to it. Set the status of the new service instance to Operational. | [ ] {#hla-data-input-gcp-pubsub-ref__table_c5d_gpc_lvb} The fields in the following table show read-only information. {#hla-data-input-gcp-pubsub-ref__table_jl4_4pc_lvb__entry__2} | Field | Description | |-|-| | Transport | Protocol used to send the log data: PubSub. | | Sources count | The number of log sources this data input has created. | | Status | Status of the data input. | | Disabled since | The time when the data input stopped or failed. | | Last log time | The time when the last log streamed in the data input. | [ ] {#hla-data-input-gcp-pubsub-ref__table_jl4_4pc_lvb} {#hla-data-input-gcp-pubsub-ref__table_irj_gqc_lvb__entry__2} | Field | Description | |-|-| | Project ID | The project ID of the Google Cloud project. For example, my-project-id. | | Topic Name | The Google Cloud Pub/Sub topic to which to subscribe Health Log Analytics. For example, my_topic. | | GCP Credential Alias | The credential alias to be used. Select the magnifying glass icon to specify a GCP credential alias. Select an existing credential alias from the Connection \& Credential Aliases list, or select New to create a new record. The default is sn_occ.HLA_Credential_Alias. For information about creating a credential alias, see [Credential aliases for Discovery](https://www.servicenow.com/docs/access?context=discovery-credential-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US). | | 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 1. Transport tab] {#hla-data-input-gcp-pubsub-ref__table_irj_gqc_lvb} ## Advanced configuration {#hla-data-input-gcp-pubsub-ref__section_drt_z1b_pvb} {#hla-data-input-gcp-pubsub-ref__table_yyq_q1d_lvb__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 | | Default timezone | The default time zone of events. The system uses this default when the log does not specify a time zone. | GMT | | Max length in bytes | The maximum length of log messages, in bytes. | 32,766 | | Character encoding | (Read-only) The character encoding for this data input. | UTF-8 | | Sub sample drop ratio | The ratio of events to drop. | -1 | | Sub sample receive ratio | The ratio of events to receive. | -1 | | Rate limit | The maximum number of events per second that this data input processes. | -1 | | Drop if queue is full | Option to discard logs if many processes are waiting in the queue to access the MID Server. | Clear | [Table 2. Advanced tab] {#hla-data-input-gcp-pubsub-ref__table_yyq_q1d_lvb}