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 and alert settings, go to one.newrelic.com > All capabilities > 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, GcpHttpExternalRegionalLoadBalancerSample, GcpInternalHttpLoadBalancerSample, GcpTcpSslProxyLoadBalancerSample and GcpInternalLoadBalancerSample events and their related attributes.
GcpHttpLoadBalancerSample
Query GcpHttpLoadBalancerSample events in New Relic to view data for the following attributes:
Attribute | Description |
|---|---|
| Mean latency (in milliseconds) calculated from when the request was sent by the External HTTP/S load balancer proxy to the backend until the proxy received from the backend the last byte of response. |
| The number of bytes sent as requests from External HTTP/S load balancer to backends. |
| The number of requests served by backends of External HTTP/S load balancer. |
| The number of bytes sent as responses from backends (or cache) to External HTTP/S load balancer. |
| Mean of the Round-Trip Time (RTT) measured for each connection between client and proxy. |
| The number of bytes sent as requests from clients to External HTTP/S load balancer. |
| The number of requests served by External HTTP/S load balancer. |
| The number of bytes sent as responses from External HTTP/S load balancer to clients. |
| Mean of the latency (in milliseconds) calculated from when the request was received by the External HTTP/S load balancer proxy until the proxy got ACK from client on last response byte. |
GcpHttpExternalRegionalLoadBalancerSample
Query GcpHttpExternalRegionalLoadBalancerSample events in New Relic to view data for the following attributes:
Attribute | Description |
|---|---|
| Mean latency (in milliseconds) calculated from when the request was sent by the Regional External HTTP/S load balancer proxy to the backend until the proxy received from the backend the last byte of response. |
| The number of bytes sent as requests from Regional External HTTP/S load balancer to backends. |
| The number of requests served by backends of Regional External HTTP/S load balancer. |
| The number of bytes sent as responses from backends (or cache) to Regional External HTTP/S load balancer. |
| The number of bytes sent as requests from clients to Regional External HTTP/S load balancer. |
| The number of requests served by Regional External HTTP/S load balancer. |
| The number of bytes sent as responses from Regional External HTTP/S load balancer to clients. |
| Mean of the latency (in milliseconds) calculated from when the request was received by the Regional External HTTP/S load balancer proxy until the proxy got ACK from client on last response byte. |
GcpInternalHttpLoadBalancerSample
Query GcpInternalHttpLoadBalancerSample events in New Relic to view data for the following attributes:
Attribute | Description |
|---|---|
| Mean latency (in milliseconds) calculated from when the request was sent by the Internal Application Load Balancer proxy to the backend until the proxy received from the backend the last byte of response. |
| The number of bytes sent as requests from Internal HTTP/S load balancer to backends. |
| The number of requests served by backends of Internal HTTP/S load balancer. |
| The number of bytes sent as responses from backends (or cache) to Internal HTTP/S load balancer. |
| The number of bytes sent as requests from clients to Internal HTTP/S load balancer. |
| The number of requests served by Internal HTTP/S load balancer. |
| The number of bytes sent as responses from Internal HTTP/S load balancer to clients. |
| Mean of the latency (in milliseconds) calculated from when the request was received by the Internal Application Load Balancer 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 |
|---|---|
| Number of connections that were terminated over TCP/SSL proxy. |
| Number of bytes sent from VM to client using proxy. |
| Mean of the smoothed RTT (in milliseconds) measured by the proxy's TCP stack, each minute application layer bytes pass from proxy to client. |
| Number of bytes sent from client to VM using proxy. |
| Number of connections that were created over TCP/SSL proxy. |
| 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 |
|---|---|
| The number of bytes sent from Internal Load Balancing (ILB) backend to client (for TCP flows it only counts bytes on the application stream). |
| The number of packets sent from ILB backend to client. |
| The number of bytes sent from client to ILB backend (for TCP flows it only counts bytes on the application stream). |
| The number of packets sent from client to ILB backend. |
| Mean of the RTT (in milliseconds) measured over TCP connections for ILB flows. |