Database Autonomy Service (DAS) provides the alerting feature. You can customize alert rules and templates in the DAS console. When an alert rule is triggered by a database instance, DAS automatically sends an alert. This topic describes how to configure and manage alert rules in the DAS console before you configure the alert feature.

Procedure

  1. Log on to the DAS console.
  2. In the left-side navigation pane, choose Alert Service > Alert Rules.
  3. On the Alert Rules page, click Add Rule in the upper-right corner.
  4. In the Add Rule dialog box, configure the parameters described in the following table. Then, click OK.
    L
    Parameter Description
    Rule Name Enter a name for the alert rule.
    Type Select Event Alert or Threshold Alert.
    • Event Alert: You can specify trigger conditions for different metrics to send alert notifications.
    • Threshold Alert: You can customize the thresholds to send alert notifications based on different metrics.
    Description Specify the conditions that must be met to trigger the alert rule. Available metrics vary based on the specified Type parameter. For more information, see Comparison of alerts supported by different access methods.
    Alert Interval The interval at which the system sends alerts 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 alerts. DAS can send alerts by SMS, DingTalk chatbot, and email.
  5. After the alert rule is created, you can perform subsequent alert configuration operations. For more information, see Configure alerts.

Comparison of alerts supported by different access methods

Note When you connect Alibaba Cloud or self-managed database instances to DAS, the access mode falls into the category of centralized-mode access.
Table 1. Event alerts
Metric Number of alert occurrences
Database Disconnected 1, 3, 5, 7, or 10 times in a row
Replication Interruption of MySQL Instances 1, 3, 5, 7, or 10 times in a row
GraphDB Instance Switching 1, 3, 5, 7, or 10 times in a row
Table 2. Threshold alerts
Metric Centralized-mode access Host-mode access Number of alert occurrences
Host-related alerts (CPU utilization, memory usage, and bandwidth usage by host network) Not supported Supported 1, 3, 5, 7, or 10 times in a row
Active Sessions of MySQL Instance Supported
Connections of MySQL Instance Supported
Replication Delay of MySQL Instance Supported
Cache Hit Rate of MySQL Instance Supported
Slow SQL Statements of MySQL Instance per Hour Supported
MySQL Data Storage Space Usage Supported
MySQL Log Storage Space Usage Supported
Connected Redis Clients Supported
Blocked Redis Clients Supported
Cache Hit RatIO of Redis Supported
Memory Fragmentation Rate of Redis Supported
MongoDB Instance Connections Supported
MongoDB Instance Cache Usage Supported
Current Operations to Be Performed on MongoDB Instance Supported
Dirty Ratio in Cache of MongoDB Instance Supported
Slow SQL statements of MongoDB Instance per Hour Supported
GraphDB CPU Utilization Supported
GraphDB I/O Usage Supported
GraphDB Used Disk Space (Unit: Bytes) Supported
GraphDB Replication Latency Supported
Average Execution Time of GraphDB Transactions (Unit: seconds) Supported
Average Success Rate of GraphDB Transactions Supported
GraphDB Disk Usage Supported
GraphDB QPS Supported
GraphDB TPS Supported
PostgreSQL IOPS Usage Supported
PostgreSQL iNode Usage Supported
PostgreSQL Space Usage Supported
PostgreSQL TPS Supported
PostgreSQL Connection Usage Supported
Average Number of Active Connections per CPU for PostgreSQL Supported
PostgreSQL Longest Bloat Duration Supported
PostgreSQL CPU Utilization Supported
PostgreSQL Memory Usage Supported