The following table describes the metrics charts that can be viewed on the
AlloyDB System insights dashboard and in the Metrics Explorer.
The metric type strings must be prefixed with alloydb.googleapis.com/
. For example, alloydb.googleapis.com/Instance
.
Metrics are either available in BETA
or GA
Launch stages
. For more information about the launch stage of the metric, see AlloyDB metrics
.
database/postgresql/tuples
The number of live and dead rows in the instance. Only available for instances with the number of databases less than 50.
Query latency
-
database/postgresql/insights/aggregate/latencies -
node/database/postgresql/insights/aggregate/latencies
The aggregated P99 query latency distribution for each instance or node. Only available for instances with Query Insights enabled.
Database load
-
database/postgresql/insights/aggregate/execution_time -
node/database/postgresql/insights/aggregate/execution_time
instance/cpu/maximum_utilization
instance/cpu/average_utilization
Available memory
-
instance/memory/min_available_memory -
node/memory/available_memory
Beginning with PostgreSQL 17, the available memory metric more accurately reflects the available memory to AlloyDB by taking into consideration memory in the operating system page cache that is used but can't be freed. As a result, the available memory metric might be lower than metrics for AlloyDB clusters using PostgreSQL 16 and earlier.
cluster/storage/usage
Queries IO wait time
-
database/postgresql/insights/aggregate/io_time -
node/database/postgresql/insights/aggregate/io_time
instance/postgresql/backends_by_state
idle
, active
, idle_in_transaction
, idle_in_transaction_aborted
, disabled
, and fastpath_function_call
.Number of tuples written
-
instance/postgresql/written_tuples_count -
node/postgres/written_tuples_count
-
database/postgresql/
inserted_tuples_count_for_top_databases -
database/postgresql/
updated_tuples_count_for_top_databases -
database/postgresql/
deleted_tuples_count_for_top_databases
insert
, update
, or delete
.
Only available for instances with the number of databases less than 5000.postgresql/vacuum/oldest_transaction_age
postgresql/vacuum/
transaction_id_utilization
instance/postgresql/wait_time
instance/postgresql/wait_count
Temp data size used
-
instance/postgresql/temp_bytes_written_count -
node/postgres/temp_bytes_written_count
join
and sort
.
Only available for instances with the number of databases less than 5000.Temporary files used for writing data
-
instance/postgresql/temp_files_written_count -
node/postgres/temp_files_written_count
join
and sort
.Number of new connections added to the instance
-
instance/postgresql/new_connections_count -
node/postgres/new_connections_count
database/postgresql/statements_executed_count
Transaction count
-
instance/postgres/transaction_count -
node/postgres/transaction_count
Transaction count per database
-
database/postgresql/committed_transactions_for_top_databases -
database/postgresql/rolledback_transactions_for_top_databases -
node/database/postgresql/committed_transactions_for_top_databases -
node/database/postgresql/rolledback_transactions_for_top_databases
Blocks hit
-
instance/postgresql/blks_hit -
node/postgres/blks_hit
Blocks miss
-
instance/postgresql/blks_read -
node/postgres/blks_read
Block read count per database
-
database/postgresql/blks_read_for_top_databases -
database/postgresql/blks_hit_for_top_databases -
node/database/postgresql/blks_read_for_top_databases -
node/database/postgresql/blks_hit_for_top_databases
Deadlock count
-
instance/postgresql/deadlock_count -
node/postgres/deadlock_count
instance/postgres/replication/maximum_lag
instance/postgres/instances
Connections per database
-
database/postgresql/backends_for_top_databases -
node/database/postgresql/backends_for_top_databases
Number of connections per application
-
instance/postgresql/backends_for_top_applications -
node/postgres/backends_for_top_applications
Unknown
.Number of tuples deleted
-
instance/postgresql/deleted_tuples_count -
node/postgres/deleted_tuples_count
Number of tuples fetched
-
instance/postgresql/fetched_tuples_count -
node/postgres/fetched_tuples_count
Rows fetched vs rows returned per database
-
database/postgresql/fetched_tuples_count_for_top_databases -
database/postgresql/returned_tuples_count_for_top_databases -
node/database/postgresql/fetched_tuples_count_for_top_databases -
node/database/postgresql/returned_tuples_count_for_top_databases
Number of tuples inserted
-
instance/postgresql/inserted_tuples_count -
node/postgres/inserted_tuples_count
Number of tuples scanned
-
instance/postgresql/returned_tuples_count -
node/postgres/returned_tuples_count
Number of tuples updated
-
instance/postgresql/updated_tuples_count -
node/postgres/updated_tuples_count
Temp data size used per database
-
database/postgresql/temp_bytes_written_for_top_databases -
node/database/postgresql/temp_bytes_written_for_top_databases
Temp files used per database
-
database/postgresql/temp_files_written_for_top_databases -
node/database/postgresql/temp_files_written_for_top_databases
join
and sort
.New connection count per database
-
database/postgresql/new_connections_
for_top_databases -
node/database/postgresql/new_connections_for_top_databases
Deadlock count per database
-
database/postgresql/deadlock_count_for_top_databases -
node/database/postgresql/deadlock_count_for_top_databases
instance/postgres/replication/replicas
startup
, catchup
, streaming
, backup
, and stopping
.instance/postgres/ultrafastcache_hitrate
A zero value indicates either no workload being run or the traffic being served from the buffer cache or the storage layer.
node/postgres/ultrafastcache_hitrate
A zero value indicates either no workload being run or the traffic being served from the buffer cache or the storage layer.
node/cpu/usage_time
node/postgres/replay_lag
replay_lag
in pg_stat_replication
. This metric is sampled every 60 seconds. After sampling, data is not visible for up to 180 seconds.node/postgres/uptime
node/postgres/backends_by_state
idle
, active
, idle_in_transaction
, idle_in_transaction_aborted
, disabled
, and fastpath_function_call
.For information about these statuses, see the state text row in the pg_stat_activity documentation .
node/postgres/backends
node/postgres/wait_count
node/postgres/wait_time
Limit on connections per node
-
instance/postgres/connections_limit -
node/postgres/connections_limit
Additionally, the Cloud Logging metric, Log entries by severity
( logging.googleapis.com/log_entry_count
),
shows the total numbers of error and warning log entries per instance. These
are extracted from postgres.log
, which is the database log, and pgaudit.log
, which contains data access information.
For more information, see AlloyDB metrics .

