Help Center/ TaurusDB/ User Guide/ Metrics and Alarms/ Configuring TaurusDB Alarm Rules

Updated on 2025-08-25 GMT+08:00

View PDF

Configuring TaurusDB Alarm Rules

Scenarios

You can create alarm rules for an instance to configure the monitored objects and notification policies and then stay aware of the instance status.

The following parameters can be configured: alarm rule names, services, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

Constraints

A maximum of 50 alarm policies can be added to an alarm rule. If any one of these alarm policies is met, an alarm will be triggered.

Creating a Metric Alarm Rule

Log in to the management console.
Click in the upper left corner and select a region and project.
Click Service List. Under Management & Governance, click Cloud Eye.

Alternatively, go to the Cloud Eye console using any of the following methods:
- On the Instances page, locate a DB instance and click View Metrics in the Operation column.
- On the Instances page, click the instance name to go to the Basic Information page. In the upper right corner of the page, click and choose View Metric.
- In the Node List area of the Basic Information page, locate a node and click View Metrics in the Operation column.
In the navigation pane, choose Alarm Management > Alarm Rules. On the displayed page, click Create Alarm Rule in the upper right corner.

On the displayed page, set parameters as prompted.

Figure 1 Setting alarm rule parameters
Click to enlarge

**Table 1** Alarm rule parameters
Parameter	Description
Name	Name of the alarm rule. The system generates a random name, but you can change it if needed.
Description	Description of the alarm rule.
Alarm Type	Select Metric.
Cloud product	Select TaurusDB.
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 Use existing template. The existing templates already contain 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. An alarm is triggered when the metric configured for this alarm reaches the preset threshold in consecutive periods. 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.
Alarm Severity	The alarm severity can be Critical, Major, Minor, or Warning.

Figure 2 Setting alarm notification parameters
Click to enlarge

**Table 2** Alarm notification parameters
Parameter	Description
Alarm Notification	Whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
Notification Recipient	You can select a notification group or topic subscription as required.
Notification Group	Notification group the alarm notification is to be sent to.
Notification Object	Object the alarm notification is to be sent to. You can select the account contact or a topic. This parameter is only available if you select Topic subscription for Notification Recipient. 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	Time window during which Cloud Eye sends notifications. If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within this window.
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	Key-value pairs that you can use to easily categorize and search for cloud resources.

Click Create.

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

Log in to the management console.
Click in the upper left corner of the page. Under Management & Governance, click Cloud Eye.

Alternatively, go to the TaurusDB console. On the Instances page, click the instance name. In the navigation pane, choose Database Proxy. On the displayed page, locate a proxy instance and click View Metrics in the Operation column to go to the Cloud Eye console.
In the navigation pane, choose Cloud Service Monitoring.
Click Database Proxy Service DBPROXY.
On the Instances page, locate a proxy instance and choose More > Create Alarm Rule in the Operation column.

On the displayed page, set parameters as needed. For details, see Creating an Alarm Rule.

Set the alarm rule name and description.

Figure 3 Setting the alarm rule name and description
Click to enlarge

**Table 3** **Name** and **Description**
Parameter	Description
Name	Name of the alarm rule. The system generates a random name, but you can change it if needed. Example value: alarm-b6al
Description	(Optional) Supplementary information about the alarm rule.

Set alarm rule parameters.

Figure 4 Setting alarm rule parameters
Click to enlarge

**Table 4** Alarm rule parameters
Parameter	Description
Method	Select an associated template, use an existing template or create a custom template as required. Modifying the template will also modify its associated alarm rules. If you select Configure manually, you can configure Alarm Policy and Alarm Severity as required.
Template	Select the template to be used. You can select a default alarm template or create a custom template. For details about how to create a custom template, see Creating a Custom Template
Alarm Policy	Specifies the policy for triggering an alarm. A maximum of 50 alarm policies can be added to an alarm rule. If any one of these alarm policies is met, an alarm will be triggered.

Set alarm notification parameters.

Figure 5 Setting alarm notification parameters
Click to enlarge

**Table 5** Alarm notification parameters
Parameter	Description
Alarm Notification	Whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
Notification Recipient	You can select a notification group or topic subscription as required.
Notification Group	Notification group the alarm notification is to be sent to.
Notification Object	Object the alarm notification is to be sent to. You can select the account contact or a topic. This parameter is only available if you select Topic subscription for Notification Recipient. 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	Time window during which Cloud Eye sends notifications. If Notification Window is set to 08:00-20:00, Cloud Eye sends notifications only within this window.
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	Key-value pairs that you can use to easily categorize and search for cloud resources.