---
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 Load Balancer

# GCP Load Balancer pattern-based discovery {#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 Load Balancer pattern-based discovery

The GCP Load Balancer pattern-based discovery enables ServiceNow customers to automatically discover Google Cloud Platform (GCP) Load Balancers in their cloud environments.
It supports both Layer 7 (HTTP/HTTPS) and Layer 4 (TCP/UDP) load balancers using dedicated Discovery patterns.
These patterns populate the Configuration Management Database (CMDB) with detailed information about load balancers, their services, pools, and related infrastructure components.
Show full answer Show less  
To ensure accurate discovery, customers should verify they meet the prerequisites outlined in the **Google Cloud Platform (GCP) Cloud discovery using Patterns** documentation and may need to update to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Key Features

* **Discovery Patterns:**
  * HTTP Pattern: Discovers Layer 7 load balancers using HTTP/HTTPS protocols.
  * TCP - UDP Pattern: Discovers Layer 4 load balancers using TCP/UDP protocols.
* **Comprehensive CMDB Population:** The patterns populate multiple CMDB tables capturing cloud service accounts, availability zones, datacenters, load balancers, load balancer services, pools, pool members, and health check services.
* **Detailed Attributes Captured:** Information such as unique object IDs, names, states, protocols, ports, IP addresses, load balancing methods, operational statuses, health check configurations, and more are gathered to provide a full discovery snapshot.
* **CI Relationships:** The patterns establish key relationships between Configuration Items (CIs) including hosting, containment, ownership, and usage relationships. This includes links between load balancers, services, pools, pool members, health services, datacenters, and cloud service accounts.

## What Customers Can Expect

* Automated discovery and mapping of GCP Load Balancers and their components within the ServiceNow CMDB.
* Accurate representation of GCP cloud infrastructure topology including regions, availability zones, and service configurations.
* Improved visibility into load balancing infrastructure to support IT operations, service management, and cloud governance.
* Enhanced ability to manage and troubleshoot GCP Load Balancer services with detailed health check and operational status data.
* Consistent and normalized data that integrates into broader ServiceNow discovery and service mapping workflows.  
Discovery and Service Mapping Patterns finds GCP Load Balancers on your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
The Discovery patterns discover GCP Load Balancing infrastructure:

