GCP AlloyDB¶
Collect GCP AlloyDB metrics.
Configuration¶
Install Func¶
We recommend enabling TrueWatch Integration - Extensions - Managed Func. All prerequisites are installed automatically; continue with the script installation.
If you deploy Func yourself, see Self-deploying Func.
Install Script¶
- Log in to the Func console, click [Script Market], open the TrueWatch Script Market, and search for
integration_gcp_alloydb. - Click [Install], then enter the required parameters: account file name, Target Principal, and account name.
- Click [Deploy Startup Script]. The system automatically creates a
Startupscript set and configures the corresponding startup script. - After enabling it, find the automatic trigger configuration under "Management / Automatic Trigger Configuration". Click [Execute] to run it immediately, then review the task record and logs.
Verification¶
- Under "Management / Automatic Trigger Configuration", confirm that the task exists and check its task records and logs for errors.
- In TrueWatch, check "Infrastructure / Custom" for the corresponding asset information.
- In TrueWatch, check "Metrics" for the corresponding measurement and monitoring data.
Metrics¶
GCP AlloyDB metrics are stored in the gcp_alloydb measurement. The original metrics come from the Cloud Monitoring alloydb.googleapis.com/ namespace. The table below lists key metrics; see GCP AlloyDB metrics for the complete metric catalog.
| Metric | Original Metric | Description | Unit |
|---|---|---|---|
| cluster_last_backup_timestamp | cluster/last_backup_timestamp |
Cluster last backup timestamp | us |
| cluster_storage_usage | cluster/storage/usage |
Cluster storage usage | Bytes |
| database_postgresql_backends_for_top_databases | database/postgresql/backends_for_top_databases |
Database postgresql backends for top databases | Count |
| database_postgresql_blks_hit_for_top_databases | database/postgresql/blks_hit_for_top_databases |
Database postgresql blocks hit for top databases | Count |
| database_postgresql_blks_read_for_top_databases | database/postgresql/blks_read_for_top_databases |
Database postgresql blocks read for top databases | Count |
| database_postgresql_committed_transactions_for_top_databases | database/postgresql/committed_transactions_for_top_databases |
Database postgresql committed transactions for top databases | Count |
| database_postgresql_vacuum_oldest_transaction_age | database/postgresql/vacuum/oldest_transaction_age |
Database postgresql vacuum oldest transaction age | Count |
| database_postgresql_vacuum_transaction_id_utilization | database/postgresql/vacuum/transaction_id_utilization |
Database postgresql vacuum transaction id utilization | Ratio |
| instance_cpu_average_utilization | instance/cpu/average_utilization |
Instance cpu average utilization | % |
| instance_cpu_maximum_utilization | instance/cpu/maximum_utilization |
Instance cpu maximum utilization | % |
| instance_cpu_vcpus | instance/cpu/vcpus |
Instance cpu vcpus | Count |
| instance_memory_min_available_memory | instance/memory/min_available_memory |
Instance memory min available memory | Bytes |
| instance_postgres_abort_count | instance/postgres/abort_count |
Instance postgres abort count | Count |
| instance_postgres_average_connections | instance/postgres/average_connections |
Instance postgres average connections | Count |
| instance_postgres_commit_count | instance/postgres/commit_count |
Instance postgres commit count | Count |
| instance_postgres_connections_limit | instance/postgres/connections_limit |
Instance postgres connections limit | Count |
| instance_postgres_instances | instance/postgres/instances |
Instance postgres instances | Count |
| instance_postgres_replication_maximum_lag | instance/postgres/replication/maximum_lag |
Instance postgres replication maximum lag | ms |