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

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

View PDF

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

**Table 1** Suggestions on alarm rules of GeminiDB Influx instance metrics
Metric ID	Metric Name	Dimension	Threshold (Raw Value) in Best Practices	Alarm Severity in Best Practices	Alarm Handling Suggestion
gemini001_cpu_usage	CPU Usage	Node	> 90% for 3 consecutive periods	Major	Upgrade instance specifications. For details, see Changing vCPUs and Memory.
gemini002_mem_usage	Memory Usage	Node	> 80% for 3 consecutive periods	Major	Upgrade instance specifications. For details, see Changing vCPUs and Memory.
nosql005_disk_usage	Storage Space Usage	Instance	> 80% for 3 consecutive periods	Major	Evaluate how much storage needs to be added based on data growth. For details, see Manually Scaling Up Storage Space of a GeminiDB Influx Instance.
influxdb005_write_concurrency	Concurrent Write Requests	Node	≥ CPU cores x 4 for 3 consecutive periods	Major	Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.
influxdb006_query_concurrency	Concurrent Queries	Node	≥ CPU cores for 3 consecutive periods	Major	Check whether the service traffic increases sharply and whether the database is normal. For details, see Viewing Metrics.