Database Autonomy Service (DAS) provides the alert 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 Alerts supported by different access methods.
    Alert Interval The interval at which alerts are sent when the alert rule is triggered.
    Effective Time The time range during which the alert rule takes effect.
    Notification Method Select the method to send alerts, such as SMS, DingTalk chatbot, or email.
  5. After the alert rule is created, you can perform subsequent alert configuration operations. For more information, see Configure alerts.

Alerts supported by different access methods

Table 1. Event alerts
Metric Number of alert occurrences
Database connection failure 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
Graph Database 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 alerts (CPU, memory, and network) Not supported Supported 1, 3, 5, 7, or 10 times in a row
Active sessions of MySQL instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Connections of MySQL instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Replication delay of MySQL instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Cache hit ratio of MySQL instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Slow SQL queries of MySQL instances per hour Supported Supported 1, 3, 5, 7, or 10 times in a row
Replication interruption of MySQL instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Connected Redis clients Supported Supported 1, 3, 5, 7, or 10 times in a row
Blocked Redis clients Supported Supported 1, 3, 5, 7, or 10 times in a row
Cache hit ratio of Redis instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Memory fragmentation rate of Redis instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Connections of MongoDB instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Cache usage of MongoDB instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Current operations to be performed on MongoDB instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Percentage of dirty data in the cache of MongoDB instances Supported Supported 1, 3, 5, 7, or 10 times in a row
Slow SQL queries of MongoDB instances per hour Supported Supported 1, 3, 5, 7, or 10 times in a row