Database Autonomy Service (DAS) supports 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 service.
Alerts supported by different access methods
Alert | Direct access | Centralized-mode access | Host-mode access |
---|---|---|---|
Host alerts (CPU, memory, and network) | Not supported | Not supported | Supported |
Database connection failure | Not supported | Supported | Supported |
Active sessions of ApsaraDB RDS for MySQL instances | Supported | Supported | Supported |
Connections of ApsaraDB RDS for MySQL instances | Supported | Supported | Supported |
Replication delay of ApsaraDB RDS for MySQL instances | Not supported | Supported | Supported |
Cache hit rate of ApsaraDB RDS for MySQL instances | Supported | Supported | Supported |
Slow SQL queries of ApsaraDB RDS for MySQL instances per hour | Supported | Supported | Supported |
Replication interruption of ApsaraDB RDS for MySQL instances | Not supported | Supported | Supported |
Connected ApsaraDB for Redis clients | Supported | Supported | Supported |
Blocked ApsaraDB for Redis clients | Supported | Supported | Supported |
Cache hit rate of ApsaraDB for Redis instances | Supported | Supported | Supported |
Memory fragmentation rate of ApsaraDB for Redis instances | Supported | Supported | Supported |
Connections of ApsaraDB for MongoDB instances | Supported | Supported | Supported |
Cache usage of ApsaraDB for MongoDB instances | Supported | Supported | Supported |
Current operations to be performed on ApsaraDB for MongoDB instances | Supported | Supported | Supported |
Dirty data percentage in cache of ApsaraDB for MongoDB instances | Supported | Supported | Supported |
Slow SQL queries of ApsaraDB for MongoDB instances per hour | Not supported | Supported | Supported |