Which Monitoring Metrics of GaussDB Instances Do I Need to Pay Most Attention To?

For a GaussDB instance, you need to pay the most attention to the CPU, memory, and storage space (disk) usage.

You can configure the system to report alarms as needed and take measures to clear any reported alarms.

Configuration examples:

• Configure the system to report alarms to Cloud Eye if its average CPU usage reaches or exceeds a specific value (for example, 90%) multiple times (for example, 4 times) within a set period (for example, 5 minutes).
• Configure the system to report alarms to Cloud Eye if its average memory usage reaches or exceeds a specific value (for example, 90%) multiple times (for example, 3 times) within a set period (for example, 5 minutes).
• Configure the system to report alarms to Cloud Eye if its maximum storage usage reaches or exceeds a specific value (for example, 85%) multiple times (for example, 2 times) within a set period (for example, 5 minutes).

For details on Cloud Eye alarm configuration, see section "Creating an Alarm Rule" in the Cloud Eye User Guide.

Measures:

• If a CPU or memory alarm is reported, you can scale up the CPU or memory by changing the DB instance specifications.

  For details, see Changing CPU and Memory Specifications.

• If a storage space usage alarm is reported, you can scale up the storage space.

  For details, see Scaling Up Storage Space.