Instance Overview

The Overview page lets you get knowledge of the statuses and alarms of DB instances in real time.

Learning About RDS

If you are new to RDS, you can quickly learn about RDS concepts, common functions, APIs, and how to buy and get started with a DB instance by referring to RDS Progressive Knowledge.

To purchase an RDS for PostgreSQL instance, click Buy on the Overview page and select your desired version and specifications. For details, see Buying an RDS for PostgreSQL DB Instance.
Once the purchase is complete, you can check instances by status and alarms on the Overview page.

Figure 1 Overview

Viewing Instances by Status

After you select PostgreSQL for Relational Database Service in the upper part of the Overview page, the statuses of all RDS for PostgreSQL instances under your account are displayed.

Figure 2 Instances by Status

**Table 1** Status description
Item	Description	Operation	Solution
Total instances	Total number of DB instances and read replicas in all statuses.	Click Total instances to go to the instance list and view all instances.	-
Abnormal	Total number of instances in the Abnormal status.	Click Abnormal to go to the instance list and view abnormal instances.	Submit a service ticket.
Out of storage	Total number of instances in the Storage full status.	Click Out of storage to go to the instance list and view instances that are out of storage.	For details, see Troubleshooting High Storage Space Usage.
Frozen	Total number of instances in the Frozen status.	Click Frozen to go to the instance list and view frozen instances.	For details, see Resource Freezing, Release, Stopping, Deletion, and Unsubscription.
Pending reboot	Total number of instances in the Parameter change. Pending reboot status. NOTE: Modifications to some parameters require an instance reboot before they can be applied.	Click Pending reboot to go to the instance list and view instances waiting to be rebooted.	Reboot the instances.

Viewing Alarms

Based on the configuration of alarm rules, you can see active alarms of all RDS for PostgreSQL instances under your current account, including alarms in the Alarm (metric) and Triggered (event) states.

In the Alarms area, click Create Alarm Rule.
Figure 3 Create Alarm Rule
In the dialog box displayed on the right, toggle on the Enable All Recommended Alarm Rules switch. Once this function is enabled, it applies to all resources in the current region.
Figure 4 Enable All Recommended Alarm Rules

After the function is enabled, you can modify alarm policies and disable alarm rules.
If the recommended alarm rules do not meet your requirements, you can create custom ones. Click create alarm rules to create alarm rules to monitor metrics or events for your DB instance. For details, see Setting Alarm Rules.
Figure 5 Creating an alarm rule
To view alarm details, select a time window in the upper part of the Alarms area.
The time window can be Last 1 hour, Last 6 hours, Last 12 hours, Last day, Last week, or Last month.

Figure 6 Alarms

Instance alarm details are displayed from multiple dimensions. For details, see Table 2 and Table 3.

**Table 2** Alarms
Item	Description
Alarm Severity	Displays the number of alarms at each severity. The alarm severity can be critical, major, minor, or informational.
Top 5 Instances by Total Number of Alarms	Displays alarm statistics of the top 5 instances with the largest number of alarms. Hover over an instance to see the number of its alarms of each severity. You can view alarm details of a specific instance and alarm severity.

**Table 3** Alarm list
Item	Description
Alarm Severity	There are four severities: critical, major, minor, and informational. Above the alarm list, you can choose to view alarms of a specific severity or all severities.
Status	Alarm: A metric value has reached the preset alarm threshold, triggering an alarm for the resource, but the alarm has not been cleared. Triggered: An event configured in the alarm policy triggered an alarm.
Last Updated	The latest time when the alarm was triggered.
Alarm Type	The alarm type that the alarm rule applies to. Metric Event
Alarm Policy	The policy for triggering an alarm. If you set Alarm Type to Metric, the system triggers an alarm if the metric value hits the preset threshold in consecutive periods. For example, an alarm is triggered if the average CPU usage is 80% or higher for three consecutive 5-minute periods. For details about how to troubleshoot high CPU usage, see Troubleshooting High CPU Usage. For details about how to troubleshoot high memory usage, see Troubleshooting High Memory Usage. For details about how to troubleshoot full storage, see Troubleshooting High Storage Space Usage. If you set Alarm Type to Event, the event that triggers an alarm is an instant operation. For example, if an instance fails to be created, an alarm is triggered. For details about the supported events and handling suggestions, see Events Supported by Event Monitoring.
Alarm Rule	The name or ID of the alarm rule.
Instance Name	The name of the instance that triggers the alarm. You can select All or a specific instance from the drop-down list to view the alarm details. Refresh the page to display details of the latest triggered alarms in real time.
Operation	Click Metrics. In the dialog box displayed on the right, you can see the metric changes in the selected time window.