New Relic integrations with the Google Cloud Platform (GCP) include one that reports Google Compute Engine data to New Relic. This document explains how to activate the GCP Compute Engine integration and describes the data it reports.
Features
Compute Engine is Google Cloud's core infrastructure-as-a-service for virtual machines and attached disks. New Relic Compute Engine integration reports your VM instances and persistent disks as entities, with firewall and reserved-core metrics for each VM instance and disk metrics for each persistent disk.
Activate integration
To enable the integration, follow standard procedures to connect your GCP service to New Relic:
중요
To see host metrics for your VM instances, such as CPU utilization, memory, network traffic, and uptime, install the infrastructure agent or the OpenTelemetry Collector on each VM. The Compute Engine integration doesn't collect these metrics from GCP Cloud Monitoring. If you can't install an agent on your VMs, contact New Relic support.
Workload Identity Federation
Find and use data
After you enable the integration, your Compute Engine resources appear as entities in the New Relic entity explorer. To see dashboards and manage services, go to one.newrelic.com > All capabilities > Infrastructure > GCP.
Compute Engine metrics from GCP Cloud Monitoring are collected as dimensional metrics in the Metric event type. VM instances report only the metrics listed in Key metrics — VM Instance. For all other resource types, including VM disks, additional metrics beyond these tables are collected automatically. See Google's Compute Engine metrics documentation for the complete list.
Entities
Metric data
Key metrics — VM Instance
Metric name | Unit | Description |
|---|---|---|
| Bytes | Incoming bytes dropped by the firewall. |
| Count | Incoming packets dropped by the firewall. |
| Count | Number of vCPUs reserved on the host of the VM instance. |
Key metrics — VM Disk
Metric name | Unit | Description |
|---|---|---|
| Bytes | Disk bytes read from the persistent disk. |
| Bytes | Disk bytes written to the persistent disk. |
| Count | Number of disk read operations on the persistent disk. |
| Count | Number of disk write operations on the persistent disk. |
| Count | Read operations throttled by disk quota. |
| Count | Write operations throttled by disk quota. |
| Bytes | Maximum disk read bytes observed on the persistent disk. |
| Bytes | Maximum disk write bytes observed on the persistent disk. |
Key metrics — Interconnect
Metric name | Unit | Description |
|---|---|---|
| Bytes/s | Total network capacity of the Interconnect circuit. |
| Bytes | Ingress bytes received over the Interconnect circuit. |
| Bytes | Egress bytes sent over the Interconnect circuit. |
| Count | Ingress packets received over the Interconnect circuit. |
| Count | Egress packets sent over the Interconnect circuit. |
| Count | Operational status of Interconnect physical links. |
Key metrics — Interconnect Attachment
Metric name | Unit | Description |
|---|---|---|
| Bytes/s | Total network capacity of the VLAN attachment. |
| Bytes | Ingress bytes received on the VLAN attachment. |
| Bytes | Egress bytes sent on the VLAN attachment. |
| Count | Ingress packets received on the VLAN attachment. |
| Count | Egress packets sent on the VLAN attachment. |
For the complete list of Compute Engine and Interconnect metrics, see Google's Compute Engine metrics documentation.
Key metrics — Service Attachment
Metric name | Unit | Description |
|---|---|---|
| Count | Count of TCP/UDP connections closed over a PSC Service Attachment resource ID. |
| Count | Number of Consumer Forwarding Rules connected to a PSC Service Attachment resource ID. |
| Count | Count of received packets dropped by a PSC Service Attachment resource ID. |
| Count | Count of sent packets dropped by a PSC Service Attachment resource ID. |
| Count | Number of total IP addresses of a PSC Service Attachment resource ID. (Value -1 means the number is larger than the max value of INT64.). |
| Count | Count of new TCP/UDP connections created over a PSC Service Attachment resource ID. |
| Count | Number of TCP/UDP connections currently open on a PSC Service Attachment resource ID. |
| Bytes | Count of bytes received (PSC -> Service) over a PSC Service Attachment resource ID. |
| Count | Count of packets received (PSC -> Service) over a PSC Service Attachment resource ID. |
| Bytes | Count of bytes sent (Service -> PSC) over a PSC Service Attachment resource ID. |
| Count | Count of packets sent (Service -> PSC) over a PSC Service Attachment resource ID. |
| Count | IP usage of the monitored service attachment. |
Key metrics — Private Service Connect Endpoint
Metric name | Unit | Description |
|---|---|---|
| Count | Count of TCP/UDP connections closed over a PSC connection ID. |
| Count | Count of received packets dropped by a PSC connection ID. |
| Count | Count of sent packets dropped by a PSC connection ID. |
| Count | Count of new TCP/UDP connections created over a PSC connection ID. |
| Count | Number of TCP/UDP connections currently open on a PSC connection ID. |
| Bytes | Count of bytes received (PSC -> Clients) over a PSC connection ID. |
| Count | Count of packets received (PSC -> Clients) over a PSC connection ID. |
| Bytes | Count of bytes sent (Clients -> PSC) over a PSC connection ID. |
| Count | Count of packets sent (Clients -> PSC) over a PSC connection ID. |
For the complete list of Private Service Connect metrics, see Google's monitoring documentation for Private Service Connect connections.
Metrics-only resource types
New Relic also collects metrics for the following Compute Engine resource types. These resource types don't create entities in the entity explorer, so query their metrics directly on the Metric event type.
Service account or user account
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
Metric data that New Relic receives from your GCP Compute Engine integration include:
GcpVirtualMachineSample
Name | Description |
|---|---|
| Delta count of incoming bytes dropped by the firewall. |
| Delta count of incoming packets dropped by the firewall. |
| Total number of cores reserved on the host of the instance. |
GcpVirtualMachineDiskSample
Name | Description |
|---|---|
| Delta count of bytes in throttled read operations. |
| Delta count of throttled read operations. |
| Delta count of bytes in throttled write operations. |
| Delta count of throttled write operations. |