GCP Load Balancer pattern-based discovery

  • Release version: Xanadu
  • Updated January 12, 2026
  • 4 minutes to read
    • Summarize
    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 discover Google Cloud Platform (GCP) load balancers within their cloud environments. It supports two patterns:

    Show full answer Show less
    • HTTP pattern: Discovers Layer 7 load balancers using HTTP/HTTPS protocols.
    • TCP-UDP pattern: Discovers Layer 4 load balancers using TCP and UDP protocols.

    Both patterns populate ServiceNow CMDB tables with detailed load balancer information, facilitating accurate infrastructure mapping and management.

    To use these patterns effectively, customers should verify GCP discovery prerequisites as outlined in the Google Cloud Platform (GCP) Cloud components discovery documentation and consider updating to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Key Features

    • Data Collection: Discovery populates multiple CMDB tables including Cloud Service Account, Availability Zone, Google Datacenter, Cloud Load Balancer, Load Balancer Service, Load Balancer Pool, Load Balancer Pool Member, and Cloud Load Balancer Health Service.
    • Detailed Attributes: Each table includes essential fields such as project and object IDs, status, protocols, ports, IP addresses, load balancing methods, operational status, health check configurations, and region information.
    • CI Relationships: The patterns create comprehensive relationships among Configuration Items (CIs) to represent hosting, containment, usage, and ownership. Examples include:
      • Google Datacenter hosts Cloud Service Account and Cloud Load Balancer.
      • Cloud Load Balancer hosts Load Balancer Services.
      • Load Balancer Services reference Load Balancer Pools and use Health Services (for HTTP pattern).
      • Load Balancer Pools own Pool Members (VM instances) and are used by Load Balancer Services (for both patterns).

    Practical Benefits

    By implementing this pattern-based discovery, ServiceNow customers gain:

    • Automated and accurate discovery of GCP load balancing infrastructure, supporting both application-layer and transport-layer load balancers.
    • Populated CMDB with granular configuration and operational data, supporting effective change management, impact analysis, and service mapping.
    • Visibility into health check configurations and operational status of load balancer components, enabling proactive monitoring and troubleshooting.
    • Clear CI relationships that enable comprehensive dependency mapping and better understanding of cloud infrastructure topology.

    Discovery and Service Mapping Patterns finds GCP Load Balancers 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.

    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

    Both patterns populate the same CMDB tables.

    Pattern-based discovery and mapping requirements

    Verify the GCP discovery prerequisites section in Google Cloud Platform (GCP) Cloud components discovery using Patterns.

    Data collected by Discovery during horizontal discovery

    Discovery populates the data in the CMDB when running the Load Balancer patterns.

    Table 1. Cloud Service Account [cmdb_ci_cloud_service_account]
    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 2. Availability Zone [cmdb_ci_availability_zone]
    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 3. Google Datacenter [cmdb_ci_google_datacenter]
    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 4. Cloud Load Balancer [cmdb_ci_cloud_load_balancer]
    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 5. Load Balancer Service [cmdb_ci_lb_service]
    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 6. Load Balancer Pool [cmdb_ci_lb_pool]
    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 7. Load Balancer Pool Member [cmdb_ci_lb_pool_member]
    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
    Table 8. Cloud Load Balancer Health Service [cmdb_ci_lb_health_service]
    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.

    CI relationships

    Both Load Balancer patterns create these relationships to support GCP Load Balancer discovery.

    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]

    The Google Cloud Platform (GCP) - Load Balancer - HTTP pattern creates relationships to support GCP Load Balancer discovery.

    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]

    The Google Cloud Platform (GCP) - Load Balancer - TCP - UDP pattern creates relationships to support GCP Load Balancer discovery.

    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]