Alert Settings for On-premises DNS
When your self-hosted DNS generates an alert event, the system sends alert notifications to the specified recipients based on your alert settings and the configured alert level. To prevent alert notification failures caused by network interruptions between your local environment and the cloud console, alert notifications are sent by the local management agent service of the self-hosted DNS software after you configure alerts.
Procedure
Switch to the On-premises DNS tab.
Configure alert notifications.
Alert Level: The supported alert levels include Severity, Advanced and Above, Intermediate and Above, and All Levels.
Repeat Interval: Set the repeat notification interval for alerts.
Configure alert methods.
You can select Email, SMS Notification, Webhook Notification, or Syslog Notification.
SMS alert notifications are not supported on the international site.
Alert categories and levels
System resource alerts
Alert Name | Alert Level | Alert Description |
CPU usage exceeds 60% | Warning | The overall CPU usage of the system exceeds 60%, which may affect system performance. Monitor the CPU load. |
Single-core CPU utilization exceeds 80% | Warning | A single CPU core utilization is too high, indicating a potential single-thread performance bottleneck or load imbalance. |
Memory usage exceeds 80% | Warning | System memory usage exceeds 80%, which may cause slow system response or insufficient memory. |
Disk I/O utilization exceeds 60% | Warning | Disk read/write operations are intensive with high I/O utilization, which may affect overall system performance. |
Disk usage exceeds 80% | Warning | Disk space usage is too high. Clean up storage or expand capacity to prevent system failures caused by a full disk. |
Disk in read-only mode | Critical | The disk has entered read-only mode, usually caused by hardware failure, file system error, or full disk. Requires immediate attention. |
DNS resolution service alerts
Alert Name | Alert Level | Alert Description |
Abnormal DNS resolution traffic | Critical | DNS resolution request traffic shows abnormal fluctuations, possibly caused by attacks, failures, or configuration issues. Current threshold: over 80,000 QPS on a single node. |
Increased DNS resolution service latency | Warning | DNS resolution response time is increasing, which may affect user experience. Check service performance and network status. Current threshold: 100ms. |
Decreased DNS resolution service success rate | Warning | DNS resolution success rate is declining, with some requests failing, which may affect normal business operations. Current threshold: 70%. |
DNS resolution service QPS sudden spike | Critical | DNS resolution service QPS suddenly increases significantly, possibly caused by traffic attacks or sudden business growth. Current threshold: 50% increase within 5 minutes. |
DNS resolution service QPS sudden drop | Critical | DNS resolution service QPS suddenly decreases significantly, possibly caused by service failure or traffic anomaly. Current threshold: 50% decrease within 5 minutes. |
DNS resolution data distribution delay | Critical | DNS resolution data distribution is delayed, affecting data synchronization and service consistency. Current threshold: data fails to remain consistent for 5 consecutive minutes. |
Network connectivity alerts
Alert Name | Alert Level | Alert Description |
Ping service detects network connectivity anomaly | Critical | Network connectivity check fails. The target host or service is unreachable, possibly due to network failure or service outage. |
Ping service detects network latency anomaly | Warning | Network latency check detects an anomaly. Excessive network response time may affect service performance. Current threshold: 300ms. |
System service alerts
Alert Name | Alert Level | Alert Description |
Container monitoring data anomaly | Critical | Container monitoring data shows an anomaly, possibly caused by container runtime issues or monitoring system failure. |
Syslog write failure | Warning | System log write fails, which may cause log loss and affect troubleshooting and auditing. |
Alert notification service push failure | Warning | The alert notification system fails to push notifications, which may prevent important alerts from reaching relevant personnel in time. |
Agent proxy alerts
Alert Name | Alert Level | Alert Description |
Agent message forwarding failure | Warning | The local agent proxy fails to forward messages, which may affect data transmission and inter-system communication. Current threshold: 1 consecutive minute. |
Agent message forwarding failure (critical) | Critical | Critical-level alert for local agent proxy message forwarding failure. Requires immediate action to prevent data loss. Current threshold: 5 consecutive minutes. |
Management alerts
Alert Name | Alert Level | Alert Description |
Non-managed node connecting to proxy risk | Critical | An unmanaged node is connecting to the cloud proxy service, posing a risk of abnormal data delivery. Requires immediate attention. |
Managed node not connected to proxy | Critical | A managed node that should be connected to the cloud proxy has lost its connection, possibly affecting management functions and data transmission. |