Monitor the health of your clusters and instances

AlloyDB for PostgreSQL integrates critical cluster and instance health issues and their recommended resolutions from Database Center and displays this information in the Google Cloud console. You can use this information to monitor and improve the health of your AlloyDB for PostgreSQL clusters and instances.

Health issues have different priorities, and the most urgent issues—those marked as critical or high priority—are displayed in your AlloyDB cluster list so that you can do the following:

• Organize, prioritize, assign, and close AlloyDB cluster issues.
• Take action at an aggregate level.
• Prevent cluster problems.
• Use intelligent assistance to predict cluster issues before they occur.

You can view a list of all issues (critical, high, medium, and low) in your database fleet in Database Center. For more information, see View and filter health issues and recommendations .

Issue priority definitions

Health issues for AlloyDB are ranked by priority. Critical and high priority issues are displayed in the Health issuesdashboard on the Clustersoverview page in the AlloyDB console. Under the Resourcestable, you can view all issues of a cluster by clicking View issuesin the Issuescolumn.

Priority	Description
Critical	High risk, immediate service disruption, or a significant security vulnerability if the issue isn't resolved. Immediate action is required .
High	High risk, but less serious than Critical . Unresolved issues might lead to downtime, performance degradation, or data loss.
Medium	Configurations that aren't recommended or deviations from best practices that require investigation to prevent performance or manageability issues.
Low	Informational items that are useful but low risk.

Before you begin

To monitor AlloyDB health issues in the Google Cloud console, you must have the following (Identity and Access Management (IAM)) roles:

• AlloyDB Administrator( roles/alloydb.admin )
  • alloydb.instances.list
  • alloydb.clusters.get

• Monitoring Viewer( roles/monitoring.viewer )

  • monitoring.timeSeries.list Note: This role is required to view insight charts in the Clusterspage, but it isn't required to view Database Center health issues.

• Database Center Viewer( roles/databasecenter.viewer ) or Database Center Administrator( roles/databasecenter.admin )

  • databasecenter.databaseGroups.list
  • databasecenter.fleetHealthStats.list

Monitor AlloyDB cluster health

The AlloyDB Clusterspage in the Google Cloud includes a Health issuessection, which displays the most critical cluster issues across your project.

View critical and high-priority issues

1. In the Google Cloud console, go to the Clusterspage.

   Go to Clusters

2. Review the Health issuesdashboard displayed on the page.

   This dashboard displays the aggregate count of critical and high priority issues affecting resources in your project. For more information about health issues, see Database health issues .

3. To view a summary of all issues affecting the resource, find the resource in the list of Resources. Click View issuesin the Issuescolumn.

   This opens the Aggregated issuesside panel. For more information, see View and filter database fleet health information .

Filter the cluster list by issue

The Issuescolumn in the AlloyDB cluster list displays the number of active issues affecting that cluster or any of its primary and read pool instances.

• To see which issues affect a specific cluster, click View issuesin the Issuescolumn for the resource.

  This opens the Aggregated issuespanel.

• To view the list of resources affected by a specific issue type, click the issue name card in the Health issuesdashboard.

  This action automatically filters the cluster list to display only the affected resources.

View and resolve issues for a specific instance

You can view a summarized list of health issues on the Overviewpage for any AlloyDB primary or read pool instance.

1. In the Google Cloud console, go to the Clusterspage.

   Go to Clusters

2. Click the name of a cluster.

3. Click the name of a primary or read pool instance to open the associated Overviewpage.

4. Find the Health issuesdashboard. If none of the resources have issues, then this section isn't displayed.

   View health issues categorized by cluster or instance.

5. To resolve an issue, do one of the following:

   • Click Edit configurationto display the required setting on the instance's Editpage—for example, for database flags or storage settings.
   • Click Go to System insightsto validate the issue with performance metrics.

View all AlloyDB issues in Database Center

Database Center provides a list of issues across your database fleet, including all medium and low priority AlloyDB issues. With Database Center you can also view database fleet health recommendations and ask questions about database fleet health issues, including availability configuration, data protection, security, and industry compliance. For more information, see Database health issues .

To view all AlloyDB issues in Database Center, follow these steps:

1. In the Google Cloud console, go to the Database Centerpage.

   Go to Database Center

2. Click Health issuesin the left navigation menu.

3. Use the table to view all issues across your organization or project. You can filter the list by the following:

   • Priority
   • Product and version
   • Issue Category
   • Location
   • Labels
   • Tags
   • Issues
   • Implications

To download a report that you can use in external tracking systems like JIRA or internal dashboards, click Export CSV of issue details.

What's next

• Learn more about Database Center .
• Monitor AlloyDB instances .
• Learn best practices for improving AlloyDB performance and availability .