The alerting feature of Database Autonomy Service (DAS) allows you to configure alert rules based on your business requirements and monitoring goals. You can monitor and manage your database instances in a more precise manner and troubleshoot issues at the earliest opportunity.
Create an alert rule
Log on to the DAS console.
In the left-side navigation pane, choose Alert Service > Alert Rules.
On the Alert Rules page, click Add Rule in the upper-right corner.
In the Add Rule dialog box, configure the parameters that are described in the following table and click OK.
Parameter
Description
Rule Name
The name of the alert rule.
Type
The type of the alert rule. Valid values: Event Alert and Threshold Alert.
Event Alert: You can select a specific event that triggers the alert rule.
Threshold Alert: You can select a metric and specify the threshold that triggers the alert rule.
Description
The conditions that trigger the alert rule. Alert metrics vary based on the Type parameter. For more information, see the Comparison of alert metrics supported by different access modes section of this topic.
Alert Interval
The interval at which the system sends alert notifications to you when the alert rule is triggered.
Effective Time
The period of time within which the alert rule takes effect.
Notification Method
The method that is used to send alert notifications. DAS can send alert notifications by text message, webhook, and email.
NoteWebhook supports DingTalk, WeCom, Lark, and Application Real-Time Monitoring Service (ARMS).
After the alert rule is created, you can configure alerting. For more information, see Configure alerting.
Manage an alert rule
Log on to the DAS console.
In the left-side navigation pane, choose Alert Service > Alert Rules.
On the Alert Rules page, manage the created alert rules.
Find the alert rule that you want to manage and click the buttons in the Actions column. You can perform the following operations:
Search: View the details and alert history of the alert rule.
Edit: Modify the alert rule. For more information about the parameters that you can configure for alert rules, see the Create an alert rule section of this topic.
Disable: Disable the alert rule.
Delete: Delete the alert rule.
ImportantAfter you modify, disable, or delete an alert rule, all alert templates that contain the alert rule are affected. Proceed with caution.
Comparison of alert metrics supported by different access modes
If you connect Alibaba Cloud database instances or self-managed databases to DAS, the access mode falls into the category of centralized-mode access.
Metric | Number of alert occurrences |
Database Disconnected | 1, 3, 5, 7, or 10 times consecutively |
Replication Interruption of MySQL Instance | 1, 3, 5, 7, or 10 times consecutively |
Event-triggered alert rules are supported for only self-managed MySQL instances.
Metric | Threshold unit | Centralized-mode access | Host-mode access | Number of alert occurrences |
Host CPU Utilization | % | Not supported | Supported | 1, 3, 5, 7, or 10 times consecutively |
Host LOAD_1min | N/A | Not supported | ||
Host Memory Usage | % | Not supported | ||
Sent Bandwidth Usage by Host Network | % | Not supported | ||
Received Bandwidth Usage by Host Network | % | Not supported | ||
Disk Usage of Host Root Partition | % | Not supported | ||
Active Sessions of MySQL Instance | N/A | Supported | ||
Connections of MySQL Instance | N/A | Supported | ||
Replication Delay of MySQL Instance | s | Supported Note Only self-managed MySQL instances are supported. | ||
Cache Hit Rate of MySQL Instance | % | Supported | ||
Slow SQL Statements of MySQL Instance per Hour | N/A | Supported | ||
MySQL Data Storage Space Usage | % | Supported | ||
MySQL Log Storage Space Usage | % | Supported | ||
Connected Redis Clients | N/A | Supported | ||
Cache Hit Ratio of Redis | % | Supported | ||
Memory Fragmentation Rate of Redis | % | Supported | ||
MongoDB Instance Connections | N/A | Supported | ||
MongoDB Instance Cache Usage | % | Supported | ||
Current Operations to Be Performed on MongoDB Instance | N/A | Supported | ||
Dirty Ratio in Cache of MongoDB Instance | % | Supported | ||
PostgreSQL IOPS Usage | % | Supported | ||
PostgreSQL iNode Usage | % | Supported | ||
PostgreSQL Space Usage | % | Supported | ||
PostgreSQL TPS | N/A | Supported | ||
PostgreSQL Connection Usage | % | Supported | ||
Average Number of Active Connections per CPU for PostgreSQL | N/A | Supported | ||
PostgreSQL Longest Bloat Duration | N/A | Supported | ||
PostgreSQL CPU Utilization | % | Not supported | ||
PostgreSQL Memory Usage | % | Supported |