Docs

RDS for MySQL

Monitoring and alerts

Creating alert policies

RDS for MySQL is integrated with Cloud monitor (VCM) for managing alarm rules through Cloud monitor (VCM).

Precautions

When creating an alarm policy with multiple trigger conditions configured, you need to select the logical relationship between conditions (All or Any), which determines how alarms are triggered:

All: Indicates that the system will trigger an alarm only when all configured conditions are satisfied simultaneously.

Any: Indicates that the system will trigger an alarm as long as any one of the configured conditions is satisfied.

Procedure

Log on to the RDS for MySQL console.

In the upper-left corner of the top menu bar, select the project and region for the instance.

tip

If the project of the instance has not been set, the project should be selected as All resources.

Click on Instances in the left navigation bar.

On the Instances page, click on the target instance name.

Click on the Monitoring tab at the top of the page.

Click Create alarm rule to open the creating alarm strategy page in Cloud monitor (VCM).

tip

When configuring alarm objects on the creating alarm strategy page, select RDS for MySQL as the resource type. For more information, refer to Creating alarm strategy.

Resource monitoring, deployment monitoring, and rngine monitoring support creating alarm policies at the Node level, while proxy monitoring supports creating alarm strategies at the instance level. If your instance does not support creating node-level alarm strategies for resource monitoring, deployment monitoring, and engine monitoring, submit a ticket to upgrade your instance version.

To simplify the operation process, you can also apply a preset alert template. For Details about the preset alarm templates for RDS for MySQL, refer to List of preset alarm templates. For more information, refer to Creating alarm strategy.