--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # GCP cloud components # Google Cloud Platform (GCP) Cloud components discovery using Patterns {#ariaid-title1} * Release version: Yokohama * * Updated June 19, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Google Cloud Platform (GCP) Cloud components discovery using Patterns This feature leverages Discovery and Service Mapping Patterns to identify and map Google Cloud Platform (GCP) components during horizontal discovery within ServiceNow. It requires up-to-date applications and specific configurations to ensure comprehensive and accurate cloud resource discovery and integration into the CMDB. Show full answer Show less ## Prerequisites * **Application Versions:** Ensure Discovery and Service Mapping Patterns (≥1.8.0), CMDB CI Class Models (≥1.49.0), and Visibility Content (≥6.13.0) are current as of September 2023. * **MID Server Requirements:** Use a dedicated MID Server for cloud discovery with at least 16 cores, 8 GB RAM, and 4 GB JVM memory. The MID Server must have internet access and be properly configured according to ServiceNow guidelines. * **Google Cloud BigQuery and Bigtable:** Enable the property *snitompattern.googledbservicetablecollection* in MID Server properties to allow discovery of these services. * **User Roles:** Assign the Google Cloud Platform member the "Viewer" role in the GCP IAM console to permit necessary read access. ## Configuration Steps * **Google API Credentials:** Configure API credentials appropriately to enable cloud discovery operations. * **GCP Service Account:** Create a service account with required permissions for discovery activities. * **Cloud Logging Events:** Enable collection of cloud logging events via Google Cloud Logging to auto-update the CMDB based on native API events. * **CI Relationships:** Activate CI relationships related to tag-based discovery introduced in ServiceNow Store release 1.0.68 to incorporate discovered components into service instances. * **Discovery Schedule:** Configure a Discovery schedule in the Discovery Admin Workspace to automate GCP discovery. * **Optional Performance Improvement:** From version 1.30.2 onwards, populate Service Account and Logical Datacenter fields directly in cloud CIs to enhance query performance. ## Additional Resources * Download the Cloud Discovery patterns spreadsheet to understand required user permissions, pattern details, CI classes, and vendor documentation links. * Check quarterly for new patterns to keep discovery capabilities current. This comprehensive setup ensures ServiceNow customers can efficiently discover, map, and maintain GCP cloud components within their CMDB, enabling better visibility, service mapping, and operational insight into their cloud environments. Discovery and Service Mapping Patterns uses patterns to discover components of the Google Cloud Platform (GCP) deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Request apps on the Store {#gcp-cloud-discovery-patterns__section_y3k_3pl_rlb} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#gcp-cloud-discovery-patterns__inline-send-to-store} ## Prerequisites {#gcp-cloud-discovery-patterns__section_sym_vwb_tfc} Verify that the applications are up to date. : * Discovery and Service Mapping Patterns starting version 1.8.0 (September 2023) * CMDB CI Class Models starting version 1.49.0 (September 2023) * Visibility Content starting version 6.13.0 (September 2023) {#gcp-cloud-discovery-patterns__ul_aln_qlb_5yb} Verify the MID Server requirements : * Use a dedicated MID Server for cloud discovery. The MID Server must have 16 Cores, 8 GB with 4 GB Java Virtual Machine (JVM) memory allocation. For information on verifying MID Server specifications, see KB article [KB2156327](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2156327). * Deploy and connect the dedicated MID Server with internet access. * For more information on the MID Server configurations, see [Install and configure MID Servers to access cloud environments](https://servicenow-prod.fluidtopics.net/J5R6fEzDsXUAwkST18d7jg "Install and configure the MID Servers correctly to enable ITOM products to access to the cloud resources."). {#gcp-cloud-discovery-patterns__ul_xdh_b33_ydc} Verify Google Cloud BigQuery and Google Cloud Bigtable requirements : To discover Google Cloud BigQuery and Google Cloud Bigtable, navigate to AllDiscoveryMID ServerProperties and ensure that the sn_itom_pattern.google_dbservice_table_collection property is set to True. Verify user role settings : Set the user permission for the Google Cloud Platform member to Viewer: 1. In the Google Cloud Platform console, navigate to IAM. 2. Select the relevant member from the list and click the Edit icon. 3. In the Edit permissions window, select Viewer from the Role list. 4. Click Save. {#gcp-cloud-discovery-patterns__ol_w2h_ctl_b3b} Configure Google API Credentials : For more information, see [Configure the Google API credentials for Cloud Discovery](https://servicenow-prod.fluidtopics.net/jDr5WSecOCRZZ0pZXlVAUQ "Create Google API credentials to allow Cloud Discovery to access the data on your Google account securely."). Create a Google Cloud Platform service account : For more information, see [Create GCP service accounts](https://servicenow-prod.fluidtopics.net/aPouvBFAvaXojnj8qxYBkQ "Create Google Cloud Platform (GCP) service accounts on the ServiceNow AI Platform to access your GCP account during GCP discovery."). Enable collecting cloud logging events : The Google Cloud Platform patterns can collect cloud logging events generated by the native Google Cloud APIs. [Configure the Google Cloud Logging service to auto-update the CMDB](https://servicenow-prod.fluidtopics.net/MaVDYaoPNWQMPtPGWD6m2g "You can activate the Google Cloud Logging (formerly Stackdriver Logging) service to auto-update Configuration Management Database (CMDB) configuration items (CI) data whenever Google Cloud Connector or your Google account makes a life-cycle state or configuration change to a Google Cloud Platform (GCP) resource. As a result, the CI data in the CMDB is updated without having to wait for Discovery to run."). Activate the cloud-related CI relationships : To include discovered components into service instances, enable CI relationships used in tag-based discovery by Service Mapping. These CI relationships are available from the 1.0.68 release on the ServiceNow Store. For operational steps, see [Tag-based discovery configuration](https://servicenow-prod.fluidtopics.net/WMqYQ9cztLwkmoyPJWnmIw "You can refine the default configuration to control which CIs Service Mapping includes in application services during the tag-based discovery process."). Verify that a Discovery schedule is configured : For more information, see [Create a GCP Discovery schedule in Discovery Admin Workspace](https://servicenow-prod.fluidtopics.net/FbrkPQwIKzGpvW5OnXDNPA "Use the Discovery Admin Workspace dashboard to create a Google Cloud Platform (GCP) Discovery schedule."). (Optional) Populate Service Account and Logical Datacenter fields in cloud CIs : Starting with Discovery and Service Mapping Patterns version 1.30.2, you can improve query performance by populating Service Account and Logical Datacenter fields directly in cloud CIs. For more information, see [Improved query performance with direct field population in CI tables](https://servicenow-prod.fluidtopics.net/H_wfVmrRA2K_BT9VRkb6iQ "The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance."). ## Verify the REST API Permissions {#gcp-cloud-discovery-patterns__id_ysv_22b_f1c} Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#gcp-cloud-discovery-patterns__cloud-discovery-api-paragraph} *[\>]: and then