AlloyDB monitoring integration

We offer a cloud integration for reporting your GCP AlloyDB data to our platform.

Activate the integration

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

Configuration and polling

You can change the polling frequency and filter data using configuration options.

The default polling interval for the GCP AlloyDB integration in New Relic is 5 minutes.

Find and use data

To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > GCP and select the integration.

Data is attached to the following event types:

Entity	Event Type	Provider
Cluster	`GcpAlloydbClusterSample`	`GcpAlloydbCluster`
Database	`GcpAlloydbDatabaseSample`	`GcpAlloydbDatabase`
Instance	`GcpAlloydbInstanceSample`	`GcpAlloydbInstance`

For more on how to use your data, see Understand and use integration data.

Metric data

This integration collects GCP AlloyDB data for cluster, database, and instance.

Metric	Unit	Description
cluster.storage.Usage	Bytes	The total AlloyDB storage in bytes across the entire cluster.

Metric	Unit	Description
database.postgresql.insights.aggregate.ExecutionTime	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.
database.postgresql.insights.aggregate.IoTime	Microseconds	Accumulated IO time since the last sample.
database.postgresql.insights.aggregate.Latencies	Microseconds	Query latency distribution.
database.postgresql.insights.aggregate.LockTime	Microseconds	Accumulated lock wait time since the last sample.
database.postgresql.insights.aggregate.Row	Count	The number of retrieved or affected rows since the last sample.
database.postgresql.insights.aggregate.SharedBlkAccess	Count	Shared blocks (regular tables and indexed) accessed by statement execution.
database.postgresql.insights.perquery.ExecutionTime	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.
database.postgresql.insights.perquery.IoTime	Microseconds	Accumulated IO time since the last sample.
database.postgresql.insights.perquery.Latencies	Microseconds	Query latency distribution.
database.postgresql.insights.perquery.LockTime	Microseconds	Accumulated lock wait time since the last sample.
database.postgresql.insights.perquery.Row	Count	The number of retrieved or affected rows since the last sample.
database.postgresql.insights.perquery.SharedBlkAccess	Count	Shared blocks (regular tables & indexed) accesssed by statement execution.
database.postgresql.insights.pertag.ExecutionTime	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.
database.postgresql.insights.pertag.IoTime	Microseconds	Accumulated IO time since the last sample.
database.postgresql.insights.pertag.Latencies	Microseconds	Query latency distribution.
database.postgresql.insights.pertag.LockTime	Microseconds	Accumulated lock wait time since the last sample.
database.postgresql.insights.pertag.Row	Count	The number of retrieved or affected rows since the last sample.
database.postgresql.insights.pertag.SharedBlkAccess	Count	Shared blocks (regular tables & indexed) accessed by statement execution.

Metric	Unit	Description
instance.cpu.AverageUtilization	Percent	Mean CPU utilization across all currently serving nodes of the instance from 0 to 100.
instance.cpu.MaximumUtilization	Percent	Maximum CPU utilization across all currently serving nodes of the instance from 0 to 100.
instance.cpu.Vcpus	Count	The number of vCPUs allocated to each node in the instance.
instance.memory.MinAvailableMemory	Bytes	The minimum available memory across all currently serving nodes of the instance. The available memory is an estimate of memory in bytes available for allocation on the VM including memory that is currently used, but can be potentially freed.
instance.postgres.Abort	Count	The number of transactions that were rolled back across all serving nodes of the instance.
instance.postgres.AverageConnections	Count	The mean number of active and idle connections to AlloyDB across serving nodes of the instance.
instance.postgres.Commit	Count	The number of committed transactions across all serving nodes of the instance.
instance.postgres.ConnectionsLimit	Count	The current limit on the number of connections per node of the AlloyDB instance.
instance.postgres.Instances	Count	The number of nodes in the instance, along with their status, which can be either up or down.
instance.postgres.replication.MaximumLag	Milliseconds	The maximum replication time lag calculated across all serving read replicas of the instance. The replication time lag is derived from the replay_lag value.
instance.postgres.replication.Replicas	Count	The number of read replicas connected to the primary instance.
instance.postgres.TotalConnections	Count	The number of active and idle connections to the AlloyDB instance across serving nodes of the instance.
instance.postgres.Transaction	Count	The number of committed and rolled back transactions across all serving nodes of the instance.

Activate the integration

Configuration and polling

Find and use data

Metric data

AlloyDB Cluster data

AlloyDB Database data

AlloyDB Instance data

AlloyDB monitoring integration

Activate the integration .css-21sua1{background:none;border:none;width:0;padding:0;}

Configuration and polling

Find and use data

Metric data

AlloyDB Database data

AlloyDB Instance data

Activate the integration