Help Center/ GeminiDB/ GeminiDB Redis API/ Best Practices/ Suggestions on Alarm Rules of GeminiDB Redis Instance Metrics

Updated on 2025-07-02 GMT+08:00

View PDF

Suggestions on Alarm Rules of GeminiDB Redis Instance Metrics

After setting alarm rules on the Cloud Eye console, for example, specifying monitored objects and notification policies, you can stay ahead of your instance status. For details, see Configuring Alarm Rules.

This section describes recommended alarm rules of GeminiDB Redis instances.

**Table 1** Suggestions on alarm rules of GeminiDB Redis instance metrics
Metric ID	Metric Name	Dimension	Threshold (Raw Value) in Best Practices	Alarm Severity in Best Practices	Alarm Handling Suggestion
redis688_qps_send_total	Total Traffic Sent by the Instance	Instance	≥ 875,000,000 bytes/s for 3 consecutive periods	Major	Comply with Development and O&M Rules.
redis689_qps_receive_total	Total Traffic Received by the Instance	Instance	≥ 875,000,000 bytes/s for 3 consecutive periods	Major	Comply with Development and O&M Rules.
redis803_cluster_all_avg_usec	Average Latency	Instance	≥ 50,000 μs for 5 consecutive periods	Major	Check whether the instance has performance bottlenecks in CPU, memory, or connections. If yes, resolve the bottlenecks based on the related suggestions. If service optimization cannot be performed, increase the instance specifications or use specifications with better disk performance. For details, see Changing vCPUs and Memory and Adding Instance Nodes.
redis804_cluster_all_p99_usec	P99 Latency	Instance	≥ 150,000 μs for 5 consecutive periods	Major	Check whether the instance has performance bottlenecks in CPU, memory, or connections. If yes, resolve the bottlenecks based on the related suggestions. If service optimization cannot be performed, increase the instance specifications or use specifications with better disk performance. For details, see Changing vCPUs and Memory and Adding Instance Nodes.
redis816_cluster_disk_usage	Storage Usage	Instance	≥ 80% for 3 consecutive periods	Major	Scale up the storage space. For details, see Manually Scaling Up Storage Space.
nosql001_cpu_usage	CPU Usage	Node	≥ 85% for 3 consecutive periods	Major	Upgrade instance specifications or add nodes to reduce the CPU load. For details, see Changing vCPUs and Memory and Adding Instance Nodes.
nosql002_mem_usage	Memory Usage	Node	≥ 85% for 3 consecutive periods	Major	Upgrade memory specifications. For details, see Changing vCPUs and Memory.
redis669_connection_usage	Connection Usage	Node	≥ 80% for 3 consecutive periods	Major	Comply with Development and O&M Rules.
gemini004_bytes_in	Network Input Throughput	Node	≥ 87,500,000 bytes/s for 3 consecutive periods	Major	Comply with Development and O&M Rules.
gemini003_bytes_out	Network Output Throughput	Node	≥ 87,500,000 bytes/s for 3 consecutive periods	Major	Comply with Development and O&M Rules.