Google Cloud Load Balancing monitoring integration

New Relic's integrations with the Google Cloud Platform (GCP) include an integration to report Google Cloud Load Balancing data to New Relic. This document explains how to activate the GCP Cloud Load Balancing integration and describes the data that can be reported.

Features

Google Cloud Load Balancing is a software-based managed service for distributing traffic in a single or multiple region. It provides seamless, immediate autoscaling and supports the latest application delivery protocols.

Activate integration

To enable the integration follow standard procedures to connect your GCP service to New Relic.

Polling frequency

New Relic integrations query your GCP services according to a polling interval, which varies depending on the integration. The polling frequency for Google Cloud Load Balancer is five minutes. The resolution is 1 data point every minute.

Find and use data

After activating the integration and waiting a few minutes (based on the polling frequency), data will appear in the New Relic UI. To find and use your data, including links to your dashboards and alert settings, go to one.newrelic.com > Infrastructure > GCP > (select an integration).

Metric data

To view metric data for your GCP Load Balancing integration in New Relic, create NRQL queries for GcpHttpLoadBalancerSample, GcpTcpSslProxyLoadBalancerSample, and GcpInternalLoadBalancerSample events and their related attributes.

GcpHttpLoadBalancerSample

Query GcpHttpLoadBalancerSample events in New Relic to view data for the following attributes:

Attribute	Description
https.BackendLatencies	Mean latency (in milliseconds) calculated from when the request was sent by the proxy to the backend until the proxy received from the backend the last byte of response.
https.BackendRequestBytes	The number of bytes sent as requests from HTTP/S load balancer to backends.
https.BackendRequests	The number of requests served by backends of HTTP/S load balancer.
https.BackendResponseBytes	The number of bytes sent as responses from backends (or cache) to HTTP/S load balancer.
https.FrontendTcpRtt	Mean of the Round-Trip Time (RTT) measured for each connection between client and proxy.
https.RequestBytes	The number of bytes sent as requests from clients to HTTP/S load balancer.
https.Requests	The number of requests served by HTTP/S load balancer.
https.ResponseBytes	The number of bytes sent as responses from HTTP/S load balancer to clients.
https.TotalLatencies	Mean of the latency (in milliseconds) calculated from when the request was received by the proxy until the proxy got ACK from client on last response byte.

GcpTcpSslProxyLoadBalancerSample

Query GcpTcpSslProxyLoadBalancerSample events in New Relic to view data for the following attributes:

Attribute	Description
tcpSslProxy.ClosedConnections	Number of connections that were terminated over TCP/SSL proxy.
tcpSslProxy.EgressBytes	Number of bytes sent from VM to client using proxy.
tcpSslProxy.FrontendTcpRtt	Mean of the smoothed RTT (in milliseconds) measured by the proxy's TCP stack, each minute application layer bytes pass from proxy to client.
tcpSslProxy.IngressBytes	Number of bytes sent from client to VM using proxy.
tcpSslProxy.NewConnections	Number of connections that were created over TCP/SSL proxy.
tcpSslProxy.OpenConnections	Current number of outstanding connections through the TCP/SSL proxy.

GcpInternalLoadBalancerSample

Query GcpInternalLoadBalancerSample events in New Relic to view data for the following attributes:

Attribute	Description
l3.internal.EgressBytes	The number of bytes sent from Internal Load Balancing (ILB) backend to client (for TCP flows it only counts bytes on the application stream).
l3.internal.EgressPackets	The number of packets sent from ILB backend to client.
l3.internal.IngressBytes	The number of bytes sent from client to ILB backend (for TCP flows it only counts bytes on the application stream).
l3.internal.IngressPackets	The number of packets sent from client to ILB backend.
l3.internal.RttLatencies	Mean of the RTT (in milliseconds) measured over TCP connections for ILB flows.

Inventory data

To view inventory data for GCP Load Balancing services, go to one.newrelic.com > Infrastructure > Inventory and search for or select the following:

