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 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 ApsaraDB RDS for MySQL instances Supported
Connections of ApsaraDB RDS for MySQL instances Supported
Replication delay of ApsaraDB RDS for MySQL instances Supported
Cache hit rate of ApsaraDB RDS for MySQL instances Supported
Slow SQL queries on ApsaraDB RDS for MySQL instances per hour Supported
Storage space usage of ApsaraDB RDS for MySQL instances Supported
Storage space usage of ApsaraDB RDS for MySQL instance logs Supported
Connected ApsaraDB for Redis clients Supported
Blocked ApsaraDB for Redis clients Supported
Cache hit rate of ApsaraDB for Redis instances Supported
Memory fragmentation rate of ApsaraDB for Redis instances Supported
Number of connections of ApsaraDB for MongoDB instances Supported
Cache usage of ApsaraDB for MongoDB instances Supported
Number of operations to be performed on ApsaraDB for MongoDB instances Supported
Dirty data percentage in cache of ApsaraDB for MongoDB instances Supported
Slow SQL queries of MongoDB instances per hour Supported
CPU usage of Graph Database instances Supported
I/O usage of Graph Database instances Supported
Disk space that is used by Graph Database instances and measured in bytes Supported
Replication delay of Graph Database instances Supported
Average execution time of Graph Database transactions Supported
Success rate of executions of Graph Database transactions Supported
Disk usage of Graph Database instances Supported
Queries per second (QPS) of Graph Database instances Supported
Transactions per second (TPS) of Graph Database instances Supported
IOPS usage of ApsaraDB RDS for PostgreSQL instances Supported
iNode usage of ApsaraDB RDS for PostgreSQL instances Supported
Space usage of ApsaraDB RDS for PostgreSQL instances Supported
TPS of ApsaraDB RDS for PostgreSQL instances Supported
Connection usage of ApsaraDB RDS for PostgreSQL instances Supported
Average number of active connections per CPU for ApsaraDB RDS for PostgreSQL instances Supported
Point in time at which data bloat occurs in ApsaraDB RDS for PostgreSQL instances Supported
CPU usage of ApsaraDB RDS for PostgreSQL instances Supported
Memory usage of ApsaraDB RDS for PostgreSQL instances Supported