New Relic integrations with the Google Cloud Platform (GCP) include one that reports Google Cloud AlloyDB data to New Relic. This document explains how to activate the GCP AlloyDB integration and describes the data it reports.
Features
AlloyDB is a fully managed, PostgreSQL-compatible database service built for demanding transactional and analytical workloads. New Relic AlloyDB integration collects performance, availability, and resource utilization metrics across clusters, instances, databases, and instance nodes.
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 that varies by integration. The polling frequency for Google Cloud AlloyDB is 5 minutes. The resolution is 1 data point every minute.
Important
AlloyDB for PostgreSQL supports 1-minute polling intervals for WIF integrations in limited preview. To request access, contact New Relic support.
Workload Identity Federation
Find and use data
After you enable the integration, your AlloyDB 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 AlloyDB 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 AlloyDB metrics documentation for the complete list.
Entities
Metric data
Key metrics — Cluster
Metric name | Unit | Description |
|---|---|---|
| Bytes | Total AlloyDB storage across the entire cluster. |
| Microseconds | Timestamp of the last successful cluster backup. |
For the complete list of cluster metrics, see Google's AlloyDB metrics documentation.
Key metrics — Instance
Metric name | Unit | Description |
|---|---|---|
| Percent | Mean CPU utilization across all currently serving nodes of the instance, from 0 to 100. |
| Percent | Maximum CPU utilization across all currently serving nodes of the instance, from 0 to 100. |
| Count | Number of vCPUs allocated to each node in the instance. |
| Bytes | Minimum available memory across all currently serving nodes of the instance. |
| Count | Number of active and idle connections to the AlloyDB instance across serving nodes. |
| Count | Mean number of active and idle connections to the AlloyDB instance across serving nodes. |
| Count | Current limit on the number of connections per node of the AlloyDB instance. |
| Count | Number of committed transactions across all serving nodes of the instance. |
| Count | Number of rolled back transactions across all serving nodes of the instance. |
| Count | Number of committed and rolled back transactions across all serving nodes of the instance. |
| Count | Number of nodes in the instance, along with their status (up or down). |
| Milliseconds | Maximum replication time lag calculated across all serving read replicas of the instance. |
| Count | Number of read replicas connected to the primary instance. |
For the complete list of instance metrics, see Google's AlloyDB metrics documentation.
Key metrics — Database
Metric name | Unit | Description |
|---|---|---|
| Count | Number of client connections to the database. |
| Count | Number of committed transactions for top databases. |
| Microseconds | Accumulated query execution time since the last sample. Sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all processes involved in query execution. |
| Microseconds | Accumulated IO time since the last sample. |
| Microseconds | Query latency distribution. |
| Microseconds | Accumulated lock wait time since the last sample. |
| Count | Number of retrieved or affected rows since the last sample. |
| Count | Shared blocks (regular tables and indexed) accessed by statement execution. |
| Microseconds | Accumulated execution times per user per database per query. |
| Microseconds | Accumulated IO time per query since the last sample. |
| Microseconds | Per-query latency distribution. |
| Microseconds | Accumulated lock wait time per query since the last sample. |
| Count | Number of retrieved or affected rows per query since the last sample. |
| Count | Shared blocks accessed per query by statement execution. |
| Microseconds | Accumulated execution times per tag since the last sample. |
| Microseconds | Accumulated IO time per tag since the last sample. |
| Microseconds | Per-tag query latency distribution. |
| Microseconds | Accumulated lock wait time per tag since the last sample. |
| Count | Number of retrieved or affected rows per tag since the last sample. |
| Count | Shared blocks accessed per tag by statement execution. |
For the complete list of database metrics, see Google's AlloyDB metrics documentation.
Key metrics — Instance Node
Metric name | Unit | Description |
|---|---|---|
| Percent | CPU usage for the node. |
| Bytes | Available memory on the node. |
| Bytes | Network bytes received by the node. |
| Bytes | Network bytes sent by the node. |
| Count | Total connections per node. |
| Count | Number of connections to the node per connection state. |
| Count | Number of deadlocks on the node. |
| Milliseconds | Replication lag for the node derived from replay_lag value. |
| Count | Number of transactions on the node. |
| Count | Ultra Fast Cache hit rate per node. |
| Count | Node database availability. |
| Count | Total number of times processes waited for each wait event on the node. |
| Microseconds | Total wait time for each wait event on the node. |
For the complete list of instance node metrics, see Google's AlloyDB 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).
Data is attached to the following event types:
Entity | Event type | Provider |
|---|---|---|
Cluster |
|
|
Instance |
|
|
Database |
|
|
GcpAlloydbClusterSample
Query GcpAlloydbClusterSample events in New Relic to view data for the following attributes:
Attribute | Unit | Description |
|---|---|---|
| Bytes | The total AlloyDB storage in bytes across the entire cluster. |
GcpAlloydbInstanceSample
Query GcpAlloydbInstanceSample events in New Relic to view data for the following attributes:
Attribute | Unit | Description |
|---|---|---|
| Percent | Mean CPU utilization across all currently serving nodes of the instance from 0 to 100. |
| Percent | Maximum CPU utilization across all currently serving nodes of the instance from 0 to 100. |
| Count | The number of vCPUs allocated to each node in the instance. |
| Bytes | The minimum available memory across all currently serving nodes of the instance. |
| Count | The number of transactions that were rolled back across all serving nodes of the instance. |
| Count | The mean number of active and idle connections to AlloyDB across serving nodes of the instance. |
| Count | The number of committed transactions across all serving nodes of the instance. |
| Count | The current limit on the number of connections per node of the AlloyDB instance. |
| Count | The number of nodes in the instance, along with their status, which can be either up or down. |
| Milliseconds | The maximum replication time lag calculated across all serving read replicas of the instance. |
| Count | The number of read replicas connected to the primary instance. |
| Count | The number of active and idle connections to the AlloyDB instance across serving nodes of the instance. |
| Count | The number of committed and rolled back transactions across all serving nodes of the instance. |
GcpAlloydbDatabaseSample
Query GcpAlloydbDatabaseSample events in New Relic to view data for the following attributes:
Attribute | Unit | Description |
|---|---|---|
| Microseconds | Accumulated query execution time since the last sample. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution. |
| Microseconds | Accumulated IO time since the last sample. |
| Microseconds | Query latency distribution. |
| Microseconds | Accumulated lock wait time since the last sample. |
| Count | The number of retrieved or affected rows since the last sample. |
| Count | Shared blocks (regular tables and indexed) accessed by statement execution. |
| Microseconds | Accumulated execution times per user per database per query. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution. |
| Microseconds | Accumulated IO time since the last sample. |
| Microseconds | Query latency distribution. |
| Microseconds | Accumulated lock wait time since the last sample. |
| Count | The number of retrieved or affected rows since the last sample. |
| Count | Shared blocks (regular tables & indexed) accessed by statement execution. |
| Microseconds | Accumulated execution times since the last sample. This is the sum of CPU time, IO wait time, lock wait time, process context switch, and scheduling for all the processes involved in the query execution. |
| Microseconds | Accumulated IO time since the last sample. |
| Microseconds | Query latency distribution. |
| Microseconds | Accumulated lock wait time since the last sample. |
| Count | The number of retrieved or affected rows since the last sample. |
| Count | Shared blocks (regular tables & indexed) accessed by statement execution. |