gcp/loadbalancing/http-loadbalancer

This entity represents HTTP and HTTPS Load Balancers.

Name	Description
project	The project id and/or name.
zone	The zone or region of the entity.
name	The name of the entity.
urlMapName	The name of the urlmap. This is also used as the name of the load balancer.
forwardingRuleName	The name of the forwarding rule.
targetProxyName	The name of the target HTTP/S proxy.
matchedUrlPathRule	The prefix of the URL defined in urlmap tree. UNMATCHED is the sink default rule.
backendName	The name of the backend group. It can be a special value if the backend wasn't assigned.
backendType	The type of the backend group. It can be INSTANCE_GROUP, NETWORK_ENDPOINT_GROUP, or a special value if the backend wasn't assigned.
backendScope	The scope (zone-name or region-name) of the backend group. It can be a special value if the backend wasn't assigned, or be empty if there is no response from the backend.
backendScopeType	The type of the scope of the backend group. It can be ZONE, REGION, or another special value in case the backend wasn't assigned.
backendTargetName	The name of the backend target - service or bucket.
backendTargetType	The type of the backend target. It can be either BACKEND_SERVICE or BACKEND_BUCKET.

gcp/loadbalancing/tcp-ssl-proxy-loadbalancer

This entity represents SSL and TCP Proxy Load Balancers.

Name	Description
project	The project id and/or name.
zone	The zone or region of the entity.
name	The name of the entity.
backendName	The name of the backend group.
backendType	The type of the backend group. It can be INSTANCE_GROUP or NETWORK_ENDPOINT_GROUP.
backendScope	The scope (zone or region) of the backend group.
backendScopeType	The type of the scope of the backend group. It can be either ZONE or REGION.
backendTargetName	The name of the backend target (backend service, equivalent to proxy name).
backentTargetType	The type of the backend target. Currently it can only be BACKEND_SERVICE.
forwardingRuleName	The name of the forwarding rule.
targetProxyName	The name of the target TCP/SSL proxy.

gcp/loadbalancing/tcp-internal-loadbalancer

Name	Description
project	The project id and/or name.
zone	The zone or region of the entity.
name	The name of the entity.
networkName	The name of the virtual network.
loadBalancerName	The name of the load balancer.
backendName	The name of the backend group that handled the connection.
backendType	The type of the backend group that handled the connection. Currently it's INSTANCE_GROUP.
backendScope	The scope (zone or region) of the backend group that handled the connection.
backendScopeType	The type of the scope of the backend group that handled the connection. It can be either ZONE or REGION.
backendTargetName	The name of the backend target that handled the connection (equivalent to load_balancer_name).
backentTargetType	The type of the backend target that handled the connection. Currently it's BACKEND_SERVICE.
backendSubNetworkName	The name of the subnetwork of the backend.
forwardingRuleName	The name of the forwarding rule.
protocol	The load balancer protocol. It can be either TCP or UDP.

gcp/loadbalancing/udp-internal-loadbalancer

Name	Description
project	The project id and/or name.
zone	The zone or region of the entity.
name	The name of the entity.
networkName	The name of the virtual network.
loadBalancerName	The name of the load balancer.
backendName	The name of the backend group that handled the connection.
backendType	The type of the backend group that handled the connection. Currently it's INSTANCE_GROUP.
backendScope	The scope (zone or region) of the backend group that handled the connection.
backendScopeType	The type of the scope of the backend group that handled the connection. It can be either ZONE or REGION.
backendTargetName	The name of the backend target that handled the connection (equivalent to load_balancer_name).
backentTargetType	The type of the backend target that handled the connection. Currently it's BACKEND_SERVICE.
backendSubNetworkName	The name of the subnetwork of the backend.
forwardingRuleName	The name of the forwarding rule.
protocol	The load balancer protocol. It can be either TCP or UDP.

For more help