This page explains how to add the primary instance of a Google AlloyDB cluster to Redgate Monitor. Host and instance metrics, along with error logs and query execution plans, are collected through the Google Cloud APIs using the service account key you provide below - on Google AlloyDB there is no separate host monitoring step to enable.

1. Go to Configuration → Monitored servers → Add → PostgreSQL
    
   
   

2. Select Google AlloyDB as the environment.

3. In the Endpoint name field, enter the IP address or hostname of the AlloyDB cluster's primary instance. You can find this on the cluster's Connectivity page in the Google Cloud console, with the primary instance selected. Use the private IP address if the Base Monitor connects over a VPC, or the public IP address otherwise.

   
4. Enter the port in the Port field. This is typically the default of 5432 for PostgreSQL.
5. Under Google Cloud credentials, provide a Google Cloud Service Account JSON key. Select Upload file to choose the downloaded key file, or Paste key to paste its contents directly.

   1. This service account is used to detect the AlloyDB cluster and primary instance, collect its host metrics, and read its error logs from Google Cloud Logging. 

   2. Grant the service account the roles/alloydb.viewer , roles/monitoring.viewer  and roles/logging.viewer  roles on the project containing the cluster, as described in Preparing PostgreSQL for monitoring.
6. Under PostgreSQL credentials, enter the username and password of the monitoring user. You should use the Monitor user you created when following the Preparing PostgreSQL for monitoring guide (redgatemonitor by default).
7. Optionally, enter the "Login database" if you are not using the same database name as your username (redgatemonitor by default).
8. You can select a group where the instance will be added, select "Uncategorized" if you don't want to put it in any particular group.
9. Click Test to verify the endpoint, credentials and service account key, then Add the instance.