Huawei Cloud GaussDB SYS.GAUSSDBV5
¶
Huawei Cloud GaussDB SYS.GAUSSDBV5
provides data on CPU, memory, disk, deadlocks, SQL
response time metrics, and more.
Configuration¶
Install Func¶
It is recommended to activate the TrueWatch integration - extensions - hosted Func: all prerequisites are automatically installed, please proceed with the script installation.
For self-deploying Func, refer to Self-deploying Func
Install Script¶
Note: Please prepare the Huawei Cloud AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permissions
ReadOnlyAccess
)
-
Log in to the Func console, click on 【Script Market】, enter the TrueWatch script market, and search for
ID: integration_huaweicloud_gaussdb
-
Click 【Install】, then enter the corresponding parameters: Huawei Cloud AK, SK, and account name
-
Click 【Deploy Startup Script】, the system will automatically create the
Startup
script set and configure the corresponding startup script -
After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to immediately execute it once without waiting for the scheduled time. Wait a moment, and you can view the execution task records and corresponding logs
Verification¶
- In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has the automatic trigger configuration, and check the corresponding task records and logs for any exceptions
- In TrueWatch, check if asset information exists in 「Infrastructure / Custom」
- In TrueWatch, check if there is corresponding monitoring data in 「Metrics」
Metrics¶
After configuring GaussDB SYS.GAUSSDBV5
, the default measurement sets are as follows. More metrics can be collected through configuration Huawei Cloud Cloud Monitoring Metrics Details
Metric ID | Metric Name | Metric Description | Display Object | Metric Unit | Measurement Object |
---|---|---|---|---|---|
rds005_instance_disk_used_size | Instance Data Disk Used Size | This metric is used to count the used size of the instance data disk, which is a real-time value. | Instance | GB | Instance |
rds006_instance_disk_total_size | Instance Data Disk Total Size | This metric is used to count the total size of the instance data disk, which is a real-time value. | Instance | GB | Instance |
rds007_instance_disk_usage | Instance Data Disk Used Percentage | This metric is used to count the usage rate of the instance data disk, which is a real-time value. | Instance | % | Instance |
rds035_buffer_hit_ratio | Buffer Hit Rate | This metric is used to count the database buffer hit rate. | Instance | % | Instance |
rds036_deadlocks | Deadlock Count | This metric is used to count the number of transaction deadlocks in the database, taking the incremental value of this period. | Instance | Count | Instance |
rds048_P80 | 80% SQL Response Time | This metric is used to count the response time of 80% SQL in the database, which is a real-time value. | Instance | us | Instance |
rds049_P95 | 95% SQL Response Time | This metric is used to count the response time of 95% SQL in the database, which is a real-time value. | Instance | us | Instance |
rds001_cpu_util | CPU Utilization | This metric is used to count the CPU utilization of the measurement object. | Current Node | % | Node |
rds002_mem_util | Memory Utilization | This metric is used to count the memory utilization of the measurement object. | Current Node | % | Node |
rds003_bytes_in | Data Write Volume | This metric is used to count the network send bytes of the corresponding VM of the measurement object, taking the average value of the period | Current Node | Byte/s | Node |
rds004_bytes_out | Data Transfer Volume | This metric is used to count the network receive bytes of the corresponding VM of the measurement object, taking the average value of the period | Current Node | Byte/s | Node |
rds014_iops | Data Disk Read/Write Operations Per Second | This metric is used to count the read/write operations per second of the node data disk of the measurement object, which is a real-time value. | Current Node | Count/s | Node |
rds016_disk_write_throughput | Data Disk Write Throughput | This metric is used to count the write throughput per second of the node data disk of the measurement object, which is a real-time value. | Current Node | Byte/s | Node |
rds017_disk_read_throughput | Data Disk Read Throughput | This metric is used to count the read throughput per second of the node data disk of the measurement object, which is a real-time value. | Current Node | Byte/s | Node |
rds020_avg_disk_ms_per_write | Average Time Spent Per Data Disk Write | This metric is used to count the average time spent per write of the node data disk of the measurement object, taking the average value of the period. | Current Node | ms | Node |
rds021_avg_disk_ms_per_read | Average Time Spent Per Data Disk Read | This metric is used to count the average time spent per read of the node data disk of the measurement object, taking the average value of the period. | Current Node | ms | Node |
io_bandwidth_usage | Disk IO Bandwidth Utilization | The ratio of current disk IO bandwidth to the maximum disk bandwidth | Current Node | % | Node |
iops_usage | IOPS Utilization | The ratio of current IOPS to the maximum disk IOPS | Current Node | % | Node |
rds069_swap_total_size | Swap Memory Total Size | This metric is used to describe the total size of the operating system swap memory, which is a real-time value. | Current Node | MB | Node |
rds068_swap_used_ratio | Swap Memory Utilization | This metric is used to describe the utilization rate of the operating system swap memory, which is a real-time value. | Current Node | % | Node |
Objects¶
The collected GaussDB SYS.GAUSSDBV5
object data structure can be seen in 「Infrastructure - Custom」
{
"measurement": "huaweicloud_gaussdb",
"tags": {
"RegionId" : "cn-north-4",
"db_user_name" : "root",
"name" : "2e10f990e139xxxxxx5fac6b59de7eein07",
"port" : "3306",
"project_id" : "c631f046252d4xxxxxxx5f253c62d48585",
"status" : "BUILD",
"type" : "Cluster",
"instance_id" : "1236a915462940xxxxxx879882200in02",
"instance_name" : "xxxxx-efa7"
},
"fields": {
"charge_info" : "{Billing type information, supporting pay-as-you-go and subscription}",
"flavor_info" : "{Specification information}",
"volume" : "{Volume information}",
"create_time" : "2023-08-01T14:17:40+0800",
"update_time" : "2023-08-01T14:17:42+0800",
"public_ips" : "[\"192.168.0.223\"]",
"nodes" : "[]",
"message" : "{Instance JSON data}",
"time_zone" : "UTC+08:00"
}
}
Note: The fields in
tags
,fields
may change with subsequent updatesTip 1: The value of
tags.name
is the instance ID, used as a unique identifierTip 2:
fields.message
,fields.charge_info
,fields.flavor_info
,fields.volume
,fields.public_ips
,fields.nodes
are all JSON serialized strings
```