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

Updated on 2025-11-26 GMT+08:00

View PDF

Suggestions on Alarm Rules of GeminiDB Mongo API Metrics

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

This section describes recommended alarm rules of GeminiDB Mongo API.

**Table 1** Suggestions on alarm rules of GeminiDB Mongo API metrics
Metric ID	Metric Name	Dimension	Threshold (Raw Value) in Best Practices	Alarm Severity in Best Practices	Alarm Handling Suggestion
nosql001_cpu_usage	CPU Usage	Node	> 80% for 3 consecutive periods	Major	You are advised to add CPUs by following Changing Specifications of an Instance.
nosql002_mem_usage	Memory Usage	Node	> 90% for 3 consecutive periods	Major	You are advised to check the cause of high CPU usage by following How Do I Solve the High CPU Usage Issue? You are advised to add CPUs if the usage remains high by following Changing Specifications of an Instance. If the CPU usage remains high and workloads cannot be completely stopped, the specification change may fail. In this case, choose Service Tickets > Create Service Ticket to submit a service ticket and ask engineers to limit the number of connections. After the specifications are changed, change back the number of connections to the original value.
nosql005_disk_usage	Storage Space Usage	Node	> 80% for 3 consecutive periods	Major	You are advised to locate the cause of high storage usage. For details, see High Storage Usage. If the storage usage remains high, scale up storage space. For details, see Scaling Up Storage Space.
mongodb007_connections_usage	Percentage of Active Node Connections	Node	> 80% for 3 consecutive periods	Major	Check whether the connection pool is properly used. You are advised to check whether common parameters, such as timeout threshold, are properly set. For details, see Common Parameter Configuration on the Driver Side. Increase the maximum number of connections. For a replica set instance whose maximum number of connections is less than 16,000, you can increase the maximum number of connections by changing the instance class. For a cluster instance, you can increase the maximum number of connections by adding mongos nodes.