---
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 SQL

# GCP Cloud SQL pattern-based discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 12, 2025
* 
* ![](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 Cloud SQL pattern-based discovery

The GCP Cloud SQL pattern-based discovery in ServiceNow enables automated identification and population of Google Cloud SQL instances and their databases into your Configuration Management Database (CMDB).
It uses the Google Cloud Platform (GCP) - Cloud SQL DB discovery pattern to gather detailed information about Cloud SQL instances, including hardware configurations, and establishes relationships among cloud resources.
Show full answer Show less  
This discovery requires the latest version of the Discovery and Service Mapping Patterns application and adherence to GCP discovery prerequisites. It supports efficient cloud resource management and accurate CMDB updates for your GCP environment.

## Key Features

* **Comprehensive discovery:** Detects Cloud SQL instances, databases, availability zones, datacenters, and related hardware types within your GCP account.
* **Hardware type management:** Discovered hardware types are stored in the Cloud Hardware Type \[cmdbcicloudhardwaretype\] table to prevent excessive record creation in the Compute Template table.
* **Detailed CI data population:** Multiple CMDB tables are populated with specific fields such as account/project IDs, availability zone states, datacenter names, database engine types, states, versions, and machine types.
* **CI relationships:** Automatically creates relevant relationships between Cloud SQL instances, databases, datacenters, availability zones, hardware types, and cloud service accounts to provide a connected and accurate CMDB topology.
* **Tag collection:** Collects resource tags from GCP and stores them in the Key Value \[cmdbkeyvalue\] table, linking them back to the corresponding Cloud SQL instances for enhanced metadata management.

## Practical Benefits for ServiceNow Customers

* Enables near real-time visibility into GCP Cloud SQL environments within your ServiceNow CMDB, supporting better cloud asset management and governance.
* Helps maintain an accurate and organized inventory of cloud databases and associated hardware, reducing manual data entry and errors.
* Supports service mapping and impact analysis by establishing clear and automated relationships between cloud resources.
* Improves compliance and reporting capabilities by capturing detailed configuration and tagging information.

## Implementation Considerations

To leverage this discovery pattern effectively, ensure that you:

* Have updated the Discovery and Service Mapping Patterns application to the latest version from the ServiceNow Store.
* Meet the GCP discovery prerequisites as outlined in the Google Cloud Platform (GCP) Cloud components discovery documentation.
* Enable the Cloud Hardware Type class extension to optimize hardware type data storage and avoid excessive records in the Compute Template table.  
Discovery and Service Mapping Patterns finds GCP Cloud SQL instances and their databases on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Discovery uses the Google Cloud Platform (GCP) - Cloud SQL DB pattern to discover hardware type configurations for Cloud SQL instances from your GCP account.

When using the Hardware Type \[cmdb_ci_compute_template\] table to store the hardware types, you may notice an unusually large number of records. To avoid this issue, you can store the discovered hardware types in the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. When enabled, Discovery populates the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. For more information, see [Enable the Cloud Hardware Type class extension](https://servicenow-prod.fluidtopics.net/KNU5OxYrIVSiFCfHbBF~6A "Enable the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table to store the predefined virtual machine (VM) hardware type records for Amazon AWS Cloud Microsoft Azure Cloud and Google Cloud Platform (GCP). This class extension helps prevent duplication of the VM hardware type records in the Hardware Type [cmdb_ci_compute_template] table, which improves performance for Discovery and related flows.").

## Pattern-based discovery and mapping requirements {#gcp-cloud-sql-db-pattern__section_rpj_fj2_bgc}

Verify the GCP discovery prerequisites section in [Google Cloud Platform (GCP) Cloud components discovery using Patterns](https://servicenow-prod.fluidtopics.net/M4N6KVOmfeA1DCboNawaBg "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.").

## Data collected by Discovery during horizontal discovery {#gcp-cloud-sql-db-pattern__section_ggp_ql2_bgc}

Discovery populates the data in the CMDB when running the Google Cloud Platform (GCP) - Cloud SQL DB pattern.  
{#gcp-cloud-sql-db-pattern__table_ps1_twd_wfc__entry__2}

| Field | Description |
|-|-|
| Account Id \[account_id\] | Name of the project used for the discovery. |
| Object ID \[object_id\] | Name of the project used for the discovery. |
| Datacenter Type \[datacenter_type\] | Datacenter type: Google Datacenter \[cmdb_ci_google_datacenter\]. |
[Table 1. Cloud Service Account \[cmdb_ci_cloud_service_account\]]

{#gcp-cloud-sql-db-pattern__table_ps1_twd_wfc} {#gcp-cloud-sql-db-pattern__table_mk4_2yd_wfc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the availability zone. |
| Description \[short_description\] | Description of the availability zone. |
| State \[state\] | State of the Availability Zone. Possible values are Available or Terminated. |
[Table 2. Availability Zone \[cmdb_ci_availability_zone\]]

{#gcp-cloud-sql-db-pattern__table_mk4_2yd_wfc} {#gcp-cloud-sql-db-pattern__table_vbd_1zd_wfc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Datacenter or region name. |
| Region \[region\] | Datacenter or region name. |
| Object ID \[object_id\] | Unique identifier allocated by GCP for this resource. |
| Description \[short_description\] | Datacenter or region description. |
[Table 3. Google Datacenter \[cmdb_ci_google_datacenter\]]

{#gcp-cloud-sql-db-pattern__table_vbd_1zd_wfc}  
{#gcp-cloud-sql-db-pattern__table_cloud_database__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The unique resource identifier URL for the Cloud SQL instance. |
| Name \[name\] | The name of the Cloud SQL instance. |
| Type \[type\] | The database engine type for the Cloud SQL instance. |
| State \[state\] | The state of the Cloud SQL instance. For example: Available or Terminated. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Version \[version\] | The database version. |
| Fully qualified domain name \[fqdn\] | The unique resource identifier URL for the Cloud SQL instance. |
[Table 4. Cloud DataBase \[cmdb_ci_cloud_database\]]

{#gcp-cloud-sql-db-pattern__table_cloud_database}  
{#gcp-cloud-sql-db-pattern__table_database__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The name of the database within the Cloud SQL instance. |
| Type \[type\] | The type of database. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
[Table 5. Database \[cmdb_ci_database\]]

{#gcp-cloud-sql-db-pattern__table_database}  
{#gcp-cloud-sql-db-pattern__table_hardware_type__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The machine type for the Cloud SQL instance. |
| Name \[name\] | The machine type for the Cloud SQL instance. |
| vCPUs \[vcpus\] | The number of virtual CPUs (vCPUs) for the Cloud SQL instance. |
| Provider \[provider\] | The cloud provider, which is GCP. This field is only populated in Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. |
[Table 6. Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\]]

{#gcp-cloud-sql-db-pattern__table_hardware_type}

## CI relationships {#gcp-cloud-sql-db-pattern__section_dc4_ghc_dgc}

The Google Cloud Platform (GCP) - Cloud SQL DB pattern creates these relationships to support GCP Cloud SQL DB discovery.  
{#gcp-cloud-sql-db-pattern__table_bkg_jhc_dgc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Google Datacenter \[cmdb_ci_google_datacenter\] | Contains::Contained by | Availability Zone \[cmdb_ci_availability_zone\] |
| Google Datacenter \[cmdb_ci_google_datacenter\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
| Cloud DataBase \[cmdb_ci_cloud_database\] | Contains::Contained by | Database \[cmdb_ci_database\] |
| Cloud DataBase \[cmdb_ci_cloud_database\] | Hosted on::Hosts | Google Datacenter \[cmdb_ci_google_datacenter\] |
| Cloud DataBase \[cmdb_ci_cloud_database\] | Provisioned From::Provisioned | Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
| Cloud DataBase \[cmdb_ci_cloud_database\] | Replicates to::Replicated by | Cloud DataBase \[cmdb_ci_cloud_database\] |
| Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] | Hosted on::Hosts | Google Datacenter \[cmdb_ci_google_datacenter\] |
| Key Value \[cmdb_key_value\] | References | Cloud DataBase \[cmdb_ci_cloud_database\] |
[ ]

{#gcp-cloud-sql-db-pattern__table_bkg_jhc_dgc}

## GCP Tag discovery {#gcp-cloud-sql-db-pattern__section_lyw_zhc_dgc}

The Google Cloud Platform (GCP) - Cloud SQL DB pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table.  
{#gcp-cloud-sql-db-pattern__table_ojy_vss_5hc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
| Configuration item \[configuration_item\] | References the Cloud DataBase \[cmdb_ci_cloud_database\] table. |
[Table 7. Key Value \[cmdb_key_value\]]

{#gcp-cloud-sql-db-pattern__table_ojy_vss_5hc}