Help Center/ GeminiDB/ GeminiDB Cassandra API/ Best Practices/ Suggestions on Alarm Rules of GeminiDB Cassandra Instance Metrics
Updated on 2025-07-02 GMT+08:00

Suggestions on Alarm Rules of GeminiDB Cassandra 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 Cassandra instances.

Table 1 Suggestions on alarm rules of GeminiDB Cassandra instance metrics

Metric ID

Metric Name

Dimension

Threshold (Raw Value) in Best Practices

Alarm Severity in Best Practices

Alarm Handling Suggestion

nosql005_disk_usage

Storage Space Usage

Instance

> 80% for 3 consecutive periods

Major

cassandra001_cpu_usage

CPU Usage

Node

> 80% for 3 consecutive periods

Major

Upgrade CPU specifications. For details, see Changing vCPUs and Memory.

cassandra002_mem_usage

Memory Usage

Node

> 80% for 3 consecutive periods

Major

Upgrade memory specifications. For details, see Changing vCPUs and Memory.

cassandra015_read_latency

Average Read Latency

Node

> 900 ms for 3 consecutive periods

Major

Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.

cassandra016_write_latency

Average Write Latency

Node

> 900 ms for 3 consecutive periods

Major

Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.

cassandra037_pending_write

Suspended Write Tasks

Node

> 3,000 for 3 consecutive periods

Major

Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.

cassandra038_pending_read

Suspended Read Tasks

Node

> 3,000 for 3 consecutive periods

Major

Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.