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 collects CPU, memory, disk, network, and uptime metrics for each VM instance and its persistent disks.
Activate integration
To enable the integration, follow standard procedures to connect your GCP service to New Relic:
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.
All Compute Engine metrics available in GCP Cloud Monitoring are collected as dimensional metrics in the Metric event type. Additional metrics beyond this table 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 |
|---|---|---|
| Percent | Fraction of allocated CPU currently in use by the VM instance. |
| Seconds | CPU-seconds consumed by the VM instance. |
| Bytes | Memory currently in use by the VM instance. |
| Bytes | Disk bytes read by the VM instance. |
| Bytes | Disk bytes written by the VM instance. |
| Bytes | Network bytes received by the VM instance. |
| Bytes | Network bytes sent by the VM instance. |
| Seconds | Uptime of the VM instance since it last started. |
Key metrics — VM Disk
Metric name | Unit | Description |
|---|---|---|
| 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.
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. |