Huawei Cloud GaussDB-Redis¶
The displayed Metrics of Huawei Cloud GaussDB-Redis include read/write throughput, response time, concurrent connections, and data persistence. These Metrics reflect the performance and reliability of GaussDB-Redis in handling high-concurrency data storage and caching.
Configuration¶
Install Func¶
It is recommended to activate TrueWatch Integration - Extensions - DataFlux Func (Automata): 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 permission
ReadOnlyAccess
)
-
Log in to the Func console, click 【Script Market】, enter the TrueWatch Script Market, and search for
ID: integration_huaweicloud_gaussdb_redis
-
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 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs
Verification¶
- In 「Manage / 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 there is asset information in 「Infrastructure / Custom」
- In TrueWatch, check if there are corresponding monitoring data in 「Metrics」
Metrics¶
After configuring Huawei Cloud Cloud Monitor, the default Measurement is as follows. You can collect more Metrics by configuration Huawei Cloud Cloud Monitor Metrics Details
Metric Name | Description | Unit | Dimension |
---|---|---|---|
nosql001_cpu_usage |
CPU utilization | % | redis_node_id |
nosql002_mem_usage |
Memory utilization | % | redis_node_id |
nosql005_disk_usage |
Disk utilization | % | redis_node_id |
nosql006_disk_total_size |
Total disk capacity | GB | redis_node_id |
nosql007_disk_used_size |
Disk usage | GB | redis_node_id |
redis017_proxy_accept |
Total clients accepted by proxy | count | redis_node_id |
redis018_proxy_request_ps |
Request rate received by proxy | counts/s | redis_node_id |
redis019_proxy_response_ps |
Response rate returned by proxy | count/s | redis_node_id |
redis020_proxy_recv_client_bps |
Byte stream rate received by proxy from clients | bytes/s | redis_node_id |
redis021_proxy_send_client_bps |
Byte stream rate sent by proxy to clients | bytes/s | redis_node_id |
redis032_shard_qps |
QPS of shard | count | redis_node_id |
Invocationredis064_get_avg_usecs |
Average latency of "get" command executed by proxy | μs | redis_node_id |
redis065_get_max_usec |
Maximum latency of "get" command executed by proxy | μs | redis_node_id |
redis066_get_p99 |
P99 latency of "get" command executed by proxy | μs | redis_node_id |
redis067_get_qps |
Rate of "get" command executed by proxy | count/s | redis_node_id |
redis316_all_avg_usec |
Average latency of all commands executed by proxy | μs | redis_node_id |
redis317_all_max_usec |
Maximum latency of all commands executed by proxy | μs | redis_node_id |
redis318_all_p99 |
P99 latency of all commands executed by proxy | μs | redis_node_id |
redis319_all_qps |
Rate of all commands executed by proxy | count/s | redis_node_id |
redis669_connection_usage |
Connection usage rate | % | redis_node_id |
redis670_hit_rate |
Hit rate | % | redis_node_id |
Object¶
The collected Huawei Cloud GaussDB-Redis 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
andfields
may change with subsequent updatesTip 1: The value of
tags.name
is the instance ID, used as a unique identifierTip 2: The following fields are all JSON serialized strings
fields.message
fields.backup_strategy
fields.datastore
fields.groups
fields.actions