* Google Cloud Platform (GCP) - Load Balancer - HTTP pattern: Discovers Layer 7 (application layer) load balancers that use HTTP and HTTPS protocols
* Google Cloud Platform (GCP) - Load Balancer - TCP - UDP pattern: Discovers Layer 4 (transport layer) load balancers that use TCP and UDP protocols
{#gcp-load-balancer-pattern__ul_lb_patterns}

Both patterns populate the same CMDB tables.

## Pattern-based discovery and mapping requirements {#gcp-load-balancer-pattern__section_rpj_fj2_bgc}

Verify the GCP discovery prerequisites section in [Google Cloud Platform (GCP) Cloud discovery using Patterns](https://www.servicenow.com/docs/hH4wPjzyLr0pmFmj6Ib5TA "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 might 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-load-balancer-pattern__section_ggp_ql2_bgc}

Discovery populates the data in the CMDB when running the Load Balancer patterns.  
{#gcp-load-balancer-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-load-balancer-pattern__table_ps1_twd_wfc} {#gcp-load-balancer-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-load-balancer-pattern__table_mk4_2yd_wfc} {#gcp-load-balancer-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-load-balancer-pattern__table_vbd_1zd_wfc}  
{#gcp-load-balancer-pattern__table_lb__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | Unique identifier for the load balancer. |
| Name \[name\] | Name of the load balancer. |
| State \[state\] | State of the load balancer. Default value is Available. |
[Table 4. Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\]]

{#gcp-load-balancer-pattern__table_lb}  
{#gcp-load-balancer-pattern__table_lb_service__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | Unique identifier for the load balancer service. |
| Name \[name\] | Name of the load balancer service. |
| Service Type \[service_type\] | Type of service. Possible values are Frontend or Backend. |
| Listener Protocol \[listener_protocol\] | Protocol used by the service listener. |
| Port \[port\] | Port number used by the service. |
| IP Address \[ip_address\] | IP address of the frontend service. |
| Pool \[pool\] | References the Load Balancer Pool \[cmdb_ci_lb_pool\] table. This field is populated only by the Google Cloud Platform (GCP) - Load Balancer - HTTP pattern. |
[Table 5. Load Balancer Service \[cmdb_ci_lb_service\]]

{#gcp-load-balancer-pattern__table_lb_service}  
{#gcp-load-balancer-pattern__table_lb_pool__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | Unique identifier for the load balancer pool. |
| Name \[name\] | Name of the load balancer pool. |
| Load balancing method \[load_balancing_method\] | Load balancing method used by the pool. This field is populated only by the Google Cloud Platform (GCP) - Load Balancer - TCP - UDP pattern. |
[Table 6. Load Balancer Pool \[cmdb_ci_lb_pool\]]

{#gcp-load-balancer-pattern__table_lb_pool}  
{#gcp-load-balancer-pattern__table_lb_pool_member__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | Unique identifier for the pool member, known as a VM instance ID in GCP. |
| Name \[name\] | Name of the pool member, known as a VM instance name in GCP. |
| Operational status \[operational_status\] | Operational status of the pool member. * Operational: Instance status is running * Non-Operational: Other instance states {#gcp-load-balancer-pattern__ul_vm5_vjd_yhc} |
[Table 7. Load Balancer Pool Member \[cmdb_ci_lb_pool_member\]]

{#gcp-load-balancer-pattern__table_lb_pool_member}  
{#gcp-load-balancer-pattern__table_lb_health__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | Unique identifier for the health check service. |
| Name \[name\] | Name of the health check service. |
| Monitor type protocol \[monitor_type\] | Type of health check monitor For example: HTTP or TCP. |
| Port \[port\] | Port number used for health checks. |
| Timeout in seconds \[timeout_sec\] | Timeout in seconds for health check requests. |
| Unhealthy threshold \[unhealthy_threshold\] | Number of consecutive failures before marking as unhealthy. |
| Healthy threshold \[healthy_threshold\] | Number of consecutive successes before marking as healthy. |
| Interval in seconds \[check_interval_sec\] | Interval in seconds between health checks. |
| Request path \[request_path\] | Request path for HTTP and HTTPS health checks. This field is populated only by the Google Cloud Platform (GCP) - Load Balancer - HTTP pattern. |
[Table 8. Cloud Load Balancer Health Service \[cmdb_ci_lb_health_service\]]

{#gcp-load-balancer-pattern__table_lb_health}

## CI relationships {#gcp-load-balancer-pattern__section_dc4_ghc_dgc}

Both Load Balancer patterns create these relationships to support GCP Load Balancer discovery.  
{#gcp-load-balancer-pattern__table_relationships__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Google Datacenter \[cmdb_ci_google_datacenter\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
| Google Datacenter \[cmdb_ci_google_datacenter\] | Contains::Contained by | Availability Zone \[cmdb_ci_availability_zone\] |
| Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
| Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Hosted on::Hosts | Google Datacenter \[cmdb_ci_google_datacenter\] |
| Load Balancer Service \[cmdb_ci_lb_service\] | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] |
| Load Balancer Pool \[cmdb_ci_lb_pool\] | Hosted on::Hosts | Google Datacenter \[cmdb_ci_google_datacenter\] |
| Load Balancer Pool \[cmdb_ci_lb_pool\] | Owns::Owned by | Load Balancer Pool Member \[cmdb_ci_lb_pool_member\] |
| Cloud Load Balancer Health Service \[cmdb_ci_lb_health_service\] | Hosted on::Hosts | Google Datacenter \[cmdb_ci_google_datacenter\] |
| Cloud Load Balancer Health Service \[cmdb_ci_lb_health_service\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
[ ]

{#gcp-load-balancer-pattern__table_relationships}

The Google Cloud Platform (GCP) - Load Balancer - HTTP pattern creates relationships to support GCP Load Balancer discovery.  
{#gcp-load-balancer-pattern__table_zs3_rhd_yhc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Load Balancer Service \[cmdb_ci_lb_service\] | Uses::Used by | Load Balancer Pool \[cmdb_ci_lb_pool\] |
| Load Balancer Service \[cmdb_ci_lb_service\] | References | Load Balancer Pool \[cmdb_ci_lb_pool\] |
| Cloud Load Balancer Health Service \[cmdb_ci_lb_health_service\] | Used by::Uses | Load Balancer Service \[cmdb_ci_lb_service\] |
[ ]

{#gcp-load-balancer-pattern__table_zs3_rhd_yhc}

The Google Cloud Platform (GCP) - Load Balancer - TCP - UDP pattern creates relationships to support GCP Load Balancer discovery.  
{#gcp-load-balancer-pattern__table_iyd_vhd_yhc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Uses::Used by | Load Balancer Pool \[cmdb_ci_lb_pool\] |
| Cloud Load Balancer Health Service \[cmdb_ci_lb_health_service\] | Used by::Uses | Load Balancer Pool \[cmdb_ci_lb_pool\] |
[ ]

{#gcp-load-balancer-pattern__table_iyd_vhd_yhc}