RDS for PostgreSQL Metric Alarm Configuration Recommendations

Creating a Metric Alarm Rule

1. Log in to the Cloud Eye console.
2. Click in the upper left corner and select a region.
3. In the navigation pane, choose Alarm Management > Alarm Rules.
4. Click Create Alarm Rule in the upper right corner.
5. On the displayed page, configure required parameters.
   Figure 1 Configuring alarm rule information
   

   Table 1 Alarm rule information

   Parameter	Description
   Name	Alarm rule name. The system generates a random name, which you can modify.
   Description	Description about the rule.
   Alarm Type	Select Metric.
   Cloud Product	Select Relational Database Service - PostgreSQL Instances.
   Resource Level	Cloud product is recommended.
   Monitoring Scope	All resources: An alarm will be triggered if any resource of the current cloud product meets the alarm policy. To exclude resources that do not require monitoring, click Select Resources to Exclude. Resource groups: An alarm will be triggered if any resource in the selected resource group meets the alarm policy. Specific resources: Click Select Specific Resources to select resources.
   Method	Associate template: After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly. You are advised to select an existing template. The existing template already contains three common alarm metrics: CPU usage, memory usage, and storage space usage. Configure manually: Configure alarm policies manually.
   Template	If you select Associate template for Method, you need to select a template. You can select a default alarm template or create a custom template.
   Alarm Policy	If you select Configure manually for Method, you need to configure alarm policies. Whether to trigger an alarm depends on whether the metric data in consecutive periods reaches the threshold. For example, Cloud Eye triggers an alarm every 5 minutes if the average CPU usage of the monitored object is 80% or more for three consecutive 5-minute periods. NOTE: A maximum of 50 alarm policies can be added to an alarm rule. If any one of these alarm policies is met, an alarm is triggered.
   Alarm Severity	The alarm severity can be Critical, Major, Minor, or Warning.

   Figure 2 Configuring alarm notification
   

   Table 2 Alarm notification

   Parameter	Description
   Alarm Notifications	Whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
   Notified By	You can select a notification group or topic subscription as required.
   Notification Group	Notification group the alarm notification is to be sent to.
   Recipient	Object the alarm notification is to be sent to. You can select the account contact or a topic. The account contact is the mobile phone number and email address of the registered account. A topic is used to publish messages and subscribe to notifications.
   Notification Window	Cloud Eye sends notifications only within the notification window specified in the alarm rule. If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
   Trigger Condition	Condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
   Enterprise Project	Enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can view and manage the alarm rule.
   Tag	A tag is a key–value pair. Tags identify cloud resources so that you can easily categorize and search for your resources.

6. Click Create. The alarm rule is created.

   For details about how to create alarm rules, see Creating an Alarm Rule in the Cloud Eye User Guide.

Metric Alarm Configuration Recommendations