GCP Passthrough Network Load Balancers

Google Cloud Platform (GCP) Passthrough Network Load Balancers are Layer 4 regional, passthrough load balancers hat distribute traffic among backends in the same region as the load balancer.

Cisco Cloud Observability supports monitoring:

Internal Passthrough Network Load Balancer
External Passthrough Network 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 Passthrough Network 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 Passthrough Network Load Balancer. See Google Cloud 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
Network Throughput (By)	`l3/internal/egress_bytes_count` `l3/internal/ingress_bytes_count`	The number of bytes sent from the backend of the internal network load balancer to the client. For TCP flows, this metric counts the bytes on the application stream only.
Packets	`l3/internal/egress_packets_count` `l3/internal/ingress_packets_count`	The number of packets sent from the backend of the internal network load balancer to the client.
RTT Latency (ms)	`l3/internal/rtt_latencies`	A distribution of the round trip time latency, measured over TCP connections for the internal network load balancer.

Display Name	Source Metric Name	Description
Network Throughput (By)	`l3/external/egress_bytes_count` `l3/external/ingress_bytes_count`	The number of bytes sent from the backend of the external network load balancer to the client. For TCP flows, this metric counts the bytes on the application stream only.
Packets	`l3/external/egress_packets_count` `l3/external/ingress_packets_count`	The number of packets sent from the backend of the external network load balancer to the client.
RTT Latency (ms)	`l3/external/rtt_latencies`	A distribution of the round trip time latency, measured over TCP connections for the external network load balancer.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Passthrough Network 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.