GCP Application Load Balancers

Google Cloud Platform (GCP) Application Load Balancers are proxy-based Layer 7 load balancers that distribute HTTP and HTTPS traffic to backends hosted on a variety of Google Cloud platforms as well as external backends connected over the internet or by using hybrid connectivity.

Cisco Cloud Observability supports monitoring:

Internal Application Load Balancer
External Application Load Balancer
Global External Application Load Balancer

You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.

Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Detail View

To display the detail view of an Application Load Balancer instance:

Navigate to the Observe page.
Under Networking & App Delivery, click Load Balancers.
The Load Balancers list view now displays.
Click the GCP tab to display only GCP load balancers. You can use the Type column header to sort the list by the type of GCP load balancer.
From the list, click a load balancer Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Application Load Balancer. See Load balancing metrics.

Some GCP metrics have been modified in Cisco Cloud Observability. Metric display names and descriptions may differ from the source metric.

Display Name	Source Metric Name	Description
Total Latency (ms)	`https/internal/total_latencies`	A distribution of the latency. Latency is measured from the time the first byte of the request is received by the GFE until the GFE receives an ACK from the requesting client for the last response byte. Total latencies are measured by request/response. Pauses between requests on the same connection using `Connection: keep-alive` do not affect the measurement. This measurement is typically reduced to 95th percentile in Cloud Monitoring views.
Requests	`https/internal/request_count`	The number of requests served by the load balancer.
Network Throughput (By)	`https/internal/request_bytes_count` `https/internal/response_bytes_count`	The number of bytes sent as requests from clients to the load balancer.
Backend Latency (ms)	`https/internal/backend_latencies`	A distribution of the latency measured from when the first request byte was sent by the GFE to the backend, until the GFE received from the backend the last byte of the response.

Display Name	Source Metric Name	Description
Total Latency (ms)	`https/external/regional/total_latencies`	A distribution of the latency. Latency is measured from the time the first byte of the request is received by the GFE until the GFE receives an ACK from the requesting client for the last response byte. Total latencies are measured by request/response. Pauses between requests on the same connection using `Connection: keep-alive` do not affect the measurement. This measurement is typically reduced to 95th percentile in Cloud Monitoring views.
Requests	`https/external/regional/request_count`	The number of requests served by the load balancer.
Network Throughput (By)	`https/external/regional/request_bytes_count` `https/external/regional/response_bytes_count`	The number of bytes sent as requests from clients to the load balancer.
Backend Latency (ms)	`https/external/regional/backend_latencies`	A distribution of the latency measured from when the first request byte was sent by the GFE to the backend, until the GFE received from the backend the last byte of the response.

Display Name	Source Metric Name	Description
Total Latency (ms)	`https/total_latencies`	A distribution of the latency. Latency is measured from the time the first byte of the request is received by the GFE until the GFE receives an ACK from the requesting client for the last response byte. Total latencies are measured by request/response. Pauses between requests on the same connection using `Connection: keep-alive` do not affect the measurement. This measurement is typically reduced to 95th percentile in Cloud Monitoring views.
Requests	`https/request_count`	The number of requests served by the load balancer.
Network Throughput (By)	`https/request_bytes_count` `https/response_bytes_count`	The number of bytes sent as requests from clients to the load balancer.
Backend Latency (ms)	`https/backend_latencies`	A distribution of the latency measured from when the first request byte was sent by the GFE to the backend, until the GFE received from the backend the last byte of the response.
Backend Requests	`https/backend_request_count`	The number of requests sent from the external HTTP(S) load balancer to the backends.
Backend Network Throughout (By)	`https/backend_request_bytes_count` `https/backend_response_bytes_count`	The number of bytes sent as requests from the external HTTP(S) load balancer to the backends.
Frontend TCP RTT (ms)	`https/frontend_tcp_rtt`	A distribution of the smoothed round trip time (RTT) measured for each connection between the client and the GFE (measured by the GFE's TCP stack). Smoothed RTT is an algorithm that deals with variations and anomalies that may occur in RTT measurements.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Application Load Balancers.

Display Name	Source Property Name	Description
Region	`region`	The region under which the backend service is defined.
Provider	-	The `gcp` string, hardcoded.
Account ID	-	The ID of the GCP project.
Platform	-	The `gcp_load_balancer` string, hardcoded.
ID	-	The ID of the load balancer.
Name	-	The name of the load balancer.
Type	-	The type of the load balancer.

Retention and Purge Time-To-Live (TTL)

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.